Scaffolding Inspection Records: A Digital Form and AI Summaries

Use a form with fixed fields, photos and a named competent person, store every entry in one register that flags overdue scaffolds, and let AI summarise only completed, signed records. The summary can count, group and highlight; it must never say a scaffold is safe, because only the competent person's inspection and signature can.

Paper registers fail in familiar ways: a missing weekly entry nobody notices, a photo that lives on one phone, a clipboard soaked by rain. A digital form fixes the first two by making the next due date visible and the photos part of the record. It does not fix competence. The inspection still depends on a person who knows what to look for, and nothing below changes that.

Follow me on Instagram@sagnikteaches

Start with the rules you work under

Scaffold inspection rules differ by region and by type of scaffold, so the form has to follow yours, not mine. The guidance I checked agrees on the outline: a competent person inspects before first use, again at a set interval, and again after events that could affect stability, such as high winds or an alteration. The interval differs. One regime asks for an inspection before each work shift; another asks for one at intervals of no more than seven days. Published summaries list the same core report fields: date and time, location of the scaffold, details of the inspection, defects found, actions taken, and the competent person's name and signature. I found no single retention period, so ask your regulator or adviser how long records must be kept.

Connect on LinkedInSagnik Bhattacharya

Two questions need answers before you build anything. Which interval and triggers apply to each type of scaffold you erect? And does your regime accept an electronic signature on the report? If either answer is unclear, settle it first, because a wrong guess produces a record that doesn't count. Rules typically define a competent person by training and experience and, in some places, by the authority to take corrective action. The form records who signed; whether that person qualifies is a matter for your training records.

Subscribe on YouTube@sagnikteaches

The form: fourteen fields and why each is there

A form earns its keep when people can complete it in a few minutes with cold hands, so every field is a dropdown, a tick, a date or a short note wherever it can be. Start from your current paper form or the standard you build to, add nothing a competent person doesn't need, and drop nothing your rules ask for.

Field 6 is where scaffolders' own knowledge belongs. A typical checklist (illustrative, so replace it with yours) asks whether base plates and sole boards are sound, standards are plumb and joints secure, ledgers, transoms and bracing are complete, ties are present and tight, working platforms are fully boarded and secured, guardrails and toeboards are complete on every working lift, access ladders or stairs are secure, the loading or status tag is displayed, there are no overhead hazards, and nobody has altered the scaffold since the last inspection. Don't ask the AI to invent this list; at most, ask it to tidy wording you already have.

Field 11 deserves care. A dropdown of "Safe to use", "Do not use" and "Safe to use with restriction", with a text box for the restriction, forces a decision and leaves no room for "mostly fine". Make "Do not use" trigger an immediate message to the supervisor, and make sure the physical tag on the scaffold says the same thing as the form.

Photo evidence: what to shoot, how to name it, where it lives

Photos turn "I checked it" into something a supervisor, a client or an investigator can see. Keep the rule simple enough that a crew follows it every time: one photo of the scaffold's tag or ID, one wide shot of the elevation, and for every defect a wide shot plus a close one, taken before and after the fix. A clean inspection is then two or three photos, and a defective one is five or six.

Name every file with the scaffold ID and date, such as A12-2026-11-04-2, or make the form do it, so a photo can always be matched to its record. Photograph the scaffold from the position of a person using it, not from the other side of the road, and avoid people's faces in shot. Where the form lets you take the photo inside it, use that, because the time then comes from the scaffold, not from a gallery tidy-up later.

Storage is where digital records quietly fail. Take an illustrative yard with 18 live scaffolds on a seven-day cycle. That is about 78 scheduled inspections a month (18 × 52 ÷ 12), plus roughly 6 handover inspections on new scaffolds and 12 after wind or alterations: 96 entries. At two photos each and about 3 MB a photo (check your own phones), that is 192 photos and some 576 MB a month. A free tool that stores 100 MB fills in about five days. One that stores 1 GB lasts about seven weeks. So decide at the start where the photos live, how you export them, and who checks that the export happened.

