Hiring your first permit coordinator or ops manager: what to set up first

When a solar installation company hires its first permit coordinator or ops manager, it's usually because something broke. A permit sat unsubmitted for two weeks. An inspection got missed. A crew showed up at a house where the interconnection application was still with the utility. The founder was doing all of it between site visits, and jobs started slipping.

When we reviewed 105 US install businesses in October 2026, 37 were advertising for operations, project management, permitting or coordination roles. That's more than a third, and it's the single most common growth signal in the set. It usually means the company has outgrown the founder doing the paperwork, and is about to hand that process to someone whose entire job is keeping it moving.

The mistake isn't the hire. The mistake is making the hire before the process exists anywhere except the founder's head. Here's what to set up first, so your first ops person starts with a system instead of an archaeology project.

The problem you're actually solving

A permit coordinator can only coordinate what they can see. If job status lives in a shared inbox, three spreadsheets and whoever last spoke to the inspector, the new hire spends their first month reverse-engineering the business instead of running it. That month is exactly when the dropped permits happen, because responsibility transferred before visibility did.

This is the same failure mode that pushes install businesses off generic CRMs in the first place: the system can hold a contact but not the actual shape of a solar job, so the real process runs around the tool. If you're deciding what to track jobs in before this hire, do you need a CRM at all is the right first question, and what solar install businesses actually use is the honest survey answer.

Set up one job record first, before anything else

Everything else in this guide assumes this one is done: every job, from signed quote to permission to operate, exists as a single record in one system. Quote, contract, permit documents, inspection dates, interconnection status, crew schedule, all attached to that job.

Without it, the best you can give a new coordinator is a procedure document that says "check the AHJ portal, check the utility portal, check the spreadsheet, ask me." With it, the question "where is this job" has one answer, and it's the same answer for you, the coordinator, sales and the crew in the field. That's what solar installer operations software is for, and it's the difference between hiring someone to run a process and hiring someone to chase one.

If you're currently running this out of spreadsheets and a shared inbox, look at why install businesses replace generic CRMs before you inherit the same problem at higher volume.

Make permit status a field, not a conversation

Permitting in the US isn't one process, it's one per authority having jurisdiction, and the timelines vary enormously. NREL's SolarAPP+ performance review found a median of 7 business days for traditional manual permit review, with 13% taking more than 30 business days. We've written about what permitting sprawl costs a growing install business in detail.

What that means for your first ops hire: they will be managing several different permitting clocks at once, sometimes for jobs a few miles apart. Give them a system where each job carries its own permit status and its own AHJ, so they can see every job's stage without opening a portal or asking anyone. Status should live on the job record, visible in one operations queue, not in a column of a spreadsheet that one person remembers to update.

Put the documents somewhere a new hire can find them

Your coordinator's second week will involve pulling together permit packages: site plans, line diagrams, spec sheets, contracts. If those live in email threads and a folder structure only you understand, every package is a scavenger hunt.

Set up standard document templates and custom fields before they start, so the job's paperwork is generated from the record rather than assembled by hand. The goal is that a complete permit package for any job can be produced by someone who has never touched that job before, on day one. That's also your test for whether the setup is done: could a stranger produce the package? If not, it's not set up yet.

Give the role authority over the pipeline, not just the paperwork

A permit coordinator who can only submit applications is half a hire. The job that actually pays for itself is someone who owns job sequencing: which installs get scheduled once permits land, which jobs are blocked on the utility, what gets escalated.

That means the hire needs:

• Visibility of every job's stage, from sales quoting through to PTO, so promises made upstream don't surprise them downstream
• The ability to reorder crews and update schedules without a chain of phone calls, using the mobile app so the field sees changes without coming back to the office
• Automations for the repetitive parts: notify the crew when a job moves to a "Permit approved" pipeline stage, chase the inspection booking, flag any job that has sat at the same stage too long

The last one matters more than it sounds. A coordinator's scarcest resource is attention. If a job sitting still doesn't raise a flag, stale jobs surface when a customer calls to complain. Automated status alerts turn that from firefighting into a list they work through every morning.

What to hand over in week one

A handover that works usually has four parts, all prepared before the start date:

1. Every live job in the system, with stage, AHJ, permit reference and next action recorded. Not "most jobs", all of them. Half-migrated is where things get lost.
2. The document templates for permits and contracts, so packages are assembled not recreated.
3. A written list of every AHJ and utility you work with, with each portal's link and your account reference on the job, and the logins themselves in a shared password manager, not in one person's browser.
4. The first escalation list: which jobs are behind, which customers are waiting, what has to happen this week.

If you're building this and realizing the current stack can't hold it, that's the signal it was built for the business you had, not the one you're hiring for. In-house systems don't survive this transition, and neither does the spreadsheet-and-inbox combination. The time to fix it is before the first day, not during the first dropped permit.

The first 90 days

Once the basics are in place, the metrics that tell you the hire is working are boring on purpose: how many days from signed contract to permit submission, how many jobs sit at any stage past their expected duration, how many inspections pass first time. Three numbers, reviewed weekly. If the system is set up as described, all three are readable without anyone compiling anything.

The install businesses that get this right describe the outcome the same way: scaling without losing control. The ops manager sees everything, the field trusts the schedule, and the founder stops being the bottleneck on paperwork. That starts not with the job ad, but with what you build in the two weeks before the start date.

If you're planning this hire, request a demo and we'll show you what the setup looks like for a business your size, with your AHJs and your utilities.