Read the discovery report

Begin with the decision and scope

Read the report against the question agreed for discovery. The sample report is a public illustration of the format. The written deliverables in your selected service or engagement define what your discovery work includes.

1. Confirm the question, scope and systems reviewed.
2. Identify the findings supported by evidence.
3. Mark recommendations that depend on further access, provider work or a business decision.

• An architecture recommendation is not proof that its connections are live.
• A proposed outcome or estimate is not an operating result.

Turn recommendations into choices

Ask which recommendation changes the next business decision and what must be true before it can proceed. A useful implementation scope identifies owners, acceptance checks, data responsibilities and the work required from your team.

• Which findings are confirmed and which are assumptions?
• What is included in the first release?
• Which dependencies could change timing, scope or cost?

Ask for clarification with a reference

Use the page or section title and explain the decision the wording affects. This keeps the follow-up specific and makes any scope change easier to assess.

• The report section and the point you want clarified.
• The relevant business constraint or missing evidence.
• The person who can answer or approve the outstanding decision.