Construction document control: every transmittal checked

Mirage's agent reads each incoming transmittal, checks numbers, revisions and status codes against your project's convention, and keeps the register current. Your document controller decides everything it flags.

A register is only as reliable as the last transmittal someone checked by hand. A number off the convention, a superseded drawing still marked current or a response nobody chased can stay unnoticed until someone works from the wrong document.

This page is about the register and the transmittals that feed it. To find an answer inside the project's documents, see document intelligence, which searches them and cites the source. For what an RFI asks or what a submittal contains, see RFI and submittal tracking.

What a document controller checks on every transmittal

Your project sets the rules, in its information standard or document control procedure and in its contract. On projects that use them, the public references below set the fields and codes the agent checks.

Document number
Under the UK National Annex to ISO 19650-2, each file's ID is a set of fields separated by a delimiter. Each field takes its value from an agreed, documented code list. Since the 2021 Annex, the fields are project, originator, functional breakdown, spatial breakdown, form, discipline and number. Their lengths are whatever the project's information standard sets. The originator is the organization of the information's author, not the lead appointed party that controls it (UK BIM Framework, Guidance Part 2, section 3.1).
Revision
A P prefix marks a preliminary, non-contractual revision, and a C prefix a contractual one. P01.01, for example, is a work in progress version of P01 (Guidance Part C, section 5). The agent treats a revision lower than the one already in the register as an error to flag, not a document to file.
Status (suitability)
S1, S2 and S3 share information as suitable for coordination, for information, and for review and comment, in that order. S4 shares it for the lead appointed party's authorization, and S5, added in 2021, for the appointing party's review and acceptance. An A code publishes it as authorized and accepted, and what each A code allows is written in the project's information standard. S6, S7 and CR were removed in 2021, and the B codes were deprecated (Guidance Part 2, section 3.1.10). A container at S3 is not for procuring materials, agreeing contract costs or building the works, and information issued for construction carries a published status (Guidance Part C, section 6). Under clause 5.6.5, a container is given a status for sharing only once its review succeeds. A failed review rejects it, and the reason and the amendments needed are recorded (Guidance Part 2, clause 5.6.5).
Classification
Each container also carries a classification code, and the 2021 Annex points to the Uniclass 2015 PM table where possible (Guidance Part 2, section 3.1.11).
Submittals and the site set
On an AIA A201-2017 contract, the contractor submits a submittal schedule for the architect's approval. If it fails to submit that schedule or to follow it, it is not entitled to more time or money for review time (section 3.10.2). The contractor also keeps at the site the contract documents, change orders included, marked currently with field changes, together with the approved submittals. At completion, it delivers them as the record of the work as constructed (section 3.11). Section 1.7 has the parties agree protocols for exchanging information in digital form (AIA A201-2017, free sample).
Transmittal and review
Bentley's ProjectWise help describes the cycle. The sender's document controller issues a transmittal, and the receiving organization's document controller receives it and assigns a lead reviewer. The reviewers mark up, then the lead reviewer consolidates one response, which goes back to the sender. The cycle repeats with each new version (Bentley, Transmittal / Submittal Design Review Workflow). The agent follows each response against its due date and the review codes your procedure sets.

What the agent does with each transmittal

Reads every incoming transmittal

Mirage reads the transmittal and each document on it, with its number, title, revision, status and purpose of issue. It checks every field against your convention. A number that does not parse, a code that is not on your list or a status that does not fit the purpose of issue is flagged for the document controller.

Prepares the register update

Mirage sets each new revision to supersede the one before it. An older revision that arrives late is flagged instead of filed as current, and the distribution matrix decides who receives what. Your controller approves the update, and the original transmittal stays attached to every entry.

Follows every review to its response

Mirage follows each document out for review against its due date and the review codes your procedure sets. Anything overdue comes back as a list with the reviewer named, so your controller chases the right person.

A register update, as the controller sees it

An invented project, numbered to the 2021 UK National Annex: four documents from one incoming transmittal, and one review past its due date.

DocumentRevision and statusCheckResult
NBR-ACM-ST1-L02-D-E-0201, level 2 lighting layoutP03, S3Fields and codes match the project's standard; P02 is current in the registerP02 superseded once approved; sent to the reviewers the matrix names
NBR-ACM-ST1-L02-D-E-201, level 2 small power layout↳ The 2021 Annex leaves field lengths to the project's information standard, so the check runs against your standard, not a generic rule.P01, S2Number field has three digits; the project's standard sets fourHeld for the document controller
NBR-ACM-ST1-L01-D-E-0198, level 1 lighting layoutP02, S3The register already holds P03 of this drawingFlagged as an older revision, not filed as current
NBR-ACM-ST1-L02-T-E-0004, level 2 lighting calculations↳ Information issued for construction carries a published status. At S3 the agent holds the line instead of distributing it.P01, S3Purpose of issue on the transmittal: for constructionHeld: an S3 container is for review and comment
NBR-ACM-ST1-L03-D-E-0310, level 3 lighting layoutP02, S3Review due date passed, no review code recordedListed as overdue, reviewer named

