Use case demo Video

Building permits: submission to certificate of occupancy

A city plans examiner walks a construction permit through completeness screening, parallel departmental reviews, revise-and-resubmit loops, issuance, milestone inspections, and the certificate of occupancy — the whole flow captured live.

Transcript

Interviewer: So somebody wants to build something — an addition, a new house, whatever. From your side of the counter, where does this actually begin?

Examiner: Honestly, before they ever file anything. The smart ones come talk to us first. We do pre-application meetings — sit down, figure out what kind of permit they even need, what zoning allows, what occupancy class it is, which reviews are gonna apply. Because "I want to build a deck" and "I want to build a duplex" are completely different animals. The ones who skip that step? They're usually the ones who end up in the loop three or four times later. So pre-app is optional, but I'm always telling people, please, just come talk to us first.

Interviewer: Okay, say they've done their homework. What do they actually put together?

Examiner: The application package. So that's the forms, but really it's the plan set — the drawings, the site plan, structural calcs if it's anything substantial, energy compliance forms, all of it. And ideally it's stamped by a licensed architect or engineer depending on scope. The quality of that package, I cannot stress this enough, that determines how painful the next two months are gonna be. Garbage in, lots of correction cycles out.

Interviewer: And they bring that to you how?

Examiner: Mostly through the online portal now — we're on Accela. Some people still walk into the counter, especially older contractors who've been doing it the same way for thirty years. Either way they submit, they pay an intake fee up front, and that creates the permit record in the system.

Interviewer: So now it's in. Does it go straight to you for review?

Examiner: No — and this trips people up. First there's a completeness check. A permit tech screens it: do we have all the forms, are the drawings signed and stamped, is anything obviously missing. That's a gate, not a review. If it's incomplete, we kick it right back before anybody technical even looks at it. "You're missing your structural calcs, resubmit." And people get so frustrated because they think they're in the queue, but they never actually got in the door.

Interviewer: So an incomplete one bounces back out before review even starts.

Examiner: Right. Doesn't count as a review cycle, doesn't start the clock in their mind even though it kind of does. It just goes back. Come again when it's complete.

Interviewer: And once it passes that gate?

Examiner: Then it gets routed. Whoever's coordinating splits it out to all the disciplines that need to touch it. And honestly a lot of that routing is still manual — somebody deciding, okay this one needs fire, this one needs public works, this one's just building and zoning. That distribution step is where the whole thing fans out.

Interviewer: Fans out into what?

Examiner: Parallel review. So this is the part outsiders never picture right. It's not one person reading the plans start to finish. It's multiple departments reviewing at the same time, independently. I'm doing the building and structural review. Meanwhile a planner's doing zoning — setbacks, height, use. Fire's checking egress, sprinklers, access. Public works is looking at grading, utilities, the right-of-way. Health or environmental if it applies. All of us, same plans, same time, different lanes.

Interviewer: And you're not really talking to each other while you do it?

Examiner: Not much, no. Everybody's heads-down in their own lane against their own code sections. And the practical effect of that is the slowest lane sets the pace. I can clear my building review in a week, but if public works is backed up three weeks, the applicant's waiting three weeks. They have no idea why — from outside it's just silence.

Interviewer: So each of you finds problems. Then what?

Examiner: Each reviewer writes up comments. Correction notices. "This stair doesn't meet rise-over-run, fix it." "Your setback's two feet short." Whatever it is in our lane, we document it in the system. And then — this is important — all those comments get consolidated. Somebody pulls every department's comments into one correction letter and sends the whole bundle back to the applicant at once.

Interviewer: One letter, all the departments' comments together.

Examiner: That's the goal, yeah. And that's also exactly where the conflicts show up. Because sometimes fire wants the door to swing one way and accessibility wants it the other, and now the applicant's holding two comments that contradict each other and they're calling me going "well which is it?" And the honest answer is the two departments need to talk, which — they don't always do quickly.

Interviewer: So now there's a decision point. Is it ever just... approved on the first pass?

Examiner: [laughs] Rarely. On a simple permit, sure, occasionally clean first pass. On anything real? Almost never. There's basically always corrections. So the realistic path is: corrections required, back to the applicant.

