A weekly handover-readiness meeting should produce decisions and actions, not a recital of every line in a spreadsheet. Use a short agenda focused on approaching dates, unresolved evidence and questions that need authority beyond the document controller. The project’s contract and communication procedures determine any formal notices; this agenda is only a practical coordination aid.

Copyable 25-minute agenda

Meeting: [project/package] — Date: [date] — Chair: [role] — Recorder: [role].

  • 0–3 minutes: confirm the milestone, review period and changes since the previous meeting.
  • 3–8 minutes: review actions due or overdue; agree the evidence needed to close each one.
  • 8–15 minutes: review the highest-priority missing or unclear records by package or system.
  • 15–20 minutes: resolve review-route questions, returned comments and decisions needed from authorised people.
  • 20–23 minutes: confirm upcoming submissions, responsible owners and target dates.
  • 23–25 minutes: read back actions, decisions and escalation items; confirm the next review.

Adapt the duration to the volume of work. If a detailed technical discussion is required, assign a separate session with the appropriate qualified people rather than forcing a decision inside a status meeting.

Bring a filtered register

Ask participants to review the relevant lines before the meeting. Show the requirement reference, expected record, latest supplied file, current status, owner and next action. Separate missing evidence from material awaiting review. Counted totals can help with workload, but a high percentage received may hide a critical unresolved item.

A hypothetical review could find that an asset schedule and a supplier manual use different identifiers. The useful action is to assign reconciliation to the responsible owner with the two source references. It is not to rename one file and mark the issue accepted without confirmation.

Issue a concise action record

For every decision, record what was agreed, by whom and which evidence or document revision it concerns. For every action, name one accountable owner, a specific outcome and a date. Keep the meeting record linked to the live register so updates do not become competing versions of the truth.

Begin the next meeting with the previous actions. If a recurring blocker cannot be resolved at the working level, use the project’s agreed escalation route. The meeting should make responsibilities clearer while preserving the distinction between coordination, technical review and contractual acceptance. A well-run short review is useful because people leave knowing precisely what they need to do next.