Why a described photo beats a vague text
A message that says "there's a leak near the lobby" starts a conversation, not a fix. Which lobby? How bad? How long has it been running? The person who can act now has to chase you for the basics — and every reply is a delay. A clear photo paired with a precise location answers those questions up front, so the work can be scheduled instead of investigated.
Photo evidence also outlives memory. Six weeks later, nobody recalls how bad the damage was on the day you found it, but a dated image does. When you document an issue with a described photo and a fixed point on a map, you're not just reporting a problem — you're creating a record that holds up when someone asks what happened, when, and whether it was dealt with.
What to capture: the problem, the scale, the location
Every solid maintenance record answers three things in pictures. First, the problem itself — a tight shot of the crack, the leak, the broken fixture, the damaged surface. Second, the scale and context — step back and show how big it is and what's around it, so a reader who has never been there understands the severity. Third, the location — enough of the surroundings that someone can find the exact spot without a guided tour.
Three photos usually beat one. A close-up proves the fault, a wider frame proves the scale, and a contextual shot proves where it is. Shoot in good light, get close enough that the detail is sharp, and avoid cropping out the reference points a reader needs. You're documenting for someone who wasn't there — give them everything they'd ask for.
Pin the location instead of describing it
Words like "by the back entrance" or "second floor, east side" mean different things to different people. A map pin doesn't. Dropping a pin on the exact spot removes the guesswork, and when the address auto-fills from that pin, you get a precise, consistent location on every report without typing it out or getting it wrong.
This matters most when you're managing more than one building, or a large site where "the usual corner" isn't obvious to a contractor seeing it for the first time. A pin plus an auto-filled address turns a vague direction into a place anyone can navigate to — and it's one less thing to clarify later. In SnagGrid you snap the photo, drop the pin, and the address fills itself in.
Write it up clearly — and factually
A photo shows the what; the write-up should give the where, when and how serious without padding. State the facts plainly: what you found, where it is, when you found it, and any safety concern that makes it urgent. Skip speculation about cause and blame — a record reads better and holds up better when it sticks to what's observable.
This is the step people rush, and it shows. In SnagGrid you jot down rough notes and the AI drafts a professional, factual report from them — but it never invents facts, and you approve every word before it goes out. You get a clean, consistent write-up that matches the photo, without staring at a blank form trying to sound official.
Send it to the right person, then keep the record
Documenting an issue only pays off if it reaches whoever can fix it. A report sitting in your camera roll, a group chat or a paper form helps no one. The point of capturing photo evidence is to route it to the right recipient immediately — with the images, location and write-up attached — so action starts the same day, not the next time someone scrolls back through the thread.
Then keep proof that it happened. SnagGrid emails the right recipient and logs everything to an audit trail, so you have a timestamped record of what was reported, to whom, and when. If anyone later questions whether an issue was raised or dealt with, the answer isn't your memory — it's a dated entry with the photos attached.
Don't let it stay broken: follow up
A report that's sent and forgotten is a problem that stays broken. The gap between reporting and resolving is where most issues quietly die — not because nobody cared, but because nobody was reminded. Documenting an issue well includes making sure it doesn't fall off the radar after the first email.
SnagGrid surfaces one-tap follow-up reminders, so an open issue keeps nudging you until it's closed out. For a team, the dashboard shows what's still outstanding across everyone, with roles, CSV export for your own records, and a scoped REST API with webhooks if you want to wire reporting into the tools you already run. The photo and the pin start the record — the follow-up is what finishes the job.