Vacancy clause triggers in builder's risk policies: what actually starts the clock
Most builder's risk disputes that end up on an underwriter's desk don't start with a fire or a storm. They start with a question nobody wrote down clearly enough: when did this building stop being "under construction" and start being occupied?
That question matters because vacancy and occupancy conditions in a builder's risk form aren't decorative. They change what's covered, sometimes to zero, the moment a trigger fires. And the trigger dates insureds report are rarely the ones a claims file can support.
What the vacancy clause protects against
A builder's risk policy is written around the assumption that the property is a job site: unoccupied, under active work, with the usual fire watch and security that comes with a live construction schedule. Vacancy clauses exist because an empty, unfinished building behaves differently from a risk standpoint than one with tenants moving in and finish crews still on-site. Once space is occupied, or once work stops for an extended stretch, the exposure profile the policy was priced for no longer matches reality.
Policy language varies by carrier, but the clause usually does one of two things: suspends certain coverages after a stated period of vacancy, or conditions coverage on construction remaining "continuous" with no extended gaps. Some forms tie the suspension to a fixed number of consecutive days with no work performed, commonly 30 or 60, though the exact number is a policy-specific fact to confirm on each form rather than a rule of thumb to carry across accounts.
Occupancy before substantial completion is the harder trigger
Vacancy gaps are at least visible on paper, since a contractor's draw schedule usually shows when work stopped. Occupancy before substantial completion is messier, because it's a fact pattern that develops on-site long before anyone files paperwork about it.
A developer leases up a few floors while the podium is still being finished. A homeowner moves furniture into a custom build before the final punch list closes. A tenant improvement contractor lets the anchor store open for soft launch while mechanical work continues above the ceiling tiles. None of that shows up in a monthly progress report, because nobody reporting progress has an incentive to flag it. The person submitting the update is also the person whose coverage depends on the building still reading as a construction site.
This is the gap that matters most for claims handling. If a loss happens after occupancy began but before the certificate of occupancy was issued and the builder's risk policy hasn't rolled to a permanent property form, the file needs an independent answer to "was this space occupied, and since when." Self-reported stage of completion doesn't answer that question. It answers "what the insured's team wants the file to say."
COC timing and the handoff between policy forms
The certificate of occupancy is the cleanest line in theory: builder's risk covers the project up to substantial completion, the COC issues, and the risk transitions to a permanent policy. In practice the COC date, the actual move-in date, and the date construction work genuinely wrapped are three separate dates that frequently don't line up. A COC can issue for a shell while tenant buildout continues under the same builder's risk form. Occupancy can begin ahead of the COC in jurisdictions where temporary certificates are common. Either way, the policy condition tied to "substantial completion" or "issuance of a certificate of occupancy" needs a documented date, not an assumed one.
For an underwriter managing a book of course-of-construction risks, the practical problem isn't knowing the clause language. It's having an independent, dated record of footprint, visible activity, and site condition that doesn't depend on the insured's own update cycle. That's the gap Builder's Risk Monitor is built to close: a monthly read of stage of completion and site activity built from repeat overhead imagery, delivered as an overlay you can file against the policy the same way you'd file a progress photo set, except nobody on the project had to supply it.
If vacancy and occupancy triggers keep showing up as disputed facts in your claims files, it's worth getting an independent monthly record running on the risk before the next renewal cycle.