Certificate of Occupancy vs. Substantial Completion: Different Triggers, Different Money
Two documents can arrive near the end of a construction project that get confused with each other: the certificate of occupancy (CO) and the certificate of substantial completion (the AIA G704). They often come within days of each other, both signal that the project is mostly done, and both affect what the owner can do next. But they're different documents with different origins, different signatories, and different legal effects.
For AP and accounting teams, the distinction matters because contract clauses often tie specific events to one document or the other. Retention release typically ties to substantial completion. Warranty start ties to substantial completion. But tenant build-out that can't begin until the space is legally occupiable ties to the CO. Risk of loss shifts can be tied to either, depending on the contract. Knowing which document triggers which consequence keeps the closeout from falling into disputes.
A certificate of substantial completion (typically AIA G704 on AIA contracts) is a contract document. It's issued by the architect, signed by the owner, architect, and contractor, and it declares that the work has reached substantial completion per the contract definition — typically meaning the project can be used for its intended purpose notwithstanding punch-list items. It triggers contract-level events: warranty start, retention release, risk of loss transfer in some contracts, and the final payment clock under many prompt-payment statutes.
A certificate of occupancy is a municipal permit document. It's issued by the local building department after final inspection, declaring that the building complies with applicable codes and can be legally occupied for its intended use. It's a regulatory document, not a contract document. It triggers occupancy-related events: the owner can take possession, tenants can move in, the insurer's coverage can shift from builder's risk to permanent.
On most projects, substantial completion and CO issuance happen close together — often within a week or two. The architect's declaration of substantial completion usually presupposes that the final inspection has or will soon produce a CO. An owner can't really "take beneficial occupancy" of a building that the city won't let them occupy.
When they align cleanly, the distinction hardly matters in practice — both events happen, both trigger their respective consequences, and the project closes out. The distinction becomes important when they diverge.
Several scenarios create a gap between substantial completion and CO:
Scenarios where CO and substantial completion don't align
- TCO (Temporary Certificate of Occupancy) — building department issues a TCO for the occupiable portion while some work continues; substantial completion can be declared on the completed portion while the TCO is still temporary
- Phased occupancy — owner takes occupancy of some floors or units while others are still under construction; substantial completion and CO can be declared independently per phase
- Inspection delays — city inspectors are backed up; CO is delayed weeks after the work is actually complete, while substantial completion can be certified by the architect based on the work's state
- Punch-list-critical issues — architect declares substantial completion with a punch list, but a punch item turns out to be code-critical and delays the CO
- Owner occupancy before CO — owner takes beneficial occupancy with some regulatory risk because the space is finished enough to use even though the CO hasn't issued yet
In these scenarios, the contract has to specify what event triggers what consequence. Well-drafted contracts handle this explicitly; poorly-drafted ones leave both sides arguing whether retention release, warranty start, etc. tie to substantial completion or to CO.
Typical events triggered by substantial completion
- Start of the one-year general warranty period
- Transfer of risk of loss from contractor to owner (in many contracts)
- Termination of builder's risk insurance (requiring owner's permanent property coverage to kick in)
- Initial retention release (typically leaving a smaller portion held against punch list)
- Start of the final payment clock under prompt-payment statutes
- Start of lien filing deadlines in some states
- 11-month warranty walkthrough calendar reminder for the owner
Typical events triggered by certificate of occupancy
- Legal authority to occupy the building
- Tenant ability to move in and take possession
- Property tax assessment can change (from construction to occupied commercial/residential)
- Operational permits that depend on occupancy (food service, daycare, etc.) can be issued
- Insurance transitions from construction/builder's risk to permanent property policies
- Utility service transitions (from construction utilities to permanent service)
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Some of these overlap — builder's risk termination can be tied to either event depending on the specific policy language. Risk of loss can be tied to either depending on contract drafting. The practical approach: make sure the contract is specific about which event triggers each consequence, and don't let ambiguity create dispute opportunities later.
Contract language that says "occupancy" without specifying "beneficial occupancy per substantial completion" or "occupancy pursuant to certificate of occupancy" is ambiguous. Clean contracts pick one and reference the corresponding document.
When a project is substantially complete but not yet fully compliant with all permit conditions (landscape not finished, specific punch items not closed, etc.), the building department can issue a temporary CO — allowing occupancy for a specific period while the remaining items are resolved. TCOs typically come with conditions and a deadline by which a permanent CO must be issued or the TCO expires.
For AP, a project under a TCO is in an unusual state: substantially complete and occupied, but not fully closed out from a permit perspective. Retention release against substantial completion can proceed under the contract. Final punch-list items may still be outstanding. The permanent CO will issue when those items resolve.
For AP managing closeout on a project with near-simultaneous substantial completion and CO:
AP actions on closeout
- Record both dates on the project master — substantial completion date (from G704) and CO date (from building department)
- Release retention per the substantial completion date, per the contract's retention release language
- Start warranty reserve tracking from substantial completion date
- Trigger insurance transitions per the CO date (coordinating with the owner's insurance team)
- Calendar the lien filing deadline per the controlling state rule (substantial completion, final completion, or last furnishing depending on state)
- Continue tracking punch completion against the retention holdback until final completion
Substantial completion is a contract event issued by the architect; certificate of occupancy is a regulatory event issued by the building department. They often happen close together but they're different documents with different effects. Contracts that handle both concepts explicitly — tying specific consequences to specific events — close out cleanly. Contracts that conflate them create disputes when the two events diverge. Knowing which document triggers retention release, warranty start, insurance transition, and lien deadlines lets the AP team execute closeout without surprises.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts