How to Build Electrical Contracting Management Software

The US electrical contracting market generates over $200 billion annually, according to IBISWorld, with labor law and licensing compliance among the top operational risks cited by contractors. A single failed inspection caused by a credential mismatch can delay a project by 1-3 weeks and trigger penalty clauses in commercial contracts.

"The number one cause of preventable project delays in electrical work is a licensing issue discovered at the inspection stage. Every one of those is a software problem at its root -- the field management system should have caught it before the crew showed up." -- Mike Holt, electrical training expert and founder of Mike Holt Enterprises

A scheduler assigns a journeyman electrician to pull a permit and oversee rough-in work on a commercial project. The assignment goes through. The electrician shows up on-site. The inspector arrives, checks credentials, and shuts the job down: only a master electrician can pull permits in that jurisdiction.

The project is now delayed. The GC is on the phone. The client is asking questions. And the root cause is a spreadsheet that didn't know the difference between a journeyman license and a master license.

This is the problem that separates generic field service software from electrical contracting management software built for the trade. Electrical work is regulated at the state and local level. Every assignment, every permit, every inspection phase carries a licensing requirement. A platform that doesn't enforce those requirements at scheduling time doesn't solve the compliance problem. It just moves the discovery of violations from the software to the job site.

This article covers the architecture behind a purpose-built electrical contracting management platform: five core systems, the hardest engineering problem, and what it costs to build.

The five systems electrical contractors actually need

RaftLabs has shipped field service and project management platforms with complex scheduling and compliance constraints. According to the National Electrical Contractors Association, 60% of electrical contractors still manage license tracking on spreadsheets or paper, creating an audit trail that fails at the first regulatory inspection.

1. Estimating and bid management

Electrical estimates start with a takeoff: reading blueprints or plans to identify and count every fixture, outlet, panel, conduit run, and device that needs to be installed. On a commercial project, that list runs to hundreds of line items.

The estimating module needs to support:

• Line-item takeoff entry by material type and quantity

• Labor hour estimation per line item based on work type and surface (exposed conduit vs. in-wall runs)

• Material unit cost lookup with markup applied per line item

• Overhead and profit margin calculation at the estimate level

• Bid document generation in a format the client can approve

The margin problem in electrical estimating is material cost volatility. Copper prices move. A takeoff done in January may underprice a job that starts in March. Your cost database needs to be updatable at the item level, and estimates need to carry a snapshot of the pricing used at time of bid, not a live pointer to current costs.

2. Project management with phase tracking

Commercial and residential electrical projects run in phases. A new construction job typically runs through rough-in (before walls are closed), trim-out (after walls are finished), and final (devices, fixtures, energization). Each phase has a distinct scope of work, its own inspection requirement, and its own billing milestone.

The project management module tracks:

• Project phases with task assignments and scheduled dates

• Technician assignments per phase (subject to license validation, covered below)

• Phase status (not started, in progress, complete, inspected, approved)

• Dependencies between phases (trim cannot start before rough-in inspection passes)

• Daily progress notes and photo documentation per phase

The scheduler needs to see both project work and service/repair calls in a single view. Electrical contractors run both. A technician finishing a project phase on Thursday morning may have a service call at a different job site Thursday afternoon. The calendar view needs to reflect both.

3. License and certification tracking: the rules engine

This is the highest-value compliance feature in the platform, and the hardest to build correctly.

Every electrician holds one or more license types. The most common:

• Master electrician license: required to pull permits, oversee certain work, and supervise journeymen. Issued by the state. Has an expiration date.

• Journeyman electrician license: required for most installation and wiring work. Also state-issued with an expiration date.

• Apprentice status: restricted work scope, must work under the supervision of a licensed journeyman or master.

Work types carry their own requirements. Permit-pulling requires a master license in most jurisdictions. Some commercial work requires a minimum ratio of journeymen to apprentices on-site (for example, no more than one apprentice per journeyman). Certain specialty work, including service entrance, metering, and high-voltage, may require specific certifications beyond the base license.

The rules engine has three components:

License registry: one record per technician per license. Fields: license type, license number, issuing state, issue date, expiration date, status (active, expired, suspended).

Work type requirements table: configurable per jurisdiction. Each work type carries: master required (yes/no), journeyman required (yes/no), permit-pulling authority required (yes/no), minimum journeyman-to-apprentice ratio if applicable.

Scheduling validator: runs every time a scheduler attempts to assign a technician to a task. It checks the technician's active licenses against the work type's requirements. If the assignment fails any check, it blocks and returns a specific message: which requirement failed, what license the technician holds, and what license the task requires.

Alerts also run on expiring licenses. A master license expiring within 30 days triggers a notification to the license holder and the operations manager before the expiration creates a compliance gap.

4. Permit and inspection tracking

Electrical work requires permits. Permits require inspections. Inspections must pass before work proceeds to the next phase. This sequence is not optional. It's enforced by the authority having jurisdiction (AHJ).

The permit module tracks:

