Scope the decision, not the buzzword.

A practical advisory framework for converting client facts into an AI readiness assessment, prioritized risks, concrete deliverables, decision owners, and a proposal that shows its working.

Discovery record

Six questions that should change the scope.

Decision

What business or release decision must this engagement enable?

System

Which models, prompts, data sources, tools, users, and environments are in scope?

Consequence

What can go wrong, who is affected, and which outcomes are unacceptable?

Evidence

What tests, policies, logs, incidents, evaluations, and approvals already exist?

Ownership

Who owns product, risk, security, legal, data, and final release authority?

Constraint

Which deadlines, regulations, integrations, budgets, and procurement rules shape delivery?

Engagement blueprint

1. Frame the decision

Replace a broad request such as “help with AI governance” with a concrete outcome: approve a release gate, establish an evaluation program, prepare for customer diligence, or remediate a known control gap.

2. Establish current state

Inventory the actual workflow and evidence. Distinguish documented controls from controls that operate in production, and distinguish planned tests from results that a reviewer can inspect.

3. Prioritize risks

Rank risks by consequence, likelihood, exposure, detectability, and reversibility. Link each priority to a client fact instead of using a generic maturity checklist as the conclusion.

4. Define deliverables

Describe artifacts and decisions, not vague activities. Examples include an evaluation plan, risk register, release gate, red-team pack, evidence map, incident playbook, or reviewer handoff.

5. Name client obligations

List the access, data, experts, approvals, and decisions the client must provide. Dependencies and exclusions belong in the scope before commercial approval.

6. Prove acceptance

Give every deliverable an acceptance criterion, reviewer, due date, and evidence format. A workshop is complete when it produces an agreed decision or artifact, not when the meeting ends.

Proposal quality gate

The proposal should expose its assumptions.

Preserve the chain from client fact to risk, from risk to deliverable, and from deliverable to acceptance decision. Make exclusions, dependencies, open questions, client responsibilities, and change-control rules visible before signature.