A reserved work window still needs a release decision.

Treat the window as a proposal with conditions

Putting an overnight or weekend activity on a building calendar reserves attention. It does not establish that the work may begin. The team still needs to know which areas and services are affected, whose permission is required, what evidence those people need, and how the space will be returned to its expected condition.

A work-window record organizes that review before people mobilize. Its purpose is to expose unanswered questions early enough to change the plan. It is not a permit, a technical procedure, an isolation instruction, a safety assessment, or an operating authorization. Those remain with the project’s established processes and qualified responsible people.

The closeout guide addresses evidence for handover. This record concerns a different decision: whether a proposed period of work has its required preparation and authorization evidence before it starts.

Define the boundary and the decision owner

Describe the window precisely

Record the date, start and finish, local time zone, affected space, proposed activity, and expected condition at return. Include related access restrictions and dependent activities in the supporting plan. If the work crosses midnight or a daylight-saving change, use explicit offsets and have the time assumptions checked. A date alone is not enough.

Check where the material actually is. An eligible stored-material payment may cover an item still offsite; it does not prove arrival for this window. Distinguish onsite storage, offsite storage, transit, and an order awaiting delivery, then obtain the responsible supplier’s transport and receiving confirmations. Use the reviewed material and current scope when checking readiness.

Confirm the applicable evidence list

Start with the current specifications, drawings, approved operating plans, and owner requirements already reviewed with the design team. Ask the retained operational and specialist reviewers to confirm their applicability to this window and resolve remaining gaps. Record the contractor’s required work-plan submittals, their revisions and dispositions, and the review roles required by the project. The six coordination gates below are an example, not replacement requirements. Reference the approved technical plans rather than copying their instructions into a general register.

Make evidence review visible

For each gate, identify a preparer, the authorized reviewer, an evidence reference, and a required-by time. Distinguish “requested,” “received,” and “reviewed for this window.” A document that was accepted for another date or scope may not cover the current proposal. Record open questions rather than inferring approval from silence.

Have each party confirm what it controls: the trade partner its crew, the vendor or its own supplier its delivery or specialist, operations its access arrangements, and the designated reviewer its attendance. The general contractor coordinates those confirmations against the same window, scope, current plan revision, and stated conditions. Keep its provisional durations separate from those commitments. A party’s availability does not approve another party’s work or replace the authorized release decision.

Keep the release decision separate

Even a fully documented register does not grant permission. Record the final release decision and its scope in the existing authorized process. If a required item remains open, escalate it to the designated authority; a spreadsheet user should not relabel it as optional to obtain a favorable count.

Worked example: four documented gates, no release

Use the evidence register without turning it into a permit

Use one row per required gate and retain the common window identifier, revision, cutoff, and start and finish timestamps. The worked CSV contains all six gates, with fictional evidence references for the four documented items. The two unresolved items have empty evidence references and empty reviewed-at timestamps. Their blanks are deliberate.

Complete the requirement-document and revision fields, design and owner review roles, required review reference, actual disposition and evidence reference, and contractor currentness check. Use the unresolved-requirement field to identify a gap and its next action. These entries carry the existing project basis into the record; filling them does not grant review approval or authorize a change.

Record the entity controlling the milestone, its scope, confirmation status and date, evidence and conditions, and the contractor’s separate forecast and coordination action. Check that the confirmation still covers the current revision. Unconfirmed values remain planning estimates.

The blank file provides an empty row to copy as needed. Enter gate status as open, evidence received, or documented review, using definitions agreed for the project. Record the reviewer’s role and actual review timestamp. The CSV applies no validation and does not decide whether a reference is sufficient. A filled cell alone is not proof.

Use the source reference to retain the applicable specification or operating requirement, drawing revision, submittal and disposition. If that basis is absent, identify the available record and missing requirement for the responsible professional; do not turn an example gate into an invented project instruction.

Keep release status separate from gate status. The example repeats the same pending window decision to make exported rows understandable; those entries represent one decision, not six separate permissions. Retain the actual authorization in the established source record and reference it when the decision is made.

Save a dated issue before changing the window. Reconfirm affected evidence when timing, scope, personnel, or operational conditions change. Do not carry a previous release into a revised proposal automatically. Share only the information each recipient needs; detailed facility procedures and sensitive access information belong in controlled project records.

Review what could invalidate the preparation

Before the decision meeting, ask whether the operational assumptions are still current, whether the receiving team can verify the promised return condition, and whether another scheduled activity competes for the same access or people. Where evidence is missing, assign a specific next action and deadline.

A successful planning review leaves a clear decision record, not a claim that this template made the work safe. Authorized specialists determine applicable technical, operational, contractual, and safety requirements. The register helps the team find and resolve missing evidence; it cannot perform that professional review.

Release edition · 2026-10-21 · Companion file version 1.1-review. The facility, dates, roles, and records are invented.

Sources, method & limitations

The explanation, field structure, and fictional scenario are original teaching material. The cited primary guidance provides context; it does not endorse this resource or make its records an official approval process.

1. U.S. Department of Energy: Commissioning Process for Federal Facilities
   Background on planning objectives, assembling qualified participants, and documenting the handoff. A work-window evidence register is not a commissioning procedure or an authorization to operate.
2. GAO Schedule Assessment Guide, GAO-16-89G (2015)
   Background on integrated schedules, dependencies, baseline comparisons, and the connection between time and cost. The date examples and review records here are original teaching devices, not a GAO assessment.
3. Caltrans Construction Manual, section 5-1: Project Records and Reports (November 2024)
   Background on retaining organized project records. These CSV fields and examples are independently authored, not copied Caltrans forms or a mandated filing structure.
4. AIA Contract Documents: what is a submittal in construction?
   Background on required submittals and their review against project requirements. The project’s own contract determines the responsible roles and procedures; a submittal disposition does not itself replace a required contract modification.
5. 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.
6. 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.