Skip to content
Our workPlatformsApplication briefing

Project Document Centre

From scattered project files to one current, auditable document record.

Workflow illustration

Workflow illustration, not real documents, projects or revision codes. Project files from legacy folders pass a controlled intake: a likely duplicate is merged, taxonomy metadata such as document type and project is applied, revision and status rules are set and permissions follow the selected project. Each document becomes one logical record with a revision timeline. A new revision, Rev C, waits in review while Rev B stays current. An authorised reviewer approves it; only then does Rev C become current and Rev B superseded, with earlier revisions kept. The record links to related RAMS, tender and programme records, and each change is added to a searchable audit history. The project team works from the current revision.

People stay in control

Permissions follow the selected project. Earlier revisions stay accessible, important changes are recorded rather than overwritten, and authorised users remain responsible for review and approval decisions.

The challenge

Project documents are often duplicated across folders, email and specialist modules. Drawings, RAMS, programmes and evidence can be hard to search, and teams risk working from superseded versions or losing the history behind a change.

What we designed

A document centre that maintains one logical record for each project document and its revisions. It captures structured metadata, detects likely duplicates or new revisions, manages current and superseded states, links evidence to related project records and provides search, filters, review status and audit history inside the wider project context.

A designed document model within a connected construction operating platform.

What it connects

  • Project files and legacy folders
  • Document taxonomy and metadata rules
  • Revision and status rules
  • Project permissions and review requirements

The difference it makes

  • Files and revisions are organised around the document itself, not duplicated across unrelated folders and modules.
  • Current, superseded and review states are explicit, so teams can see which version should be used.
  • Revision timelines and audit events keep earlier evidence available instead of silently replacing it.
  • The same controlled record can support RAMS, tenders, commercial workflows and other project applications without new copies.

Business profile

Sector
Construction
Team
Project delivery
Workflow
Document control and revision review

One logical record for every project document, with current, superseded and review states explicit and approval kept with authorised people.

Inputs and outputs

Inputs

  • Project files and legacy folders
  • Document taxonomy and metadata rules
  • Revision and status rules
  • Project permissions and review requirements

Outputs

  • Searchable document register
  • Revision timeline with current or superseded state
  • Related-record links
  • Review and approval status with audit events