- A report closes on site only when findings, photos and measurements are captured together as you go.
- The structure has to be decided before the visit, not invented while you write up.
- Client, project and asset details entered at the start remove most of the retyping later.
- The export has to run from the device you carried, leaving no desk step behind.
- Pro entitlement is verified periodically, and that check needs a connection.
What has to be true before a report can close on site
You can finish an inspection report on site when three things are true. Every finding was captured with its evidence as you went, the report structure was decided before the visit, and the export runs from the device in your hand rather than a desk. Miss one and the report follows you back to the office. The evidence half of that is the harder part, and keeping photos linked to their findings is where most visits fall back to a desk.
- One record holds the checklist results, notes, measurements, photos and signature
- Each photo and measurement is attached to the item or finding it supports
- The template, sections and required fields were decided before the visit
- Client, project and asset details were entered once at the start
- The export runs in the app, with no desktop step afterwards
- Pro entitlement was confirmed while there was still a connection
What can genuinely close on site, and what cannot
Most workflows that claim to close on site only close the capture half. Name every step between the last finding and the file the client receives, then ask which step needs a desk or a signal.
Paper, a camera roll and a laptop move work rather than remove it. If a lack of signal pushes a step back to the desk, that is covered in offline inspection app. The structure matters the same way, because a form that does not carry the fields you need sends work back to a desk, which is the difference checklist software compared with inspection report software turns on.
| Approach | What it needs on site | What is left for the desk |
|---|---|---|
| Printed checklist and pen | Paper, pen and camera | Retyping notes and matching photos to items |
| Camera roll and a document afterwards | Camera and notebook | Choosing where photos go, then writing from memory |
| Laptop carried to site | Power and a flat surface | Formatting if the template is desktop-bound |
| Inspection Report (ours) | Phone or tablet, measurements entered in the record | Nothing: with Pro the report is generated from the record |
A field-to-report example: pump baseplate at a treatment works
You are recording a visual inspection of a horizontal pump and motor set, asset P-104, at a wastewater treatment works. The template is a rotating equipment check with Pass, Observation, Fail or N/A results, and the client, project and asset details were entered before you left.
At the pump the baseplate and holding-down bolts are recorded as Fail: rear feet on a collapsed shim pack, grout cracked along roughly 400 mm of the north edge, water tracking underneath. Two photos, of the rear left foot and the cracked grout, are captioned and linked to that finding. The gap under the front right foot is entered as 2 mm, with the recommendation to re-shim, regrout and reinspect before the pump returns to service.
The shift supervisor reviews the summary and signs. The inspection was saved locally as you worked, and with Pro the branded PDF and Word copy are generated from that record. Dictation is the other shortcut on a walk like this, and voice notes in inspection reports covers the review step that keeps it reliable.
How Inspection Report handles this
Inspection Report is a mobile app for iPhone and Android built around one inspection record. Guided checklists and a custom checklist builder keep the structure consistent, photos are captioned and linked to items or findings, measurements carry explicit units, and client, project and asset details are captured once. Findings can be resolved or reopened while keeping their history, and earlier report revisions stay separate from later corrections.
Records and photographs are stored locally, so field work continues without a connection. With Pro, a branded PDF report and an editable Word copy are generated from the captured record. Pro is $9.99 a month or $79.99 a year, and the free tier allows a limited inspection allowance, three starter templates and report preview.
Where it is not the right tool: it does not assign work to other people, it has no team dashboards or user seats, and it does not attach project documents such as specifications. It records what the inspector enters and does not certify equipment. Purchases and periodic Pro verification need internet, so confirm Pro before a visit with no signal.
What still needs a desk
Three situations still pull a report back to a desk, and it is better to know them before promising a client a same-day document.
If the client's layout is bespoke for every job, the editing happens somewhere, whatever tool captured the data. If the report needs a long narrative discussion rather than structured findings, that writing is a desk job. If several people review the document before it goes out, the review chain is the delay, not the app.
The honest split is to capture everything on site, export from the device and edit the copy. An editable Word export exists for exactly that reason.
Test it on one real inspection
Take one real inspection, not a demo, with a mix of results, at least one photo-linked finding, a measurement and a signature. Run the whole path on the device you actually carry: capture, review, sign, export, timed from the first finding to the customer-ready file.
If the report was finished before you left the site, the workflow fits. If a step followed you home, you have found what to fix, and the same visit is worth repeating against a second app.
Run that one inspection this week, capture through export, and write down the time. If more than one tool is in the running, what to test before choosing inspection software sets out a script you can run on the same visit.
