Finishing the report before you leave site is not a matter of working faster. It is a different workflow. Here is the business case in brief, then the practical playbook: what to prepare, the on-site sequence that works, and the pitfalls that catch most teams on their first few jobs.
Part One: Why On-Site Reporting Is Worth Restructuring For
Most thermographers do not resist on-site reporting because they think it is a bad idea. They resist because the traditional two-phase workflow, survey in the field then write up at a desk, is deeply familiar and appears to work. The reports go out. The clients pay. Nothing is obviously broken.
What is broken is invisible until you measure it.
The Time Cost
Post-survey reporting typically absorbs three to five hours per inspection: data transcription, load correction calculations, fault grading, remedial writing, report assembly, and revision cycles. Across two or three inspections a week, that is six to fifteen hours of weekly overhead per engineer. The full breakdown, including what recovering those hours is worth in billing capacity, is in our article on how to cut 4+ hours per week without hiring another engineer.
The Risk Cost
Every hour between finding a fault and documenting it is an hour where a known issue sits undocumented. For a data centre, hospital, or continuous process facility, that gap is a genuine liability rather than an administrative delay. We cover the exposure argument in detail in why same-day reporting changes the game for DC operators.
The Quality Cost
Writing up an inspection two days later means reconstructing context from notes and images. Details that were obvious on site (which panel, which orientation, what the adjacent equipment was doing, what the site engineer mentioned in passing) degrade quickly. Reports written on site are more accurate because the context is still in front of you.
The Commercial Cost
A supplier who hands over a finished, professional report before leaving site occupies a different competitive position from one promising delivery next week. In competitive procurement, particularly with data centre and FM clients, this difference is frequently decisive.
The short version: on-site reporting recovers hours, closes the risk window, improves accuracy, and strengthens your commercial position. The rest of this article covers how to actually do it.
Part Two: The Playbook
On-site reporting works when the preparation is done properly and the on-site sequence is disciplined. The following playbook is built around what consistently works in the field.
Before the Job: Kit Checklist
The right kit removes most of the friction that causes teams to abandon on-site reporting after a bad first attempt.
- Android tablet, 10 inch or larger. A phone works, but a tablet is significantly faster for data entry across dozens of findings. Rugged case recommended for switchroom environments.
- Power bank. A full inspection with continuous screen use will drain a tablet. Carry enough charge for the longest realistic job.
- Image transfer method sorted in advance. SD card reader, USB-C cable, or camera Wi-Fi, tested before you arrive. This is the single most common cause of on-site reporting failing on the first attempt.
- Offline capability confirmed. Switchrooms and plant rooms frequently have no signal. Confirm your reporting app works fully offline before relying on it.
- Stylus (optional but useful). Faster and more accurate than gloved fingers on a tablet screen.
Before the Job: Data Preparation
Ten minutes of preparation the day before saves an hour on site.
- Build or import the asset list. Asset IDs, locations, circuit descriptions, and component ratings entered ahead of time means you are selecting from a list on site rather than typing from scratch.
- Confirm reference temperatures. Set the correct reference for the standard you are working to (commonly 75°C for cable terminations under BS7671) so grading is automatic and consistent.
- Check the company profile and template. Logo, thermographer name and certification level, and the correct client template selected. This appears on every report page, so it is worth getting right once.
- Review prior inspection data. For repeat sites, having last year's readings available means you are trending in real time rather than discovering changes weeks later.
- Confirm expected load conditions. Coordinate with the site contact so the equipment will be at representative load during your inspection window.
On Site: The Sequence That Works
The sequence matters. Teams that try to capture everything first and report afterwards usually end up doing the reporting back at the desk anyway. The discipline is to report as you go.
The Panel-by-Panel Rule
If you take one thing from this playbook, take this. Complete each panel entirely before moving to the next: capture, import, tag, enter data, confirm grade. Do not batch.
Batching feels faster in the moment because you are not stopping to type. But it defers the work rather than removing it, and by the third or fourth panel you have accumulated a backlog that is easier to deal with back at the desk. That is precisely the failure mode on-site reporting is meant to eliminate. Teams that adopt the panel-by-panel discipline finish the report with the inspection. Teams that batch end up back where they started.
Part Three: Pitfalls and How to Avoid Them
Most teams that try on-site reporting and abandon it hit one of the following. All are avoidable.
Pitfall 1: Untested Image Transfer
The thermographer arrives on site, tries to get images from the camera to the tablet, and discovers the cable is wrong, the SD adapter is missing, or the camera Wi-Fi needs a firmware update. The inspection proceeds, the reporting does not, and the team concludes on-site reporting does not work.
Fix: test the full transfer path in the office before the first job, and carry a backup method.
Pitfall 2: Trying It First on a Difficult Job
A 400-point data centre survey is not the right place to learn a new workflow. The volume and pressure guarantee a poor first experience.
Fix: run the first on-site report on a small, familiar, low-pressure job. Build confidence, then scale up.
Pitfall 3: No Asset List Prepared
Typing asset IDs, locations, and component ratings from scratch on a tablet in a switchroom is slow and error-prone. Without preparation, on-site reporting genuinely does take longer.
Fix: always import an asset list, even a rough one. It can be refined on site far faster than it can be built there.
Pitfall 4: Assuming Connectivity
Plant rooms, basements, and switchrooms routinely have no signal. A workflow that depends on being online will fail exactly where you need it.
Fix: confirm full offline capability, including report generation, and let syncing happen later when signal returns.
Pitfall 5: Reverting Under Time Pressure
A job runs late, and the instinct is to shoot everything quickly and write it up later. This is understandable but it rebuilds the backlog you were trying to eliminate.
Fix: treat the report as part of the inspection rather than as something that follows it. The job is not complete until the report is generated.
Pitfall 6: Skipping the Summary Review
Generating the report without reviewing the inspection summary produces reports with missing data, incomplete entries, or grades that were never confirmed. Speed without a quality gate creates rework.
Fix: always review the summary before generating. It takes two minutes and prevents most revision requests.
Part Four: Scaling the Playbook Across a Team
An individual thermographer can adopt on-site reporting in a single job. Rolling it across a team requires slightly more structure.
Start With One Willing Engineer
Mandating a workflow change across an entire team creates resistance. Starting with one engineer who is interested, letting them run it on a few jobs, and sharing the results internally is considerably more effective. Once one engineer is finishing reports on site while colleagues are writing up at their desks, the argument makes itself.
Standardise the Templates First
Before rolling out widely, agree the report templates, reference temperatures, and remedial library language centrally. Otherwise each engineer builds their own variations and you lose the consistency benefit. Report consistency across multiple technicians is a topic in its own right and one we will cover separately in this series.
Build the Shared Remedial Library
Every fault description written from scratch is time lost. Capture the phrasing your team uses most, refine it once, and make it available to everyone. Over ten to twenty inspections this becomes one of the biggest single time savers in the workflow.
Review the First Reports Together
The first few on-site reports from each engineer are worth reviewing as a group. It surfaces inconsistencies early, spreads good practice, and gives newer engineers confidence that the faster workflow is not compromising quality.
Frequently Asked Questions
How long does it take to get comfortable with on-site reporting?
Most thermographers are productive on their first full inspection and comfortable by the third. The first inspection walkthrough covers the workflow end to end and is worth reading before the first attempt.
Does on-site reporting work for very large inspections?
Yes, and the panel-by-panel rule matters most on large jobs. For multi-day surveys, generate progressive reports at natural break points rather than holding everything until the end. The client receives documented findings continuously rather than waiting for the whole survey to conclude.
What if the client wants a different format than our standard template?
Configure a client-specific template once, and it applies to every subsequent inspection for that client. The setup cost is one-time; the benefit repeats on every job.
Is the on-site report the final deliverable, or a draft?
It is the final deliverable. The report generated on site is complete: cover page, methodology, executive summary, fault pages with images and data, load corrections, grades, remedial recommendations, and trending where available. If something needs changing afterwards, the inspection can be edited and the report regenerated in under a minute.
Do we still need a desk-based review step?
For most jobs, no. Some teams keep a light review step for the first few months of adoption, or for high-value clients, which is reasonable. The distinction is that a review is a quick check of a finished report, not the multi-hour process of building one.
Make the Report Part of the Inspection
On-site reporting is not about working faster under the same workflow. It is about removing the desk phase entirely, so the report finishes when the inspection finishes.
Prepare the kit and the asset list. Work panel by panel. Flag Critical findings the moment they appear. Review the summary before generating. Deliver before you leave site. That is the whole playbook, and it holds whether you are a solo thermographer on a single board or a team running a multi-megawatt data centre survey.
Try SnapCor Free for 14 Days >>
New to SnapCor? Start with the installation guide. For UK enterprise thermography services, contact the TI Thermal Imaging team. For UAE and GCC enquiries, see Thermal Imaging UAE.
SnapCor is a thermographic inspection reporting platform built by TI Thermal Imaging. Reports are aligned to ISO 18436-7 and informed by BS7671 reference temperatures. All on-site inspection work must be conducted by qualified thermographers under appropriate safe systems of work and in line with site-specific electrical safety procedures.