Finds where the drawings and the specification disagree
A construction information set is drawings, a specification, schedules and room data sheets — four documents describing one building, written by different people and revised at different times. They are supposed to agree. In practice a late change lands in one and not the others, because updating the drawing is what the meeting asked for and updating the specification is what somebody was going to do afterwards.
The contractor then prices the set. Where two documents disagree they price the cheaper reading — entirely reasonably — and the difference arrives later as a variation, at a moment with no competitive pressure on the price at all.
The other half is absence. A door on a plan with no entry in the door schedule. A finish code on a room data sheet appearing in no specification clause. A specified product with no location shown. Each is a question the contractor must ask, and every question is time; unasked, it becomes an assumption that surfaces on site.
A model can clash-detect geometry. Almost nothing checks whether the words agree with the drawings, and the words are where the money is.
This agent reads the set against itself and reports every contradiction and gap, ranked by cost exposure. It changes no document and makes no design decision.
When the price still has competition on it.
Each one costs time and invites an assumption.
Which is what everyone believes they issued.
Clash detection handles geometry. Almost nothing checks whether the specification agrees with what is drawn, and that is where the money is.
Where two documents disagree, a contractor prices the lower one. The difference returns as a variation with no competition on it.
A door on a plan with no schedule entry, a finish code in no clause, a product with no location.
A late change landing in one document. It is how almost every inconsistency is created.
A finish discrepancy across two hundred rooms outranks a bespoke item nobody will query.
Which document is right is the designer's call, with consequences for appearance, performance and compliance.
Why Architecture & Engineering in particular. Clash detection compares geometry; almost nothing compares the words. Where two documents disagree a contractor prices the cheaper one, and the difference returns as a variation with no competition on it.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Design Information Consistency Agent has no path to sending, spending or committing. That limit is why its output is safe to act on.
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.
Demo dataIllustrative sample output, abridged.
{
"stage": "Tender issue",
"project": "Riverside Block C",
"currency": "USD",
"contractValue": 8400000
}{
"escalate": true,
"disclaimer": "A cross-check of the documents retrieved against each other. No document has been changed or issued, no design decision made or suggested, no view given on which document should govern, and no assessment of compliance with building regulations or any fire, structural or accessibility requirement.",
"documentsRead": [
"Specification Rev D",
"Door schedule Rev C",
"Finishes schedule Rev E",
"Room data sheets Rev C"
],
"contradictions": [
{
"item": "Corridor floor finish",
"sourceA": "Specification clause 12.3, Rev D",
"sourceB": "Finishes schedule Rev E, all corridor rooms",
"exposure": 96300,
"quantity": 214,
"readingA": "\"Vinyl sheet, welded seams, 2.0mm\"",
"readingB": "\"LVT plank, glue down\"",
"safetyRelated": false,
"cheaperReading": "The specification. A contractor will price the vinyl and the LVT becomes a variation later."
},
{
"item": "Riser door fire rating",
"sourceA": "Door schedule Rev C",
"sourceB": "Specification clause 9.1, Rev D",
"exposure": 21600,
"quantity": 18,
"readingA": "\"FD60S\"",
"readingB": "\"FD30S\"",
"safetyRelated": true,
"cheaperReading": "The specification."
}
],
"missingEntries": [
"Six doors appear on the plans with no row in the door schedule. Each is a question, and unasked, an assumption.",
"Finish code F14 appears on 22 room data sheets and in no specification clause."
],
"couldNotRetrieve": [
"The ironmongery schedule is referenced in specification clause 8.4 and is not in the knowledge base."
],
"escalationReason": "A fire rating contradiction affects 18 doors on a 16-week lead item, and a finish contradiction across 214 rooms has an exposure above 1% of contract value.",
"longLeadFindings": [
"The riser doors are a 16-week lead item and carry a fire rating contradiction. This one has to be resolved before anything else in this report."
],
"revisionsNotPropagated": [
"The finishes schedule went to Rev E on 14 August. The specification is still Rev D from 2 July. Every finish contradiction above dates from that gap."
],
"unlocatedOrUnspecified": [
"A specified acoustic wall panel system appears in no drawing or room data sheet. Either it is not required or its locations were never shown."
],
"questionsAContractorWouldRaise": [
"Corridor floors: please confirm whether vinyl sheet or LVT is required.",
"Riser doors: please confirm FD30S or FD60S.",
"Please issue the schedule for the six unscheduled doors on plans A-201 and A-202."
]
}No integrations required.
The last point where a contradiction is free to fix.
What changed and what did not follow it.
Which documents did not receive it.
The state of a set you did not produce.
$399/month
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits.
No. That is a design decision with consequences for appearance, performance and compliance, and it belongs to the designer. It reports both readings and the exposure.
No, and it does not replace it. Clash detection compares geometry. This compares what the documents say, which is where variations come from.
No. It checks the set against itself. Whether a specified build-up meets a regulation is a compliance judgement requiring a qualified person.
No reviews yet. Reviews open once customers have run this agent.
Tell us what to change and our team will scope a customised version for your business.
Customize this agent