Every solar company's permit tracker starts the same way: a spreadsheet, built by whoever cared most, and honestly — it works. At ten concurrent jobs in three cities, a good coordinator with a good sheet is unbeatable. The failure isn't the spreadsheet's design; it's arithmetic. Jobs × jurisdictions × stages × deadlines grows multiplicatively, and the sheet's core assumptions — one owner, manual updates, no memory of time — fail on a schedule you can predict. Knowing the failure modes lets you replace the sheet before it costs you, instead of after.
The five failure modes
1. The sheet doesn't know what time it is. A spreadsheet stores states ("submitted"), not durations. Nothing in it distinguishes submitted yesterday from submitted 26 days ago and aging toward the 45-day line — or a permit drifting toward expiration — unless a human recomputes ages by eye, daily, forever. Every silent-aging failure in this library (unread corrections, unsigned utility documents, unscheduled inspections) is the timeless-spreadsheet failure wearing different clothes.
2. It holds statuses, not requirements. The sheet says where a job is; it doesn't know that Dallas wants PE seals, that TNMP approves before installation, or that Houston validates ownership against HCAD. That knowledge lives in the coordinator's head — which is failure mode three.
3. Tribal knowledge doesn't scale or survive. The person who built the sheet is the system. Their vacation is an outage; their resignation is a data loss event. At 30+ AHJs and a half-dozen utilities, no single head holds the requirement matrix — the AHJ database post is the structural answer.
4. Two-clock jobs break single-row thinking. Every job runs a city clock and a utility clock in parallel (and an HOA clock, and an engineering clock). One row with one status column forces a choice about which clock to show — and the hidden clock is where jobs die.
5. No history means no learning. Overwritten cells can't answer the questions that improve the operation: which AHJ's median blew out this quarter, which rejection category is trending, whether the new QA checklist moved first-pass approval. A tracker that can't produce your KPIs can't improve them.
The signals you've hit the wall
You've crossed the breaking point when: status meetings exist mainly to update the sheet; homeowner "where's my project?" calls require research instead of a glance; a permit expires or a correction ages more than a week undiscovered; onboarding a coordinator takes months because the process is oral tradition; or you genuinely cannot say what your median contract-to-PTO is by city. Most companies hit this somewhere between the third city and the fiftieth concurrent job.
What the replacement must actually do
Whether you buy or build, hold the replacement to five requirements the sheet structurally can't meet: stage timestamps with aging alarms (time as a first-class citizen); per-jurisdiction requirement profiles attached to jobs (the AHJ database, operationalized); parallel clocks per job (city, utility, HOA, engineering — visible simultaneously); history that survives (every transition logged, so the KPIs compute themselves); and shared visibility (sales, ops, and the homeowner-facing team reading the same truth). That list is, not coincidentally, the spec TexPTO was built against — because the spreadsheet's five failure modes are the same at every scaling installer, and the fix is structural, not heroic effort by a better coordinator.
FAQ
When exactly does the spreadsheet fail? When the multiplication (jobs × jurisdictions × parallel clocks) exceeds what one attentive human recomputes daily — commonly around the third metro or ~50 concurrent jobs.
Can we just add more tabs and formulas? You can buy months. You can't make a spreadsheet know time, hold requirements, or keep history — the failure modes are architectural.
Build or buy? Build if permitting workflow is your differentiator and you have engineers to spare; buy if your differentiator is installing solar. Hold either to the five requirements.
What should we migrate first? The requirement profiles and the open-job timestamps — knowledge and time. Historical closed jobs can follow.
Sources
- Failure-mode references throughout this library: 45-day rule, permit expiration, interconnection deficiencies, permitting KPIs
Operations guidance from pattern, not prophecy — your breaking point arrives on your own multiplication schedule.