Reviewing deliverables before publishing

Review is where you catch problems before the client does. Read the whole pack in the preview, then decide what to regenerate and whether it is ready to publish.

Open the deliverable preview

Open the preview at /deliverable/engagements/{id}/packs/current. This shows the pack as the client will see it, in admin chrome. Read each page in order.

Read each page

Work through every page, not just the diagnostics. Check that the narrative reads cleanly and that nothing is empty, truncated or generic.

Check the diagnostics against the intake

The diagnostic pages are generated from the intake, so sanity-check them against what you know about the client. Does the maturity band, the readiness status and the priorities match the business you took through intake? If a diagnostic contradicts the intake, that page needs a regenerate.

Read the status badges

Each page on the workspace grid carries a status badge:

• Generated: produced successfully.
• Failed: the page did not generate and needs attention.
• Superseded: an older version replaced by a newer one.

Decide

Do not publish a pack with unacceptable failed pages. A stray failure on a minor page may be tolerable, but a failed or weak diagnostic is not. Regenerate what needs it, re-read, then publish.