Before you scope
Clarify the decision before you define the work.
You do not need a finished program or a complete evidence package. Use this checklist to make the trigger, decision, owner, and timing clear enough for a focused first conversation.
Five prompts
Prepare the context—not the whole environment.
Keep answers high level and non-sensitive. The purpose is to define the decision and a sensible scope, not to transfer technical evidence.
- 01
What changed?
Name the event creating pressure: an AI initiative, customer request, access concern, leadership decision, or readiness gap.
- 02
What must be decided?
Describe the business decision the work should support—not every control or technical task that might follow.
- 03
Why now?
Identify the deadline, dependency, exposure, or consequence of waiting. If there is no timing pressure, say that clearly.
- 04
What evidence is available?
List the categories of evidence that may exist, such as an architecture view, request, plan, policy, workflow, or ownership record. Do not send the evidence through the public form.
- 05
Who owns the outcome?
Name the decision owner and the technical, business, legal, or operational participants who may need to provide context.
Boundary
Do not send secrets to get started.
Do not submit credentials, regulated data, incident artifacts, vulnerability details, or sensitive technical evidence through the form or ordinary email. Appropriate transfer and access methods can be agreed after fit and scope are clear.
Email a high-level summary insteadWhen you are ready
Bring the decision, not the whole environment.
A short account of what changed, what must be decided, and when is enough.
Start a scoped conversation