What goes in, what comes out

Who uses it
Document controllers and information managers on general contracting, heavy civil and EPC projects, and on joint ventures that keep their own register next to the owner's system.
What you send
Incoming transmittals as they arrive, from the project's system or an inbox, with your register or its export and your procedure: numbering convention, status and review codes, distribution matrix. Documents in English or French.
What comes back
Every document checked against the convention, a register update with older revisions superseded and the distribution applied, and a list of what is overdue, with the reviewer named.
Where your team decides
The document controller decides everything the agent flags: a number off the convention, an out-of-sequence revision, a status that does not fit the purpose of issue. Nothing is written into the project's system before the named approver set for the workflow signs off, and every action is logged.
What it does not do
It does not give review codes in a reviewer's place, approve a document for construction, or replace your common data environment. Where a system's API documents no write path, your team makes the change in the system from the agent's list.
Where it runs
In your cloud, on your premises, or hosted by Mirage.
How it is priced
A fixed-price pilot first, then an annual subscription priced by volume, not per user.

On a joint venture: the owner's system and your own register

When the owner runs its own common data environment and the joint venture keeps its own register for its partners, designers and subcontractors, every document exists twice, under two numbers. The agent keeps the pair in step. Each transmittal received from the owner's system is logged in the joint venture's register with the owner's number alongside. Each document going out is checked against the owner's convention before it is transmitted.

In ISO 19650 terms, the owner is the appointing party and the joint venture is the lead appointed party. The joint venture is accountable for the delivery of its information, while each appointed party remains responsible for its own (Guidance Part 2, section 3.1.4). Since the 2021 Annex, the originator field names the organization that wrote a document, as its task information delivery plan identifies it (same section). That is why the agent checks the field against that plan instead of accepting the joint venture's code on everything.

How the agent reaches Oracle Aconex, Bentley ProjectWise or Autodesk Docs, and what it may write in each, is set out system by system: see the document control integrations.

The nearest published proof

No deployment on document control is published yet. The nearest published construction proof is OCBM: three agents in production, every quantity tied to the drawing it came from.

OCBM

Three agents in production

100% of quantities tied to a source drawing

See the case study

Send us a transmittal and your register

A reply within two business hours, a proof of concept one week after the first meeting, the first workflow in production in 4 to 6 weeks. The proof of concept runs on your own transmittals.

Attach a transmittal and your register export (recommended)

We use your email to reply to you and, now and then, to tell you about Mirage. You can opt out at any time. Privacy policy

How a deployment runs: Observe, Map, Build, Run, Expand. See the method

FAQ

Frequently asked questions

  • On each transmittal, a document controller checks that each document number follows the project's convention, that its revision is newer than the one in the register, that its status code fits the purpose of issue, and that it reaches the people the distribution matrix names. The controller then checks that every review comes back with a response. On projects run under ISO 19650-2 in the UK, the National Annex sets the fields and codes. Elsewhere, the owner's or the contractor's procedure does.

  • No, Mirage does not replace Aconex, ProjectWise or Autodesk Docs: the common data environment stays the record. Mirage reads from it and writes to it through the interfaces Oracle, Bentley and Autodesk document, within the access your administrator grants. Where a vendor documents no write path, the agent's output is a list your controller acts on. The detail per system is on the document control integrations page.

  • The agent checks against your own naming convention and status codes, as the project's information standard or document control procedure sets them. Under the 2021 UK National Annex to ISO 19650-2, that standard sets the field lengths and what each A status allows, so a generic rule would be wrong. The agent is set up on your code lists before the first transmittal.

  • No, the agent never approves, rejects or supersedes a document on its own. It prepares each change: the supersession, the distribution, the list of overdue reviews. A named person on your side approves before anything is written into the project's system, and review codes are given by the reviewers, never by the agent.

  • On a joint venture that uses the owner's system, the agent keeps both registers in step. Each transmittal from the owner's system is logged in the joint venture's register with the owner's number alongside, and each outgoing document is checked against the owner's convention before it is sent. In ISO 19650 terms, the owner is the appointing party and the joint venture the lead appointed party.

  • Document control keeps the register right: numbers, revisions, status, distribution and reviews. Document intelligence searches across the project's documents and answers a question with its source. RFI and submittal tracking follows what each RFI asks and what each submittal contains.

  • No deployment of this workflow is published yet. The nearest published construction proof is OCBM: three agents in production, with 100% of quantities tied to a source drawing. The proof of concept runs on your own transmittals.

  • A reply within two business hours, a proof of concept one week after the first meeting, the first workflow in production in 4 to 6 weeks. Pricing is a fixed-price pilot first, then an annual subscription priced by volume, not per user.

Sources

Checked on November 10, 2026. The register rows in the sample above are invented, but the conventions are the ones these documents describe.