How to Document Inspection and Plan Review Decisions So They Hold Up

Short answer: if a permit, plan review or inspection decision ends up in court, the records made at the time usually carry the most weight. Write down each decision, the code section behind it and the date, keep the photos and correspondence unaltered, and store them so you can show later that they haven’t been edited since. Building officials who have been sued often say the same thing: the written trail was what won the case.

Disclosure: I’m Inna Hall, co-founder of TimeBinder, a tool that timestamps files. This page is general information, not legal advice. Follow your jurisdiction’s records-retention rules and your attorney’s advice.

Why contemporaneous records matter

Lawsuits over permits and inspections often arrive years after the work. By then memories have faded and staff have moved on. A note written on the day, citing the code section and the reason, is far more persuasive than a recollection in a deposition. It also answers the most damaging allegation, that a decision was arbitrary.

What to record for each decision

• The date, address, permit number and who made the decision.
• The code edition and section relied on, quoted or cited.
• What was approved, denied or required, and why.
• Which plan sheet or revision you reviewed. Record the revision date or number, not just “the plans”.
• Who was told, how, and when, with copies of letters or emails.

Inspection photos and field notes

Keep original photo files, not just copies pasted into a report. Originals keep their camera metadata, and they can be compared later against any copy. Note what each photo shows and where it was taken. Don’t crop or edit originals. If you need a marked-up version, save it as a separate file.

Showing records weren’t changed later

In a dispute, the other side may ask whether a note or photo was created later or changed. Some ways to answer that:

• A permitting system with an audit log that records who changed what and when.
• Emails sent at the time, which carry server dates outside your control.
• A cryptographic hash (a SHA-256 fingerprint) of each file, recorded when you save it. Any change to the file changes the hash. You can check one with our SHA-256 file hash checker.
• An independent timestamp on that hash, so the date doesn’t depend on your own computer clock. Agencies use the same step when timestamping permits and other public records.

Our guide on proving files are genuine covers the same ideas for photos and video.

For architects and designers

The same habits protect the design side: keep each issued drawing set and revision, record what was submitted and when, and keep the comments you received. If a dispute turns on what the plans showed at permit time, a dated record of the exact file set answers it. See our design file timestamping guide.

What a timestamp does and doesn’t do

TimeBinder hashes your files locally in your browser, so the files are never uploaded. It anchors that fingerprint to Bitcoin and issues a Proof of Time Certificate. That gives you verifiable evidence of when a file existed: you can show that the file existed no later than the anchor date and still matches its fingerprint.

It doesn’t show who made the file, whether the decision was right, or that the photo shows what you say it shows. It also doesn’t replace your jurisdiction’s official records system or retention rules.

The free plan includes 1 Token a month, and one TimeBind covers up to 10 files. See pricing.

Sources were checked on 28 October 2026.