Keep originals. A cropped, compressed or annotated copy is useful for the summary, but the record should keep the photo as taken. If photos are stored in a form tool, export both the entries and the images regularly to storage you control, and test that you can open an old export before you ever need to.

Where the form lives: Google Forms, Jotform or a dedicated app

Three kinds of tool fit a small scaffolding yard. These are the figures on the vendors' own pages as I read them in November 2026; check them again before you commit.

The decision rule I would use: if you already live in Google or Microsoft tools and have fewer than five competent persons, start with a form and a sheet, because the register in the next section is easy to build there. If photos and signed reports are the daily pain, or you have more than a handful of inspectors, trial a dedicated inspection app for two weeks. Mitti's pricing page I read doesn't list inspection scheduling or reminders, so confirm those features directly before you rely on them for overdue alerts. The comparison of scaffolding business software against a spreadsheet plus AI goes into the wider yard-management question.

Overdue alerts: a register that speaks up before an auditor does

The form records what happened. A register records what should happen next. Keep one row per live scaffold in a second tab, and let formulas read the form's responses to find each scaffold's last inspection, work out the next due date and show a status. Nobody types the status, so nobody can forget to.

Say the responses tab holds the scaffold ID in column B and the inspection date in column C, and the register has the ID in column A, the interval in days in column E and a "Closed" flag in column I. The formulas for row 2 then read:

F2 (Last inspected):  =MAXIFS(Responses!C:C, Responses!B:B, A2)
G2 (Next due):        =F2+E2
H2 (Status):          =IF(I2="Yes","Closed",IF(F2=0,"NEVER INSPECTED",IF(G2<TODAY(),"OVERDUE",IF(G2=TODAY(),"DUE TODAY","OK"))))

MAXIFS is available in Google Sheets and in recent versions of Excel. Colour OVERDUE and NEVER INSPECTED red, and DUE TODAY amber, with conditional formatting. Test the sheet with three dummy rows before you trust it. On Friday the 8th a small register reads like this (illustrative):

D01 is two days late, and E09 is the sort of entry a paper register hides: a scaffold erected and handed over with no first inspection on file. Whether the formula's seven days is right depends on your rules, and if they ask for an inspection before each shift, the interval and status logic change. Events don't need special handling: an inspection after high winds is another response row, so the last-inspected date and next due date move on by themselves.

A register nobody opens alerts nobody. The cheapest alert is a morning routine: the foreman opens the register's filtered view of DUE TODAY and OVERDUE before the first lift is used. A step up is a daily email of those rows, which a short script on a daily trigger, or your automation tool's schedule step, can send. Ask the AI to write the script if you are comfortable testing it on dummy data first. Then agree an escalation ladder: DUE TODAY goes to the site foreman at the start of the day; OVERDUE goes to the foreman and supervisor at once; still open after 24 hours goes to a manager. Treat an overdue scaffold as out of use until a competent person has inspected it.

Where AI helps, and the line it never crosses

AI is good at reading a week of records and telling you what repeats. It is not an inspector, and four rules keep it in its place.

1. Records first, AI after. No AI step sits between the scaffold and the signature. The competent person inspects, fills in the form and signs. Summaries are made afterwards from what is already on file.
2. Signed records only. An unsigned entry goes on an "Unsigned" list, which a formula can build, and never into the summary as if it were complete.
3. No safety verdicts. The summary quotes the "Result" field exactly as the competent person recorded it. It never writes safe, unsafe, compliant, approved, passed or certified in its own voice.
4. A person reads it, and acts from the original. Anything marked "Do not use" is handled from the original record and photos, never from a summary of them.

The same principle runs through the series: AI drafts, a person signs. The tutorial on whether AI can design a scaffold draws the line for design work, and the electrical RAMS tutorial does it for method statements.

Prompt: the weekly summary, with a draft and what we cut

Export the week's signed records as a table, then paste them under this standing instruction (remove personal details you don't need first).

You summarise a week of scaffold inspection records for [COMPANY NAME]. Use only the table below.

