A project-closeout tracker is a navigation and follow-up tool. It helps a team see which records are expected, where the supplied files are located and what action remains. It does not determine whether construction work is compliant or whether a contractual milestone has been achieved. Tailor the tracker to the project’s actual deliverable requirements before using it.

Copyable starter fields

Create a spreadsheet with one row per identifiable deliverable and these headers:

  • Item ID; package or work area; discipline or system.
  • Requirement reference; deliverable title; expected source or issuer.
  • Document number; revision or date; original file link.
  • Responsible owner; reviewer or acceptance route.
  • Status; gap or comment; next action; due date.
  • Submission reference; response reference; last updated by and date.

Keep the requirement reference and file link separate. One explains why the record is being tracked; the other points to the evidence actually supplied. A blank field should remain visibly blank or be marked for confirmation rather than filled by guesswork.

Set status meanings before entering files

A simple sequence could use requested, received, under review, returned for action and accepted by authorised reviewer. Define each label in a key on the sheet. “Received” means a file arrived, not that its technical content was approved. Use “not applicable” only with a recorded reason and the responsible person’s confirmation.

A hypothetical row could read: “PKG-014; pump station; equipment manual; supplier schedule item 8; model identifier unclear; supplier to confirm.” Mark that row as an example and delete it from the working register once the team understands the fields. It illustrates a question to resolve, not a technical finding about a real pump.

Use the sheet as a live coordination record

Start with one package and sample several links with the people who will use the pack. Check that a reviewer can find the source file and understand the location or asset to which it applies. Keep originals intact and retain superseded issues in a controlled archive.

Review due items and gaps at an agreed interval. Save a dated submission snapshot when the pack is formally issued, and keep the current working copy distinguishable from that snapshot. The Queensland Building and Construction Commission’s (QBCC) handover guidance gives useful Queensland context, while the exact records and approval route remain project-specific. The tracker supports that process; it does not replace it.