Migrating fromOpenText?—Get started
AODocs

Kick off in hours
Keep every deliverable right from day one

The master document register is imported, placeholders are created, numbering and due dates come from last month's template, and every submission is checked before anyone reviews it. Document control starts on day one instead of catching up in month three.

Request a demoDocument control at work

Works alongside Autodesk Forma, Procore and Oracle Aconex. Your cloud, your storage, your LLM.

Start on last month's template, not on an empty folder tree

Before the first deliverable arrives, the reference set has to exist: specifications, standards, contractor's deliverables list, numbering rules. On a folder tree, that takes weeks and one person who knows where everything goes. In AODocs, the master document register is imported, numbers and due dates are generated, and overdue items surface on their own. A project set up on last month's template starts in hours.

  • The master document register is imported from the contractor's deliverables list.
  • One placeholder per expected deliverable, numbered by the project's rules.
  • Due dates generated; overdue deliverables flagged without a chase by email.
  • The next project reuses the configuration: template, numbering, workflows, roles.
A project register built in hours from a deliverables listThe project starts from the template of Project 2038. The mechanical contractor's deliverables list is imported. Each line becomes a register entry with its document number, its due date and the status Placeholder, and a counter climbs to 2,400 placeholders. The clock moves from day 1 to day 30: two deliverables are received, two are flagged overdue by the register itself, 38 overdue across the project, with no chasing by email.MDR-001 · MASTER DOCUMENT REGISTERDAY 1DAY 30Deliverables list.xlsxMechanical contractorStarted from templateProject 2038importedDOCUMENT NUMBERDUESTATUS2041-GEN-SPC-000105 AprPlaceholderReceived2041-CIV-DWG-010208 AprPlaceholderReceived2041-MEC-DBK-000712 AprPlaceholderPlaceholder2041-ELE-CAL-003102 Apr02 AprPlaceholderOverdue2041-INS-RPT-000419 AprPlaceholderPlaceholder2041-MEC-CRT-001203 Apr03 AprPlaceholderOverdue2,400 placeholders38 overdueOverdue deliverables flagged on their own, no chasing by emailSet up in hours. Nothing overdue goes unnoticed.

Catch the error at submission, not in the third review loop

Much of review time goes on documents that should never have reached a reviewer: a wrong number, a skipped revision letter, a title block that disagrees with the metadata. AI Quality Control reads each incoming document against the project rules before it enters the queue. What fails goes back to the submitter the same day, with the reason in plain words; reviewers only see documents worth reviewing.

  • Numbering checked against the project's scheme.
  • Revision letter and sequence checked against the register.
  • Title block compared with the metadata, field by field.
  • Completeness checked before the document joins the queue.

One review, every party, one comment sheet

Owner, engineer, EPC and vendor review the same revision in the same place. Drawings open in the browser, in more than a hundred formats. Comments are reconciled on the original comment sheet, each one answered before the next revision is issued, and the approval records who decided, when, and on which revision.

  • Drawings and documents viewed in the browser, more than a hundred formats.
  • Markups made on the drawing and kept with its revision.
  • Every comment answered and recorded on one sheet.
  • No new revision while a comment has no recorded answer.

A new project, set up in a few hours

It's a big risk not to have any document control, that companies don't necessarily see directly, because a lot of time passes between when the document is generated and when the problem happens at the site.

Nicolas Tourneur, Deputy Director for Projects, Veolia Water Technologies

Setting up AODocs for a new project now takes a few hours, with controlled routing from initiation.

Read the story

Questions on this phase.

Is this one more system for document control to keep in step?

It removes the keeping in step. Register, submissions, reviews and transmittals live in one place, so there is no spreadsheet register to reconcile with a folder tree and an inbox. Where a project platform stays, AODocs connects to it instead of copying it.

Migrating a live project is out of the question. Where do we start?

Agreed: nobody moves the record of a live project halfway through. Start with the next project, set up from a template in hours, or with one document class on the current project, such as commissioning certificates or permits. The first project is where your document control configuration is defined; every project after it starts from that configuration.

Our document controllers already do this well. What does AODocs add?

Good document controllers are the reason manual control works at all. The limit is that it depends on people staying and paying attention, under deadlines that keep shortening. AODocs takes the repetitive part: numbering, completeness checks, routing, retirement of superseded revisions, overdue tracking. Controllers keep the judgment, and an agent asked a question reads the version they approved, not a copy on a shared drive.

Will governance slow the project down?

Ungoverned projects are the ones that lose weeks at kickoff and at handover. Veolia Water Technologies sets up a new project in a few hours and has controlled routing from initiation. Fewer steps, named: no manual numbering, no chasing overdue deliverables by email, no reconciling comment sheets by hand.

More questions and answers

See how much faster one document class can move.

In a one-hour session, we take one document class from one of your projects and show how it is checked, approved, retired when superseded and read by AIDA, without a person remembering to do any of it.

Request a demo

Start with the next project, or with one document class on the current one.