Roofing Data Model — How It's Built | FieldCamp

A roofing business is not a simple service call. A roof moves through sales, an insurance claim, a measurement, a material order, a production crew, a punch list, and a warranty — a multi-stage project, not a one-hour repair.

FieldCamp models that directly. Your Customers, Requests, Estimates & Invoices, Jobs, and Visits already carry the customer, the sale, the install schedule, and the billing.

On top of that, a roofing setup adds the records a roof needs and core has no home for: a roofing project, an insurance claim, a roof measurement, a material order, and a warranty.

The result works for any size — a single-truck residential re-roofer or a multi-location commercial outfit bidding campus work — and everything here is yours to tailor.

What the core already gives you

Most of a roofing workflow is already wired into the core records. Keep them as-is and add the roofing layer on top.

• The customer book — a Customer carries a separate property address and billing address, lead source, and account history, so storm leads and repeat clients live in one place.
• The sales front end — a Request captures the lead and the inspection appointment, then converts into an Estimate. Roofing estimates are usually multi-option: the Good / Better / Best shingle-tier proposal is one estimate with selectable options, plus a deposit and an approval step.
• Billing — an Invoice handles deposits, progress payments, payment terms, overdue reminders, and card or online payment.
• The install schedule — a Job is the actual scheduled install, carried out as one or more Visits. A multi-day tear-off and install is one visit per day, each with crew assignment, on-site check-in and check-out, and a signature-gated finish step.
• On-roof data capture — inspection checklists, photo-required punch lists, a safety tie-off sign-off, and a completion sign-off are captured as job forms, not loose fields.
• The price book — shingles, underlayment, and fasteners live in the price book with vendors and cost ladders, and feed every estimate, invoice, and material order.

So the roofing layer is additive. Core handles the customer, the sale, the billing, the schedule, and the forms; the specialized objects handle the project, the claim, the measurement, the material order, and the warranty.

What roofing adds

Each item below is a custom object built on FieldCamp's customization engine — its own fields, its own links to the core records, its own stages where it needs them, and its own record page assembled from building blocks.

Roofing Project — the production spine

The Roofing Project is the record that runs a roof from a signed deal through warranty. It exists because a core Job models a service appointment, while a roof is a sales-to-procurement-to-production project with its own long lifecycle.

It carries the project name, type (residential or commercial), work type (repair, replacement, re-roof, or new construction), roof system (asphalt shingle, metal, tile, TPO, EPDM, mod-bit, or built-up), the service address, contract value and signed date, production start and target-complete dates, permit number and whether a permit is required, project photos and documents, and notes.

It links to the rest of the model: to the Customer it belongs to, to a building (for commercial campuses), to the Insurance Claim, to the Roof Measurement, to the Estimate and Invoice that handle the sale and billing, to the install Job that produces the visits and crews, to its Material Orders and Warranties, and to the team member running as crew lead.

Insurance Claim — a first-class record

For residential storm work, the insurance claim drives the deal.

It is its own record because carrier, claim and policy numbers, adjuster details, and the claim's money — replacement cost, actual cash value, recoverable depreciation, deductible, and supplement total — are too structured to bury on the customer.

It carries the claim number, carrier, policy number, date and cause of loss (hail, wind, hurricane, or other), the adjuster's name, phone, and email, the dollar figures above, a calculated net amount to the contractor, and the claim documents.

It links back to its Roofing Project.

Roof Measurement — the takeoff record

Squares, pitch, facets, and linear feet are reused by the estimate and the material order, so they are a record, not a note.

The Roof Measurement holds the report source (EagleView, QuickMeasure, Hover, or manual entry), the report date, total squares, predominant pitch, facet count, and ridge, hip, valley, eave, and rake linear feet.

It also carries a waste-factor percentage, separate steep-slope and low-slope areas (so residential and commercial both fit), an adjusted-squares figure that applies the waste factor automatically, the report file, and links to the Customer and the building.

Material Order — the supplier order

The order to the supplier is its own lifecycle, separate from the customer's invoice.

The Material Order carries an order number, the supplier or vendor, line items drawn from the price book, the order total, requested delivery date, delivery address, delivery type (ground drop or rooftop load), the confirmation number, and the order file.

Its page adds a vendor-pricing view for the cost ladder and alternate suppliers, a loadout sheet comparing projected, loaded, and actual material, and a shortage alert.

Warranty — coverage with an expiry clock

The Warranty record tracks manufacturer, workmanship, and system coverage. It carries the warranty type, manufacturer, coverage term in years, start and expiry dates, registration number, and the warranty certificate, and links back to its Roofing Project.

Its page uses a compliance block that counts down to the expiry date, so coverage that is about to lapse surfaces on its own.

How the roofing objects link to the core

A Customer owns Roofing Projects and, for commercial accounts, Buildings that group several roof sections. Each Roofing Project pulls in a claim, a measurement, the core sale and billing records, the install Job, its material orders, and its warranties.

The roofing project lifecycle

A roofing project moves through a named production lifecycle — far longer than a service call. The diagram below shows the stages a roof runs through, including the two insurance steps that the residential path requires and the commercial path skips.

A few of these stages carry requirements before a project can move on. Moving past inspection asks for the measurement link.

Marking a project signed asks for the contract value and signed date and shows a confirmation. Moving from punch and quality check to final invoice asks for completion photos and, on residential work, a homeowner signature.

The insurance steps are configurable: the residential path requires the claim to be filed and approved, and a commercial outfit can skip them and hide the claim record entirely.

Along the way, the project keeps itself in sync. Marking it signed spins up the install Job.

The project rolls to in-production when the install starts and to paid when its invoice is paid. Reaching a material-ordered, claim-approved, or paid stage sends a notification to the office, the supplier, or the homeowner.

Residential vs commercial

One model serves both. The differences are a handful of fields and stages that turn on or off per segment — not a separate build.

The Roof Measurement object serves both — fill the steep-slope fields or the low-slope fields as the roof requires. The Insurance Claim is residential-dominant and can be hidden for commercial-only shops; the Building object is commercial-dominant and can stay off for single-home work.

Built on the customization engine

Everything above is assembled from the same engine every FieldCamp account has.

The roofing project, claim, measurement, material order, and warranty are custom objects with their own fields; the production lifecycle and the claim-approval steps are stages and workflows with their own requirements and automations; and each record page is arranged from building blocks like the project board, the loadout sheet, the cost view, and the warranty countdown.

Rename a stage, add a field, or rearrange a page, and the model bends to how your shop actually runs.

Related records

Coming from AccuLynx

Most roofing shops on AccuLynx can bring their structure into FieldCamp directly. The contact, the job file, the estimate, the measurement numbers, the material order, the crew, and the production board all have a home here — and JobNimbus shops will recognize the same shapes.

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 AccuLynx 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. AccuLynx orders aerial measurement reports inside the app and ships insurance-specific estimate templates aimed at the carrier process.

FieldCamp stores the numbers from an aerial report and lets you attach the report file, but it does not order or auto-import the report from the provider, and it does not generate a carrier-format claim estimate.

Enter the figures, attach the file, and hold the claim totals on the Insurance Claim record.

If supplier-catalog ordering or in-app measurement ordering is central to how you run, plan that part of the move deliberately.

See also

More in the FieldCamp data model.