When an inspection passes on Thursday but nobody checks until Tuesday, the crew loses days they could have been on site. That gap is not bad luck, it is a process hole. Knowing what to watch, when to look, and who gets told turns a five-day delay into a same-day restart.
The inspection passed on Thursday afternoon. The inspector closed it out in the portal, the status changed, and the job was clear to proceed. Nobody on the contractor side looked until the following Wednesday morning. The crew had been holding off the site the entire time, waiting on a result that had been sitting there for six days.
That gap does not show up anywhere obvious. There is no invoice for the lost days, no line item called 'crew time we paid while waiting on a result we already had.' It lands quietly in the schedule as a delay, in the payroll as hours that earned nothing, and in the client relationship as a contractor who seemed slow to move.
How the gap opens
Most jurisdictions post inspection results to the same portal where you pulled the permit. The inspector marks the visit, enters a result — pass, fail, or conditional — and the record updates, sometimes within the hour, sometimes the next morning. The portal does not call you. It does not text you. It changes a field in a table and waits.
On a busy week, nobody is assigned to check that specific job's status. The project manager assumes the inspector will call if something is wrong. The field lead assumes the office is watching. The office is handling three other jobs and a supplier issue. Thursday passes. Friday passes. The weekend is not a portal day. Monday comes and goes. Tuesday is a site visit somewhere else. Wednesday, someone finally logs in.
What those days actually cost
Say your crew runs two people at a day rate of $400 combined. Six idle days tied to one job is $2,400 in labor that produced nothing on that site. That figure does not include the downstream jobs that got pushed, the subcontractor who had to reschedule, or the client who started asking questions by day four.
Now say this happens three times in a quarter — not because inspections are failing, but because passed inspections are sitting unread. That is a five-figure drag on the quarter from a problem that costs nothing to fix except attention.
The math is always reader-supplied, because every shop runs different rates and different crew sizes. But the structure of the loss is the same everywhere: time that could have been recovered was not, because no one was watching the right screen at the right moment.
Why this is a process problem, not a portal problem
It is tempting to blame the jurisdiction for not sending a notification. Some do send emails; many do not. Some portals have notification settings buried three menus deep that nobody turned on during setup. But waiting for the portal to improve is not a plan.
The real problem is that checking inspection status is not owned by anyone on a specific schedule. It is assumed. Assumed tasks do not get done consistently, especially when the team is stretched across multiple active jobs.
The fix is to make it owned and scheduled. One person, one daily check, every job that has an inspection pending. Five minutes in the morning, logged in, status confirmed, result recorded. If the result changed overnight, the crew lead knows before the morning meeting ends.
The Thursday-to-Wednesday pattern in practice
Thursday afternoon inspections are common because inspectors often work through a morning list and catch up on paperwork in the afternoon. Results posted Thursday evening are easy to miss because the office day is already winding down.
Friday morning is the natural catch window — but only if someone is specifically looking for Thursday results. If the Friday check is not on anyone's list, the result sits through the weekend. Monday is often consumed by job starts and material deliveries. By Tuesday, the job that passed Thursday has been idle for four full working days and nobody has flagged it as a problem yet.
Building a Friday-morning inspection check into the weekly routine catches most of these. For jobs with a Monday or Tuesday inspection, a same-day afternoon check is worth the two minutes it takes.
Permit delays that look like inspection delays
Sometimes what looks like a slow inspection result is actually a permit that moved to a new status after the inspection, a correction notice, a hold from another department, or a required re-inspection that was not communicated directly. The portal reflects it; no one called.
This is why the check needs to be a full status read, not just a glance for 'passed.' A job that passed rough-in but now shows a hold for a fire-department sign-off is not clear to proceed, even though the last inspection result was positive. Reading the full current status takes thirty seconds more than reading one field.
Who should own the check
On a solo operation, the owner is the only option, and the check needs to be a non-negotiable part of the morning, the same way checking the day's schedule is. On a crew of four or five, the person who handles permitting and scheduling is the right owner, not the field lead, who should be focused on the site, and not a subcontractor, who has no visibility into your other jobs.
The output of the check should be a short daily note: job name, current status, any action needed, who was notified. It does not need to be a formal system. A shared note in a group text works. What matters is that the information moves from the portal to the people who need it before the workday begins.
When the phone side of the business is handled by something like cheaply, which answers calls, texts back missed callers, and books jobs into the schedule, the owner has more mental space for exactly this kind of operational check. Not because the tool does the permit work, but because fewer things are falling through cracks simultaneously.
The client conversation when the delay was yours
When a client asks why the crew was not back on site Monday, 'we were waiting on the inspection result' is true but incomplete if the result was posted Thursday. Most clients will not know the difference between a jurisdiction that is slow to post and a contractor who was slow to check. But if they find out the result was there days ago, the trust cost is real.
The cleaner answer is to never be in that position. When the check is daily and the result is acted on the same day it posts, the crew is back on site in 24 to 48 hours of the inspection closing. That is a timeline clients remember favorably, and it is built entirely on a five-minute morning habit.
Frequently asked questions
How often should I check the portal for inspection results?
Do most permit portals send automatic notifications when an inspection passes?
What if the inspection passed but the portal shows a new hold I did not expect?
Who should be responsible for checking inspection status on a small crew?
Is a six-day gap between a passed inspection and a crew restart unusual?
The missed-call calculator does this article's math with your real call volume and ticket size — in the open, no email gate.
Open the calculator →Solo $97 · Crew $197 · Shop $397 per month, minutes included, no contracts.
