Guide
Document control decides which version of a drawing, specification or report is current, who received it and what was approved. Whichever platform a project uses, each document control step raises the same three points: what a model can read and propose, which check must stay a fixed rule in the register, and which decision stays with the document controller.
A model is good at reading content that arrives in inconsistent forms, such as title blocks, cover emails, transmittals and comment sheets. It should not be the record. The register stays the source of truth, software enforces its rules, and a named person accepts every change to it.
Hugo Sequier runs State Method, which sells the assessments, pilots and builds these guides discuss. Apply the same tests to it as to any other provider.
01 / Split
Writing this split down before any tool is chosen is the most useful step. It shows where a model adds speed and where it would add risk.
Classifies an incoming file, reads the document number, title, revision, date and discipline from the title block or cover sheet, matches an email attachment to a register entry, summarises what changed between revisions and finds references to a document that has been superseded. Every proposal names the page or field it was read from.
Checks the naming convention, the revision sequence, the status codes, duplicates, required fields and the distribution matrix. These are fixed rules with one correct answer, so they belong in code or in the register’s own validation, not in a model’s judgment.
The document controller accepts an entry into the register, issues a transmittal and marks a revision as superseded. Reviewers keep the status they give a submittal or drawing. Nothing changes the controlled record without that approval.
02 / Step map
The usual document control steps on a construction project, what a model can prepare in each, and the check or approval that stays outside it. The examples linked below use synthetic project data.
A model reads incoming files and their cover emails and proposes the register fields. Software checks the proposal against the naming convention and the existing register, flags duplicates and missing attachments, and the controller accepts or corrects it.
Where filenames are inconsistent, a model can propose the correct document number and metadata from the content itself. Software validates the format. No file is renamed or moved without a register record of the change.
Software checks the revision sequence against the register. A model then finds which open RFIs, submittals, work packages or notices still reference the superseded revision, so the controller can issue one coordination notice instead of searching by hand.
Who receives which document stays a rule table, the distribution matrix. A model can draft the transmittal cover text and the summary of changes; the controller sends it.
A model can extract comments from marked-up sets and comment sheets, map each one to a sheet and revision, and surface conflicts between packages with the source cited. The reviewer still issues the review record.
A model can answer questions across the project documents, provided it reads only current revisions and every answer names the document number and revision it came from. An answer without that citation cannot be checked.
A model can match O&M manuals, certificates, warranties and as-built drawings to the handover obligations list and show every gap. The handover manager approves the pack.
03 / Limits
These are the points where a fluent model output causes the most damage, because the error looks like a valid record.
A model that reads a superseded drawing answers just as fluently as one that reads the current revision. Requiring every output to name the document number and revision it read is the simplest control against that failure.
04 / Before starting
If documents already arrive and live in one platform, start with that platform’s own features. A custom workflow is worth considering when documents arrive from several parties and channels, the register sits in a separate system, and supersession has to be traced to open items across them.
05 / Trial
The same trial works for a platform feature, a specialist tool or a custom workflow, so the options can be compared on equal terms.
Before uploading project files to any tool, check its data handling with the vendor questions in the AI proof of concept guide.
FAQ
Not in a controlled process. It can move the document controller’s time from typing metadata and searching for references to checking proposals and resolving exceptions. Someone still has to own the register, accept entries, issue transmittals and answer for what is current.
Software should check the revision sequence against the register, and a model should only help find what the change affects: open RFIs, submittals, packages or notices that still cite the superseded revision. Every output should name the document number and revision it read, and the controller issues the coordination notice.
Continue with the evidence
Assessment / one workflow
Describe where documents arrive, the register they go into, who controls it and how long each document takes today. A person reviews every assessment. Do not send confidential documents through the public form.