ProductSolutionsTradesPricingArticlesContact Log in Start free trial

Field & cost

Inspection holds and retests: the gate between your work and your money

For the PM or office manager at a trade whose billing stops at an inspection somebody else calls.

10 min read

Four of our trade pages say a version of the same sentence, in four different trades’ words.

Plumbing: your billing is gated behind inspections you do not control. Fire sprinkler: every phase is gated behind an inspection you do not schedule. Fire alarm: you get retested for somebody else’s mistake. Waterproofing: a flood test is a pass-or-fail day, and nobody budgets the retest.

That is one problem wearing four coats. Your work is finished. Your money is not released, because a person who does not work for you, scheduled by a person who does not work for you, has not yet written a word on a card. And when that word is the wrong one, the second visit gets billed to somebody — often you, by default, because nobody wrote down why it failed.

This is how to track that so the default stops being you.

The three parties, and you are only one of them

An inspection has at least three people in it, and the trade that performs the work usually controls the least.

The authority having jurisdiction. A city or county inspector, a state fire marshal’s office, a third-party agency on a deferred submittal. They set the sequence, the lead time and what gets looked at. On most commercial jobs they also set the one thing that hurts most: you cannot cover it up until they have seen it.

Whoever holds the permit and calls the inspection. Sometimes that is you, under your own trade permit. Often it is the GC, and more often than anyone admits it is a GC’s project engineer working from a schedule that has your rough-in finishing on Friday and the inspection on Friday.

You, who performed the work. You know whether it is ready. You are frequently the last to know when it was called.

The gap between party two and party three is where the money goes. An inspection called before the work was ready produces a failure that is nobody’s fault and your fee. An inspection called a week late produces a week of a crew with nothing to cover up and nowhere to go.

So the first piece of tracking is not a date. It is a name: who calls your inspections on this job, confirmed at the start-up meeting and written down. That question belongs on the job start-up checklist alongside the permit, next to who receives your submittals and who signs a change order. Three sentences in a kickoff save a month of guessing.

The two dates that are not the same date

Most subs track one date per area: the day the work was done. That is the wrong number of dates.

“Ready for inspection” is its own date. It is the day your crew finished, cleaned up, pulled their ladders and left it in a condition somebody can walk. It is the date you own, the date you can prove, and the date every entitlement argument runs from.

“Inspected” is the other date, and it belongs to somebody else. The distance between the two is the hold — and the hold is a number you can only produce if you wrote the first date down on the day, not reconstructed it in month four from a text message.

Log them separately. In practice that means a line in the day’s daily log that says the area is complete and ready for inspection, with the area named the way the GC names it, and then a second entry on the day the inspector actually shows up with what they said.

Three things fall out of having both dates:

  • A hold you can measure. “Second floor east was ready on the 9th and inspected on the 23rd” is a fact. “We were waiting forever” is a feeling, and feelings do not get paid.
  • A defense against a failure that is not yours. If the work sat open for two weeks before anyone looked at it, and in those two weeks four other trades worked in the same ceiling, that matters to whose damage the inspector found.
  • A billing argument that survives a percentage dispute. When your draw gets cut because an area is “not complete”, complete-and-ready-for-inspection against a named date is the sentence that moves it.

Re-inspection fees, and who they actually land on

Many jurisdictions charge for a second visit. The amount is usually modest on its own — the problem is never the fee, it is the precedent and the schedule.

Who pays depends on two things, and neither is universal: what your subcontract says about fees and permit costs, and what caused the failure. Read your own agreement, because this is one of the clauses that varies the most from GC to GC. Broadly, the failures sort into three buckets, and the bucket is the whole argument.

You failed it. The work was not right. Fix it, eat the fee, call it again. There is nothing to document except the fix.

It was called before you said it was ready. This is a common one, and one that is rarely recovered, because recovering it requires that somebody wrote down when you said ready. If you have that date and the call came before it, the fee is not obviously yours, and in many contracts it is not. Your contract governs.

