Classify
Define the outcome, users, data, impact, and whether AI or automation is actually needed.
Use this page to decide what can proceed, who must be involved, what evidence is required, and when work must stop or escalate.
This is the single governance route for AI Marketplace tools, AI use cases, automations, dashboards, agents, and data-heavy requests. Governance is proportionate to risk, but every request follows the same lifecycle.
Define the outcome, users, data, impact, and whether AI or automation is actually needed.
Name the business, product or app, data, and support owners. Identify required reviewers.
Complete the relevant data, security, architecture, evaluation, and approval records.
Monitor use, quality, access, cost, incidents, changes, and the eventual retirement decision.
| Rule | What it means |
|---|---|
| You build it, you own it | The app owner maintains the tool, its dependencies, user guidance, and retirement. The central team does not take ownership of the app. |
| Not an IT-supported service | There is no app-level SLA, change-management service, or helpdesk unless a separate service arrangement is agreed. |
| Internal use only | Marketplace tools are for internal productivity. Do not share them with clients, use them in front of clients, or reference them in client deliverables. |
| Experimental by default | Any tool should be built assuming it could be deprecated within a year. |
| No work-product retention | Uploaded files and results are not stored permanently. Operational access logs may be retained for platform monitoring. Download your outputs before closing. |
| No critical workflows | Do not make the Marketplace a dependency for a mission-critical process. |
| Infrastructure is central | The platform team manages hosting, routing, identity integration, and deployment pipelines; the app owner remains responsible for app behavior. |
| Onboarding is controlled | Initial questions and app registration go through the platform admin before deployment. |
| Platform cost is central | Base platform infrastructure is not charged back to app owners. Material model, storage, traffic, or third-party costs still need an identified owner and monitoring plan. |
Choose the highest applicable route. Lower-risk work still requires approved tools, appropriate data, and human review; higher-risk work adds formal review and evidence.
Public or non-sensitive information, individual drafting, summarising, or exploration with no automated action. Use an approved tool and verify the output.
Internal data, multi-user tools, stored outputs, connectors, dashboards, or repeatable workflows. Name owners and complete data-readiness and control review before build.
Client confidential, personal, financial, regulated, restricted, external-facing, system write-back, or high-impact decisions. Engage the relevant governance teams before proceeding.
| Review area | Required question | Evidence or decision |
|---|---|---|
| Data and privacy | What classification, personal data, client restrictions, retention, residency, or cross-border obligations apply? | Classification, permitted-use position, access approval, and privacy or DPIA decision where triggered. |
| Security and platform | Is the tool approved for this data and use? Are access, secrets, logging, vendor, and incident controls adequate? | Approved platform and control record; AI Security or Cyber Security decision where triggered. |
| Legal and client | Do contracts, licences, regulation, or account commitments permit the proposed processing and output? | Legal, account, or client approval and any conditions. |
| Automation and impact | Could the output affect people, clients, safety, finance, compliance, or write back to a system? | Human decision point, audit trail, testing threshold, override, and accountable decision owner. |
| User accountability | Can users understand limits, verify output, and report a suspected exposure or unsafe result? | User guidance, prohibited uses, validation steps, and incident route. |
Start with the user need, not the technology. Decide whether the work is self-service, Microsoft Copilot, Copilot Studio, Power BI, Power Platform, a custom mini app, a reusable micro-tool, or a full application.
Identify whether the workflow uses public, internal, client confidential, personal, financial, regulated, commercially sensitive, or restricted data. Check client contract terms and residency needs before any sensitive data is used.
For data-heavy requests, the Requirements Agent should not treat the work as build-ready until the source landscape and ongoing ownership are clear.
Use the lightest approved route that fits the workflow, but do not bypass controls for speed. Sensitive data needs an approved or Trusted platform, least-privilege access, logging, retention clarity, and security review.
Define what good output looks like before pilot. Test accuracy, edge cases, bias, sensitive information exposure, prompt injection, over-reliance, and any automated action or system write-back.
Governance does not end at launch. The owner must monitor use, cost, incidents, access, model or data changes, accuracy drift, support demand, and whether the tool should be changed or retired.
Do not start by asking which app to build. First decide what governed data capability is missing, who owns it, whether the proposed use is permitted, and whether a reusable data layer should exist before an app, agent, dashboard, or workflow is built.
Name the decision, report, workflow, agent response, system action, or client outcome that would rely on it.
List systems, APIs, files, SharePoint sites, dashboards, warehouses, exports, and manual steps.
Name each source owner, access approver, quality owner, and the business owner accepting the output.
| Pattern | What it means | Governance move |
|---|---|---|
| Single accountable owner | One owner controls the source of truth, access, definitions, quality, and change decisions. | Confirm permission, quality limits, refresh, retention, and support before build or AI use. |
| Multiple domain owners | The workflow combines functions, regions, systems, projects, or dashboards. | Align definitions, permitted use, quality gaps, and who accepts the combined-output risk. |
| No clear owner | The request depends on inherited spreadsheets, unmanaged exports, unofficial dashboards, or tribal knowledge. | Do not treat it as build-ready. Establish ownership or a governed dataset first. |
| Client or third party | The data is client-provided, licensed, regulated, externally sourced, or contractually constrained. | Review contract, residency, permitted use, AI restrictions, retention, and security before processing. |
| Move | Use when | Must be clear first |
|---|---|---|
| Use the existing source | One owner, one source of truth, low sensitivity and reuse, known quality, simple workflow. | Owner approval, access, quality caveats, retention, and human review. |
| Create a governed dataset or view | Recurring reporting, repeatable extracts, stable sources, clear owner, inconsistent manual handling. | Fields, definitions, refresh, quality checks, access group, support, and change process. |
| Create a reusable data product or layer | Multiple consumers or owners, conflicting definitions, sensitive data, AI retrieval, apps and dashboards sharing data. | Ownership, lineage, controls, service expectations, monitoring, and architecture ownership. |
| Route to architecture or platform review | System write-back, master data, regulated workflows, audit-heavy operation, cross-border constraints, or long-lived dependency. | Architecture, security, legal, data platform, and operational governance decisions. |
Governance needs named decisions, not just consultation. Record one accountable owner for the outcome and make each specialist decision visible.
| Role | Accountability to record |
|---|---|
| Business owner | Outcome, users, value, acceptable business risk, funding where needed, and the decision to continue or stop. |
| App or product owner | Design, user guidance, testing, dependencies, support, changes, monitoring, and retirement. |
| Data owner | Source of truth, definitions, quality limits, access, permitted use, retention, and change approval. |
| Platform team | Marketplace hosting, routing, identity integration, deployment controls, platform monitoring, and platform standards. |
| Specialist reviewers | AI Security, Cyber Security, Privacy, Legal, Architecture, Data Platform, or account leadership decisions when triggered by the use case. |
| Users | Follow permitted use, protect data, verify outputs, keep human judgement, and report failures or suspected exposure. |
Business owner, support owner, decision owner, intended users, expected outcome, and escalation route.
Data classification, source inventory, source of truth, access approver, quality limits, update cadence, and retention need.
Approved platform, access model, logging, secrets handling, residency, vendor position, and required AI Security review.
Test cases, accuracy threshold, prohibited uses, human review point, failure modes, bias checks, and pilot results.
Monitoring, cost review, incident path, support process, change review, review date, and sunset criteria.
Risk level, required reviewers, decision, open conditions, and the date the decision needs to be revisited.
| When | Minimum control | Trigger for action |
|---|---|---|
| Before launch | Named owner, user guidance, passed tests, approvals, support and incident route, cost visibility, review date, retirement plan. | Any missing owner, approval, critical test, or safe rollback prevents launch. |
| In operation | Monitor availability, usage, cost, access, errors, output quality, incidents, and user feedback in proportion to risk. | Unexpected use, material drift, rising cost, control failure, or recurring support demand prompts review. |
| On change | Reassess material changes to model, prompt, data, vendor, connector, user group, geography, output, or automated action. | A change that alters risk or obligations returns to the relevant delivery gate. |
| On incident | Contain, preserve evidence, notify the correct owner and security route, assess impact, correct, and record lessons. | Suspected exposure, unsafe output, unauthorised access, or harmful action is escalated immediately. |
| At review or retirement | Confirm the use case still has value, ownership, acceptable quality, valid approvals, affordable operation, and a supported platform. | Remove access and integrations, handle retained data, archive the decision record, and communicate retirement. |
Add the request context once, then open or copy the relevant email. Replace placeholders and select the actual accountable recipient; a template does not constitute approval.
These fields may be prefilled with ?request_id=..., &title=..., &requester=..., and &route=....
Use when ownership, sources, quality, access, refresh, pipeline, or support is incomplete.
Use when an apparent owner needs to confirm authority, access, quality, refresh, and permitted use.
Use when several teams, regions, systems, or dashboards need one agreed data position.
Use when reusable datasets, shared definitions, integrations, AI retrieval, or platform ownership may be needed.
Use for sensitive, client, personal, regulated, external-facing, automated-action, or high-impact AI.
Use for client-provided, contractually constrained, licensed, regionally restricted, or regulated data.
| Topic | Decision still needed |
|---|---|
| App review | Whether all new apps require a recorded review of security, code quality, accessibility, dependencies, and ownership before launch. |
| Data classification | Which additional controls apply to each class of data and which classes are prohibited from the Marketplace. |
| Usage and value | Which adoption, outcome, quality, and user measures determine continued investment or retirement. |
| Cost governance | When per-app budgets, alerts, chargeback, or approval thresholds are required. |
| Lifecycle | Review frequency and formal criteria for unsupported, unmaintained, unused, or superseded tools. |
| Incident response | A published runbook with severity, contacts, containment, evidence, notification, recovery, and learning steps. |
| Access control | When an app requires a restricted group, privileged access, periodic recertification, or segregation of duties. |
| Compliance mapping | How applicable legal, regulatory, contractual, AI, privacy, records, and sector obligations map to controls and evidence. |
These references inform the control model; ERM policy, client obligations, and decisions from accountable governance teams take precedence.