Permits, Inspections & the Paper Trail

Six weeks after your firm wins a renovation contract, everyone assumes it's time to start swinging hammers: the contract's signed, insurance is in place, the crew is scheduled. Then the owner's attorney sends a one-line email: work can't begin until the notice to proceed goes out, and that hasn't happened yet. A superintendent who mobilizes a crew anyway, on a signed but not-yet-started contract, has just created a scheduling and payment headache nobody wanted. A notice to proceed is a formal, written notice from the owner authorizing the contractor to actually begin, and it's the specific document that starts counting toward the contract's completion date, not the day the contract was signed, and not the day a crew happens to show up. A contract can be fully executed and sit for weeks before an owner is actually ready to issue it, waiting on financing, a permit, or a site that isn't cleared yet. Confusing "the contract is signed" with "we can start" is exactly the kind of assumption that costs a contractor real money if a crew mobilizes early and the schedule clock hasn't actually started. Once the notice to proceed does go out, a legal paper trail follows the project all the way to its final day, an ordered sequence of approvals and inspections that keeps the work legally authorized to continue at every stage, not just at the very beginning.

It's tempting to think the legal paperwork is mostly done once a project clears plan review and gets its building permit. In practice, a permit doesn't just get issued and forgotten: it stays open, with a checklist of required inspections tied to it that have to be scheduled and passed as construction actually proceeds. Cover a wall before the rough electrical behind it gets inspected, and an inspector can require it opened back up to verify what's inside, an expensive way to relearn why those checkpoints exist in the order they do. Some of that field verification goes even further than a routine building department visit. Special inspection adds a second, independent set of eyes on top of whatever the building department itself checks, specifically for the highest-risk categories of work: structural welds, high-strength bolting, concrete placement. The inspector performing it answers to neither the contractor nor the building department, which is exactly the independence the requirement is built around. A lot of that field verification is also where a QA/QC Inspector spends their entire day: physically walking the work, pulling concrete test cylinders, checking weld quality against spec, and documenting exactly what doesn't meet it, distinct from a building department inspector, who's checking against code rather than the project's own quality standard.

Sometimes an inspection, or something a superintendent notices directly, is serious enough to halt work altogether. That's a stop work order, a formal directive, issued by the owner, a government authority, or occasionally the contractor's own safety team, halting some or all of the job, most often over an unpermitted change, a serious safety hazard, or a code violation significant enough that continuing would make the underlying problem worse. It's worth keeping that clearly separate from something you may have already run into elsewhere: stop work authority, the right of any individual worker, regardless of position, to halt work on the spot when they see an imminent safety hazard. A stop work order comes from an authority formally directing the job to pause; stop work authority is exercised by a person in the moment, no formal process required, no permission needed first. Both exist to interrupt work before a problem compounds, but they come from very different places and carry very different levels of formality.

Eventually a project reaches its last stretch, and newcomers often assume one final check covers everything. It doesn't. The owner and architect first walk the finished work against the project's own punch list, the small, mostly cosmetic items identified near the end that still need fixing before the owner considers the work fully complete. Passing that walk is a real milestone, but it says nothing about whether the local building department will pass its own, separate final inspection, the building department's own last check confirming the completed project actually meets code. A contractor can clear the owner's entire punch list and still fail the department's final inspection over something the punch list never even covered, because the two are checking the work against entirely different standards. Passing that final inspection is what actually earns a project its certificate of occupancy, the official document confirming the building meets code and can legally be occupied. Without it, nobody can legally move in or open for business, no matter how finished the space looks to a visitor walking through it. On a phased project, an owner sometimes needs to move into part of a building before the whole thing reaches that point, which is what beneficial occupancy exists for: an agreed early move-in for part or all of a facility, with clear terms for who now carries insurance, maintenance, and warranty responsibility for that space once occupancy begins.

Zoom out across a project's entire life, and the sequence looks like this: a notice to proceed formally starts the clock, ongoing field inspections, routine and special, keep the work legally verified as it happens, a stop work order exists as the emergency brake if something's seriously wrong, and a final inspection followed by a certificate of occupancy is what actually lets the finished building be used. Miss a step anywhere in that chain, and a project doesn't just fall behind schedule, it can become legally unable to proceed at all. This entire thread, permitting, inspections, and the government-facing side of that paper trail, is the daily work of a Permit Expediter, preparing and tracking permit applications and resolving plan review comments so a project doesn't stall in a review queue, while a QA/QC Inspector handles the hands-on verification that the physical work itself actually meets spec along the way. Between them, very little of what actually gets built escapes some form of documented check. If you remember one thing from this lesson, make it this: a construction project's legal right to keep moving forward isn't granted once at the start and then assumed for the rest of the job. It gets re-earned at specific checkpoints, from notice to proceed all the way to certificate of occupancy, and skipping or rushing any one of them can stop a project just as fast as running out of money.