AI DOCUMENT CONTROL · GENERAL CONTRACTORS
Rev 04 · Issued for construction

The clash was in revision 03. Nobody read revision 03.

Submittal reads every drawing revision, RFI, submittal and transmittal as it lands, checks it against the specification, and tells your project manager exactly what changed and who is now holding the programme up.

2,410
Documents on a mid-size job
14%
Contain a change nobody flagged
0
PMs with time to read them
Live register · Blackthorn Phase 2Updated 07:14
A-201 R04Level 2 floor planRiser relocated 900mm east, conflicts with M-114 R02Clash
RFI-088Slab edge detail at grid 7Open 11 days, response due to structural engineerOverdue
SUB-142Curtain wall · thermal breakU-value 1.6 submitted, spec section 08 44 13 requires 1.4Non-conf.
SUB-139Roof membraneMatches spec, warranty period confirmed at 20 yearsApproved
A-305 R02Stair core sectionsDimensional change only, no downstream impact foundCleared
63 documents processed since Friday3 require action today
01

What it reads and what it does with it

Everything that arrives in the project inbox or the common data environment, in whatever format the subcontractor felt like sending.

DWG

Drawing revisions

Compares the new revision against the superseded one and describes what actually moved, in words, not a colour overlay nobody opens.

RFI

Requests for information

Tracks who owns each one, how long it has been open and which trade is blocked behind it. Escalates before it hits the programme.

SUB

Submittals

Checks the product data against the specification section clause by clause and flags every value that falls short.

TRN

Transmittals

Logs what was issued, to whom and when, so the record exists without anyone maintaining a spreadsheet.

CO

Change orders

Links each variation back to the drawing revision or RFI that caused it, which is the paperwork that wins the claim.

MIN

Site minutes

Extracts actions and owners from meeting notes and matches them to open items already in the register.

02

The four checks that catch the expensive ones

Every finding cites the drawing number, revision and specification clause it came from. A PM can verify any flag in under a minute.

A

Cross-discipline clash

Reads architectural, structural and services revisions together. A riser that moves on A-201 is checked against every mechanical drawing that references it.

41clashes caught before install
B

Specification compliance

Submitted product data is tested value by value against the spec section. A U-value of 1.6 against a required 1.4 is a non-conformance, not a rounding difference.

96%submittals auto-checked
C

Open item ageing

Every RFI, action and submittal carries an owner and a clock. Anything that will breach the response period escalates the day before, not the week after.

0silently overdue items
D

Change traceability

Each variation is linked to the document that caused it, with dates. The entitlement argument is assembled as the job runs rather than reconstructed at the end.

100%variations traced to source
03

Measured on two live projects

A £38m residential scheme and a £12m industrial fit-out, both mid-programme at the point of adoption.

RESULT

41 clashes

Caught in document review rather than on site. Nine were in areas already released for construction.

RESULT

11 days saved

Median RFI turnaround fell from 19 days to 8 once ownership and ageing were visible daily.

RESULT

6 hours a week

Returned to each project manager, previously spent comparing revisions by eye.

Load a project you have already finished

Give us the document set from a completed job. Submittal reads it blind and reports the clashes and non-conformances it would have flagged. You already know which ones cost you money.

Load a project