Keeping an eye on a place · 4 min read

Documenting a neighbourhood incident properly (without the hassle)

The phrase “document it properly” sounds like homework. It conjures spreadsheets, folders, and effort you don’t have when something’s just happened near a property you look after. So most people do a bit — snap a photo, send a text — and hope that’s enough. Sometimes it is. But the times it isn’t are exactly the times you’d have wanted the record: when an insurer asks, when a committee needs to decide, when a pattern only becomes clear months later.

Here’s the reassuring part: documenting an incident properly isn’t about doing more. It’s about capturing the right few things while they’re fresh, in one place, and then stopping. Done well, it takes minutes and leaves you calmer, not busier.

Capture facts, not theories

The most useful documentation is plain and factual. Describe what happened and what you can see — the behaviour, the damage, the timing — not who you think did it or why. This isn’t just good manners; it’s what keeps a record credible and useful. Speculation dates badly and helps no one, while “the rear gate latch was forced, screen bent, no entry, discovered 7am Tuesday” is exactly the kind of line an insurer or committee can work with.

The five things worth capturing

For almost any incident near a property, five things do the job:

• When — the date and time, or the window between last-known-secure and discovery.
• Where — specific to the property or the common area involved.
• What — a plain, factual description of the behaviour and any damage.
• Evidence — photos taken before you clean up or repair (wide shots, then close-ups), plus any footage neighbours offered.
• References — any police event or report number, and a note of who you told and when.

If you have those five, you’ve documented it properly. Everything beyond that is usually effort for its own sake.

Photograph before you fix

The one irreversible mistake is cleaning up or repairing before you’ve photographed. A tidied scene can’t be un-tidied, and a fixed latch tells no story. So the instinct to “sort it out” — which is strong, because a damaged property feels wrong and you want it right — is worth pausing for just long enough to take the photos. Wide shots to establish the scene, then close-ups of the specific damage. Two minutes now saves you from a claim or committee conversation where the only evidence is your description of something that no longer exists.

A worked example

Say you own a small shopfront that you lease out, and one morning the roller door’s been tagged and a side window cracked. Your tenant wants it cleaned and fixed before opening — understandably; graffiti on the door is bad for their business. Before the cleaner arrives, you spend five minutes documenting it properly: photos of the whole frontage and close-ups of the cracked window and the tagging, a note of the date and that it was found at 8am, the police reference your tenant obtained, and a quick check of whether the café two doors down (which has a camera facing the street) might have caught anything overnight.

Then you let the clean-up happen. When you lodge the insurance claim that afternoon, you attach the photos and the reference and it’s straightforward. A fortnight later, another shopfront on the strip is tagged, and because you documented yours cleanly, you can add a clear, dated data point to the conversation the local business owners start having with the council. The documentation didn’t take long, didn’t get in the tenant’s way, and quietly did its job twice. The key was doing it before the door was scrubbed — after that, it would have been your word against a clean roller door.

Keep it in one place, and know its limits

Documentation scattered across a camera roll, a text thread, and a note-to-self is barely documentation. The value comes from keeping the five things together, so that when someone asks, you produce one tidy account rather than reassembling it from fragments. And it’s worth being clear-eyed about what that account is: a support document that makes conversations smoother, not legal proof. A clean incident record for insurers and strata goes deeper on what a good support document looks like and where its limits sit.

It also helps to document against context. Seeing whether an incident is isolated or part of a run of similar reports nearby changes how you frame it — you can check the honest recorded context for the area around a property so your single, well-documented incident sits inside the bigger picture.

Proper, not perfect

The aim is documentation that’s proper, not perfect. Perfect never happens on a busy morning with a tenant waiting and a cleaner on the way. Proper — the five things, captured before the clean-up, kept in one place — happens in five minutes and holds up when it counts. Lower the bar to “proper and low-hassle” and you’ll actually do it every time, which beats an immaculate system you use once and abandon.