Identify the review purpose
State whether the pack supports an operational handover, quality review, procurement decision or campaign closeout. The purpose determines which records are needed and who should receive them. A review export is not a complete database dump by default. Name the programme reference, reporting date and relevant scope revision. Include a short description of the actual campaign so reviewers can interpret site and item references without the original chat.
Choose the required records
Include current specifications, approved artwork references, site quantities, accepted external scope and actual event outcomes where they matter to the review. Keep unresolved questions and their owners easy to find. Financial values need their own permission and document basis. A public source reference can be included without exposing the private campaign evidence linked to it. Avoid mixing fictional demonstrations with real organisation records or presenting a draft export as an accepted supplier job pack.
Preserve version and status meaning
Make each record’s version, state and relevant date readable. Distinguish planning assumptions, responsible decisions and observed outcomes. Include a manifest so someone can identify the intended files and missing dependencies. If an export contains conditional approval or a proposed recovery route, show those conditions plainly. A PDF-looking report is not inherently more authoritative than its underlying records and must not imply checks that were never performed.
Worked example — fictional
A fictional internal review examines a five-site event programme. The pack contains the accepted brief revision, current artwork manifest, actual installed quantities and two outstanding return actions. The buyer’s private finance appendix is provided only to authorised reviewers; installers receive the operational subset. A fictional learning scenario is excluded entirely. The review records that one recovery destination remains unconfirmed, rather than claiming the programme achieved a completed material outcome. Another colleague can identify the sources and owners needed for the next decision.
Common pitfalls
An unrestricted archive can expose rival supplier quotes, personal contacts or unrelated clients. A screenshot may conceal conditions visible in the underlying record. Old attachments can survive under familiar filenames and appear current. Removing all history can make accepted variations impossible to explain, while dumping every version can overwhelm the recipient. Select useful evidence and preserve references to authorised history.
Verify the exported result
Use the brief or workspace export to prepare a scoped pack, then open it as the recipient would. Check that links or files remain usable through approved access and that private fields are excluded where required. Reconcile totals and current versions. Retain an export date and scope note, and ask the actual connected service to enforce permissions when private multi-user exports are activated.
Decision checkpoint
Ask whether the recipient can tell what needs action without reading the whole file history. If not, add a concise exceptions list with owners and references. The useful review pack supports the next responsible decision and preserves traceability rather than simply accumulating documents.
Take this to the next job
- Define review audience and purpose
- Select authorised relevant records
- Preserve versions and conditions
- Include a readable manifest
- Open and verify the actual export