Interviewer: And that kicks off the part everybody complains about.

Examiner: The resubmittal loop. Yeah. So they take our comments, the design team revises the plans, and they resubmit. And then we re-review — every affected department re-checks their own comments against the revision. And here's the thing, it's almost never one and done. It's comment, revise, resubmit, re-review, and around again. Two cycles, three cycles, I've seen permits go five, six rounds. And sometimes a resubmittal introduces a new problem, so now there's a fresh comment that wasn't there before, and the loop gets longer.

Interviewer: That sounds maddening from the applicant's side.

Examiner: It is. And the worst part for them is the black box. They resubmit, and then... silence. They don't know if it's in my pile or fire's pile or sitting in a routing queue. No visibility into status. They just wait and call and wait. That's the number one complaint we get, the not-knowing.

Interviewer: At some point everybody's satisfied, though. How does it actually clear?

Examiner: Every department has to sign off. Individually. And this is the brutal part — one holdout blocks everything. I can be approved, zoning approved, fire approved, public works approved, but if the health reviewer has one open condition, the permit does not issue. Period. Four green lights and one red means red. So we're all tracking it, but it only moves when the very last lane clears its last comment.

Interviewer: And once that final lane clears?

Examiner: Then plan review is approved and we finalize the fees — the real fee schedule, usually based on valuation, not the little intake fee from the start. They pay that, and then the permit issues. That's the big moment for them — issuance is the authorization to actually start building. Permit's active, work can begin.

Interviewer: So they start construction. Are you done with them?

Examiner: Oh no, now it flips to inspections. As they build, they schedule inspections at milestones. Foundation before they pour. Framing before it gets covered up. Electrical, plumbing rough-in, mechanical, and then a final. Each one gates the next phase — you don't get to close up the walls until framing passes.

Interviewer: And an inspector goes out. Pass or fail?

Examiner: Pass or fail. Inspector shows up, and if it's good, that milestone clears, on to the next. If it fails, correction notice — fix it, and call for a re-inspection. And that's another loop, right? Same shape as the plan review loop, just out in the field now. Fail, fix, re-inspect, until that milestone passes. Foundation can't move forward till foundation passes.

Interviewer: Until eventually everything's passed.

Examiner: Every required inspection clears, final passes, and then we issue the certificate of occupancy. The CO. That's the legal one — that's what says the building can actually be used. Not just an administrative checkbox, it's the thing that makes it lawful to occupy. Then we close the permit out, archive the record, done.

Interviewer: Are there branches off that you didn't mention?

Examiner: Couple of side ones. Permits expire — if they don't start work, or they stall out, the permit lapses and they have to extend it or reactivate it. And there's an appeals path — if somebody really disputes a comment, thinks we're wrong on a code interpretation, they can appeal to a board or the building official, and that can bounce the thing right back into review. But those are the exceptions, not the main road.

Interviewer: Last question. What's the thing people get wrong about how this works?

Examiner: They think it's a line. A queue. Like their permit is item number forty and it advances one at a time until it's their turn and then it's done. And it's just not that. It's parallel — it's five departments going at once, and it only moves at the speed of the slowest one, and it only finishes when every single one independently clears. So when somebody calls and says "where's my permit," there isn't one answer. It might be ninety percent done and stuck on one open comment in one lane that nobody's looked at in two weeks. The whole thing held up by one holdout. People picture a conveyor belt. It's really five conveyor belts that all have to finish before anybody gets off — and nobody can see any of them. That's the real shape of it, and it's why the wait feels so random from outside.

Interviewer: That's a great place to stop. Thank you.

Examiner: Anytime. Just — tell people to come to the pre-app meeting. Saves everybody.

Keep exploring

More resources

Browse all resources

Built to SOC 2 standards

Sapeum is designed with enterprise-grade security practices from the ground up: encryption at rest and in transit, role-based access controls, and auditable change history.

Learn more

Your processes, captured the same way.

Everything you just saw runs on real workshops, not staged demos. Bring a process of yours and see for yourself.

Request a demo