The carbon copy in the site folder
A technician finishes a routine visit at a food premises. They have checked every bait station, noted activity at two of them, found a gap under a door that needs proofing, and taken some photos on their phone. They fill in a carbon-copy report, leave the top copy in the site folder, and take the bottom copy back to the office.
In the office, someone types it up so it can be emailed to the client's head office. That happens when they get to it. The photos stay on the technician's phone unless someone remembers to ask for them. When the client's auditor visits and asks for the last six months of reports and trend of activity, somebody spends an afternoon pulling them together.
The same pattern applies to planned maintenance visits, fire door inspections, water hygiene checks and most other routine site visits that end in a report.
Why the paper report survives
The paper form is familiar, quick to fill in on site and always works. It is also often a legacy of what clients used to ask for: a signed sheet left in a folder on site.
What has changed is what clients do with the report. Multi-site clients want reports centrally, in a consistent format, soon after the visit, and they want trends over time. A carbon copy in a folder on site answers none of that, so the office makes a second version by hand.
Earlier attempts at going digital often meant a generic form app that produced a list of answers, not a report a client would recognise. Technicians disliked it, clients found it hard to read, and paper crept back.
What the paper route costs
| Problem | Effect |
|---|---|
| Retyping | Office time spent turning handwritten reports into documents |
| Late reports | Clients receive findings days after the visit |
| Missing photos | Evidence stays on personal phones or is lost |
| No trend view | Activity across visits is hard to see, so recurring problems are missed |
| Audit scrambles | Pulling historical reports together takes hours |
Late reports matter most where the findings need action. A proofing recommendation that reaches the client a week later is a week in which the problem continues, and the client may reasonably ask why they were not told sooner.
How we build reports that finish on site
- A technician app, working offline, laid out around your visit structure: site, areas, devices or assets to check, findings and recommended actions.
- Each device or asset on a site listed with its location, identified by a label or QR code, so the technician records the check against the right one and nothing is skipped.
- Photos taken inside the app and attached to the finding they relate to, with time and, where the phone allows it, location.
- Recommendations recorded with a priority and a responsible party (you or the client), so actions can be tracked after the visit.
- The client report generated on completion in your branded format, signed off on site if the client contact is present, and emailed to the contacts you list for that site.
- A site history: every visit, finding and photo for a location in one place, with a simple trend view per device or area, and outstanding recommendations shown until they are closed.
What goes in the report, and what counts as a finding, is your professional judgement. We build the tool around your method; we do not change it.
After the switch
The client has the report before the technician has left the car park. The office stops retyping and instead follows up the recommendations that need action. When an auditor or head office asks for history, it is a filtered view and a download, not an afternoon of searching.
Technicians also benefit. They can see previous findings for a site before they arrive, so they know where to look first, and they stop being asked for photos days after the visit.
Is this your business?
- Visit reports are written on paper or carbon-copy forms
- Someone in the office types reports up before they go to clients
- Photos from visits sit on technicians' phones
- You struggle to show a client the trend across several visits
- Audit requests for report history take hours to answer