Which document serves as the official authorization for a project in construction documentation

The document that serves as the official authorization for a construction project is the owner's signed notice to proceed (NTP), issued after the contract is executed and typically after permits and insurance are verified. The NTP converts a signed agreement into authorized work: it fixes the start date, releases the schedule, and obligates funding. Contracts authorize the relationship; the NTP authorizes execution.

What follows traces how that authorization actually works in practice, where it breaks down, and how to document it so the paper trail survives audit, delay claims, and closeout.

How authorization flows from contract to notice to proceed

Construction authorization is not a single signature. It is a chain of instruments, each granting a different kind of permission (Engineers Joint Contract Documents Committee forms organize this sequence).

The agreement (A101-style owner-contract form) establishes price, scope, and time. Signing it creates an obligation, not a start signal. Many agreements explicitly state the contractor shall not begin work until receiving written notice. That clause is the hinge: without it, contracts and NTPs blur together, and disputes arise over when the clock started.

The NTP is usually a one-page letter. It references the agreement date, states the effective date of authorization, confirms that conditions precedent are satisfied, and sets the contract time running. It may authorize full work or phase it (notice to proceed with foundations only, for example). The mechanism matters because schedule, payment, and delay claims all attach to that date.

Conditions precedent typically include building permit issuance, proof of insurance and bonding, owner financing confirmation, and sometimes utility or right-of-way clearance. The NTP is the owner's written confirmation that these gates are cleared. A useful mental model: the contract is the promise, the permit is the legal permission, and the NTP is the owner pressing "go."

Documentation systems should treat the NTP as a controlled record with a unique number, date, distribution list, and acknowledgment from the contractor. In electronic document management (Procore, Autodesk Construction Cloud, or equivalent), it belongs in the contracts or owner-directives module, not general correspondence. Version control matters: a superseded NTP that authorized a different start date can quietly undermine a delay claim.

What the numbers say about authorization timing and risk

Exact statistics vary by project type, so treat the following as planning ranges rather than measured universals. Public agency practice offers the most concrete anchors. The Federal Acquisition Regulation treats the notice to proceed as the instrument that establishes the contract start date, and agencies commonly issue it within days of award; on some federal construction solicitations, contractors must acknowledge the NTP within a set period, often around 10 days.

On private commercial projects, the gap between contract execution and NTP commonly runs two to eight weeks when permits are pending. That interval is where authorization risk concentrates: trades mobilized early, storage costs, and preconstruction invoices accumulate before any work is formally authorized.

Retainage and payment schedules also key off the NTP. If the contract sets substantial completion at 365 calendar days from NTP, a four-week permitting delay shifts every downstream milestone and liquidated-damages exposure by the same four weeks. A single date on one page propagates through the entire schedule.

Industry surveys consistently rank documentation and communication breakdowns among the top causes of construction disputes. The NTP sits at the center of that exposure because it defines when the contractor was entitled to proceed and when the owner became obligated to pay for time.

Edge cases: when the notice to proceed is not the whole story

Authorization fractures in several common situations, and each needs its own paper.

Letter of intent (LOI). An LOI may authorize limited preconstruction work (mobilization, submittals, long-lead procurement) before the full contract and NTP exist. It is authorization for a defined slice, not the project. Treat LOIs as time-boxed and dollar-capped; an open-ended LOI is how unauthorized scope creeps in.

Early work agreements. Some owners issue a separate early-work contract with its own NTP, then a main contract with a second NTP. Two authorization dates, two clocks. Mixing them confuses delay analysis.

Owner-directed changes. A verbal "go ahead" on a change is not authorization for the changed work. Field directives and change orders carry their own authorization; the original NTP does not cover them. Contractors who proceed on a handshake risk nonpayment, and owners who issue verbal directives risk losing cost control.

Phased or partial NTPs. Large projects often authorize work in packages (sitework first, then structure). Each package NTP should define its own scope boundary and completion date.

Public-sector variations. Some agencies use a notice of award plus executed contract in place of an NTP; others issue a formal NTP letter signed by the contracting officer. The authorization instrument differs, but the function is identical: written confirmation of the right to start.

Suspension and resumption. A suspension of work followed by a resume-work order is a second authorization event. Documenting the resumption date protects both parties in time-extension negotiations.

