Why You Should Keep Service Records Across Client Sites, Not With Crews

Ask a contractor how a particular client's plant has been behaving and you will often get an
excellent answer — from one technician, the one who has covered that site for years. Ask when
that person is on leave and the answer is usually that nobody knows.

That is the whole problem, and it is invisible until it is acute. The knowledge is real, it is
just held in a place that leaves the business at the same time the person does.

Records belong to the site

The principle is simple and is what everything else follows from: service history is an
attribute of the asset and the site, not of the person who attended.

That means every record needs a site and, where possible, an asset identifier attached at the
moment it is created. Not the technician's name instead — as well as. The technician matters for
accountability; the site matters for continuity.

Filing by date or by crew answers questions nobody asks. Filing by site answers the question
that comes up constantly: what has been happening here?

Ask for the client's asset identifiers

Where a client has their own asset numbers, use theirs rather than inventing your own.

This sounds like a small administrative choice and it is unusually valuable. It means your
records and their records refer to the same things, which makes every conversation faster,
every report verifiable, and every dispute resolvable by comparison rather than by argument.

It also makes you materially harder to replace, because a successor contractor starts with no
history against those identifiers and you can demonstrate exactly what they would be losing.

Capture what the technician knows, not just what they did

The most valuable content in a service record is often an observation rather than an action: this
unit runs hot, this door has been adjusted repeatedly, the access arrangement here is
unreliable, this part is obsolete.

None of that appears on a job sheet unless you ask for it. Add one field — anything worth knowing
next time — and it becomes part of the record rather than part of one person's experience.

That field is what makes a site handover to a different technician survivable.

Test it with a deliberate handover

The honest test of whether your records work: send a technician who has never attended a site,
give them only the record, and see whether they can work.

Do this on purpose, occasionally, rather than discovering the answer during an illness or a
resignation. Whatever they have to phone someone to find out is precisely what is missing from
the record, and you now have a specific list rather than a vague concern.

Keep history through contract changes

Records are most often lost at transitions: a contract renewed under a new reference, a client
restructuring, a site changing hands, your own system being replaced.

Migrate deliberately at those moments. A history that stops at a contract boundary tells you
nothing about whether the plant is deteriorating, which is the exact question a renewal
conversation turns on.

Use it to make the renewal case

At renewal, a contractor with per-site history can do something competitors cannot: describe the
client's own estate back to them.

Which assets are consuming the most attention. What has been recurring. What is likely to need
capital soon. Where the access arrangements are costing everyone money.

That conversation is not about price, which is the only conversation available to a contractor
without records. It is the strongest commercial reason to keep them properly, quite apart from
the operational one.

Decide retention beyond the contract

Keep site records for a period that extends past the end of the relationship. Questions arrive
after contracts end — warranty issues, disputes, a client returning after trying someone else.

Set the period deliberately and confirm what applies to your situation and jurisdiction,
particularly for anything safety-related. Then apply it, rather than keeping everything until
the store is unusable or clearing it the moment a contract closes.