NewDocument Control

One register.
Nothing unchecked.

A common data environment your firm runs for the whole project team, designed around ISO 19650. Every firm issues into it, you check and review, and only what has a status is published.

Consultancy AI·Larkspur House › Document Control › Register
Document Control
Larkspur House · Register · issuing as Tarn & Ashby (TAA)
My tasks 3Awaiting QA 2Consultancy AIUpload
Work in progress
13
Shared
6
Published
147
Archived
212
Document No.TitleRevPOIStateReview statusReview due
LH-BME-ZZ-ZZ-M3-M-0001MEP coordination modelC02A5PublishedA—
LH-LRD-ZZ-01-DR-A-2001General arrangement — Level 01C02A5PublishedA—
LH-LRD-ZZ-01-DR-A-2301Reflected ceiling plan — Level 01P04B5PublishedB—
LH-HAL-ZZ-01-TS-A-0007Fire-rated partition systemP02S3SharedAwaiting Consultant Comments14 Nov (3d)
LH-BME-ZZ-01-DR-E-6101Small power and data — Level 01P03S2PublishedFor Information—
LH-HAL-ZZ-02-DR-A-3105Partition setting-out — Level 02P02S3WIPC—
LH-MRL-ZZ-RF-DR-M-5601Roof plant layoutP01S0WIPNot submitted—

From upload to archive

The whole life of a document, in the order it happens

Consultancy AI·Larkspur House › Document Control › Awaiting QA
Awaiting QA
Batch from Marlow Mechanical · 4 drawings · 1 of 4
‹ PrevNext ›
Document numberCompliant
LH
Project
MRL
Originator
ZZ
Volume
02
Level
DR
Type
M
Role
5201
Number
Title
LTHW pipework layout — Level 02
Revision
P03
Purpose of Issue
S3 · Review and comment
Discipline
Mechanical · LTHW
Originator
Marlow Mechanical
The filename says P02; the title block says P03. The title block wins, and the mismatch is recorded.
Return with a reasonPublish for informationPass and start a workflow
01

Every upload is checked before anyone else sees it

Whoever uploads, the batch lands with your document controller first. The number, revision and title are read from the title block, split into the fields of your naming standard, and held against it.

  • Where the filename and the title block disagree, the title block wins and the difference is recorded.
  • Publish for information, pass it into a review, or return it with a reason.
  • Upload on another firm’s behalf and the record says so.
Consultancy AI·Larkspur House › Document Control › LH-MRL-ZZ-02-DR-M-5201
LH-MRL-ZZ-02-DR-M-5201
LTHW pipework layout — Level 02 · P03 · Design Review
WIPExport marked-up PDF
LRD-01LRD-02BME-01
Review workflow · Design Review
  1. 1Information manager reviewAccepted · S. Okafor
  2. 2Reviewers, in parallelLaird Studio · due 21 Nov
    Brook Mercer Engineers · due 21 Nov
  3. 3Final statusABC
Comments0 of 3
LRD-01Laird Studio
Flow main clashes with the bulkhead at gridline C. Drop 150 mm or reroute north of the core.
LRD-02Laird Studio
Branch at E to stop short of the acoustic partition; sleeve detail required.
BME-01Brook Mercer EngineersCarried from P02
Commissioning set omitted on the return at the riser. Carried from P02, still open.
B · Approved with commentspublished; stays open until an A supersedes it
02

Reviewed on the sheet, by the people you named

The first stage accepts it into review, the reviewers comment in parallel on the drawing itself, and the final status is A, B or C. Only the outcomes that are valid at a step are offered.

  • Pins, revision clouds, arrows and text, a layer per reviewer, exported as a marked-up PDF.
  • Open comments carry to the next revision and must be answered before it can be submitted.
  • Response periods per stage; overdue reviews show on the register and the dashboards.
Can a model be reviewed?
Consultancy AI·Larkspur House › Document Control › Workflows
Workflows
Larkspur House · Design Review · the project default
Pull in a templateSave
  1. 1Information manager reviewDecisionAcceptedRejected
    Who does this stage
    S. OkaforR. Venn
    Days
    2
  2. 2ReviewComments, in parallelComments
    Who does this stage
    Laird StudioBrook Mercer Engineers
    Days
    5
  3. 3Final statusDecisionABC
    Who does this stage
    S. OkaforR. Venn
    Days
    2
Naming standard
Project-Originator-Volume-Level-Type-Role-Number
Revision scheme
P01, P02 … then C01
03

The template says what happens. The project says who.

Build your review workflows once as a firm: the stages, the outcomes, the default days. Each project pulls in the ones it needs and puts people and firms against each stage.

  • Any number of firms on a stage, or your own people, or nobody: an empty stage does not run.
  • Adjust who reviews and how long they have for a single document as you start it.
  • Naming standard, revision scheme and code lists set per project, from your firm’s defaults.
Our own numbering and process
Consultancy AI·Larkspur House › Document Control › Register
Document Control
Larkspur House · Register · issuing as Tarn & Ashby (TAA)
Awaiting QA 2Consultancy AIUpload
Work in progress
13
Shared
6
Published
147
Archived
212
Document No.RevPOIStateReview status
LH-BME-ZZ-ZZ-M3-M-0001C02A5PublishedA
LH-LRD-ZZ-01-DR-A-2001C02A5PublishedA
LH-LRD-ZZ-01-DR-A-2301P04B5PublishedB
LH-HAL-ZZ-01-TS-A-0007P02S3SharedAwaiting Consultant Comments
LH-BME-ZZ-01-DR-E-6101P03S2PublishedFor Information
LH-HAL-ZZ-02-DR-A-3105P02S3WIPC
04

