Most field service work happens twice. The first technician arrives at an address, diagnoses the problem, takes a few photos on their phone, fixes what they can, and writes a short note in the job management system. Six months later — sometimes six weeks — the next callout comes through. A different technician is dispatched. They arrive at the same address with no idea what was found last time, no photos of the meter cupboard, no record of which circuit was acting up, and no context for the conversation they are about to have with the customer.
The information existed. It just wasn’t anywhere the second technician could find it.
That gap — between the information field professionals capture and the information their colleagues can actually use later — is the gap a site record closes.
What field service teams actually capture
Walk through a typical day for an electrician, plumber, HVAC technician, or facilities manager and you will see a steady stream of site-specific information being generated:
- Photos of switchboards, meters, plant rooms, leaks, damage, completed work
- Notes about quirks: the second-floor isolator that is mislabelled, the access panel hidden behind the bookshelf, the customer who is hearing-impaired and prefers texts
- Receipts, parts lists, and serial numbers from equipment installed
- Inspection reports, compliance certificates, test results
- Occasionally a video walkthrough or a 360° photo of a plant room
- The completed job sheet from the field service management system
Every one of these artefacts says something specific about a physical address. Together, they are the most accurate record of that site’s condition that exists anywhere. And almost without exception, they end up in three or four disconnected places: photos on the technician’s personal phone, notes in the dispatch system, certificates emailed to the customer, parts lists in the accounting software.
The next time someone is dispatched to that address, none of it is in one place.
Why “the photos are in the job system” isn’t enough
Most field service management platforms — the dispatch and invoicing tools that run the back office — let technicians attach photos to a job. That sounds like the problem is solved. In practice, it is not, for three reasons.
First, photos attached to a job are filed under the job, not under the address. To find them later, the next technician has to know which job the photo was attached to. If the previous visit was 18 months ago, that means scrolling through a job history and opening individual job records to find what they are looking for.
Second, the photos are usually low-resolution thumbnails optimised for the dispatch app, not full-resolution images that hold up to zooming in on a serial number plate or a wiring diagram.
Third, the photos are the only spatial information that travels well. A 360° photo of a plant room, a short video walkthrough, a PDF of a switchboard layout, an inspection report — these don’t fit the “attach to job” workflow neatly. They get emailed instead, which means they end up in someone’s inbox, not on the site.
A site record fixes all three. It is anchored to the address rather than the job, it stores files at full fidelity, and it accepts every file type a technician might want to capture or share — photos, video, 360s, PDFs, scans.
What a site record actually is
A site record is a single, persistent place where everything ever captured at a physical address lives. Three properties make it different from a folder in Dropbox or a job in your dispatch system:
Address-anchored. The record is keyed to the physical location, not the job, the customer, or the work order. Customers change. Tenants change. Jobs come and go. The address is the constant.
Time-indexed. Every file knows when it was captured. The record shows you the site’s condition at any point in the past, and you can compare what’s there now with what was there a year ago.
Persistent and additive. Every visit adds a layer to the record. Nothing is deleted to make room. The record gets more valuable with every callout, not less.
This is the same pattern Swyvl uses across every vertical we work with — surveyors, drone operators, heritage agencies, environmental teams. For more on the underlying idea, see what is a site record.
How it works in practice
The workflow is simple and adds about 60 seconds to the end of a callout.
- The technician finishes the job as they normally would — close it out in the dispatch system, get the customer’s signature, send the invoice.
- Before driving off, they open Swyvl on their phone, find the site (or create it if it’s a first visit), and upload the photos and notes from the visit. Photos can be batch-selected from the camera roll. Documents can be added from email or a PDF reader.
- The files are automatically organised under that day’s capture session for that site, time-stamped to the job date.
The next time anyone — the same technician, a different one, the office, the customer — needs to know what’s at that address, they open the site and see everything that has ever been captured there, in chronological order.
What changes operationally
The benefits are not hypothetical. They show up in three places.
Less repeat diagnosis
The most expensive minutes in field service are the ones where the technician is figuring out what the problem is, not fixing it. When the next person dispatched can see photos of the switchboard, notes from the previous visit, and the make and model of the equipment installed, the diagnosis phase shrinks dramatically. They walk in already knowing where things are and what’s been done before.
For larger or more complex sites — a commercial building, a multi-tenant property, an industrial facility — this can be the difference between a 30-minute callout and a 90-minute callout.
Better proof of condition
Field service work is full of moments where condition matters: before-and-after photos for insurance claims, evidence that an issue existed before you arrived, documentation that a repair was completed to standard. A time-indexed site record provides all of this without anyone having to dig.
When a customer queries why a charge was incurred, you can show them the photo from that visit. When an insurer asks whether damage was pre-existing, you have a dated photo from the previous callout. When a regulator audits a maintenance contract, you have proof that the inspections happened on schedule.
Higher-quality customer relationships
When you can speak with confidence about a customer’s site — “last time we were here in November, the second sub-board was tripping intermittently and we replaced the breaker on circuit 7” — the conversation is qualitatively different. You are not asking them to remember; you are reminding them. The customer experiences your firm as competent and organised, not as a sequence of unrelated visits.
For property managers, facilities teams, and any customer with multiple sites, this is the difference between being a vendor and being a partner.
What about file sharing with the customer?
Many field service customers — facilities managers, property managers, asset owners — want a copy of the documentation themselves. A site record makes this trivial. Each site can be shared via a branded link that the customer opens in any browser, with no software to install and no login required. They see the same time-indexed history their technician sees.
For technicians delivering complex spatial files — drone surveys of a roof, a 360° photo tour of a plant room, a point cloud of a switchboard — the same share link displays everything in browser-based viewers. A facilities manager who could never open a LAS file before can now spin a 3D model of their plant room on their phone.
For more on how this delivery model works for trades and field teams, see Swyvl for field service.
The site as a long-term asset
The compound effect of a site record is the part that surprises people. After three months of using one, you have a useful reference. After a year, you have a history. After three years, you have an asset that meaningfully changes how the business operates — what you charge for, how you onboard new technicians, how you respond to disputes, what you can offer customers.
The information was always being captured. The only thing changing is whether it ends up somewhere you can find it again.
If you run a field service business and you are tired of hearing “I think there’s a photo of that somewhere on Mike’s old phone,” a site record is the answer. Start with one site, get one technician using it, and watch what happens after the second visit.