The Permit Coordinator Opens Nine City Portals Before 8 A.M. Now an Agent Does That Round and Notes Every Lot.

5:50 a.m., and the Accela login page is still spinning

The permit coordinator at a builder closing sixty homes a year keeps nine tabs pinned in her browser. One is Accela Citizen Access for the county. One is Tyler EnerGov for the city that annexed the back half of your subdivision. One is eTRAKiT for the small town where you hold eleven lots. There is a CityView portal, a MyGov portal, the water district's separate meter-set request page, the state stormwater filing site, and two supplier portals where your electrician and your plumber are supposed to have pulled their own sub-permits — which you cannot confirm unless somebody looks.

She signs into all nine before the supers start calling at seven. Each has its own password rule, its own session timeout, and its own hiding place for the plan review corrections letter. On a good morning the round takes forty minutes. On the morning after a jurisdiction posts twenty comments on a resubmittal, it takes two hours, and by the time she has read them the framer has already been told he is starting Thursday on a lot that has no permit.

None of those portals will send you anything useful. A few email a notice, eventually, to whichever address the applicant typed in eighteen months ago. There is no export, no feed, no file you can drop into Buildertrend. The city built that portal for a homeowner pulling a deck permit, not for a builder running eleven lots through plan review at once.

Why nobody ever built you a connection to the building department

Software vendors connect to things that pay them. There are roughly twenty thousand permit-issuing jurisdictions in the United States, most of them running one of six or seven portal products with local customizations layered on top, and none of them owe your scheduling software anything. So the industry did what it always does: it hired a person to be the connection. That person is your permit coordinator, and on a lot of builder org charts she is also the closing coordinator and the one who orders the temporary power poles.

A browser-driving agent is software that signs into a website using your own login and clicks through it the way a person would — which is why it can work inside permit portals that were never built to connect to anything else. That is the whole idea. It does not need the city to cooperate. It does not need a vendor to publish anything. It needs a username, a password, and a description of what to look at.

Computer use and browser use existed in rough form in 2024 and 2025, and if you tried them then you probably watched one get lost in a dropdown and quit. What changed by 2026 is reliability on long, boring, multi-step screens — the kind where you pick a record type, then a lot, then scroll a table, then open a document that launches in a new tab behind the one you were on. The agents now handle the tab that opens behind the other tab. That sounds small. It is the entire difference between a demonstration and a Tuesday.

What the 6:10 a.m. round looks like when nobody is awake for it

The agent signs in with the same credentials your coordinator uses, on your machine, under her account, with a record of every click. It walks the lots you told it about. It reads plan review status, opens correction letters, notes which sheets are affected, checks whether the mechanical and electrical sub-permits have been issued, books tomorrow's inspections in whichever portal that jurisdiction uses, and reads yesterday's inspection results — including the ones marked Partial, which are the ones that quietly cost you a week.

flowchart TD
  A["6:10am — agent signs into Accela, EnerGov, eTRAKiT"] --> B["Reads status on 11 lots in plan review"]
  B --> C{"Corrections posted overnight?"}
  C -->|Yes| D["Opens the letter, lists the sheets affected"]
  D --> E["Sends the redline to the designer, sets resubmittal date"]
  E --> B
  C -->|No| F["Books tomorrow's inspections in each jurisdiction"]
  F --> G["Reads yesterday's results, flags every Partial or Not Approved"]
  G --> H["8:00am digest: lot, jurisdiction, what moved, what stopped"]

At eight o'clock your coordinator opens one page instead of nine. Lot 47 in the county: corrections issued at 11:52 p.m., three comments, all on the truss layout, already forwarded to the truss supplier. Lot 12 in the city: footing inspection Not Approved, rebar clearance, reinspection fee owed, and the agent has flagged the concrete order so you do not pour on Thursday and pay for it twice. Lot 6: the electrical sub-permit still has not been pulled by your electrician, sixteen days after the building permit issued — exactly the kind of thing that otherwise surfaces the morning the rough-in inspection is refused.

The number that matters is days of carry, not hours of labor

