Home services and trades
Data inventory template for HVAC, plumbing and electrical companies
By SourceX Editorial · Updated
Short answer
A data inventory template for contractors gives every record family one row and records its system, accessible years, steward, export route and rights flags beside it. Fill it in from metadata only, never from exported files, and write unknown rather than guessing. The finished sheet supports software migrations, sale preparation and data licensing fit checks.
Key takeaways
- One row per record family, not per system, keeps a contractor inventory readable.
- Accessible years matter more than company age, so record what can still be exported today.
- Rights flags such as home warranty jobs, property manager contracts and call recordings belong in the inventory from the start.
- Software subscriptions in accounts payable and card statements are a quick way to find every system that holds records.
- The inventory describes records and never contains customer data itself.
What a contractor data inventory is for#
A contractor data inventory is a one-page map of where a company's records live, how far back they go, who looks after them and what limits apply. It is built from descriptions, not files, so it can be shared with advisers, buyers or a licensing partner without exposing any customer data.
The same inventory serves several decisions. A COO uses it to plan a software switch, an owner uses it to prepare for a sale, and a licensing fit check uses it to see whether records link calls, jobs, invoices and callbacks. Building it once and keeping it current saves rebuilding it under pressure for each event.
The template: columns to fill in#
The template has twelve columns, each answering a question that a buyer, adviser or migration lead will eventually ask. Copy the column names into a spreadsheet exactly as written so different people fill them in the same way.
| Column | What to enter | Trades example |
|---|---|---|
| Record family | The type of record, in plain words | Technician notes and forms |
| System and account holder | Software name and whose name is on the account | ServiceTitan, company account |
| Years accessible | Earliest and latest dates you can still export | From the platform switch to today |
| Rough volume | An order of magnitude from a system report | Job count from a year-end report |
| Linked IDs | Which other records share an identifier | Job ID links to invoice and estimate |
| Personal data | Personal details the records hold | Names, addresses, phone numbers, gate codes |
| Notice or consent basis | What customers or staff were told when the records were created | Recording greeting on calls; privacy notice on the booking form |
| Data steward | The person who knows the records best | Service manager |
| Export route | How a copy can be taken | Report export, API, vendor request |
| Rights flags | Contracts or terms that may limit use | Home warranty company terms |
| Shutdown risk | Any planned cancellation or migration | Old phone system retiring soon |
| Notes and unknowns | Open questions to settle later | Unclear whether photos export with jobs |
Pre-filled rows for a typical HVAC, plumbing or electrical company#
Most HVAC, plumbing and electrical companies hold the same core record families, even though their systems differ. Start with these rows, delete any that do not apply and add your own, such as a separate row for each brand if you run more than one.
| Record family | Where it often lives | Flags to check first |
|---|---|---|
| Calls and bookings | Phone system, call tracking, field service software | Recording notice and consent |
| Estimates and proposals | Field service software or an estimating tool | Commercial customer confidentiality |
| Jobs and work orders | Field service software such as ServiceTitan, Housecall Pro, Jobber or FieldEdge | Franchise or platform terms |
| Technician notes, forms and photos | Field service mobile app | Personal details and photos of homes |
| Invoices and payments | Field service software and accounting | Card data held by the payment processor |
| Memberships and maintenance agreements | Field service software | Terms customers signed up under |
| Equipment and installed base | Field service software | Manufacturer warranty portal terms |
| Warranty claims and callbacks | Field service software, manufacturer portals | Manufacturer and distributor agreements |
| Third-party jobs | Home warranty, insurance or property manager portals | The third party's contract and data terms |
| Permits and inspections | Shared drives, municipal portals | Public records mixed with customer details |
| Purchasing and inventory | Supply house accounts, accounting | Supplier pricing confidentiality |
| Fleet and GPS | Telematics system | Employee monitoring notices |
| Training and certifications | HR system or shared drive | Employee personal data |
How to fill it in without exporting anything#
The inventory can be completed entirely from system screens, built-in reports and short conversations, with no export at all. These steps work for most companies that have an office manager, a service manager and a controller.
- Step 1: pull the list of software subscriptions from accounts payable and card statements; every paid tool is a possible record source.
- Step 2: add systems no one pays for anymore whose data still exists, such as an old platform in read-only mode or a shared drive.
- Step 3: fill one row per record family, naming the system and the account holder.
- Step 4: use built-in reports to find the earliest record date and a rough count, without downloading records.
- Step 5: ask the dispatcher, service manager and controller which records link to which, and where the links break.
- Step 6: mark rights flags and personal data in their columns, and write unknown wherever nobody is sure.
- Step 7: give the sheet a named owner and a review date.
Rights flags that are specific to the trades#
Rights flags in a trades inventory mark records that someone other than your company may have a say over. Flagging them early keeps them from being swept into a migration plan, a sale disclosure or a licensing scope by mistake.
Third-party work and partner terms are the most common sources. Jobs dispatched by home warranty companies and insurance carriers often come with their own data terms. Commercial service agreements with property managers and builders may include confidentiality clauses. Manufacturer warranty portals and distributor programs carry their own conditions, and franchise agreements can reach the whole job history.
Internal records carry flags too. Call recordings depend on the notice and consent given at the time. GPS and dash camera records involve employees. Technician notes may hold gate codes or comments about a customer's health. Mark these now and leave the decision about what to do with them for later.
Illustrative: a COO inventories a three-trade company before a platform switch#
Illustrative: a fictional HVAC, plumbing and electrical company is moving to new field service software. The COO builds the inventory first, so the migration team knows what exists outside the new vendor's import scope.
The accounts payable list turns up an old call tracking service, a photo app technicians used before the current platform, and a manufacturer warranty portal the service manager logs into. The inventory shows that photos and call recordings are not in the migration plan and that home warranty jobs carry separate terms. The COO schedules exports for the missing record families, flags the warranty-company jobs and keeps the inventory as the company's reference map.
What to do with the finished inventory#
A finished inventory becomes the reference for exports, retention decisions and outside conversations. Share it with whoever needs a picture of your records, and keep the records themselves where they are.
Keep the history of the sheet as well. When a system is retired, update its row instead of deleting it, noting where the archive now lives and who holds the export log. A row describing a retired system is often the only trace of history that a later buyer or auditor asks about.
For a licensing fit check, SourceX uses exactly this kind of metadata: record families, systems, years and links. If a package moves forward, the inventory becomes the starting point for the provenance section of the SourceX Evidence Packet, and the rights flags set the agenda for the Rights step of the SourceX five-step transaction.
Frequently asked questions
How precise does the volume column need to be?
Rough is fine. An order of magnitude from a system report, such as jobs per year, is enough for planning and for a fit check. Exact counts matter later, when a specific export is reconciled against the system before an old account is closed.
Should employee records go in the inventory?
List them, but flag them clearly. Payroll, HR files and certifications hold employee personal data and are rarely part of any outside use. Including them keeps the map complete for migrations and sales, where buyers will ask about them.
Who should own the inventory?
The COO or operations manager usually owns it, with the controller covering financial systems and the service manager covering field records. One named owner keeps it current; a shared document with no owner goes stale quickly.
How often should it be updated?
Update it whenever a system is added, retired or migrated, and review it on a regular schedule, such as at year end. The shutdown risk column is the one that most often needs attention between reviews.
Can I share the inventory without sharing customer data?
Yes. A properly built inventory holds no customer records, only descriptions of them. Keep examples generic in the notes column and never paste sample rows from real jobs into the sheet.
Related resources
- QuestionCan SaaS data be licensed?
- InsightConstruction software companies: what project data you can and cannot license
- InsightAI features in acquired products vs licensing records out: a holdco rule
- IndustryFintech software data
- QuestionWho owns enterprise data?
- InsightData licensing rules for call centers and BPOs
See if your company qualifies
A short company assessment. No data uploads are needed.