--- title: "Commercial HVAC Service Lifecycle — One Connected Record | FieldCamp" url: "https://fieldcamp.ai/hvac-software/commercial/lifecycle/" date: "2026-07-10T00:00:00.000Z" modified: "2026-07-19T00:00:00.000Z" type: "WebPage" resource: "https://fieldcamp.ai/hvac-software/commercial/lifecycle/" timestamp: "2026-07-27T10:33:32.718Z" author: name: "FieldCamp Team" word_count: 4546 reading_time: "23 min read" summary: "HVAC software · Commercial · Lifecycle The commercial HVAC service lifecycle, on one connected record — first request to renewal. Client → sites → equ…" description: "The commercial HVAC service lifecycle on one connected record: client → sites → equipment → agreements → projects, from first request to renewal. How a commercial HVAC operation should be structured in software." language: "en" --- HVAC software · Commercial · Lifecycle # The commercial HVAC service lifecycle, on one connected record — _first request to renewal._ Client → sites → equipment → agreements → projects. This page walks the record a commercial HVAC operation should run on, stage by stage — what each layer holds, why residential-first tools lose it, and how FieldCamp keeps break-fix calls, PM contracts, and capital projects on the same client and the same site. [Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)We'll build your hierarchy live on the call. Clients›Beacon Property Group Commercial HVAC templateActive Record mapone client · 0 duplicate customers ClientRoot Beacon Property Group Property manager · Toronto Contacts 3 by role Chief eng · facilities · AP Sites 3 buildings Access notes on each Equipment Chiller-1 · Trane 150 tons · +11 units AgreementsActive Gold PM Quarterly · renews Mar '27 ProjectsIn progress RTU Fleet Retrofit 5 phases · 45% ClientRoot Beacon Property Group Property manager · Toronto Contacts 3 by role Chief eng · facilities · AP Sites 3 buildings Access notes on each Equipment Chiller-1 · Trane 150 tons · +11 units AgreementsActive Gold PM Quarterly · renews Mar '27 ProjectsIn progress RTU Fleet Retrofit 5 phases · 45% One structured record: every request, visit, agreement, and invoice attaches to this spine — the full context AI needs to run the whole lifecycle. One connected record · first request to renewal0 duplicate customers Six layers, one record — the structure everything else on this page hangs from. Client→Contacts→Sites→Equipment→Agreements→Projects 01 What it is ## What is the commercial HVAC service lifecycle? The commercial HVAC service lifecycle runs on one connected record: a client with multiple sites, each site with its own equipment, service agreements that auto-schedule preventive maintenance on that equipment, and projects for retrofit and replacement work — from first request to renewal. Every stage of the relationship — the tenant request, the estimate, the work order, the visit, the invoice, the renewal — attaches to that record, so the account's history accumulates in one place instead of scattering across jobs, spreadsheets, and separate tools. The word doing the work is lifecycle. In residential service the unit of work is a job at an address: it opens, it closes, it's done. In commercial and mechanical HVAC the unit of work is a relationship with a client — usually a property management company — that spans years, buildings, equipment fleets, maintenance contracts, and capital projects. Software structured around one-off jobs keeps the jobs and loses the relationship. Software structured around the client record keeps both. This page is the architecture reference underneath our [commercial HVAC software](https://fieldcamp.ai/hvac-software/commercial/): it walks the record layer by layer — client, contacts, sites, equipment, agreements, projects — then follows the chain of work that moves through it. Each layer has its own deep-dive page; this one explains how they connect, because the connection is the part most software gets wrong. 02 The record, stage by stage ## Client → sites → equipment → contracts → projects, _all on one record._ That sentence is the whole architecture. Below is how it looks in FieldCamp, using Beacon Property Group as the working example: a property management client with three buildings, an equipment fleet, a live PM agreement, and a retrofit in flight, on one record. Clients›Beacon Property Group Commercial HVAC templateActive Beacon Property Group Property management company · 3 sites Active SalesWorkFilesContactsSitesEquipmentAgreementsProjects Beacon Tower Downtown12 units · 2 mechanical roomsActive Roof via freight elevatorChiller-1 · TraneAHU-3 · Daikin+10 Albert Street Plaza8 units · rooftop packageActive Loading dock behind Albert StRTU-1 · Carrier+7 Harbor Point Offices7 units · chiller plantDue soon Mechanical room · level B2RTU-2 · Lennox+6 Contacts · by roleone group DWDana WhitfieldChief engineer LOLuis OrtegaFacilities director APAsha PatelAccounts payable AgreementActive Gold coverage · quarterly PM CoversChillers + RTUs · all 3 sites BillingMonthly · 4% escalation RenewsMar 2027 · auto-watched ✓ ProjectIn progress RTU Fleet Retrofit Beacon Tower Downtown · billed by phase Phase 3/5 · 45% Contract$248K · 10% retainage Every tab answers while the client is on the phoneone record Stage 1 · The client ### One company, one record — not forty In commercial HVAC your customer isn't a house — it's a property management company with a portfolio of buildings. FieldCamp makes that company one client record, the root everything else hangs from. Its sales tab holds every new request from the portfolio — tenant requests included — plus every estimate and invoice for the account in one place. Its work tab holds every work order across every building: recurring schedules, one-off calls, multi-day jobs. Files keep the equipment diagrams and contracts; activity keeps team to-dos, with Google Calendar and Outlook synced for in-person client meetings. The client record doubles as the account layer of your [HVAC CRM](https://fieldcamp.ai/hvac-software/crm/) — the relationship, not just an address-book entry. Residential-first tools are built on the opposite assumption: one customer equals one address, maybe two or three with billing. A forty-building client physically doesn't fit, which is where the fake-customer workaround comes from — more on what that breaks below. Client record · tabsActive Beacon Property Group Every tab, one client — nothing lives outside the record. SalesWorkFilesActivityContactsSitesEquipmentAgreementsProjects Stage 2 · Contacts ### The chief engineer isn't the one who pays One property group means several people, each owning a different part of the lifecycle: the chief engineer who meets your tech at the mechanical room, the facilities director who approves the estimate, and accounts payable, who never sees a roof but receives every invoice. FieldCamp stores site contacts by role under the one client group, so the estimate routes to the approver and the invoice to AP without anyone maintaining a cheat sheet. Residential tools give you a name and a phone number per customer. When the customer is an organization, that means the role knowledge — who approves, who pays, who opens doors — lives in a dispatcher's head, and leaves with them. Contacts · one client, three roles DWDana Whitfieldmeets techs on siteChief engineer LOLuis Ortegaapproves estimatesFacilities director APAsha Patelreceives invoicesAccounts payable Stage 3 · Sites ### Buildings and mechanical rooms, with access notes Each site is its own child record under the client — a building, a mechanical room, another building across town — with its own equipment, its own contact, its own history. And each site stores access notes where they belong: roof access via the freight elevator, the loading dock behind Albert Street, which level the mechanical room is on. Every work order at that site carries them automatically, so the tech isn't calling the office from a locked parking lot. When the address _is_ the customer — the residential model — sites don't exist as records at all. Access knowledge ends up in old job notes and senior techs' memories, and it evaporates with turnover. Sites · under one client Beacon Tower Downtown Roof via freight elevator Albert Street Plaza Loading dock behind Albert St Harbor Point Offices Mechanical room · level B2 Stage 4 · Equipment ### Every unit, an asset record the system points at Under each site sits its equipment — every unit the property group owns and where each one physically lives. Each unit is a structured asset record: nameplate data, warranty dates, and a unit-level service history that every visit rolls up to. That structure is what turns “when did we last touch that chiller?” into a one-click answer instead of a dig through closed jobs. In job-centric tools, equipment is a line in a job note — so the history follows the job, not the machine, and the machine's story fragments across every visit that ever touched it. The full treatment of nameplate fields, parts-vs-labor warranty, and unit-level history lives on our [HVAC asset management software](https://fieldcamp.ai/hvac-software/commercial/asset-management/) page. Equipment · Beacon Tower Downtown Chiller 1 · Trane RTAC-150Chiller plant · level B2Good RTU-3 · Carrier 48TCRoof · north bankDue soon RTU-7 · Lennox LGHRoof · south bankOverdue Stage 5 · Agreements ### Contracts that watch their own calendar Service agreements signed with the property group live on the same record, as structured fields: PM frequency, coverage tier, start and end dates, billing cadence. Because the agreement scopes real sites and real equipment records — quarterly PM on the chillers, filters on every RTU — preventive maintenance auto-schedules against the exact units it covers, and renewal is a date the system watches rather than a spreadsheet column someone has to remember over the holidays. How PM programs, tiers, and renewal automation run across a multi-site portfolio is its own page: [commercial HVAC preventive maintenance software](https://fieldcamp.ai/hvac-software/commercial/preventive-maintenance/). Agreement · Beacon Property GroupActive Gold coverage tier PM frequencyQuarterly ScopeChillers + RTUs · 3 sites TermApr 2026 → Mar 2027 Billing cadenceMonthly Auto-scheduled: next quarterly PM visits created on the covered units. Stage 6 · Projects ### Retrofits with phases and progress billing A six-unit rooftop replacement is not a service ticket — it's a project: phased, scheduled, billed in stages. Per site, the record holds projects for retrofit and replacement work, each with contract sum, budget, retainage percentage, and percent complete. In an RTU fleet retrofit, the project runs five phases — estimate & approval, procurement, site prep & rigging, installation & tie-ins, commissioning & handoff — each phase with its own work orders and its own schedule, and the estimate broken into phases so you invoice as work completes instead of all at the end. Cram that into one job and you lose the phases, the budget, and the staged billing. Push it into a separate project app and it loses the client, the site, and the equipment history. The full story is on our [HVAC project management software](https://fieldcamp.ai/hvac-software/commercial/project-management/) page. Project · RTU Fleet RetrofitIn progress Retainage 10% · billed by phase45% complete ✓Estimate & approval ✓Procurement 3Site prep & riggingown work orders · own schedule 4Installation & tie-ins 5Commissioning & handoff Break-fix calls. PM contracts. Capital projects. _Same client, same site, same record._ No separate project app. No duplicate customers. One data model, residential to large-scale commercial. 03 The chain in motion ## Request → estimate → work order → visit → invoice — _attached to the same spine._ The hierarchy is the anatomy; this is the circulation. Work enters the lifecycle as a request and moves through the record hop by hop — and because every hop references the same client, site, and equipment, nothing has to be re-keyed and nothing gets orphaned. Beacon Property Group›Work in motion request → renewal Work chainsame client · same site · same record Request tenant intake, on the client same client Estimate good-better-best, per site site + units Work order one-off · recurring · multi-day access notes Visit scheduled & dispatched the AP contact Invoice routed to accounts payable the full history Renewal the loop restarts Requesttenant intake, on the client carries same client Estimategood-better-best, per site carries site + units Work orderone-off · recurring · multi-day carries access notes Visitscheduled & dispatched carries the AP contact Invoicerouted to accounts payable carries the full history Renewalthe loop restarts Renewal reopens the loop on the same record — the year of visits, units, and invoices already there. Nothing re-keyed, nothing orphaned: every hop references the same client, site, and unit — so history accumulates instead of scattering. Request → renewal · nothing re-keyed0 orphaned records Concretely: a tenant reports a no-cool floor, and the request lands on the client's sales tab — intake, not a sticky note. It becomes an [estimate](https://fieldcamp.ai/hvac-software/estimating/) built against the site and the exact units on file, good-better-best if the fix competes with a replacement. Approval converts it to a work order — one-off, recurring, or multi-day — and the visit gets scheduled and [dispatched](https://fieldcamp.ai/hvac-software/dispatch/) to a tech who arrives carrying the access notes and the unit's history. The invoice routes to accounts payable, the right contact on the record, and the closed visit rolls up to the equipment it touched. Then the loop closes where it started. The agreement's end date comes up, and the renewal conversation opens with the whole year on the record — every visit, every unit, every invoice — so it starts from evidence instead of memory. That's the payoff of the connected record in one sentence: when the property group calls, there's no “let me get back to you” — you open the client profile and pinpoint the agreement, the unit, or the invoice in one tab. ### Which software components run each stage Every hop in the chain is run by a module — and in FieldCamp each module reads and writes the same record, which is what keeps the chain connected. The deep capability detail lives on each module's own page; here's the map of what powers what. Intake AI receptionist A tenant's no-cool call gets answered, logged, and landed on the client's sales tab as a request — the [HVAC AI receptionist](https://fieldcamp.ai/hvac-software/ai-receptionist/) picks up even when the office can't. The visit Scheduling, dispatch & work orders Approved work becomes a work order — one-off, recurring, or multi-day — and [HVAC scheduling](https://fieldcamp.ai/hvac-software/scheduling/) plus [AI dispatch](https://fieldcamp.ai/hvac-software/dispatch/) put the right tech on the right roof with the access notes attached. The money Estimating & invoicing [Good-better-best estimates](https://fieldcamp.ai/hvac-software/estimating/) broken into phases, and [invoices](https://fieldcamp.ai/hvac-software/invoicing/) that follow the agreement's billing cadence or bill phase by phase as work completes — synced to [QuickBooks](https://fieldcamp.ai/hvac-software/quickbooks/). The contract Maintenance agreements The [agreement's frequency and scope](https://fieldcamp.ai/hvac-software/commercial/preventive-maintenance/) auto-generate PM work orders on the covered sites and units, and AI Dispatcher fills the calendar before SLA deadlines pass. Capital work Projects Retrofit and replacement work runs as [phased projects](https://fieldcamp.ai/hvac-software/commercial/project-management/) — each phase with its own work orders and schedule, different team members per phase, invoiced by phase. 04 The workaround ## Forty fake customers — _and everything that breaks._ You've seen the workaround, or you're running it: “Beacon Group — Property 1”, “Beacon Group — Building 3”… a fake customer per building, forcing a commercial account into a one-address tool. Tools like Jobber and Housecall Pro are built on the one-customer-one-address assumption — fine at residential work, but a portfolio has to be shredded into duplicates to fit. And most platforms that do have a commercial hierarchy aren't customizable to how your shop actually operates. Here's what the workaround costs, operation by operation. | The operation | Forty fake customers | One connected record | | ---------------------- | ------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | | Client-level reporting | Revenue for one company scattered across dozens of “customers” — no single rollup to the account | One client record rolls up every site, request, work order, and invoice | | Equipment history | History buried in whichever duplicate got the job — the unit has no story of its own | Every visit rolls up to the unit it touched, on the site it lives at | | Data entry | Contacts and billing details re-keyed into every duplicate, then updated in none of them | Entered once on the client — sites, contacts, and billing inherit | | Agreements & renewals | One PM contract split across fake customers; renewal dates live in a side spreadsheet | The agreement scopes sites and units; renewal is a date the system watches | | Capital projects | A three-week retrofit crammed into one job — or exiled to a separate project app | Projects with phases, work orders per phase, and progress billing on the same client and site | | AI operation | AI can’t infer that forty “customers” are one client — automation has no ground truth | Full context in structured data — the precondition for AI to run the operation | The pattern across every row is the same: the workaround doesn't just make reports ugly — it breaks the data itself: reporting fragments, equipment history orphans, and the same information gets entered twice and trusted never. Humans paper over it with memory and cross-referencing. The next section is about the operator that can't. 05 The AI argument ## What data does AI need to run commercial service operations? Full context in structured data: one connected record where the client, sites, contacts, equipment, agreements, and projects are explicitly linked. AI will not operate in workarounds the way humans do. A dispatcher can mentally merge forty duplicate “customers” back into one client; an AI agent can't reliably infer it — it acts on the records it's given. Make it concrete. For AI to schedule a preventive-maintenance visit, it has to know which agreement covers which units at which site — three explicit links. For [AI dispatch](https://fieldcamp.ai/hvac-software/dispatch/) to send the right tech, it has to see the real site with its access notes, not a duplicate customer with an address in the name. For AI to draft a renewal or flag an aging unit for a retrofit proposal, it needs the client-level history that only exists if every visit landed on the same record. Each of those is trivial on the hierarchy and impossible on the workaround. This is the part of the data-model conversation that's new. The hierarchy used to be an argument about tidiness — cleaner reports, less double entry. Now it's an argument about capability: structured, connected records are the precondition for AI running any of the operation. A shop that shreds its commercial accounts into fake customers isn't just tolerating messy data — it's starving the AI it will want next year of the context that AI needs today. Purpose-built commercial HVAC software matters more in the AI era, not less. 06 The foundation ## A commercial template out of the box. _Customizable underneath._ The hierarchy on this page isn't a diagram we aspire to — it's FieldCamp's commercial HVAC business template, shipped out of the box: client, contacts by role, sites with access notes, equipment as asset records, agreements, and projects — there on day one. And because it's built on a [customizable data model](https://fieldcamp.ai/customizable-data-model/), it bends to how your shop actually operates: rename the objects, add the fields you track, change the statuses — without a developer. That combination is deliberately rare. Residential-first tools can't hold the hierarchy; most enterprise commercial platforms hold it rigidly, their way. FieldCamp holds it your way — the same data model runs a two-truck shop and a two-hundred-tech operation, because you reshape it to fit rather than the reverse. Add a coverage tier past bronze-to-platinum, rename a retrofit phase, track the one nameplate field your manufacturer cares about on the equipment record, or add a warranty-claim object to the chain — no developer, no second system. And because one model runs residential, commercial, and large-scale project work, a mixed shop doesn't run two tools. The platform view of everything the record powers is on the [commercial HVAC software](https://fieldcamp.ai/hvac-software/commercial/) page. Commercial HVAC template · objects Clientthe property management companycustomizable Site contactschief engineer · facilities · APcustomizable Sitesbuildings · access notescustomizable Equipmentasset records · service historycustomizable Agreementstiers · PM frequency · renewalscustomizable Projectsphases · progress billingcustomizable +Your custom layerwarranty claims · custom tier · extra phaseno code Two trucks or two hundred techs: the template loads out of the box — then reshapes to how your operation runs. 07 Why it matters ## One record, three payoffs. _Every single day._ 01 ### When the property group calls. No “let me get back to you.” Open the client profile and pinpoint the agreement, the unit, or the invoice in one tab — while they're still on the phone. For a contract business, that response speed is the relationship. 02 ### The account compounds instead of scattering. Every request, visit, and invoice lands on the same record, so renewals and retrofit proposals start from evidence — the year of visits, the aging units, the coverage gaps — not from whatever the account manager happens to remember. 03 ### You're structured for what's next. AI doesn't operate in workarounds. The connected record is the context AI needs to schedule PM, dispatch the right tech, and draft the renewal — so structuring the lifecycle now is what makes the automation real later. 08 FAQ ## The commercial HVAC lifecycle, _answered._ What are the stages of the commercial HVAC service lifecycle? Six: request, estimate, work order, visit, invoice, renewal. Work enters as a request on the client's record, becomes an estimate built against the site and equipment on file, converts to a work order — one-off, recurring, or multi-day — runs as a scheduled and dispatched visit, and is invoiced to the right billing contact; then the agreement's end date brings the loop back around at renewal. Break-fix work repeats the middle stages on demand, maintenance agreements auto-generate the work-order stage on their own schedule, and capital projects run the same chain phase by phase — all of it attached to one connected client record. How do commercial HVAC companies organize clients with multiple buildings? As a hierarchy: one client record for the company — typically a property management company — with each building as a site under it, and each site holding its own equipment, contacts, and access notes. Service agreements and projects then reference those sites and units. In FieldCamp this structure ships out of the box in the commercial HVAC template. The alternative — creating a separate 'customer' per building — fragments reporting, equipment history, and billing across duplicates of the same company. What is a customer hierarchy in field service software? A customer hierarchy is a parent-child structure in which one client record holds many child records — sites, site contacts, equipment, agreements, and projects — instead of the software treating every address as an unrelated customer. It matters in commercial HVAC because the customer is an organization with a portfolio, not a homeowner with an address. With a hierarchy, revenue and history roll up to the real client; without one, a single company looks like forty small ones and nothing rolls up at all. Why does residential field service software break for commercial HVAC? Because it's built on one assumption: one customer equals one address, maybe two or three counting billing. A commercial account is a single client with dozens of locations, each with its own equipment, site contact, and history — and that structure physically doesn't fit the residential model. Shops force it in with a fake customer per building, which breaks client-level reporting, splits equipment history across duplicates, and doubles data entry. Jobber and Housecall Pro are common examples of tools built on the one-address assumption: strong at residential jobs, but with nowhere for a multi-site hierarchy to live. How should equipment tie to agreements and projects? Through the site, on one record. Each unit is an asset record under its site. A service agreement scopes the specific sites and units it covers — quarterly PM on the chillers, filters on every RTU — so preventive maintenance auto-schedules against real equipment. When a unit ages out, the replacement runs as a project with phases and progress billing on the same client and site. The unit's whole arc, from covered asset to retrofit line item, stays on one connected history instead of splitting across a maintenance tool and a project tool. Do break-fix calls, PM contracts, and capital projects share one record? Yes — that's the point of the connected record. In FieldCamp, break-fix calls, preventive-maintenance contracts, and capital projects all live on the same client and the same site. A no-cool call is a work order; a quarterly PM visit is generated by the agreement; a six-unit rooftop replacement is a project with five phases, each phase carrying its own work orders and schedule, invoiced by phase as work completes. You don't need to buy a separate project app — one data model covers residential work, commercial service, and large-scale projects. What are access notes and why do they matter in commercial HVAC? Access notes are the site-level instructions for physically reaching the work: roof access via the freight elevator, the loading dock behind Albert Street, which level the mechanical room is on, who holds the key. In commercial buildings they decide whether a visit starts on time or a tech waits in a parking lot calling the office. FieldCamp stores them on the site record itself, so every work order at that site carries them automatically — they don't live in one closed job note or one dispatcher's memory. Where does the lifecycle start and end? It starts at intake: a request — often a tenant request routed through the property manager — lands on the client's record. It becomes an estimate built against the site and equipment on file, converts to a work order, is scheduled and dispatched as a visit, and is invoiced to the accounts-payable contact. It ends at renewal, which is really the loop restarting: the agreement's end date comes up, the record shows every visit and unit it covered, and the renewal or retrofit proposal starts from that evidence. First request to renewal, one record. Which software components support each lifecycle stage? Each stage maps to a module: intake runs on the AI receptionist that answers the call and logs it as a request, visits run on scheduling, dispatch, and work orders (one-off, recurring, or multi-day), and the money stages run on estimating and invoicing — good-better-best quotes broken into phases, invoices that follow the agreement's billing cadence or bill by phase, synced to QuickBooks. Contract work runs on maintenance agreements that auto-generate PM work orders, and capital work runs on projects with phases. In FieldCamp these aren't separate apps — every module reads and writes the same client → sites → equipment → agreements → projects record, which is what keeps the lifecycle connected. What data does AI need to run commercial service operations? Full context in structured data. AI will not operate in workarounds the way humans do — a dispatcher can mentally merge forty duplicate 'customers' into one client, but an AI agent acts on the records it's given. To schedule preventive maintenance, AI needs the agreement explicitly linked to the units it covers; to dispatch, it needs the real site with its access notes; to draft a renewal, it needs client-level history on one record. The connected client → sites → equipment → agreements → projects structure is the precondition for AI operation — which is why the data model matters more as AI takes on the busywork, not less. How do you configure the lifecycle to match how your shop operates? Start from FieldCamp's commercial HVAC template — client, contacts by role, sites with access notes, equipment, agreements, and projects come configured out of the box — then reshape it on the customizable data model: rename objects, add the fields you track, and change statuses to match your pipeline, without a developer. That means the lifecycle bends to your operation — your tiers, your phases, your approval steps — instead of forcing your shop into someone else's workflow. The fastest way to see it is a demo: we'll build your hierarchy live on the call and walk the lifecycle from request to renewal. Get started ## Want your whole book of business _on one record?_ Fifteen minutes. We'll build your hierarchy live — your clients, sites, equipment, and agreements — and walk the lifecycle from first request to renewal. [Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)