Published once, to the whole project, and into the registers

An approved revision becomes visible to every firm on the project and is copied into the Drawings register. The revision it replaces moves to the archive; nothing is deleted.

  • Work in progress is the issuing firm’s; shared is the review’s; published is everyone’s.
  • Who can see a revision is decided by its state, in the database, not by a folder.
  • Search, filter, sort and export the register; download a selection as a ZIP, recorded per file.
What happens once it is approved
Consultancy AI·Larkspur House › Document Control › Deliverables
Deliverables
Larkspur House · the delivery plan, firm by firm, against the register
Chase listExportImport
All 48Late 3Due 5At risk 2Issued 30Unmatched 4
NumberTitleBaselineForecastFloatStatus
Laird Studio · delivery plan rev 3 · Stage 4Accepted
LH-LRD-ZZ-02-DR-A-2002General arrangement — Level 0203 Nov03 Nov+9dIssued
LH-LRD-ZZ-02-DR-A-2302Reflected ceiling plan — Level 0207 Nov07 Nov-4dLate
LH-LRD-ZZ-XX-DR-A-4011Section B-B through the plant deck10 Nov18 Nov-2dAt risk
Brook Mercer Engineers · delivery plan rev 2 · Stage 4Accepted
LH-BME-ZZ-02-DR-M-5102Mechanical services — Level 0212 Nov14 Nov+6dDue
LH-BME-ZZ-RF-DR-M-5600Roof plant general arrangement14 Nov28 Nov+3dSlipped
LH-BME-ZZ-ZZ-SH-M-0003Valve and commissioning schedule12 Dec12 Dec+14dPlanned
LH-LRD-ZZ-02-DR-A-2302 P01 reached Shared at S3 · the milestone counts as issued
05

What each firm promised, against what has arrived

Import each firm’s delivery plan from its own spreadsheet. Every planned document has a baseline, a forecast and a date you need it by, and counts as issued only when a revision is actually shared at the suitability required.

  • Late, due, at risk and slipped, by firm, on the dashboard before the design team meeting.
  • Float is the date you need it less the date they forecast: the warning before anything is late.
  • A chase list in Excel, with each firm’s contacts, in one click.
Consultancy AI·Larkspur House › Document Control › LH-MRL-ZZ-02-DR-M-5201 › Audit
Audit trail
LH-MRL-ZZ-02-DR-M-5201 · every state change, decision, view and download
Export
WhenEventDetailBy
24 Nov 16:42PublishedP03 · B5 · visible to the whole projectS. Okafor · TAA
24 Nov 16:42Decision recordedFinal status · B · Approved with commentsS. Okafor · TAA
21 Nov 11:08Comments submittedReviewer · 1 comment · BME-01 kept openP. Nair · BME
20 Nov 09:31DownloadedP03 · LH-MRL-ZZ-02-DR-M-5201.pdfD. Whitlock · LRD
19 Nov 14:15SharedP03 · with Laird Studio, Brook Mercer EngineersS. Okafor · TAA
19 Nov 14:02Review startedDesign Review · new revisions lockedS. Okafor · TAA
19 Nov 13:47QA passedTitle block read · number compliantS. Okafor · TAA
19 Nov 10:20UploadedP03 · supersedes P02 · P02 archivedJ. Marlow · MRL
8 of 31 events · the trail cannot be edited, only added to
06

Who did what, and when, without asking anyone

Every state change, decision, comment, view, download, export and share is written to the document’s audit trail as it happens. It can be added to and exported; it cannot be edited.

  • The answer to “when did they have it?” is a line, with a name and a time.
  • Withdrawn documents stay on the register with their numbers; a void frees the number.
  • Two-factor sign-in can be required for the whole organisation.

Questions

Is it an ISO 19650 common data environment?
It is designed around one: work in progress, shared and published states with access to each enforced in the database, the UK suitability codes, preliminary and contractual revision sequences, a naming standard you set per project, and an audit trail of every state change, decision, view and download. There is no product certification against ISO 19650, for us or for anyone, and we do not claim one.
Who runs the register on a project?
The firm that switches Document Control on for the project: usually the lead designer or whoever holds the information management role. That firm sets the naming standard and the workflows, checks what is uploaded and records the final status. Every other firm issues into it and reviews in it.
How do the contractor and the other consultants get in?
You invite a firm to the project and give its people View or Edit access to Document Control. They issue and review as that firm, and they see the revisions their firm is entitled to see and nothing else. A contractor that runs its jobs on Construction AI can also be connected through its contract, so the drawings you publish arrive in its own account.
Can we keep our own numbering and our own review process?
Yes. The naming standard, the revision scheme, the code lists for types, disciplines and suitability, and the review workflows are all yours to set, as a firm-wide default and per project. A workflow template says what the stages are; each project says who does each stage and how many days they have.
What happens to a drawing once it is approved?
A revision given a final status of A or B is published to the whole project and copied into the Drawings register within a few minutes, where your team and the agents already work. A B stays open, with its comments on the sheet, until an A revision supersedes it.
Can a model be reviewed, or only drawings?
Both. A PDF opens with the mark-up tools: pins, clouds, arrows, text, a layer per reviewer. An IFC opens in 3D and comments are pinned to the elements they concern. Either way the comments land on the same comment register and carry to the next revision until they are closed.