← Field notes

How to photograph defects so the report almost writes itself

31 July 2026 · 7 min read · Aiman Salem

The photographs are the part of an inspection you cannot go back and redo. Notes can be rewritten from memory the same evening and usually survive it. A photograph that does not show where it was taken, how big the thing in it is, or which wall you were facing is simply lost — and you will not find out until you sit down to write, by which point the site visit is over.

Most of the time lost writing a report is not writing. It is looking at forty-one photographs and trying to work out what half of them were for. What follows is the set of habits that removes that step.

Shoot in threes: context, subject, scale

For every defect worth reporting, take three frames in the same position, in the same order, every time.

Context — stand back far enough that the photograph identifies itself. The corner of a room, a window, a doorway, the end of a wall. This is the frame that answers "where is this?" without needing your notes. It is the one people skip, and it is the one that costs the most when it is missing.

Subject — the defect, filling the frame, square-on rather than at an angle. Cracks read very differently on the diagonal; a photograph taken at forty-five degrees to a wall makes a 2 mm crack look like a 5 mm one and makes the step in a fracture almost impossible to judge.

Scale — the same shot with something of known size in the plane of the defect. A crack gauge if you carry one, a tape, a coin, a pen. In the plane matters: a tape held 200 mm in front of a wall is not a scale, it is a distraction. If you use a crack width gauge, photograph it seated in the crack rather than beside it.

Three frames per defect sounds like a lot until you count the ones you currently take of the same crack from six slightly different angles because none of them looked right.

Give every photograph a location before you move

The single habit that changes report writing most is fixing location at the moment of capture rather than reconstructing it afterwards. Whatever the mechanism — a marker dropped on a floor plan, a spoken note, a number written on a pad — do it before you take the next photograph, not at the end of the room.

Direction matters as much as position. "Crack to the north wall of Bedroom 2" is a location. A dot on a plan is half a location: it tells the reader where you stood, not what you were looking at. If your marker can carry a direction, set it. If it cannot, say the direction out loud in the note attached to the photo. A reader following your report around the building six months later, possibly in a dispute, is trying to stand where you stood and see what you saw.

Photograph what is not there

Inspection reports get read hardest at the points where they are silent. If a subfloor was not entered, photograph the access hatch — closed, obstructed, or too small. If the roof space could not be reached, photograph the manhole and whatever was in front of it. If a room was full of stored goods, photograph the stored goods.

This is not defensive padding. A limitation with a photograph beside it is a fact about the building. A limitation in prose alone reads, to a lawyer, like an excuse written afterwards. It takes four seconds on site and it is the cheapest protection in the whole job.

Caption on site, in fragments

Captions written on site are worth several times captions written that night, and the difference is not effort — it is that on site you are describing something in front of you, and at home you are describing a photograph.

They do not need to be sentences. "NE corner, master bed, diagonal crack from window head, ~3mm, no displacement" is a better caption than anything you will reconstruct later, and it takes eight seconds. Fragments are fine. Measurements are the part that cannot be recovered.

Record the number you measured, not an impression of it. "Hairline", "moderate" and "significant" mean different things to different readers and none of them survive cross-examination. A number and the tool you measured it with does.

Consistency beats quality

Two practical settings, and then stop thinking about the camera.

Turn the flash on indoors, including in daylight. Interior walls near a window are almost always backlit, and a backlit crack disappears. Fill flash at 300 mm from a wall flattens the texture that hides fine cracking.

Shoot everything in the same orientation, and prefer landscape. Mixed portrait and landscape photographs are the reason report layouts look untidy, and correcting them later is manual work that produces nothing.

Resolution is rarely the problem. A modern phone photograph is far more detail than any report needs and far more file size than any report wants — a job with thirty full-size photographs can run to well over a hundred megabytes before anyone has written a word. Sharpness at the subject distance matters; megapixels do not.

The order you shoot in is the order you will write in

Work the building in a fixed route and keep to it — exterior clockwise from the front, then interior room by room in a consistent direction, then roof space, then subfloor, then services. The same route every time, on every job.

Two things come out of this. Your photographs arrive in the order the report needs them, so sequencing stops being a task at all. And the route itself becomes the checklist: when you always finish at the subfloor, the day you did not enter the subfloor is obvious rather than forgotten.

Where the software fits

Nothing above depends on any particular tool. All of it is faster with one that captures the caption and the plan location at the same moment as the photograph, because the cost of these habits is almost entirely the friction of recording them — and that is the part worth automating.

reportai.au's field capture is built around exactly this loop: photograph, caption, marker on the plan with a direction, next. It works offline, because the places where photographs matter most tend to be the places with no signal. The free plan covers plan upload, marker pinning, photo annotation and offline export, at up to five photos per report; the paid plan raises that to thirty and adds cloud storage, so a job captured on a phone can be opened in the report builder afterwards.

Written for practising inspectors and engineers. This is general guidance about documenting an inspection, not engineering advice about any particular building. reportai.au is software for writing reports — it does not carry out inspections, and it does not certify anything. Professional judgement stays with the person who signs the report.

More field notes · What reportai.au does · Pricing

Home · Pricing · FAQ · About · Field notes · Contact · Create an account · Sign in · Terms · Privacy · Refunds

reportai.au is a report documentation tool. It does not carry out inspections, does not assess or certify the condition of any building, and does not provide engineering services. Reports are AI-assisted drafts prepared for the inspecting engineer to check, correct, and sign off. All professional judgement remains yours.

Aiman Salem, trading as ReportAi.au · ABN 95 973 765 172 · admin@reportai.au · Prices in Australian dollars.