Choose a completed process
HVAC, electrical, plumbing, equipment maintenance, and other service businesses document practical decisions every day. Those decisions may live across dispatch software, service reports, parts records, and internal instructions. Begin by identifying repeated job types and the records that explain how the work progressed.
A count of invoices does not tell a reviewer whether the archive includes diagnosis or follow-up. A long technician note may still omit what happened after a return visit. Describe the completed history, the gaps, and the systems involved before treating the archive as a single collection. Different service lines may have very different record quality.
An illustrative record trail
| Stage | What happened | What to locate internally |
|---|---|---|
| Reported symptom | A piece of equipment shuts down intermittently during normal operation. | Job type, symptom category, equipment class, and earlier work reference. |
| Diagnostic choice | The technician rules out one cause, documents a test, and orders a replacement component. | Reason for the test, observed result, and component category. |
| Follow-up | The customer reports a repeat symptom; a second visit identifies a separate issue. | Linked return visit, revised diagnosis, and recorded closeout. |
This is an illustrative job history, not a North Fox Digital client example. Its value as an inventory exercise is that it separates an initial diagnosis from the later outcome. Failed attempts and repeat visits can explain the work as clearly as straightforward repairs, provided the records preserve the connection.
Check whether mobile notes, photos, and customer approvals were captured under the same job identifier. A change in dispatch software may break those links. Technician shorthand may also need explanation: an abbreviation that everyone on the crew understands can be ambiguous outside the business. Record a short glossary without copying customer records into it.
Before the first conversation
- Choose a few broad job categories and count completed histories by category and period.
- Check whether diagnosis, parts, work notes, and return visits share a stable job reference.
- Record which instructions were written by employees, contractors, suppliers, or manufacturers.
- Flag customer addresses, access codes, payment details, faces in site photos, and confidential facility information.
- Identify who approves the company’s records and who reviews customer or contractor restrictions.
Describe the scope without sending the records
A first description can stay practical: “Our service system contains completed equipment-maintenance jobs, including diagnoses and linked return visits. Dispatch records go back further than detailed technician notes. Manufacturer manuals and customer-site images would need separate review.” That gives Neil enough context to ask useful questions without receiving the source material.
A specialist service archive may need individual review even if the company is small. The estimator’s observed business domain and reference rules remain the same across sectors; job counts and technical complexity do not add monetary multipliers. Use the result as a starting point, then establish the actual scope, rights, buyer interest, and proposed terms.