There is a particular moment every project team knows. Someone asks for the record. It may be a funder, an internal review team, an oversight function, leadership or a new manager trying to understand what happened.

The pressure usually does not come from the work itself. It comes from the scramble to prove the work: finding the approved scope, locating site evidence, reconstructing decisions, checking what remains outstanding and trying to make several different reporting formats agree.

Most teams are not unprepared because they did bad work. They are unprepared because they did not build the record while the work was happening.

The 5 questions every review eventually asks

Whatever the institution or programme, most reviews come back to the same basic questions:

• What was approved? What was the agreed scope, budget, workplan or mandate?
• Where did the work happen? Which sites, communities, facilities or locations were involved?
• What was actually delivered? What is complete, in progress, delayed or still outstanding?
• What evidence exists? What can be shown through photographs, video, location data, interviews, reports and supporting documents?
• What happens next? What actions remain, who owns them and when should they be closed?

The documents that answer those questions

A team that is ready for review should not need to create a new story from scratch. The record should already contain the core documents that explain the project.

• Approved workplan and scope
• Project budget or authorised cost framework where appropriate
• Site or location list
• Progress reports and status updates
• Photographic and video evidence
• Relevant GPS or geo-tagged records
• Stakeholder or beneficiary records where relevant
• Issue logs and action records
• Supporting correspondence and approvals
• Close-out or follow-up requirements

The gaps that create problems later

The most common problems are rarely dramatic. Evidence sits on personal phones. Decisions are made in meetings but never logged. Different teams use different reporting formats. One contractor reports by email while another uses WhatsApp. Follow-up actions are agreed but nobody owns the record of whether they were completed.

When that happens, a project can be genuinely active and still look poorly controlled when someone later reviews it.

Readiness is a discipline

The simplest way to prepare for review is to stop treating review as a future event. Build the record as part of delivery.

Use one consistent structure. Capture evidence when activity happens. Record decisions and issues close to the time they occur. Review the file before anyone asks for it. Make sure outstanding actions have owners and dates.

The teams that handle review well are usually not the teams that suddenly became organised when the review notice arrived. They are the teams that were already organised before the question was asked.

Preparation is a habit, not a scramble.