Every builder can tell you their cycle time — start to certificate of occupancy — to within a few days, and every builder knows what a day is worth, because the construction loan meter runs whether or not the framer showed up. The labor savings from taking the portal round off a person's desk are real but small. The carry savings are the reason to do it.

Here is an illustration with the assumptions stated plainly. Suppose you close 60 homes a year, your average direct construction cost is $340,000, and your construction line runs at 9 percent, interest only.

Where do six days come from? Two from catching plan review corrections the morning they post instead of the following Monday. Three from rescheduling a failed inspection the same afternoon rather than the next morning, which in most jurisdictions is the difference between a next-day slot and a next-week slot. One from catching missing sub-permits before they block a rough-in. Add the reinspection fees you stop paying — call it $95 apiece, and if you avoid twenty of them that is another $1,900 — plus the forty minutes a day your coordinator gets back, which over 250 working days is about 165 hours.

Prove it the boring way. Pull your last forty homes out of Buildertrend and calculate two numbers: days from permit application to permit issued, and days from a failed inspection to a passed reinspection. Run the agent ninety days on half your jurisdictions and compare.

Where this still needs your permit coordinator, and always will

The agent should read and schedule. It should not submit. There is a real difference between booking a framing inspection and uploading a revised plan set to a jurisdiction that charges a resubmittal fee and restarts the review clock, and that difference is worth a person clicking the last button. Keep submittals, fee payments, and anything that creates a legal filing in human hands.

It will also break. A city will redesign its portal on a Saturday in March, add a code texted to a phone, or move plan review to a different product entirely, and the agent will come back with nothing. Your coordinator has to know that "nothing changed on eight lots" and "the agent never got in" look identical unless you build the digest so a failure is loud rather than silent.

And the part no software touches: the plans examiner who will take your call at 7:40 a.m. and tell you what he actually wants to see on sheet A2.1. That relationship is the fastest permitting tool in this trade, and it belongs to a person. The point of handing over the morning round is that your coordinator now has the hour to make that call.

Frequently asked questions

Is it against the terms of use for a city portal to have software log in for me?

Read the terms for each jurisdiction. Some prohibit automated access outright, most say nothing, and a few have started issuing contractor accounts specifically because they are tired of the phone calls. The defensible position is an agent that behaves like your employee: her credentials, a normal pace, reading and scheduling only, and a click log you can produce if anyone asks. If a jurisdiction objects, drop that one and keep the other eight.

What about the counties that still schedule inspections on a phone tree?

Plenty do — you key in the permit number and an inspection code before 3 p.m. and hope. A voice agent works that line the same way your super does: less pleasant to set up than a web portal, more dependable afterward, because a phone tree never gets redesigned on a Saturday.

Do I have to switch off Buildertrend or MarkSystems to do this?

No. This sits beside whatever you run. The agent's output is a note on the lot, a task for the designer, and a message to the super. If your system accepts email or a task import, push it there; otherwise the digest is one page your coordinator reads at eight.

What does it cost to run across eleven lots a day?

Frontier AI got roughly ten times cheaper between 2025 and 2026, so a daily round across nine portals costs less than your job-site water. The real cost is two or three weeks of setup, teaching it where each jurisdiction buries plan review status.

Start Monday with your worst jurisdiction

Do not try to cover all nine portals. Pick the one that costs you the most days — usually the county with the slow plan review and the inspection request line that closes at three — and give the agent exactly two jobs there: read plan review status on your open lots, and read yesterday's inspection results. No writing, no scheduling, no submitting. Run it for two weeks alongside your coordinator doing the same round by hand, and compare their notes every morning. When the notes match ten days straight, let it start booking inspections. Then add the second jurisdiction.

One thing shows up the moment permits and inspections stop slipping: the phone gets busier, not quieter. Trade partners call to confirm the new dates, buyers call the sales trailer asking why framing started early, and the county calls back at 4:50 p.m. when everyone is in the field. CallSphere builds the voice and chat agents that answer those lines around the clock, take the message with the lot number attached, and book the callback on the right person's calendar — so the morning you win back in the permit portals does not get spent on the phone instead.