Submittal Review Agent · Use case
How can a design team use an AI agent to check a submittal against the specification on its own infrastructure?
A submittal review agent reads one contractor's or supplier's submittal, sets it against the project's specification, and lists each departure, with the clause and the place in the submittal. The designer accepts, comments or rejects. The agent approves no design and no product, gives a submittal no status and returns nothing to the contractor.
Every submittal is read twice.
Once just to find what departs.
- ✗ 01A submittal arrives as product data, drawings, calculations and certificates, and a designer reads all of it against a specification that runs to hundreds of clauses.
- ✗ 02A departure found after the product is ordered or built in costs far more than one found at review, and reviews queue while the programme runs.
Where it stops for a person
Always. The designer accepts, comments or rejects.Always. It compares documents, it does not design: it does not judge whether a departure is acceptable, whether a product is equal to the one specified, or whether a calculation is right. Acceptance, comment and rejection belong to the designer, and responsibility for the design stays where the appointment puts it.
It lists each departure.
The designer decides.
Step · 01
A designer or a document controller uploads the submittal and names the specification section.
Step · 02
The agent reads the submittal: the product, its stated performance, the standards it claims and the documents supplied.
Step · 03
It sets them against the specification, one clause at a time, citing each.
Step · 04
It lists each departure, each requirement the submittal does not address, and any entry it could not read with confidence.
Step · 05
The designer checks the list against the submittal, and accepts, comments or rejects.
Reads from · connectors
The submittal and its attachments, as uploaded files, and the project's specifications and the standards the company holds, indexed as a knowledge source. No operational system.
Acts through · MCP servers
Nothing. It sets no status on a submittal, changes no document and sends nothing to a contractor or a supplier.
What you set up
- Index the project's specifications, and the standards the company holds, as a knowledge source.
- Tell the agent which documents each type of submittal must carry.
- Build the agent in Katonic Studio and test it on submittals your designers have already reviewed.
- Publish it to one design team, one specification section 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. Specifications, drawings and suppliers' documents 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 approve a submittal?
No. It lists where the submittal departs from the specification. The designer accepts, comments or rejects.
Does it say whether a product is equal to the one specified?
No. It shows the difference and the clause. Whether the product is acceptable is the designer's judgement.
Does it reply to the contractor?
No. It has no tool that sends anything. The designer's response goes out through your own process.