- State the failed item in plain language, with its location and how far the failure extends.
- Name the requirement it breaches, from the standard or the client's criteria.
- Attach the evidence to the item: a captioned photo, a measurement, or both.
- Give the reader a next step, written as a recommendation rather than a concern.
- Record the date and status so a reinspection can see what has changed.
The short answer
Document a failed inspection item in plain language: state the requirement it breaches, attach the evidence that shows the failure, and give the reader the next step. A result of fail, a written finding, a captioned photo, any measurement and a recommendation make the item unambiguous. Add the date and the status, and keep the record available for reinspection.
Below is the difference between a fail and an observation, the lines every failed item needs, and where the report stops and your own follow-up process begins.
- Unambiguous language: what failed, where it is, and how far it extends
- The requirement it breaches, from the standard, specification or the client's own criteria
- Evidence: a captioned photo, a measurement, or both, attached to the item
- A stated result, so the item reads as a fail rather than as a concern
- A next step the reader can act on, written as a recommendation
- A date and a status, so a later reinspection can see what changed
- Honest scope: what could not be accessed or verified
What 'fail' has to mean
A fail is not a strong opinion. It is a statement that a specific item does not meet a specific requirement, written so that a reader who was not there can check it.
The difference between the result options matters. Pass means the item met the requirement at the time of inspection. Observation means something worth watching was noted but no requirement is breached. Fail means a requirement was not met. N/A means the item was not applicable or could not be accessed, which is not the same as a pass.
Choosing between observation and fail is the judgement call inspectors make most often, and the one most likely to be questioned later. The test is simple: can you point to the requirement the item breaches? If you can, it is a fail. If you cannot, it is an observation, and it should be written as one rather than left to look like a fail. Where the failure is a safety condition, the record also needs who was exposed and the severity, which is what a construction safety inspection app must capture.
The five lines a failed item needs
A failed item can be short, but it cannot lose any of these.
- What failed: the component or item, named the way the client names it rather than in shorthand
- Where: the location, room, level or device reference, so the item can be found again
- What it breaches: the requirement from the standard, specification, manufacturer instruction or the client's own criteria
- The evidence: a captioned photo, a measurement with its unit, or both, attached to the item
- The next step: what should happen, and anything the reader needs to know about urgency
A worked example: the emergency light that failed
The example is a monthly check of the escape lighting in a two-storey office. One luminaire, at the west stair landing, is tested and the lamp goes out well before the duration recorded in the site's maintenance schedule.
The finding is written as: the emergency luminaire serving the west stair landing failed to illuminate for the required duration during the monthly test. It remained lit for approximately 22 minutes against the 90 minutes recorded in the maintenance schedule for this unit. Photographs show the luminaire before and after the test, and the measurement is the 22 minute duration.
The recommendation is to replace the battery pack and retest the unit, and the item is left recorded as a fail with the date of the test. Wording like this can be dictated at the item and reviewed before you leave site, which is the review discipline voice notes need. The report does not announce that the building is non-compliant, because that is not the inspector's call to make in a maintenance record. It states what was tested, what happened, and what the reader should do about it.
This is where a report and a tracking system get confused. The report communicates the failure. It does not decide who fixes it, order the part, or check that the work was done. Those steps belong to the reader's process.
Where the report stops and your process starts
A failure that is documented well is easy to act on, and the acting is still somebody's job. The table separates what the report can carry from what happens after it is sent.
| Step | What the report provides | What happens outside the app |
|---|---|---|
| Identify the failure | The result, the finding and its location | Nothing further; the inspector has recorded it |
| Show what it breaches | The requirement text entered against the item | Someone confirms it against the current rulebook or specification |
| Show the evidence | The captioned photo and any measurement | Nothing further at this stage |
| Agree the next step | A recommendation written into the finding | The client, landlord or supervisor decides and instructs the work |
| Assign and chase the work | Not something Inspection Report does | Your own process: a work order, a tracker or an email chain |
| Confirm it was fixed | Inspection Report records the item again on reinspection and keeps the history | The report documents the outcome; it does not verify the repair for you |
How Inspection Report handles this
Findings can be recorded with supporting evidence, due information and status, then resolved or reopened later while preserving their history. Photos can be captured or imported, captioned and linked to checklist items or findings, and measurements are recorded with explicit units. Result options include pass, observation, fail and N/A, the inspection keeps client, project and asset details, and issued report revisions stay separate from later corrections. If the photo is likely to be the main evidence, inspection report app with photos covers keeping it attached to the item.
Inspection Report does not assign corrective actions to people, schedule the work or chase it to completion, and it does not certify compliance. It records the judgement the inspector made, with the evidence for it. A reinspection returns to the same asset and item so the history is available, and the report documents what was found on each visit.
If your process needs work orders, owners and deadlines tracked to closure, that lives outside this app. If you need the failure recorded properly, evidenced and exported, Inspection Report is built for it, and an inspection report example shows how a failed item reads inside the finished document.
Write up one failed item properly
Take the most recent failed item on your books and check it against the five lines above. Most weaknesses in the write-up are a missing requirement or a missing next step rather than a missing photo.
Then run one real inspection from capture through export and time it, and read the failed item back as the client would. If the client would have to ask what happens next, the recommendation is the part to fix. Writing an inspection report without Word covers removing the retyping step from that workflow.