Somebody else’s work failed inside yours. Another trade’s penetration in your rated assembly. A hanger somebody hung off your pipe. Steel bolted up by a crew whose weld did not pass over work you set. This travels like any other recoverable cost — as a back charge to the trade, if you have privity, or as a change event to the GC if you do not.

Two practical notes. First, the fee is rarely the real cost — the real cost is the crew you remobilized and the four days the area stayed open. Price the day, not the receipt. Second, say it in the week it happens. A re-inspection fee argued at closeout is an argument about a bill. Argued the same week, it is a question about a cause, and questions do better than bills.

The record that makes a retest somebody else’s cost

An inspection dispute is settled by whoever has dates and pictures. Four things, all cheap, all gathered the day of.

A photo of the work before cover-up, filed with the date it was taken. This is the whole ballgame on underground, in-wall and above-ceiling work, and it is why our waterproofing page puts it bluntly: your work disappears. Once it is covered, the only version of the condition that exists is a photograph.

The correction notice itself, kept as a document and not as a memory. What was written on the card, by whom, on what date. Transcribe it into your record the same day, because the paper version lives in a GC’s trailer.

A daily log entry naming the cause. Not “inspection issue” — the actual reason, in a sentence, with the area and the trade involved.

Your own re-walk before you call it again. A second failure on the same correction is the one that turns an inspector skeptical about everything you do on that job for the next eight months.

This article is general information, not legal advice. Who owes a re-inspection fee, what notice your contract requires, and what counts as readiness are set by your subcontract, your permit and your jurisdiction; have an attorney read yours.

Special inspections are a different animal

Code inspections and special inspections get filed under one word and behave nothing alike.

A special or third-party inspection — weld and bolt-up testing, soils and compaction, concrete breaks, firestopping, sprinkler hydro, fire alarm acceptance — is usually performed by an agency hired by the owner or the GC, on a schedule set by a statement of special inspections, against work you installed. Structural steel’s version of the complaint is exact: somebody else’s pass or fail on your work.

Three differences worth building into how you track them.

  1. They produce a report, not a card, and the report often arrives days later. Ask who distributes it and get on that list, because a report you have not seen is a deficiency you are not fixing.
  2. They are often billed by the hour, and the cost of a wasted trip can land on whoever caused it. A canceled test and a second mobilization of an agency are costs with a named owner, and the name is the one in the scheduling email.
  3. They are a payment gate on their own. Low-voltage’s version — the final ten percent waits on a test report — is true across the test-report trades. Treat the report like a lien waiver: an administrative document standing between you and money, with an owner and a due date.

What it looks like by trade

The structure is the same everywhere. What gets held is not.

Plumbing. Underground and top-out are the two that bury your riskiest money. The pressure test window and the inspector’s window rarely line up, and a line that has to be re-charged for a second visit is a crew day. Photograph the trench and the hanger spacing before anyone backfills or closes a wall.

Fire sprinkler. Hydro is a pass-or-fail day with a crew standing on it, and a failed hydro is almost never a single repair — it is a day, a drain-down, a repair and a refill. Impairment and fire watch around a test are also the costs most often absorbed without a ticket.

Fire alarm. Acceptance testing is the whole back end of the contract, it depends on devices installed by other trades, and a retest for one wrong address on a loop costs you the programmer who is on six jobs. Get the device-level punch out of the acceptance test and into its own list.

Electrical. Rough and final are the hard gates, and the rough is the one that gets called early. Trim-level failures — labeling, panel directories, cover plates, blanks — are cheap to fix and expensive to re-inspect, so run your own trim walk before the call.

Wood framing. Frame inspection is usually called building by building, which turns one inspection into fourteen, each with its own readiness date. That alone is a reason to track readiness per building rather than per contract.

Waterproofing and roofing. The flood test is the event, the retest is the unbudgeted day, and the substrate you were told to proceed over is the reason it failed. Document the substrate in writing before you install, not after it leaks.

