Measure readiness by what can be demonstrated.

A percentage cannot authorize a handover

A project can have almost every closeout item checked while one unresolved requirement prevents safe or authorized use. The missing item may be a test result, an inspection, an operations document, or a decision by the party responsible for acceptance. Counting rows alone hides the difference between a minor finish correction and a condition required for occupancy.

Start by defining the handover decision. A system turnover, partial occupancy, substantial completion, and final commercial closeout may have different requirements and different approving parties. Name the specific decision at the top of the register. Do not use “complete” as a single status for all of them.

Stored-material payment is another separate state. An owner may have paid for identified equipment held at an approved offsite location under the contract while delivery, installation, testing, and acceptance remain outstanding. Carry its location, protection, insurance, custody, and delivery obligations into closeout. Reconcile stored value as it is incorporated; payment is not turnover evidence.

The method below coordinates evidence. It does not certify construction, declare a facility safe, approve occupancy, or replace the responsibilities of the designer, commissioning provider, contractor, owner, or authority having jurisdiction.

Build a register around the acceptance question

1. Establish the requirement and reviewer

Start with the turnover, testing, training, and documentation requirements in the current specifications, drawings, and authorized revisions. These carry the design team’s expertise and the owner’s reviewed needs into closeout. For every item, cite the applicable requirement and the review or acceptance role assigned by the contract. Use the contractor’s required submittals to confirm the proposed records and equipment remain consistent with that basis; retain the design team’s and owner’s applicable review dispositions. “Operating manual received” and “operating manual reviewed and accepted” describe different conditions.

2. Group by system and handover boundary

Organize the record so a reviewer can see everything needed for a particular system, area, or phase. Avoid grouping only by subcontractor if that separates interdependent evidence. A control sequence may connect equipment, software configuration, functional testing, and operator instruction across several participants.

3. Make the evidence reference specific

Use a document identifier, revision, date, and repository reference. Record the test or inspection result, reviewer, and review state. An empty folder link should not count as proof. If an item is accepted with a condition, write that condition, its responsible party, and the limit of the acceptance.

4. Identify blocking requirements explicitly

Agree with the responsible decision-makers which items block the defined handover. Give those items an obvious flag and escalate them separately from the general open-item count. A blocked item cannot become nonblocking simply because its due date is approaching.

5. Carry dependencies into the schedule

Training may depend on stable controls and accepted operating information. Final testing may depend on utility availability or another system. Capture these dependencies as work with owners and dates. Document why a deferred seasonal test can or cannot coexist with the particular acceptance decision being considered.

Obtain each commitment from the party able to deliver it: the equipment vendor confirms its trainer or specialist, the testing provider confirms its attendance, and the designated reviewer confirms its review availability. The general contractor coordinates those parties and any upstream supplier through the appropriate trade partner. Label an unconfirmed appointment as a planning estimate, with its conditions and evidence still due. Record the scope and current requirement revision; a confirmed appointment is not a passed test or acceptance.

Worked example: installed is not accepted

Use the workbook

Read Guide and inspect Worked example, then use the fifteen blank rows in Register. In a separate project copy, define the turnover boundary and reporting date. Add one row per reviewable requirement, with the responsible party, required date, evidence reference, review status, and dependency.

Complete the lower Requirement basis block for each row. Its record identifier follows the main register. Enter the requirement document and revision, the design and owner review role, required submittal or request, actual disposition and supporting evidence, and the contractor’s confirmation that the basis remains current. Evidence linked means those fields are populated; it is not an approval, authorization to proceed, or assessment of the review’s adequacy.

Use the linked commitment record to name the responsible entity and its scope, confirmation status and date, evidence, conditions, and the contractor’s separate forecast and coordination action. Carry the current requirement revision with the evidence. A completed record is not independent confirmation; an unconfirmed date remains an estimate.

The workbook’s accepted state requires an acceptance date, evidence, reviewer, and cleared dependency. Submission alone stays open. Check each of those fields against the actual record; filling them is not itself an authorization. Dates in these teaching tools are limited to the years 2000 through 2100.

Use the workbook’s summary to find open and overdue work. Then read the individual blocking rows. A summary ratio is a workload measure; it is not a readiness certificate. Inspect each claimed completion against the actual evidence and identify who accepted it. Do not infer acceptance from a file being uploaded.

For a rejected submittal or failed test, retain the earlier result and record the corrective action and resubmission. If the workbook has a single current-reference cell, place the full revision history in the controlled source record and link to it. This preserves traceability without stuffing every document into the spreadsheet.

Carry the specification section and drawing revision into that source record, together with the submittal identifier, current disposition, and required reviewer. If the written criteria are unavailable or conflict, record the available basis and obtain clarification from the responsible professional. Do not substitute the register’s sample rows for missing project requirements.

At handover, capture the exact decision and any exceptions in the authorized record. Preserve the issue copy, transfer open obligations to named owners, and identify ongoing testing, warranty follow-up, and operational documentation duties. Continue tracking those obligations after physical work stops.

Run a short readiness review

1. Confirm the boundary. State which area, system, and acceptance decision the meeting covers.
2. Review the blockers first. Open the evidence for each; do not accept a verbal “done” as its replacement.
3. Resolve handoffs. Confirm who receives records, training materials, access information, and continuing obligations.
4. Record the decision. Identify the authorized decision-maker and the written disposition, including conditions.
5. Keep the open work visible. A partial acceptance does not erase remaining responsibilities.

When a prerequisite needs an owner decision, carry it into the decision register. When it changes planned dates, assess it in the working schedule. These links help the team see readiness as a connected process rather than a folder-cleanup exercise.

Sources, method & limitations

This guide’s examples, workflow, and workbook instructions are original teaching material from Pacific Project Controls. The public references below supply background. They do not endorse this site or make this workbook an official assessment tool.

1. U.S. Department of Energy: Commissioning Process for Federal Facilities
   Background on planning, investigation, implementation, and documented handoff. Our readiness matrix is an original coordination aid and does not replace commissioning, inspections, or acceptance by the responsible authority.
2. GAO Schedule Assessment Guide, GAO-16-89G (2015)
   Background on reliable schedules, their relationship to cost, and the need to assess dependencies and change. The screening checks here are a limited teaching aid, not a GAO compliance assessment.
3. AIA Contract Documents: contractor review of submittals
   Explains contractor coordination and review under A201–2017 before forwarding submittals to the architect. Use the actual project contract to identify review responsibilities; this reference does not make that agreement applicable to every project.
4. AIA Contract Documents: payment for materials stored offsite
   Explains A201–2017 section 9.3.2 as one contractual approach: advance owner approval for offsite storage and payment, an agreed location, protection of the owner’s interest, and applicable insurance and transport arrangements. The executed project contract governs eligibility.
5. AIA Contract Documents: payment applications and stored-material reconciliation
   Describes required payment support and moving stored value to completed work as incorporation occurs without charging for the same material twice. Use the project’s actual payment rules and applicable waiver requirements.

Apply the actual project requirements and obtain the relevant professional review. This guide does not establish contractual entitlement, certify technical performance, or replace authorized acceptance. No actual client record or project outcome is represented by the fictional examples.

Release edition · October 21, 2026. Source notes identify the references used in preparation. Report an error or review our correction policy.