Handover Document Check Agent · Use case
How can a project team use an AI agent to check the handover documents for a building on its own infrastructure?
A handover document check agent reads the register of documents supplied for a building, sets it against the contract's list of what must be handed over, and lists what is missing, out of date or unsigned, with the item on the list. The project manager accepts the handover. The agent accepts nothing, signs off no inspection, issues no certificate and submits nothing to an authority.
The building is finished.
The documents often are not.
- ✗ 01A building is handed over with thousands of documents: manuals, test certificates, warranties and as-built drawings, from dozens of subcontractors.
- ✗ 02The team that will run the building finds what is missing months later, when a warranty is needed or an inspection falls due.
Where it stops for a person
Always. The project manager accepts the handover.Always. It checks that a document is there, not that it is right: it does not judge a test result, a drawing or a certificate. Acceptance of the handover is the project manager's, the inspections and certificates behind it are signed by the people the contract and the law name, and what a building's safety record must hold is its duty holder's decision.
It lists what is missing.
The project manager accepts the handover.
Step · 01
A project manager or a document controller names the project and the contract's handover list.
Step · 02
The agent reads the document register: each document, its type, its revision, its date and its status.
Step · 03
It sets the register against the list, item by item, by system and by subcontractor.
Step · 04
It lists each item with no document, each document that is unsigned or superseded, and each warranty with no start or end date.
Step · 05
The project manager chases what is missing and accepts the handover.
Reads from · connectors
Your own APIs
The document register, read through your own APIs with the operations that change something left out, or as an uploaded export, and the contract's handover list and the employer's requirements indexed as a knowledge source.
Acts through · MCP servers
Nothing. It changes no document's status, uploads nothing to the register and sends nothing to a subcontractor.
What you set up
- Index the contract's handover list and the employer's requirements as a knowledge source.
- Import the description of the API that holds the document register and keep only the operations that read, or start with an uploaded export.
- Build the agent in Katonic Studio and test it on a project already handed over, whose gaps you know.
- Publish it to one project team first.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. As-built drawings and building records stay inside the company.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does it accept the handover?
No. It lists what is missing. The project manager accepts the handover.
Does it check that a certificate is valid?
No. It checks that the document is there, signed and current. Whether a test or an inspection passed is for the person who signs it.
Does it send anything to a building authority?
No. It has no tool that reaches an authority's system. Your team makes every submission.