How SubMark handles it

Start with what is not there. SubMark does not schedule inspections. There is no AHJ integration, no permit portal, no inspection calendar, no correction-notice workflow. Inspections are called in the city’s system or the GC’s, and we are not going to pretend otherwise.

What SubMark holds is the dated record the argument turns on.

Daily logs with inspection as a fixed delay cause. One log per job per day is enforced, so there is never a competing second version of a Tuesday. A delay is recorded with its cause from a fixed list — weather, material, labor, access, GC direction, inspection, other — plus a narrative, work areas and phases, labor hours and photos. The cause is the field that decides who pays for the day, and “inspection” being one of seven choices rather than free text is what makes a month of inspection holds something you can actually find. Field users are free and unlimited, which is what makes this work at all: the moment a log costs a seat per foreman, you get logs from two of your eight.

Job photos with an Inspection category. Every project has a photo area with filing categories — General, Progress, Before, After, Damage, Material, Inspection, Safety and Punch List, plus your own. Photos filter by category, so “show me everything filed under Inspection on this job” is one click rather than a scroll through nine hundred images. The habit worth building is the Before photo on the day the area goes ready, not the day it fails.

Inspection as a daily-log phase, in your trade’s own words. Each setup pack seeds its own phase list for the log’s work areas, and on the inspection-gated trades the gates are in it as phases rather than as an afterthought: the electrical pack carries Rough Inspection, the plumbing pack Underground Inspection, HVAC Rough Inspection, fire sprinkler Rough Inspection and Hydro Test. A foreman picking “Rough Inspection” as the phase on the day the area went ready is recording the readiness date in the field everybody already looks at.

The same packs carry an inspection-pass vocabulary for labor — Rough Inspection, Trim or Start-Up, Final Inspection, Hydro Test, depending on the trade — which is what an hours-by-pass report would use. One honest limit, because it matters before you go looking: the patch-and-phase surface that reports hours by pass is a drywall default today, so on an electrical or plumbing job it stays off unless patch tracking is switched on. The pass names are in the pack either way.

A permit line on the job checklist. The job checklist that ships with the inspection-gated trade packs opens with Permit and Submittals, which is the right place for “who calls our inspections” to get answered on week one.

Change events, dated when you create them, with photos. A retest caused by somebody else goes here on the day it happens. It records the event rather than the dispute, and if it turns into recoverable work it carries forward into a change order through the normal process. When the GC wants the correction fixed now and priced later, that is what a T&M tag is for: on by default in most trade setup packs, priced in the office off your rate lists, signed by the GC on site, with several tags converting into one change order. T&M hours do not feed job-costing actuals; your crew’s clocked hours still do.

See the product for how the field side fits together, and pricing for what the office side costs.

What to do before your next rough inspection

  1. Name who calls inspections on this job, at start-up, in writing.
  2. Log “ready for inspection” per area on the day it happens, separately from “complete”.
  3. Photograph everything that is about to be covered, filed under Inspection with the date.
  4. Transcribe every correction notice the same day, with who wrote it.
  5. Sort each failure into one of three buckets — ours, called early, somebody else’s — in the week it happens, not at closeout.
  6. Price the day, not the fee, when the failure was not yours.
  7. Walk it yourself before the second call.

None of that gets the inspector there sooner. It changes who pays when they get there twice — and after the inspections are done, the rest of the end-of-job sequence is in closing out a commercial construction job.

An inspection argument is a date argument. Keep the dates.

SubMark has no inspection scheduling and no AHJ portal. What it has is the dated record an inspection argument turns on: daily logs with inspection as one of the fixed delay causes, job photos filed under Inspection with the day they were taken, change events, and a trade pack that already names your inspection gates as daily-log phases.

Start free trial

14-day free trial, no card needed. Field users and the subs you invite are free and unlimited — see how pricing works. What SubMark does