Score useful attributes
Assess each document for completeness, currency, ownership, readability and sharing permission. Define what a satisfactory result means for each attribute before assigning numbers. Keep the score as an internal preparation aid rather than an external assurance. A file may be beautifully formatted yet unsuitable for public distribution. Another may be visually plain but contain the exact evidence a reviewer needs.
Keep blocking issues separate
Mark items that require action regardless of the overall score, such as an unresolved contradiction or an unidentified source. Show those exceptions prominently. Assign owners and review dates, then repeat the assessment after changes. Compare readiness within similar document types rather than pretending that a photograph and an operating agreement can be judged identically. The decision is whether the next review can proceed responsibly, not whether the team can claim a perfect percentage.
Put the guide to work
Test the scoring method on two deliberately different files before applying it to the full pack. If the same score hides very different weaknesses, revise the criteria. The score should help the team prioritise preparation work, not become another polished number that requires its own explanation.
Hypothetical example
A hypothetical pack scores well because most documents are current and readable. One key schedule has no confirmed owner. The team flags that schedule separately instead of celebrating the average, and resolves responsibility before using the pack in a formal partner discussion.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
