Field service management: proving a visit that holds up to a dispute
Field service management companies live and die by what happens on site. A technician shows up, runs a maintenance check, swaps a part, ticks a box, and leaves. Multiply that by thousands of visits a month across dozens of technicians, and you have an operation built almost entirely on trust: the customer trusts the report, the back office trusts the technician, billing trusts both. Most of the time that trust holds. The problem starts the day it doesn't.
Because digital tools made everything easier to log, they also made everything easier to contest. A client looks at an invoice and asks whether the technician was really there for the two hours billed. A facility manager claims the unit was never serviced, or that the work was rushed, or that the photo in the report could be from any day. Suddenly the company has to prove something it always assumed was self-evident: that a specific person did specific work at a specific place and time. A signed PDF and a few phone photos rarely settle the argument. When SLAs, penalties and payment are on the line, that gap gets expensive fast. This is exactly the problem we unpack in our guide to digital evidence for installation and maintenance work.
So how do you build proof of a visit that actually survives a challenge, instead of a report that only looks official until someone pushes back? The short answer: you stop relying on documents that can be edited after the fact, and you start capturing evidence at the source. A defensible field service record rests on four elements, each certified at the moment it happens, so that the whole thing can be verified later by anyone, not just taken on faith.
This insight is part of our guide: Certified installation and maintenance: digital evidence for technical interventions
Why the traditional service report does not hold up to a dispute
The traditional service report fails under challenge because every part of it can be altered or denied after the fact. A signature on paper or a flat PDF is easy to repudiate. Photos carry no trusted timestamp. The GPS log lives in an app the company controls, so the other side dismisses it. And the document itself stays editable, which means nobody can be sure it wasn't touched between the visit and the invoice.
Think about what a normal report actually is. It's a form, filled in by the same company that wants to get paid, stored on systems that same company manages. There's nothing dishonest about that, but it's also not independent. In a billing dispute, an arbitration, or a court, the question isn't "did you act in good faith?" It's "can you prove this wasn't created or changed to suit you?" A file your own team can open and re-save doesn't answer that.
The individual pieces are weak in specific ways. A scanned signature proves someone signed something, not when, and not that the document above it stayed unchanged. A photo with EXIF data can have that data stripped, edited, or simply doubted, because EXIF is trivial to rewrite. A geolocation entry in your own dashboard is a number you typed into a system you own. None of these were captured to be shown to a skeptical third party. They were captured to close a ticket.
Here is the difference between a report that documents work and one that proves it:
| Element | Traditional service report | Defensible proof |
|---|---|---|
| Presence on site | GPS logged inside the company's own app | Arrival and departure geolocation captured and certified at the source |
| Work performed | Phone photos, timestamp easy to alter or strip | Before and after photos with a qualified timestamp anchored to capture |
| Customer agreement | Signature on paper or flat PDF, easily repudiated | Checklist signed electronically by the customer on site |
| Document integrity | Editable file, no way to prove it wasn't changed | Report with a verifiable hash that flows into billing |
The four elements of defensible field service proof
Defensible field service proof rests on four certified elements: where the technician was, what they did, that the customer agreed, and that the report wasn't altered afterward. Capture each one at the moment it happens, seal it, and you replace a story the customer has to believe with evidence anyone can check. Here is how each element works.
Certified arrival and departure geolocation
Presence is the first thing that gets denied, so it's the first thing worth nailing down. The point isn't to drop a pin on a map. It's to record arrival and departure as part of a forensic acquisition: the position, the timestamps for when the visit began and ended, and the surrounding context, captured so the metadata can't be quietly rewritten later. TrueScreen handles this as contextual evidence, not as a raw coordinate. Certified arrival and departure geolocation captured with TrueScreen proves the technician's presence on site with evidentiary value, not with a plain GPS reading that the other side can wave away.
Before and after photos with a qualified timestamp
Photos are where most reports quietly fall apart. A picture of a serviced unit means little if nobody can show when it was taken or that it wasn't pulled from an earlier job. The fix is to capture before and after images and bind each one to a qualified timestamp at the moment of capture, so the photo and its time are sealed together. Now the image isn't just illustrative. It's dated, anchored, and hard to argue with.
A checklist signed electronically by the customer
The strongest proof of agreement is the one made on the spot. When the customer or their representative reviews the completed checklist and signs it electronically on site, you capture their acknowledgment while they're standing in front of the work. This is an electronic signature, or an advanced electronic signature where stronger assurance is needed, operating within the framework of Regulation (EU) 910/2014 (eIDAS). It ties a real person to a real acceptance, at a real moment, instead of a box ticked back at the office.
A hash of the report that flows into billing
The last element is the one that protects everything above it. Once the report is finalized, it gets a cryptographic hash, a unique fingerprint of that exact file. Change a single pixel or character and the hash no longer matches. When that hash travels with the report into billing, you have a document whose integrity is provable end to end. The invoice no longer rests on "trust us"; it rests on a number that anyone can recompute and verify.
How to certify a field service visit with legal value
To certify a field service visit with legal value, capture the evidence at the source and seal it the moment it's created, rather than assembling a report afterward. The technician documents the visit in the field, and each element is acquired, verified, certified and preserved through a forensic methodology, so the finished record carries weight before any dispute appears.
In practice, that methodology runs in four phases. First, forensic-grade acquisition at the source, which captures photos, geolocation and signature in a way that preserves their authenticity and prevents tampering. Second, verification of the information collected. Third, certification with legal value, which applies an official digital seal and a qualified timestamp. Fourth, preservation on secure systems so the evidence stays available and intact for as long as you need it. TrueScreen captures and certifies the photos, geolocation and signature of each visit, applying internationally recognized digital seals and qualified timestamps that make them defensible.
For the field service manager, the payoff is operational, not just legal. With TrueScreen, the field service manager gets a report with a verifiable hash that flows straight into billing, removing disputes over presence and duration. The team works through the TrueScreen App on site, applies an advanced electronic signature where the customer signs off, and for companies running their own dispatch or ERP systems, the same certification is available through the TrueScreen API. It all sits on one data authenticity platform, so evidence from every visit is captured the same way and verifiable on the same terms.
Take elevator and lift maintenance, an area governed by strict safety and maintenance regulations that require periodic, documented servicing. A building manager disputes whether a scheduled inspection actually took place, or a question of liability surfaces after an incident, and the maintenance company needs to show exactly who was there, when, and what was checked. A certified record, geolocation, timestamped before and after photos, the technician's checklist, the customer's signature, and a hashed report, turns "we always service it on time" into something that stands up when it matters. The same applies to HVAC servicing, fire safety systems, industrial machinery, and any intervention where missing or contested proof carries real consequences.
From report to evidence
The shift here is small in effort and large in consequence. You're not asking technicians to do more paperwork; you're changing what their work produces. Instead of a document that looks official until someone challenges it, every visit generates evidence that was built to be challenged and to hold. Presence, work, agreement, integrity, each one certified at the source. For more on how this plays out across installations, repairs and inspections, see our guide to certifying on-site technical interventions. When the next dispute lands, and in field service it always does, the difference between losing the argument and ending it comes down to whether your proof was made to survive scrutiny in the first place.
