FieldCamp

Garage Door Data Model — Doors & PM | FieldCamp

How a garage door install and repair business is modeled in FieldCamp — door and opener assets, components, preventive-maintenance agreements, and the core flow.

A garage door business runs almost entirely on the records FieldCamp gives you the moment you sign up.

The same chain a repair shop already lives by — a customer calls, you quote the work, you schedule and dispatch a tech, you bill, you get paid — is modeled directly as Request → Estimate → Job → Visit → Invoice → Payment.

What makes this trade different is one thing: the physical door and opener installed at a customer's address, tracked over its life.

That installed door is the heart of the business — every repair, tune-up, and warranty claim is against a specific door — so FieldCamp adds a small asset layer on top of the core flow to track it.

FieldCamp works for any size garage door operation, from a single-truck repair tech to a multi-location commercial installer, residential or commercial — and everything below can be tailored to how your shop actually runs.

What the core already gives you

Roughly eighty-five percent of a garage door workflow is the standard field service flow, handled by core records with no setup.

  • A Request captures the inbound "my door won't open" call, schedules an inspection visit, and converts in one click to an estimate or job.
  • A spring replacement or cable repair is a flat-rate Job with line items drawn from the price book.
  • A new-door quote is a multi-option Estimate — the Good / Better / Best door tiers a tech presents at the door are a single estimate with selectable options.
  • Deposits, fixed-price billing, payment terms, and overdue tracking are the standard money model on estimates and invoices.
  • Scheduling, dispatch, crew assignment, GPS, and signature-gated completion all live on the Visit, staffed by team members.
  • On-site measurements and the preventive-maintenance safety checklist are captured as job forms attached to the visit, with photo and signature capture.
  • Service territories are handled by the built-in service areas feature.

Customers with separate property, billing, and company addresses, preferred techs, and lead source are all native to the Customer record, so a homeowner and a property-management company both fit without changes.

What Garage Door adds

On top of the core flow, the garage door setup adds three specialized records, each a custom object built on the same engine as the core records.

They give the business the one thing core does not carry on its own: a first-class record of each installed door, the parts on it, and the maintenance contracts that cover it.

How the specialized records connect

A Door Asset belongs to the customer it lives at and is made up of one or more Door Components. Jobs and visits link to the door they service, building its history.

A Maintenance Agreement belongs to a customer and covers many doors.

Door Asset — the installed door and opener

The Door Asset is the primary specialized record: the physical door and opener at a customer's address, tracked across every job for its whole life.

It is a standalone custom object that belongs to a customer, so the full fleet of doors stays searchable while each one is still owned by the address it sits at.

FieldWhat it holds
Door nameA label for the door, such as "Bay 3 overhead" or "Main garage".
Service typeResidential or commercial.
Door typeSectional, rolling steel, one-piece, carriage, high-cycle, or dock leveler.
ManufacturerThe door maker.
Model numberThe door model.
Serial numberThe nameplate serial, entered by hand.
Opener make and modelThe opener installed with the door.
Width and heightThe opening size in inches.
Spring typeTorsion or extension.
Install dateWhen the door was installed.
Warranty expiresThe warranty end date, which drives a countdown on the record.
Location addressThe building and bay, for multi-building commercial sites.
PhotosNameplate and install photos.

The Door Asset links to its customer, holds many Door Components, optionally belongs to a Maintenance Agreement, and links to the jobs performed on it so service history rolls up automatically.

Its record page is assembled from building blocks: a header, a specs panel, an asset card showing serial and warranty, a service-history list, a warranty-expiry countdown, a photo gallery, a table of linked jobs and components, and a timeline.

A Door Asset moves through its own stages as it ages.

A door starts Active, can move to Needs Service or Under Warranty, and ends at Decommissioned when it is removed. When a door enters Needs Service, an automation can notify dispatch.

Door Component — the springs, cables, and rollers on a door

A Door Component is a serviced part that belongs to a specific door — the springs, cables, rollers, hinges, remotes, keypads, photo-eyes, and sections.

It is a child record of the Door Asset, so each part's own warranty and replacement date is tracked against the door it sits on. Springs are the single most common garage door replacement, and this is where that history lives.

FieldWhat it holds
Component typeTorsion spring, extension spring, cable, roller, hinge, remote, keypad, photo-eye, or section.
Part numberThe manufacturer part number.
Cycle ratingThe rated life of the part, such as 10,000 or 25,000 cycles.
Installed onWhen the part was installed.
Warranty expiresThe part's warranty end date.
Price book linkThe catalog item the part bills as.

The stock side of parts — truck and warehouse levels, reorder points, and vendor pricing — is already handled by the core price book and inventory. The Door Component only records which part is on which door; it does not rebuild inventory.

