Electrical Data Model — Permits & Assets | FieldCamp

FieldCamp runs an electrical business on one connected set of records that works on day one and bends to how your shop actually operates.

A homeowner or general contractor calls, you quote the work, you schedule and dispatch a crew, you bill, and you get paid — that whole chain is modeled directly as Request → Estimate → Job → Visit(s) → Invoice → Payment.

Most residential service runs on this core alone.

Where electrical work gets specific — the panels and EV chargers you service over time, and the permits and inspections a city drives on its own timeline — FieldCamp adds a small, tightly-scoped set of specialized records on top.

FieldCamp works for any size, from a single-truck residential operator to a multi-location commercial contractor, and everything below can be tailored to how you run.

What the core already gives you

Before anything electrical-specific, the standard records cover roughly four-fifths of the business — and all of residential break-and-fix service.

• Customers holds homeowners, property managers, builders, and general contractors. The customer type marks individual or business, and three separate addresses let a bill go to a GC while work happens at the site.
• Requests capture the inbound service call or quote request, with inspection-scheduled and quote stages already built in.
• Jobs are the work order — one-off, multi-day, or recurring. Recurring jobs cover maintenance-agreement visits.
• Visits handle dispatch, en-route, on-site, photo capture, and the finish-work signature gate.
• Estimates & Invoices carry the quote — including a Good / Better / Best comparison for "repair vs. replace the panel" — plus deposits, purchase-order numbers, and net terms for commercial billing.
• The Price Book holds devices, fixtures, breakers, and hourly labor, with vendor pricing and taxable flags.
• Team Members carry license class as a skill, and service areas carry territory — no custom object needed.

On-site checklists, NEC sign-offs, and field photos use job forms, which are built for structured on-site capture, signature, and photos. That is a separate thing from the inspection record below, which tracks the city's inspection event and its result.

What electrical adds

On top of the core, the electrical setup adds four specialized records.

Each one is a custom object built on the same engine as the core records, with its own fields, its own stages where it needs them, and its own record page assembled from building blocks.

Two of them — Serviced Asset and Permit — anchor the model. Inspection hangs off a permit, and Project is a commercial-only grouping that residential accounts can ignore entirely.

Serviced Asset

The Serviced Asset is the panel, sub-panel, generator, EV charger, transformer, or switchgear you service at a property. It is the textbook equipment pattern: one record per piece of gear, tracked across many jobs, building a service history.

It records the asset name and type, manufacturer, model, serial number, amperage rating, voltage and phase, breaker count, install date, warranty expiry, a note for where it sits on site, and nameplate or panel-directory photos.

Each Serviced Asset belongs to a Customer. A Job or Visit can reference the assets it touched, so every panel and charger carries its own service history.

An optional workflow tracks an asset as active → needs service → decommissioned. Its record page shows a serial-and-warranty card, the service history, a warranty countdown, attached files, and your own field groups.

Permit

The Permit is the city or county authorization for permitted work, and it has a lifecycle of its own — driven by the authority having jurisdiction, not by your job.

A job can be in progress while its permit is still applied-for and waiting on the city, which is exactly why the permit is its own record with its own stages.

It records the permit number, permit type (service upgrade, solar, EV charger, generator, low-voltage), the jurisdiction, application and issued dates, the permit fee, the expiration date, whether it is posted on site, and the scanned permit document.

A Permit is a child of its Job, and can optionally link to the Customer for cross-job lookups.

Its record page shows the status header, field groups, a breadcrumb back to the job, the files, the related table of its inspections, a reminder block, and a timeline.

Reminders keep the process moving: a recurring follow-up runs while a permit sits applied-for and waiting on the city, and a notification fires as the expiration date approaches.

Inspection

The Inspection is the city's inspection event and its result. A permitted job routinely has several — rough-in, service, cover or close-in, final, and re-inspections — and each result gates the next phase of work.

It records the inspection stage, the scheduled date and time (which becomes a calendar event), the inspector's name, the result, correction notes, any re-inspection fee, and the signed-off inspector card or green tag.

An Inspection is a child of its Permit and also references its Job. Its record page shows the status header, field groups, the breadcrumb to the permit, the scheduled event, files, and a timeline.

The result drives the rest: a failed inspection requires correction notes before it can move, and passing the final inspection can require a green-tag photo.

When every inspection on a permit has passed, the permit rolls forward on its own — the same children-roll-up-to-parent pattern the core uses for visits completing a job.

Project

The Project is a commercial and new-construction grouping. It gathers many Jobs across a multi-month build, with phase and progress tracking. Residential accounts ignore it; their Jobs stand alone.

It records the project name, the general contractor, the site address, the contract value, start and target-completion dates, the current phase (rough-in, in-wall, trim-out, energization, closeout), percent complete, and retainage percent.

A Project has many Jobs, and Jobs reference their Project. Permits and inspections roll up to their Job, and Jobs roll up to the Project.

Its record page shows the status header, key numbers for contract value and percent complete, the related table of Jobs, a cost report comparing estimated and actual, a timesheet, the financial summary, files, and a map.

The permit and inspection lifecycle

A permit and its inspections each move through their own stages. The permit follows the city from application to closeout; each inspection passes, fails into a re-inspection, or is cancelled. When the inspections are done, the permit advances.

Each inspection scheduled against the permit runs its own short cycle.

A failed inspection notifies the project lead and creates a follow-up. Once every inspection has passed, the parent permit moves to final-passed without anyone having to update it by hand.

Residential vs. commercial

The same records serve both modes. What changes is which of them you lean on and how billing is shaped.

Permits, Inspections, and Serviced Assets serve both modes. They attach to a Job for residential work, or to a Job under a Project for commercial work, so there is one shared model rather than two.

The crew side flexes the same way. A single-truck operator runs one tech across every Visit; a multi-location contractor assigns Visits across teams and locations using the same Job and Visit records.

Built on the customization engine

Every specialized record above is a custom object built on the same engine you use to tailor anything else in FieldCamp.

None of it is special-cased; the permit lifecycle, the inspection roll-up, and the asset service history are all assembled from the same primitives any account can use.

Add your own objects and fields for the gear and paperwork your shop tracks, define the stages and workflows each record moves through, and arrange every record page from the library of record layouts.

The core flow works on day one; the customization layer makes it match how your business actually runs.

Related records

Coming from ServiceTitan

Most electrical shops on ServiceTitan can bring their structure into FieldCamp directly — customers, the properties under them, the panels and chargers you service, the jobs and appointments, the permits, and the price book all have a home here.

The difference is that in FieldCamp you own and shape the model, rather than fitting your shop to a fixed one.

What you gain. In ServiceTitan the structure is fixed — the objects, their fields, and how they relate are set for you.

In FieldCamp every one of those records is yours to rename, extend, restage, and relayout, so you can match your old setup first and then go past it with custom objects and fields and your own stages and workflows.

One honest difference. ServiceTitan ships a built-in membership billing engine that runs recurring invoice cycles on its own schedule.

FieldCamp models the membership itself as a Service Agreement that schedules the seasonal Job and carries the renewal date and plan price; the recurring billing runs through the standard invoice flow rather than a separate billing engine.

If automatic dunning cycles are central to how you bill, plan that part of the move deliberately.

See also

More in the FieldCamp data model.

Related guides

Hands-on, step-by-step guides from the rest of the FieldCamp documentation.