• Permit type (electrical, low-voltage, specialty)

• Permit number and issuing AHJ

• Required inspections by project phase

• Inspection scheduled date, actual date, result (passed/failed/correction required)

• Inspector notes on failed inspections

• Permit expiration date

The workflow integration matters. When a phase is marked complete, the system checks whether the associated inspection is scheduled. If not, it surfaces an alert. A phase cannot be signed off as approved until the required inspection passes. Failed inspections log the correction notes and re-open the phase for remediation before re-inspection.

Permit expiration is also a real operational risk on long projects. A permit issued in January on a six-month commercial project can expire before work is complete if not renewed. The system tracks expiration dates and alerts the PM when renewal is needed.

5. Material procurement and job cost allocation

Every project generates a materials list at the estimating stage. That list needs to follow the project through procurement and into the job cost ledger.

The workflow:

1. Estimating produces the materials list per project and per phase
2. PM or project coordinator generates purchase orders from the materials list
3. POs go to vendors (tracked in the vendor registry with pricing history)
4. When materials are received, the receipt is logged against the PO
5. When the vendor invoice arrives, it posts against the PO and allocates the cost to the project
6. Job cost reports compare estimated vs. actual material cost per project, per phase, and per line item

This level of job-cost allocation is what makes profitability analysis meaningful. Without it, you know the project revenue. You don't know the project margin.

Progress billing and change orders

Electrical projects bill by milestone, not by completion. A rough-in complete on a 12-week commercial job warrants a progress invoice. Waiting until final creates cash flow problems and collection risk.

The billing module needs to support:

• Milestone-based billing schedules (rough-in 30%, trim 40%, final 30% is a common structure)

• Automatic invoice generation when a phase is approved

• Change order management with scope description, cost impact, and client e-signature before work proceeds

• Time tracking for billable hours per phase and per technician (for T&M work)

Change orders are a specific discipline. When a client adds scope (an additional panel, an extra circuit run, a fixture upgrade), that scope needs a formal change order approved before the crew touches the work. A platform that lets crews do additional work without a signed change order creates billing disputes at project close.

Service and repair call workflow

Most electrical contractors run two types of work: projects and service/repair calls. The service workflow is different. It's dispatch-based, same-day, and doesn't follow a multi-phase project structure.

The service module needs:

• Inbound call or work order intake with customer history lookup

• Same-day or next-day dispatch to an available technician

• On-site time tracking and parts used capture

• Invoice generation at job completion

• Customer signature on mobile for approval

The same technicians work both project phases and service calls. The scheduling view needs to show both in a single calendar so dispatchers don't double-book a technician who's assigned to a project phase that day.

Build costs and timeline

MVP: $130,000-$220,000, 14-18 weeks

Includes: estimating and bid management, project management with phase tracking, license and certification tracking with the scheduling rules engine, permit and inspection tracking, progress billing, change order workflow, basic time tracking, and a web-based dispatcher interface.

Team: 2 senior backend engineers, 1 frontend engineer, 1 designer, 1 QA.

Full platform: $260,000-$420,000, 24-32 weeks

Adds: native mobile field app for iOS and Android (clock-in/out, photo uploads, job notes, materials capture), material procurement with vendor PO integration, payroll integration with certified payroll reporting for prevailing wage jobs, and reporting dashboards for job costing and technician utilization.

Infrastructure post-launch: $1,500-$4,000/month for a platform serving 50-200 technicians.

Build versus buy

Buy when:

• You have fewer than 50 technicians

• Your work is primarily residential service calls

• You don't need multi-state license compliance rules

ServiceTitan ($398+/month) is the dominant platform in electrical, HVAC, and plumbing. It handles dispatching, invoicing, and project work. Jobber ($69-$249/month) covers lighter field service operations without the project management depth. Volt ($150-$350/month) is built specifically for electrical contractors with licensing and permit features.

Build when:

• You run 50+ technicians across mixed project and service work

• You need license compliance rules configurable per state and work type

• You're building a white-label platform for other electrical contracting companies

• Existing platforms don't support your apprentice-to-journeyman ratio rules or your specialty certification requirements

The economics of build versus buy shift when the platform becomes a product you sell rather than software you use.

The technology stack

Backend: Node.js or Go for the API layer. PostgreSQL for the primary data store (projects, licenses, permits, time records). Redis for scheduling conflict checks and license expiration alerts. Background job queue (Bull or Sidekiq) for permit expiration alerts and invoice generation.

Frontend: React with TypeScript for the web dispatcher interface. React Native for the field mobile app if building cross-platform. Swift/Kotlin if native performance is required for the field crew experience.

Storage: S3 or compatible object storage for permit documents, inspection photos, and signed change orders.

Integrations: QuickBooks or Sage for accounting. ADP or Gusto for payroll if adding certified payroll reporting.

RaftLabs has shipped field service and project management platforms with complex scheduling and compliance constraints. See our SaaS platform engineering service or talk to us about your architecture.