An electrical permit tracker should answer four questions for every open job: what the jurisdiction currently shows, who owns the next action, when that action is due, and what dispatch may schedule. Keep the permit or application identifier, inspection request, result, customer update, and closeout record connected to the same job.
Do not turn one city's process into a company-wide rule. A qualified person should confirm whether a permit is required, which authority has jurisdiction, what documents are needed, and when field work is ready for inspection. The office workflow begins after those decision boundaries are clear.
Build the tracker around the authority having jurisdiction
Permit portals do not use one national vocabulary. Your tracker needs a jurisdiction field and a link to the current official record, not just a generic “permit pending” note. Store the issuing authority, application or permit number, portal URL, current official status, last checked time, and the person who verified it.
Seattle's current electrical-permit guidance says the contractor or installer is responsible for scheduling each inspection before the permit expires and must have the permit number available. Its inspection page also says results and inspector notes are available through the city portal, and the next available inspection may be several days out. Those details support separate fields for the permit number, request date, confirmed date, result, and next customer update. They are Seattle examples, not universal requirements. Review Seattle's current electrical-permit process and electrical-inspection guidance.
Portland illustrates why a second identifier can matter. Its current IVR guide says the IVR number is distinct from the permit number, asks the caller to record a confirmation number, and posts inspection results back to the system. It also says only permits in “issued” or “under inspection” status can request inspections through that channel. A tracker serving Portland work should preserve those official identifiers and statuses rather than translating them from memory. Read Portland's current inspection-request guide.
Use statuses that create a next action
A useful internal status is specific enough to drive work without pretending to replace the jurisdiction's official record. “Submitted” should point to a submission receipt and the next check date. “Review comment received” should point to the comment and the qualified person responsible for the response. “Inspection requested” should point to the request identifier or confirmation. “Result posted” should point to the actual result and the next approved office action.
Keep the jurisdiction status and your internal workflow status in separate fields. The first reports what the official source shows. The second reports what your team must do. That distinction prevents an internal label such as “ready” from being mistaken for official approval.
If your company uses ServiceTitan, its current project-status documentation includes “Pending Scheduling” for projects waiting on parts or permits and allows custom sub-statuses. That is a platform-specific option, not a requirement to buy or configure a particular product. The same ownership model can live in another field-service platform or a controlled shared tracker. Review ServiceTitan's current project-status documentation.
Run one workflow from sold job to closeout
1. Open the permit record at the job handoff
When a sold job enters operations, create the tracker row before documents scatter. Record the job reference, service address, customer contact, project owner, jurisdiction candidate, and the qualified person who will confirm the permit path. Do not let office staff infer requirements from an old job with a similar description.
2. Assign packet assembly and approval separately
One person can collect the approved scope, signed proposal, forms, drawings, product documents, contractor information, and other jurisdiction-requested material. A qualified person should review anything requiring technical, licensed, design, or code judgment before submission. Record missing items as named tasks with due dates, not as a single “waiting on docs” status.
3. Capture the submission receipt immediately
Save the submitted version, date, application identifier, payment or fee status where appropriate, and official portal link with the job. Assign the next status check. If the jurisdiction sends comments or requests a revision, attach the original message and route it to the authorized reviewer rather than paraphrasing technical content.
4. Put issuance where dispatch can see it
The permit record should expose the verified official status to the person scheduling electricians, apprentices, return trips, and project phases. Define what dispatch may schedule at each approved status. If the record is unclear or contradictory, the next action is an escalation, not a guessed schedule.
5. Treat the inspection request as its own handoff
Once the qualified field owner says the applicable work is ready, the office owner can follow the jurisdiction's approved scheduling process. Capture the inspection type as provided by the qualified owner, request date, requested window, confirmation or request number, site contact, access notes, customer message, and the person responsible for watching the result.
6. Close the result loop
After the jurisdiction posts a result, attach or link the official record. A passed or complete result moves to the company's approved closeout path. A partial result, correction, or unavailable result goes to the qualified owner with the original notes intact. Schedule customer communication and any return visit only after the authorized person defines the next step.
Complete the ownership checklist
Use these checks during the daily open-job review. A checked item means the responsibility is documented and visible in the working system.
Review the board by exception
A short daily review should focus on records that have no owner, no due date, an overdue next action, conflicting statuses, a customer update due, an inspection without a confirmation, or a result without a routed next step. Review by jurisdiction when portal practices or cutoffs differ.
Useful counts include open applications, records missing identifiers, days since the last official check, inspections requested but not confirmed, results waiting for an owner, and closeouts without a stored result. These are workload signals. Do not convert them into promised approval times, revenue claims, or compliance scores.
Where a dedicated assistant fits
Early Bird provides one dedicated, full-time executive assistant with ongoing support. Onboarding maps the full operating scope, including systems, people, approvals, and decision boundaries. The team then stabilizes one priority workflow at a time, such as permit and inspection tracking, without treating the assistant as a one-task hire.
Inside the client's approved process, the assistant can maintain records, assemble routine documents, monitor official portals, record identifiers, schedule authorized inspections, send approved customer updates, and route results. Permit decisions, licensed submissions, technical responses, field-readiness decisions, code interpretation, and safety judgment stay with the qualified people the company names.
See how Early Bird supports electrical contractors, review the field-service software handoff guide, and use the responsibility and escalation framework to define boundaries.
Electrical permit tracking questions
Should every jurisdiction use the same status list?
No. Preserve the official status exactly as the jurisdiction displays it, then use a separate internal next-action status that your team controls.
Can office staff decide when work is ready for inspection?
Not from this workflow. A qualified field or technical owner should make that decision. The office owner can then complete the approved scheduling and documentation steps.
Does the workflow require new software?
No. Use the field-service system or controlled tracker your team can maintain reliably. Clear fields, ownership, and review habits matter more than adding a disconnected tool.