The permitting coordinator is the most leveraged seat in a residential solar company and usually the least defined. Sales has quotas, crews have schedules — and the person standing between a signed contract and an energized system too often has a job description that reads "handle the paperwork." Here's the playbook that turns the seat into a system: the operating rhythm, the internal SLAs, and the handoff contracts that stop jobs from dying in the gaps between teams.
The role, actually defined
The coordinator owns calendar velocity between contract and PTO: every application (city, utility, HOA), every signature, every inspection request, every deficiency response, and the honest status the rest of the company quotes from. Not the design (engineering's), not the install (field's) — the movement. One number captures the mandate: detection latency — how long anything sits in an actionable state before someone acts. A great coordinator's pipeline has a detection latency measured in hours.
The daily rhythm
The job is a loop, not a queue of favors:
- Morning sweep (non-negotiable): every portal, every inbox — city corrections, utility deficiencies, agreement statuses, inspection results. Everything found gets triaged same-day. Silent aging is the enemy; the sweep is the weapon.
- Signature chase: every customer-pending document, touched daily until signed. Same-day signature turnaround is the cheapest schedule improvement in solar.
- Submission block: QA new packages against the per-AHJ checklist, submit, timestamp.
- Aging review: anything past its stage SLA gets an action or an escalation — including the polite, dated status inquiry when a city approaches its statutory line.
- Weekly: log the week's corrections and deficiencies by category, update requirement profiles with anything learned, review permit expirations on the horizon.
Internal SLAs worth enforcing
External clocks (city review, utility processing) get all the attention; internal SLAs are where the recoverable days live. A workable starter set: design package to coordinator within 3 business days of survey; QA-and-submit within 2 days of receiving a complete package; correction responses out within 2 days; customer signatures chased daily, escalated to the sales rep at day 3; inspections requested within 1 day of install completion; utility applications filed at contract, not at inspection (sequence per territory). Publish the SLAs, measure them, and treat misses as process findings rather than personal failings.
Handoff contracts
Jobs die in gaps between teams, so define each handoff as a contract with an acceptance test: Sales → coordination delivers the verified jurisdiction/utility/HOA determination and utility account details (ESI-ID) — not "the address." Survey → design delivers panel photos, framing data, and roof condition — the MPU and structural surprises are survey failures wearing later costumes. Design → coordination delivers a package that passes the AHJ checklist — QA rejects incomplete handoffs back, visibly. Coordination → field delivers permit-in-hand plus approved plans on the truck. Field → coordination delivers the closeout photo set to utility spec same-day. Every rejected handoff logged; patterns fixed upstream.
Scaling the seat
One coordinator with tight process handles a surprising load — until the multiplication wins. Split by geography/jurisdiction cluster first (depth in an AHJ's quirks compounds), by function (permits vs. interconnection) only at real volume. And give the seat instrumentation before headcount: a coordinator whose pipeline self-reports aging, deadlines, and next actions covers double the load of one recomputing a spreadsheet by eye. That's the design center of TexPTO — the morning sweep, the SLA clocks, and the handoff gates as software, so the playbook runs the same on the coordinator's best day and their busiest one.
FAQ
When do we hire the first dedicated coordinator? When permitting tasks consume more than half of someone's job informally — usually around 15–25 concurrent projects — hire before the pain, not after the first expired permit.
What background works? Detail-obsessed process people: paralegals, dispatchers, construction admins. Teach solar; you can't teach caring about a portal sweep.
Who owns the timeline the homeowner hears? The coordinator's data, delivered by whoever owns the relationship — one source of truth, however many voices.
What's the one metric for the seat? Detection latency first, internal-SLA attainment second. Contract-to-PTO follows both.
Sources
- Companion frameworks in this library: permitting KPIs, the AHJ database, cost of delays
Operations guidance — calibrate the SLA numbers to your volume and market mix.