Maintenance Agreement — the commercial PM contract

A Maintenance Agreement is the recurring preventive-maintenance contract that commercial garage door shops run on. It is a standalone custom object that belongs to a customer and links to the doors it covers.

FieldWhat it holds
Agreement nameA label for the contract.
Coverage levelBasic, full, or parts-included.
Visit frequencyQuarterly, semi-annual, or annual.
Start and end dateThe contract term.
Annual valueThe yearly contract value.
Billing cadenceMonthly, per-visit, or annual.
Covered doorsThe doors the agreement covers.
Contract documentThe signed contract file.

A Maintenance Agreement moves through a renewal lifecycle.

When an agreement enters Up for renewal, an automation can send a renewal notice, and a separate rule can notify the team when a maintenance visit is due.

Generating the next recurring maintenance visit on a set cadence is handled by core recurring jobs — which support quarterly, semi-annual, and annual schedules — rather than by the agreement record itself.

Model each covered door's tune-up as a recurring job, and the agreement record carries the contract terms and coverage.

Measurements and inspections as job forms

Two field forms attach to the visit rather than living as fields on a record:

  • An install measurement form captures opening width and height, headroom, backroom, sideroom, door type, spring type, wind load for commercial doors, photos, and a customer sign-off.
  • A preventive-maintenance inspection checklist captures door balance, spring cycle wear, cable fray, roller and hinge wear, the opener force and reverse test, photo-eye alignment, and lubrication.

The install and repair lifecycle

A garage door job — whether a same-day spring repair or a multi-day commercial install — moves through the standard Job stages, with the door it services linked along the way.

When a job is completed, an automation appends it to the linked Door Asset's service history and stamps the warranty fields, so the door's record stays current without anyone re-entering it.

A repair links the door being fixed; an install creates and links a new door.

Residential vs commercial

One Door Asset and one Maintenance Agreement serve both residential and commercial work. The difference is which fields get filled and how many doors link to one agreement, not a forked model — handled by the residential-or-commercial marker and configurable completion requirements.

Residential

A homeowner usually has one or two doors at a single address. Jobs are flat-rate repairs or a single-door install, billed as a deposit plus a flat rate on one invoice. Maintenance agreements are rare — an optional annual tune-up. Finish Work is gated by a signature.

Commercial

A business has many doors and dock levelers across one or more buildings, each tracked individually. Work is an install project plus a recurring maintenance agreement per building, the core revenue line. Billing carries purchase-order numbers, and Finish Work can require a photo as well as a signature.

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

Built on the customization engine

Every specialized record above is built from the same parts you have access to yourself: the Door Asset, Door Component, and Maintenance Agreement are custom objects with typed fields and relationships, their lifecycles are stages and workflows you can rename and reorder, and each record page is arranged from record layouts.

Nothing here is locked — you can add a field, add a stage, or shape the door record to match your trade.

Coming from ServiceTitan

Most garage door shops on ServiceTitan can bring their structure into FieldCamp directly — customers, the locations under them, the doors and openers at each location, the jobs and appointments, the service agreements, 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.

In ServiceTitanIn FieldCampNotes
CustomerCustomersThe party responsible for billing. FieldCamp keeps billing, service, and property addresses on one record.
LocationA Door Asset's location address, or a Property as a custom object under the customerServiceTitan keeps equipment on the location; FieldCamp keeps the location address on the door and models a separate Property record when a customer has several buildings.
Equipment / Unit (the door and opener)Equipment — the Door AssetThe installed door and opener, tracked as an asset with full service history. Springs, cables, and rollers are child Door Components on it.
JobJobsThe work order — a same-day spring repair, a multi-day install, or a recurring tune-up.
AppointmentVisitsEach scheduled trip on a job, with dispatch, en-route, on-site, and sign-off.
Project (grouping jobs)A custom Project object that groups related Jobs at one siteBuilt on the same engine as custom objects.
Estimate / InvoiceEstimates & InvoicesGood / Better / Best door quotes, deposits, and the payments that follow.
PaymentRecorded on the InvoicePartial and full payments, with overdue tracking.
Service Agreement / MembershipService AgreementsThe preventive-maintenance contract that covers the doors and schedules the next tune-up Job.
TechnicianTeam MembersCarry skills and territory as service areas.
Business UnitA team or service areaUsed to assign and report on work by group.
Price Book (Services / Materials / Equipment)Price BookDoors, openers, springs, cables, and labor, with vendor pricing and taxable flags.
Dynamic FormsJob FormsInstall measurement and PM inspection forms that live on the visit for structured on-site capture.
Tags / Custom FieldsCustom fieldsAdd a select or multi-select field to label and filter records.

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 agreement itself as a Service Agreement and generates each covered door's tune-up through core recurring jobs; 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.

On this page