Fixed quote after a free call

Solar permit and interconnection tracking in one place

Between contract and switch-on a job moves through plan sets, permits, inspections and utility interconnection or, in the UK, a DNO notification or application. We build a tracker that creates a checklist per job from the requirements of its authority and utility, alerts coordinators when an application has gone quiet, and sends homeowners plain progress updates at each milestone. A typical build costs $1,000 to $2,500 and takes about four to five weeks.

The problem

Why solar jobs stall between contract and switch-on

Permitting coordinators often keep a spreadsheet per job and log into a different portal for each building department and utility. Requirements vary by jurisdiction: some US communities issue instant permits through NREL's SolarAPP+ for code-compliant residential systems, others need a full plan review, and the utility has its own interconnection application.

In the UK the step is usually a DNO notification under G98 or an application under G99, handled by the installer. Meanwhile the homeowner hears nothing for weeks, worries they have been forgotten and calls the office, or cancels.

What we build

What our solar permit and interconnection tracker includes

Checklist per job

Documents each authority and utility asks for, as recorded by your team: plan set, single-line diagram, data sheets, site photos and homeowner signatures.

Milestone tracker

Design approved, permit submitted, permit issued, inspection booked, interconnection submitted, approval to operate, with dates and owners.

Quiet-application alerts

An alert when any step has had no movement beyond the number of days you set for that authority or utility.

Homeowner updates

A plain-language message at each milestone, so homeowners know where their job stands without calling.

Signature requests

Utility and financing forms sent for signature and chased until returned.

Backlog view

Jobs stuck by authority, utility and step, for the weekly operations meeting.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Contract signed

    The signed job creates a tracker record and checklist.

  2. 02 Automated

    Documents gathered

    Missing items and signatures are requested and chased.

  3. 03 Automated

    Milestones logged

    Coordinators record submissions and approvals; homeowners get updates.

  4. 04 Coordinator review

    Coordinator chases

    Stalled applications are flagged for the coordinator to follow up.

  5. 05 Consultant or designer decides

    Submissions approved

    A qualified designer or electrician approves every plan set and application before submission.

How it behaves

How permit and interconnection tracking behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the homeowner sees

  • A clear update at each milestone
  • Signature requests that are easy to complete on a phone
  • Fewer reasons to call the office

What the team sees

  • One tracker with every open job and its next step
  • Alerts when an application goes quiet
  • A backlog view by authority and utility

What the automation does

  • Creates checklists from your requirements
  • Chases missing documents and signatures
  • Sends milestone updates and logs dates

Edge cases and fallbacks

Authority asks for a correction
The job moves back a step and the designer gets a task.
Utility rules change
Checklist templates are versioned; open jobs keep the version they started with unless the coordinator updates them.
Homeowner unresponsive to a signature request
Two reminders, then a coordinator call task.
Tracker or messaging outage
The backlog view is exported daily so coordinators can keep working.

Architecture

Permit and interconnection tracking at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Signed job From the CRM n8n tracker Checklists, timers Job documents Plans, signatures Stall alerts Days without news Coordinator Submits, chases Homeowner Milestone updates Backlog view By step and AHJ
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 A signed job arrives from the CRM and gets a checklist for its authority and utility.
  2. 2 Documents and signatures are gathered, and timers watch every open application.
  3. 3 Coordinators submit and chase; homeowners get an update at each milestone.
  4. 4 A backlog view shows stuck jobs by step, authority and utility.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Permit, interconnection & homeowner update tracking project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Authorities and utilities you work with, current tracker, documents and milestones.

  2. 02

    Design

    2 to 3 days

    Checklist templates, stall thresholds, update wording and backlog fields.

  3. 03

    Build

    About 2 weeks

    Tracker, checklists, alerts, signature requests, homeowner updates and backlog view.

  4. 04

    Shadow run

    About 1 week

    Live jobs tracked alongside the old spreadsheet; updates go to coordinators first.

  5. 05

    Launch

    1 to 2 days

    Move open jobs across and train coordinators.

  6. 06

    Support

    Ongoing

    New authorities and utilities, checklist and wording changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Your CRM or project board DocuSign eSignature API Google Drive or SharePoint for job documents Twilio SMS and email Slack or Microsoft Teams alerts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Authorities, utilities, checklists and milestones.

    $200 – $400

  • Build

    Tracker, alerts, updates and backlog view.

    $500 – $1,300

  • Integrations

    CRM, documents, e-signature and messaging.

    $150 – $400

  • Testing and shadow run

    Side-by-side with your current spreadsheet.

    $100 – $250

  • Launch and training

    Open-job migration and coordinator training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. We do not log into authority or utility portals on your behalf unless their terms allow it; coordinators submit. Tools and messaging are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: automated permitting

SolarAPP+ issues instant permits for code-compliant residential rooftop PV and PV-plus-storage in participating jurisdictions; the tracker records which route each job uses.

Source: www.nrel.gov

UK: notifying the DNO

MCS sets out how installers notify or apply to the distribution network operator; the tracker holds the date and form for each job.

Source: mcscertified.com

California: interconnection completeness

A complete net billing interconnection application includes the signed Solar Consumer Protection Guide and CSLB disclosure document, so both sit on the checklist.

Source: www.cpuc.ca.gov

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Permit, interconnection & homeowner update tracking questions, answered.

After design and permitting, the installer applies to the utility to connect the system to the grid; the utility reviews it and, after inspection, grants permission to operate. Steps and documents differ by utility, so the tracker uses a checklist for each one.

We prepare the package and track it. Submission stays with your coordinator, and a qualified person approves every plan set. Where a jurisdiction uses SolarAPP+, the tracker records that route.

Yes. The checklist covers G98 notifications and G99 applications as your team handles them, with the date and form stored on the job.

It is the operations tracker part of one, built around your CRM or project board. If you already use a solar project management platform, we connect to it rather than replacing it.

A short message at each milestone, such as permit submitted, inspection booked or approval received, in plain language with no promised dates unless your coordinator adds one.

Days from contract to permit, permit to inspection, interconnection submitted to approval, jobs stalled by authority and utility, and inbound "where is my job" calls.

Free 20-minute call

Want this for your solar & home energy installer?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call