What an AI admin system for a construction company actually includes
Strip away the sales language and an AI admin system for a construction firm is five or six boring pieces, connected. Capture takes in the site messages, photos and calls that already exist. Filing puts documents where they belong with names that mean something. Registers fill themselves from what was captured. Actions get chased without a human doing the chasing. Documents get drafted from the record instead of from a blank page. And a person signs off anything that leaves the building.
That is the whole system. None of the pieces is impressive on its own, which is rather the point: the value is not in any component but in the connections between them, the fact that a photo sent to a WhatsApp group at 10.15am ends up filed, named, in the diary and attached to the right register entry without anyone touching it again.
If you are evaluating a proposal, or a proposal is being made to you, this is the map to hold it against.
What are the pieces?
| Piece | What it does | What it replaces |
|---|---|---|
| Capture | Pulls site messages, photos, emails and call notes into one place | Copying and pasting out of WhatsApp, or losing it entirely |
| Filing | Names and files every document to an agreed structure | The Downloads folder, the camera roll, "final_v3_NEW" |
| Registers | Fills the diary, plant, delivery and quality registers from capture | The Friday-night retyping session |
| Chased actions | Reminds the person who owes an answer, on schedule | The director as the firm's human reminder engine |
| Drafted documents | Produces first drafts of letters, minutes and reports from the record | Starting every document from a blank page |
| Human sign-off | A person reviews anything sent externally | Nothing. This was always there and must stay |
Two observations about the table. First, every row replaces labour that is currently done in the evening, which is why the honest business case is measured in reclaimed hours rather than anything grander. Second, the rows are in dependency order. Registers cannot fill themselves without capture; documents cannot be drafted from a record that does not exist. Firms that buy row four without building row one get a chatbot with amnesia.
Why does filing deserve its own line?
Because filing is the piece that wins bigger work, and it is the piece most firms skip as too dull to specify.
Larger clients and public frameworks increasingly expect information managed along the lines of ISO 19650, the standard behind the UK BIM Framework: agreed naming conventions, a common data environment, documents that can be found by someone who did not file them. Professional guidance from RICS points the same way on document control. A small contractor whose files already follow a sensible ISO 19650 style structure walks into prequalification able to answer the information management questions with evidence rather than intent.
The automation angle is what makes this achievable for a ten-person firm. Nobody is going to hand-rename three hundred photos a month to a naming convention, and nobody should. A system that names and files on capture makes the standard free at the point of use, which is exactly what a properly structured SharePoint CDE setup does. The structure is designed once; the machine enforces it forever.
Where do the registers get their data?
From the traffic the firm already generates, which is the part most people find hard to believe until they watch it.
A working site produces a continuous stream of evidence: the 7.42am photo of the delivery, the message about the blocked access, the voice note about the variation, the 4.55pm "all off site, gate locked". Today that stream lives in group chats and dies there, despite being a project record in everything but format. Capture turns the stream into entries; the registers are simply views of those entries. The site diary is the day's entries in order. The delivery register is the entries tagged as deliveries. The quality register is the photos tagged to inspections.
Which means the register-filling piece is not really an AI writing fiction into your records. It is sorting and summarising things humans actually said and photographed, with the source attached to every line. When a summary is wrong, the fix is one tap: the human corrects it, the correction is logged. That distinction, generated from evidence versus generated from nothing, is the one to interrogate hardest in any demo you are shown.
What does the system deliberately not do?
It does not price work, decide margin, assess commercial risk, or send anything of consequence without a human approving it. It does not have difficult conversations. It does not pretend to be a person on the phone or in writing. And it does not replace the judgement of whoever runs the firm; it removes the clerical silt that stops that judgement being applied to more than one thing at a time.
It also does not need to arrive all at once. The sensible sequence starts with capture and filing, adds one register, then extends, the same shape as the three solutions every contractor should start with. Document drafting comes last, because drafting from a record is only as good as the record.
Held against this map, most offerings reveal themselves quickly: some are one piece sold as the whole, some are the pieces without the connections. The whole thing is unglamorous plumbing, honestly described. But plumbing is what lets a ten-person contractor run the information discipline of a fifty-person one, and that gap is where the next tier of work gets won.