Field notes

Notes on certification, templates and the work around them

Short, practical writing for the people who inspect buildings and issue the paperwork afterwards. No trend pieces, no thought leadership — just things that came up with real teams.

New notes roughly every month

Templates & AI12 September 20264 min read

AI field detection still needs a human in the loop

Automatically spotting blank fields on a scanned certificate feels like magic the first time you see it. It is not magic, and treating it as magic is how teams end up with a template that quietly writes into the wrong box.

Layout detection works on visual evidence: whitespace, ruling lines, label wording, alignment. On a clean digital PDF it is usually right. On a photographed certificate with a shadow across the bottom third, or a form that was designed with two columns of uneven height, it can be confidently wrong.

The failure mode matters more than the error rate. A missed field is obvious — your report has a gap where a reading should be. A misplaced field is worse: the value lands a few millimetres off, prints over a label, or ends up in the adjacent row. Nobody notices until the customer does.

So the workflow we build for is detection followed by deliberate confirmation. AI proposes the boxes, you accept, resize or delete them, and you see the result rendered with real data before the template goes live.

A practical review routine

Render one real certificate from the template before you share it with the team.
Check the fields nearest page edges, logos and stamps — that is where detection drifts.
Scan the same template with a long value (a full site address) to catch overflow early.
Repeat the check whenever the source PDF is replaced with a new supplier version.

Housing28 August 20265 min read

What a void inspection actually needs to capture

Void inspections fail for a predictable reason: the report records what the inspector remembers, not what they saw. By the time the works order is raised, the evidence is a week old and the contractor disputes it.

A useful void report is room-by-room and evidence-first. Photograph the defect, record where it is, note the action. Anything that costs money later needs a picture taken at the time, from an angle that shows both the item and its location.

The second requirement is the boring one: meter readings, keys handed over, and the condition at handover date. These are the fields that get skipped on a clipboard and then block an invoice.

Capture on the device you already carry, then generate the PDF from the same record. Re-keying the notes into a desktop template is exactly where the discrepancies creep in.

Minimum evidence per room

One wide shot showing the room and its condition.
Close shots of each defect, with the location written next to it.
Readings on the day (gas, electric, water) where the property has them.
Key handover notes and any items left behind.

Workflow5 August 20263 min read

The real cost of retyping certificates

Nobody bills for the hour spent rebuilding a PDF. It just sits at the end of the day, unpaid, and it is the first thing that gets rushed when the diary is full.

Retyping has three costs. The obvious one is time: copying readings, addresses and customer details from notes into a document. The second is accuracy — every handoff is a chance to transpose a digit in a certificate number or miss a classification code.

The third is the one that hurts most in an audit: the trail. When a report is assembled by hand, there is no clean link between the inspection record and the document that was issued. If a customer queries a result six months later, answering them means finding the paper file.

A template that merges live data solves all three at once. The data is entered once, the document is generated from the record, and the issued certificate stays attached to the job it came from.

Want these by email as they are published? Ask us to add you to the list and mention which certificate types you work with.

Have a workflow worth writing about?

If your team has solved something awkward in the field, we would like to hear how. The best notes here started as customer conversations.

Share your workflow See what we are building