--- title: "Lifecycle" url: "https://fieldcamp.ai/hvac-software/commercial/lifecycle/" date: "2026-08-03T05:10:45+00:00" modified: "2026-08-07T11:23:10+00:00" type: "Article" resource: "https://fieldcamp.ai/hvac-software/commercial/lifecycle/" timestamp: "2026-08-07T11:23:10+00:00" author: name: "Jeel Patel" categories: - "Uncategorized" word_count: 2662 reading_time: "14 min read" summary: "Home›HVAC Software›Commercial›Service Lifecycle" description: "How a commercial HVAC job moves from client request to site visit, equipment record, agreement coverage and invoice — one connected record instead of five ..." keywords: "Uncategorized" language: "en" schema_type: "Article" related_posts: - title: "Insulation Estimate template" url: "https://fieldcamp.ai/insulation-software/estimate-template/" - title: "36 Cleaning Business Ideas to Start in 2026 (Low Cost to High Profit)" url: "https://fieldcamp.ai/cleaning-business-software/business-ideas/" - title: "CRM" url: "https://fieldcamp.ai/hvac-software/crm/" --- # Lifecycle _Published: August 3, 2026_ _Author: Jeel Patel_ [Home](/)›[HVAC Software](/hvac-software/)›[Commercial](/hvac-software/commercial/)›Service Lifecycle Commercial · Service Lifecycle # The commercial HVAC service lifecycle, on one connected record — first request to renewal. This page is the architecture reference underneath our [commercial HVAC software](/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. Part of FieldCamp’s [HVAC software](/hvac-software/). [Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)Bring your largest account — we’ll walk the record live. One connected record · first request to renewal 0 duplicate customers Clients›Beacon Property Group Commercial HVAC template Active Record map one client · 0 duplicate customers ClientRootBeacon Property Group Property manager · Toronto Contacts3 by role Chief eng · facilities · AP Sites3 buildings Access notes on each EquipmentChiller-1 · Trane 150 tons · +11 units AgreementsActiveGold PM Quarterly · renews Mar ’27 ProjectsIn progressRTU 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. **Six layers, one spine.** Client → contacts → sites → equipment → agreements → projects. Multi-site Role-based contacts Unit-level history Phased 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 whose configured recurring workflows create preventive-maintenance jobs or visits, 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. That sentence is the whole architecture. Below is how it looks in practice, using a property management client with three buildings, an equipment fleet, a live PM agreement, and a retrofit in flight — on one record. 02 The record, stage by stage ## Client → sites → equipment → contracts → projects, *all on one record.* 01 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. 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 calendar integrations for in-person client meetings. The client record doubles as the account layer of your [HVAC CRM](/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. Client record · tabsActiveBeacon Property Group Every tab, one client — nothing lives outside the record. SalesWorkFilesActivityContactsSitesEquipmentAgreementsProjects02 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 organisation, the role knowledge — who approves, who pays, who opens doors — lives in a dispatcher’s head, and leaves with them. Contacts · one client, three rolesDWDana Whitfieldmeets techs on siteChief engineerLOLuis Ortegaapproves estimatesFacilities directorAPAsha Patelreceives invoicesAccounts payable03 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. Configured work views present those notes to the technician, so the context doesn’t stay trapped in a closed job. 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 clientBeacon Tower Downtown Roof via freight elevatorAlbert Street Plaza Loading dock behind Albert StHarbor Point Offices Mechanical room · level B204 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 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-versus-labour warranty, and unit-level history lives on [HVAC asset management](/hvac-software/commercial/asset-management/). Equipment · Beacon Tower DowntownChiller 1 · Trane RTAC-150Chiller plant · level B2GoodRTU-3 · Carrier 48TCRoof · north bankDue soonRTU-7 · Lennox LGHRoof · south bankOverdue05 Agreements ### Contracts that carry 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 units, a configured recurring workflow can create the required preventive-maintenance jobs or visits — and the renewal date is a field the system watches rather than a note in a side spreadsheet. How PM programmes schedule across a portfolio is covered on [commercial preventive maintenance](/hvac-software/commercial/preventive-maintenance/), and the agreement record itself on [maintenance agreements](/hvac-software/maintenance-agreements/). Agreement · Beacon Property GroupActiveGold coverage tier PM frequencyQuarterlyScopeChillers + RTUs · 3 sitesTermApr 2026 → Mar 2027Billing cadenceMonthlyAuto-scheduled: next quarterly PM visits created on the covered units.06 Projects ### Capital work, beside the service work A retrofit or a fleet replacement isn’t a long job — it’s a project with phases, each with its own work orders, its own crew, and its own billing point. Contract sum, budget, retainage percentage, and percent complete sit on the project record, attached to the same client and site as the break-fix calls. Which is why a mixed shop doesn’t need a second system for capital work. Detail on [HVAC project management](/hvac-software/commercial/project-management/). Project · RTU Fleet RetrofitIn progressRetainage 10% · billed by phase45% complete✓Estimate & approval✓Procurement3Site prep & riggingown work orders · own schedule4Installation & tie-ins5Commissioning & handoff03 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. 01 Request tenant intake, on the client 02 Estimate options, per site 03 Work order one-off · recurring · multi-day 04 Visit scheduled & dispatched 05 Invoice routed to accounts payable 06 Renewal the loop restarts ### What powers each hop Every hop is run by a module — and 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. Intake · AI receptionist A tenant’s no-cool call gets answered, logged, and landed on the client’s Sales tab as a request — the [AI receptionist](/hvac-software/ai-receptionist/) picks up even when the office can’t. The visit · scheduling, dispatch & work orders A person or configured workflow creates the work order for approved work — one-off, recurring, or multi-day — and [scheduling](/hvac-software/scheduling/) plus [AI dispatch](/hvac-software/dispatch/) provide an assignment recommendation for review. The money · estimating & invoicing [Estimates](/hvac-software/estimating/) broken into phases, and [invoices](/hvac-software/invoicing/) that follow the agreement’s billing cadence or [bill phase by phase as work completes](https://docs.fieldcamp.ai/estimates-invoices/creating-invoices) — reaching [QuickBooks Online](/hvac-software/quickbooks/). The contract · maintenance agreements The [agreement’s frequency and scope](/hvac-software/commercial/preventive-maintenance/) drive configured recurring jobs or visits for covered sites and equipment. [Dispatch recommendations remain subject to review](https://docs.fieldcamp.ai/ai-dispatcher/what-is-ai-dispatcher). Capital work · projects Retrofit and replacement work runs as [phased projects](/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. Residential-first platforms are built on the one-customer-one-address assumption — fine for house calls, but a portfolio has to be shredded into duplicates to fit. And many platforms that *do* hold a commercial hierarchy hold it rigidly, their way. Here’s what the workaround costs, operation by operation. | Operation | On the workaround | On one 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 | 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. 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 part 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. What the [agents](/hvac-software/ai-agents/) can actually do depends entirely on what the record can actually tell them. 06 The foundation ## A commercial template out of the box. *Customizable underneath.* That combination is deliberately rare. Residential-first tools can’t hold the hierarchy; many enterprise commercial platforms hold it rigidly, their way. FieldCamp holds it your way. The [data model](/customizable-data-model/) adapts to multi-site and multi-branch operating complexity, because you reshape it to fit rather than being assigned to a crew-count category. 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](/hvac-software/commercial/) page. Commercial HVAC template · objectsClientthe property management companycustomizableSite contactschief engineer · facilities · APcustomizableSitesbuildings · access notescustomizableEquipmentasset records · service historycustomizableAgreementstiers · PM frequency · renewalscustomizableProjectsphases · progress billingcustomizable+Your custom layerwarranty claims · custom tier · extra phaseno codeTwo 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 ### The technician arrives informed Site access notes, the unit’s nameplate and warranty, and its service history are on the record before the van door opens — not in a senior tech’s memory. 02 ### The account has a number Because every request, work order, and invoice rolls up to one client, “what is this account worth?” is a report rather than an afternoon of adding up duplicates. 03 ### Nothing lapses quietly Agreements carry their own renewal dates and scope real sites and units, so a contract ending is a prompt instead of a discovery. 04 ### Automation has ground truth [The agents that answer the phone and propose the board](https://docs.fieldcamp.ai/ai-agents/agents-overview) read the same structured record — which is the difference between AI that helps and AI that guesses. 08 FAQ ## The commercial HVAC lifecycle, *answered.* **What is the commercial HVAC service lifecycle?** One connected record: a client with multiple sites, each site with its equipment, service agreements whose configured recurring workflows create PM jobs or visits, and projects for retrofit work — from the first request to the renewal. Every stage attaches to that record. **Why does the hierarchy matter so much?** Because without it, a commercial account has to be split into a fake customer per building. Service history fragments, agreements point at the wrong record, contacts are re-keyed everywhere and updated nowhere, and no report can answer what the account is worth. **How is a site different from a customer?** A site is a child record under the client — a building or a mechanical room — with its own equipment, contact, history, and access notes. In a residential model the address *is* the customer, so sites don’t exist as records at all. **Where does equipment history live?** On the unit. Each piece of equipment is a structured asset record with nameplate data and warranty dates, and every visit rolls up to the unit it touched rather than to the job that happened to include it. **Do agreements create their own work?** The agreement carries frequency, coverage, and billing cadence, and a configured recurring workflow creates the required jobs or visits for the sites and units it scopes. Scheduling and assignment remain explicit steps. **Can projects and service work coexist?** Yes — a retrofit runs as a phased project with contract sum, budget, retainage, and percent complete, attached to the same client and site as the break-fix calls. **Can I change the structure to fit my contracts?** Yes. The commercial template is a starting point on a customizable data model — add coverage tiers, rename phases, add nameplate fields, or add a whole new object like a warranty claim, without a developer. **What does this have to do with AI?** Everything. A dispatcher can mentally merge forty duplicate customers back into one client; an AI agent can’t. Structured, connected records are the precondition for automation doing anything reliable. **Does a mixed residential and commercial shop need two systems?** No — one data model runs both, plus large-scale project work, so the account structure changes without the platform changing. Related ## Each layer, in depth. [Commercial HVAC Software The platform view — every module this record powers.](/hvac-software/commercial/)[HVAC Asset Management Nameplate fields, warranty, and unit-level service history.](/hvac-software/commercial/asset-management/)[HVAC Project Management Phases, progress billing, job costing, and retainage.](/hvac-software/commercial/project-management/)[Commercial Preventive Maintenance How PM programmes schedule across a portfolio.](/hvac-software/commercial/preventive-maintenance/)[HVAC Software The whole platform this record sits inside.](/hvac-software/)[HVAC CRM The account layer — contacts by role, sites, and history.](/hvac-software/crm/)[Maintenance Agreements The agreement record: tiers, terms, renewals, covered equipment.](/hvac-software/maintenance-agreements/)[HVAC Dispatch Recommendations that read the site, access notes, and agreement.](/hvac-software/dispatch/)[AI Agents for HVAC What the agents can do depends on what the record can tell them.](/hvac-software/ai-agents/) Get started ## Want your whole book of business *on one record?* Fifteen minutes. Name the property group, the buildings, the contract, and the retrofit in flight — and watch the record take shape around them. [Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min) --- _View the original post at: [https://fieldcamp.ai/hvac-software/commercial/lifecycle/](https://fieldcamp.ai/hvac-software/commercial/lifecycle/)_ _Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1_ _Generated: 2026-08-07 11:23:11 UTC_