What should a device register actually contain?
Use one row for each distinct assembly, with a stable key linking its history. Keep the site address, customer, location within the site, device details, and current status together. A customer may have several sites, and one site may have several devices.
Separate the device register from the visit calendar and invoice list. A planned test is a future task; a completed test is a work record. The buyer needs both, plus the customer terms that explain who hired the contractor and who owes the bill.
The market hub helps compare specialty-service businesses. For this niche, the register is a practical diligence starting point. It shows which questions to ask about the revenue, without turning every device into a guaranteed sale.
A device acceptance trail links an assembly's test to the tester, submitted report, receiving authority, acceptance status, and any required follow-up. It supports the business review. It is not a test result, proof of safe water, or permission to carry out the next test.
Which authority sets the device's actual requirements?
Identify the water authority and other applicable rules for each site. Request current instructions, accepted forms, due-date records, and contact details. Do not copy one customer's schedule across a service area merely because the devices appear similar.
EPA's distribution resources for small drinking water systems include guidance on cross-connections and backflow. That resource page gives broader context. It does not set one testing interval, form, credential, or approval route for every device in the target's register.
Check a sample of due dates against the source notice or applicable requirement. Distinguish an authority's deadline from a reminder chosen by the seller. If a date was entered by hand, find out what evidence supports it and who keeps it current.
Keep the authority's requirements beside the actual device and customer. That makes the handoff usable for dispatch and testing staff. It also helps the buyer find accounts where a reminder exists but the next job has not been agreed or properly scoped.
Who may test, repair, and submit the report?
List the tasks performed at each site and the people who do them. Testing, repair, surveys, program administration, and report work may call for different roles. Do not use the phrase certified staff as a substitute for checking each person's actual credential.
ASSE's professional qualifications standards page lists its Series 5000 backflow standards and distinguishes professional roles. Use it to understand the credential named in the file. Then confirm local requirements with the authority that receives the report.
Collect current credential details, any local registration, relevant equipment records, and the way reports are submitted. Ask what changes if the buyer uses a new legal entity or different tester. A successful past report does not settle permission for a future crew.
The qualifying-party definition helps keep licensed plumbing supervision distinct from other roles. The skilled-trades labor guide supports a backup plan. Confirm which people can cover tests, repairs, and report work rather than assuming one departure affects all tasks equally.
Does the file show an accepted report or just a visit?
Trace one assembly from customer request through the completed test, report submission, and any follow-up. Record who received the report and what status the authority returned. A technician's note that the visit ended is not the same as an accepted filing.
Look for rejected forms, missing fields, disputed readings, repair work, and repeat visits. Ask who corrected each issue and whether the customer was charged. Keep the record factual; a buyer's spreadsheet cannot resolve a technical defect or declare a device compliant.
Review open items by deadline and responsible person. Some issues may be a file gap that can be fixed with an existing receipt. Others may require more work or a decision from the authority. Do not assign the same cost or response to every missing status.
Match the final service record to the invoice and cash received. That chain helps show whether the company delivered the work it billed. It also separates unpaid work and unresolved duties from future jobs that dispatch hopes to book.
Can an export preserve the details the buyer needs?
Request a detailed export with the relevant keys and source links. Ask which date range, filters, and row limits were used. Retain a read-only copy of the source records so that the buyer can trace a disputed row back to its origin.
ServiceTitan's reporting instructions describe PDF and XLSX exports, an option to export aggregated data, and filters that can change results. Those features explain why a summary may differ from the needed detail. The instructions do not prove full database portability or the buyer's access rights.
Test a small set of rows before relying on the whole calendar. Confirm that a device's site, past test, report status, invoice, and current due date can still be linked. Record any fields or attachments that the export left behind.
Consider an illustrative file, with no real customer records. It contains 30 rows called devices. Assume three rows are duplicate entries and two describe removed assemblies. That leaves 25 distinct, active candidates for further review, not 25 guaranteed customers or future paid tests.
The example shows a record-count check rather than a retention forecast. The buyer still needs customer rights, valid requirements, trained staff, scheduling, and cost evidence. Keep each unresolved fact in the file instead of adjusting a revenue estimate from the row count alone.
Which records should affect the closing decision?
Inspect each layer separately, then join them using the device key. A neat calendar may conceal a stale device, a report still open, or a customer who now uses another provider. The buyer needs a clear explanation of what each count includes.
| Record layer | Evidence to inspect | Question for the buyer |
|---|---|---|
| Customer | Signed scope, contacts and notice terms | Who has hired this contractor? |
| Site | Address, authority and site permissions | Where may the crew work? |
| Assembly | Stable ID, location and active status | Is this a distinct current device? |
| Tester | Role, credential and local acceptance | Who can perform the task? |
| Report | Submission, response and follow-up | What work is still open? |
| Billing | Invoice, credit and cash receipt | What earnings does the file support? |
Use the service-agreement revenue definition when reviewing promises of repeat work. A required future test and a signed service agreement are different records. Confirm the customer's actual commitment, cancellation terms, and any needed consent for the buyer.
Assign a response to each material gap. Obtain a missing record, correct a duplicate, confirm an approval, or change the supported service plan. The file should help the buyer make specific decisions, not suggest that one missing field defeats every account.
How should the device records be handed over?
Agree which records, attachments, credentials, and account rights the buyer will receive. Confirm that the transfer is permitted and that the future team can use the data. Keep customer information within the agreed access and privacy controls.
- Establish a stable key for each distinct active device.
- Match the site and assembly to current authority requirements and due dates.
- Link the tester, completed work, report status, and open follow-up.
- Reconcile the service record with bills, credits, cash, and customer terms.
- Test the buyer's permitted access and assign the next task before takeover.
Have a dispatcher and a tester review a routine account and an account with an open issue. Ask them to find the source requirement, last report, customer contact, and next action. Fix gaps while the seller's records and knowledge remain available.
The plumbing M&A market guide and private-equity plumbing guide help assess buyer fit. The useful asset is a supported service process with people and records behind it. A long list of devices or reminder dates cannot establish that process on its own.