Rules
- Report counts, repeated defects and unsigned entries. Quote each Result exactly as recorded.
- Never write that a scaffold is safe, unsafe, compliant, approved, passed or certified in your own words.
- Do not say whether any inspection was on time or overdue; the register does that.
- List every unsigned record under UNSIGNED, with scaffold ID and date.
- Cite scaffold ID and date for every statement.
- Start with: WEEKLY INSPECTION SUMMARY (draft for the competent person's review; not an inspection).

TABLE
[paste the records]

This week's records look like this (illustrative):

ID  | Site | Date  | Reason       | Result        | Defect found             | Action                      | Signed
A12 | S3   | Mon 4 | Scheduled    | Safe to use   | None                     |                             | CP1
A14 | S3   | Mon 4 | Scheduled    | Do not use    | Loose ledger, lift 2     | Barred off; replacement due | CP1
A14 | S3   | Tue 5 | After repair | Safe to use   | None                     | Ledger replaced             | CP1
B03 | S5   | Tue 5 | Scheduled    | Safe to use   | Toeboard missing, lift 3 | Toeboard fitted             | CP2
B07 | S5   | Wed 6 | After wind   | Safe to use   | Two ties loose           | Ties re-tightened           | CP2
C02 | S8   | Wed 6 | Scheduled    | Safe to use   | Toeboard missing, lift 2 | Toeboard fitted             | CP3
C05 | S8   | Thu 7 | Scheduled    | Safe to use   | None                     |                             | (blank)

A typical first draft comes back like this:

WEEKLY INSPECTION SUMMARY (draft)
7 records across 3 sites. All scaffolds were inspected on time and are safe to use.
Four defects were found: a loose ledger on A14, missing toeboards on B03 and C02, and loose ties on B07. All were fixed.
Toeboards were missing on two scaffolds at different sites, which suggests a crew habit.

Three problems. "Inspected on time" is a claim only the register can make. "Are safe to use" is a verdict in the AI's own voice, and it overlooks that A14 was "Do not use" for a day. And C05 has no signature, so it should have been listed as unsigned, not counted as a clean inspection. The version that passes the four rules:

WEEKLY INSPECTION SUMMARY (draft for the competent person's review; not an inspection)
Records: 7 (6 signed; UNSIGNED: C05, Thu 7).
Results as recorded on signed entries: "Safe to use" on 5 entries; "Do not use" on A14, Mon 4, followed by "Safe to use" after repair on Tue 5.
Defects recorded: 4 entries. Toeboard missing: B03 lift 3 (Tue 5), C02 lift 2 (Wed 6). Loose ledger: A14 lift 2 (Mon 4). Loose ties: B07 (Wed 6).
Repeated defect: missing toeboards on two scaffolds at two sites in one week.

Notice what the better version does not say. It doesn't conclude that the crews are careless, because two entries are two entries. It doesn't judge the late sign-off. It flags the gap and leaves the next step, chasing whoever inspected C05 for the missing signature, to a person.

What a month of summaries shows that a clipboard hides

One week's summary tells you little. A month of them shows patterns, which is where the digital record pays back. Suppose (illustrative) four weeks of records hold 19 defect entries, and 7 of them are missing toeboards, mostly on one crew's scaffolds. That is 37 per cent of all defects from one cause. The response isn't blame. It is a short talk with that crew, a "last lift" tick on the handover checklist, and the same summary the following month. If the next four weeks show 2 toeboard entries in 15 defects, 13 per cent, the fix is working.

The AI's job in that exercise is narrow: group the defect categories and count them across four summaries you paste in, then say which category repeats and where. You still decide what to do, and the tutorial on toolbox talks and what a competent person must check covers writing the talk. The same habit works for reports that matter to clients: a monthly summary of inspections on time, defects found and defects closed is easy to produce from the register, and, as with the weekly one, you check it before it leaves the building. The fire protection tutorial on inspection reports and reminders uses a similar pattern for a different kind of recurring inspection.

Closing a scaffold's record and keeping what the rules require

A scaffold's record ends when it comes down. Add a closing entry with the dismantle date, set the register's Closed flag, and export that scaffold's inspections and photos into one folder or PDF. The register then stops flagging it, and the archive holds everything about it in one place.

Two points about keeping records. First, retention is set by your rules, not by your storage plan, so find out how long you must keep them and diarise the deletion date as carefully as the inspection date. Second, protect the originals: let only competent persons create entries, let supervisors view and export, and keep edits to a minimum, with a note whenever an entry is corrected, not overwritten. The AI should work on exports or copies. If you ever use it to assemble an audit pack for a client, check every page against the originals, because a pack built from summaries is only as good as the summaries.

A two-week pilot that shows whether the form works

Don't switch every site at once. Pick two sites and run paper and digital side by side for a week. Compare the two for each inspection: did the digital version capture everything the paper did, how long did it take, and what did the inspector say was awkward? Fix the form's wording and dropdowns, then run digital only on those sites for a second week and measure four things.

• On-time rate: inspections done by their due date, divided by inspections due. If 21 of 24 were on time, that is 87.5 per cent, and the three late ones need a reason each.
• Completeness: entries with photos, a result, a next due date and a signature. Aim for every entry.
• Time to complete: note it for five inspections. If a clean one takes more than a few minutes, cut fields or move to dropdowns.
• Unsigned entries: the number should be zero. Anything else is a process problem to fix before the AI sees a single summary.

Only when those hold should the weekly AI summary start. By then you will know which fields people skip, which defect categories need splitting, and whether the register's alerts reach the right phone. That groundwork matters more than the choice of tool.

Questions scaffolders ask about digital inspection records

Is a digital scaffold inspection record as valid as paper?

That depends on the rules you work under, so ask your regulator or adviser. What usually matters is that the record is complete, made at the time, names the competent person who signed, and can be produced when asked. Check whether an electronic signature is accepted, and keep a way to print a signed copy for the site.

Can AI decide whether a scaffold is safe to use?

No. A scaffold's status comes from a competent person looking at it, and that person's signature is the record. AI can summarise completed, signed records, group repeated defects and flag unsigned entries, but it should never mark a scaffold safe, unsafe or compliant. Put that rule in the prompt, and read every summary before anyone relies on it.

How many photos should an inspection record include?

Enough to show what the competent person saw: one photo of the scaffold's tag or ID, one wide shot of the elevation, and a wide plus a close photo for each defect. For a clean inspection that is often two or three photos. Name each file with the scaffold ID and date so it can be matched to the record later.

What should happen when an inspection is overdue?

The cautious approach is to treat the scaffold as out of use until a competent person has inspected it. Your register should flag the overdue entry, notify the person responsible, and escalate if it isn't cleared within a set time. Check whether your rules also require you to record why the inspection was late.

Further reads

• Can AI Draft a Scaffolding Hire Agreement? Terms a Solicitor Checks — Who inspects between erection and dismantle is a hire-terms question too.
• How to Quote Scaffolding: Elevations, Boards and Hire Periods With AI — The quote sets the hire period your inspection schedule runs across.
• Scaffolding Invoice Template: Erect, Hire and Dismantle Billing With AI — Bill the weekly hire lines the register already counts.
• Tree Surgeon Risk Assessment Template: AI Drafts, You Sign Off — Another trade where AI drafts and a competent person signs off.
• Roof Inspection Reports: Photos to a Customer-Ready Report With AI — Turning inspection photos into a clear report.
• Can Roofers Use Voice AI to Turn Inspection Notes Into Estimates? — Voice notes as a faster way to capture inspection detail.
• Emergency Lighting Certificate With AI: Test Log to Signed Paperwork — A worked emergency lighting test log, from site readings to a signed certificate: what AI can draft and what the competent person records and signs.
• How to Use Google AI Form Builder for a Builder's Site Visit Checklist — A walkthrough for a small building firm: draft a site visit checklist with Gemini in Google Forms, add sections and photo fields, and link a response sheet.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Jotform pricing page and Mitti pricing and home pages (read November 2026); Google Forms help on file uploads (respondents sign in to a Google account); published regulator and industry summaries of scaffold inspection triggers and report contents.