The counterintuitive professional caveat: an NTP does not guarantee payment authority exists. On some publicly funded projects, work can be authorized before funds are fully appropriated, and contractors have pursued claims over exactly this gap. Verification of funding is a separate check, not implied by the NTP.

Misconceptions that create unauthorized work

Several recurring beliefs cause documentation failures. Correcting them is cheaper than litigating them.

Misconception one: the signed contract authorizes work. It authorizes obligation. Without an NTP clause or letter, the start date is ambiguous, and ambiguity favors whoever documents better, not whoever is right.

Misconception two: the building permit is the authorization. The permit is the jurisdiction's permission to build. It says nothing about the owner's willingness to fund or the contractor's contractual right to proceed. A project can be fully permitted and still not authorized to start.

Misconception three: emails count as NTPs. An email can constitute written notice if the contract defines notice that way, but most contracts specify formal notice procedures and addresses. Relying on a project manager's email invites disputes about authority and receipt.

Misconception four: NTP equals notice to start spending. Owners sometimes want mobilization costs tracked from contract execution. That requires explicit language; the default NTP date controls.

Red-flag warnings to watch for: Work beginning before any written NTP or early-work agreement exists. An NTP issued before permits are actually in hand, shifting permit risk to the contractor by implication. NTP letters that omit the effective date or reference the wrong contract version. Verbal authorizations to proceed on changes, with paperwork "to follow." Multiple NTPs for the same scope with different dates and no supersession note. Contractors who never acknowledge receipt, leaving the start date unconfirmed.

Each of these is a documented cause of payment disputes and schedule claims. A five-minute acknowledgment letter closes the gap.

Comparing the authorization instruments

The instruments differ in what they authorize, who signs, and what they control. The table below maps the common ones.

The pattern: only the NTP and its variants are authorization to perform. Everything else either creates the obligation, grants legal permission, or modifies an existing authorization.

Practical actions to document authorization correctly

These steps apply whether the project is a USD 300,000 tenant build-out or a USD 30 million institutional job. The scale changes the formality, not the sequence.

Step one: put the NTP clause in the contract. Require written notice before work begins, define who may issue it, and specify the notice address. Without this clause, the NTP letter has no contractual teeth.

Step two: list conditions precedent in the agreement. Name them explicitly (permit, insurance certificates, bond, financing confirmation), so the NTP certifies something checkable rather than something assumed.

Step three: issue the NTP as a numbered, dated, signed letter. Reference the contract date and version. State the effective date and whether the authorization is full or phased. Include acknowledgment instructions.

Step four: obtain written acknowledgment within a defined window, commonly 5 to 10 business days. Log receipt in the document control system and link it to the schedule baseline.

Step five: reconcile every start date before the first pay application. Confirm that the schedule baseline, the pay application period, and the NTP date agree. Discrepancies here surface later as disputed time.

Step six: treat early work separately. If preconstruction or procurement starts before NTP, issue a written early-work authorization with a dollar cap and an expiration. Convert or close it at NTP.

Step seven: audit annually. On multi-year projects, verify that phase NTPs, change orders, and resume-work orders are all logged and cross-referenced. A ten-minute audit prevents a year of claim reconstruction.

One threshold to reconcile explicitly: contracts sometimes state a notice period for commencement ("work shall begin within 10 days of notice") while the NTP sets a specific calendar date. When both exist, the specific date in the NTP governs, and the notice period becomes a performance obligation measured from that date. Document the reconciliation in the NTP itself so no one has to interpret later.

Limitations and what authorization cannot guarantee

Authorization documents establish the right to proceed. They do not establish that proceeding is wise, funded in full, or free of risk.

The NTP cannot cure a defective contract, an unfunded appropriation, or a permit condition discovered after issuance. It also does not resolve scope ambiguity; if the contract's scope language is vague, the NTP simply authorizes work whose boundaries remain contested.

Documentation quality varies enormously by organization, and the practices described here reflect common industry standards rather than a universal legal requirement. Contract law, public procurement rules, and local recording requirements differ by jurisdiction and by project type. What counts as valid written notice in one contract may be insufficient in another.

Finally, this article is general educational information about construction documentation practice. It is not a legal opinion and does not create a professional-client relationship. For contract drafting, notice provisions, or claim documentation on a specific project, consult a licensed attorney or construction professional in your jurisdiction.