ISO 19650 Documentation for UK University Expansion – 85% Error Reduction

Success Story · ISO 19650 · United Kingdom

ISO 19650 Documentation Reduced Errors by 85% on a £25M UK University Expansion

Optimar Precon consolidated and restructured more than 500 drawings, RFIs, submittals and compliance records for a 100,000 sq ft research facility in Manchester. A controlled documentation workflow improved version management, approval routing and multidisciplinary coordination across the 18-month programme.

  • Manchester, United Kingdom
  • £25 million project value
  • 100,000 sq ft research facility
  • 500+ project documents
  • BREEAM Excellent target

Outcome figures shown in this success story are based on the project information, document registers, review records and delivery data associated with this engagement.

University research facility ISO 19650 documentation management for a UK university research facility in Manchester
Reported project outcomes
85% Fewer document errors
5 weeks Saved on approvals
£800K+ Cost risk reportedly avoided

Project overview

ISO 19650 Documentation UK Project Overview

The university expansion included specialist laboratories, building-services systems and sustainability documentation within a live multidisciplinary programme. The document-control process also had to align with the project’s UK BIM delivery workflows , supporting clear document status, revision tracking and coordinated approvals.

Project value £25 million
Location Manchester, UK
Facility size 100,000 sq ft
Delivery programme 18 months
Document volume 500+ files

Optimar Precon assignment

Document Restructuring, Workflow Control and Quality Review

Through our construction documentation services , Optimar Precon reviewed the supplied files, applied the agreed ISO 19650-aligned naming and information structure, established document-routing workflows and checked records before they moved through the approval process.

Document consolidation

Bring drawings, RFIs, submittals and supporting records into a controlled project repository.

Information restructuring

Apply the agreed naming, classification, revision, status and document-control conventions.

Approval workflow setup

Route RFIs, technical submittals and change records through defined review and response stages.

Quality and compliance checks

Review document metadata, completeness, status and supporting sustainability information.

Stage 01 Receive information Collect the current project documents, registers and supplied information requirements.
Stage 02 Check and classify Review file identity, revision, status, discipline, originator and document purpose.
Stage 03 Route for review Move information through the agreed checking, approval and response workflow.
Stage 04 Record and issue Maintain the document register and issue approved information through the controlled environment.

Primary project objective

Create a dependable project information structure that helped architects, engineers, contractors and client representatives locate current documents, understand their status and move information through the required review process without relying on disconnected manual trackers.

The information challenge

Fragmented Files and Manual Tracking Put Document Reliability at Risk

More than 500 drawings, RFIs, technical submittals and supporting records were distributed across multiple platforms. Without one controlled information structure, project teams could not consistently confirm which files were current, reviewed or suitable for use.

Project information 500+ Drawings, RFIs, submittals and compliance records requiring structured control
Reported error rate 12% Documents reportedly affected by manual handling, status or information inconsistencies
Programme 18 months Multidisciplinary delivery period requiring dependable review and approval cycles
Reported cost exposure £1M+ Potential impact associated with delay, rework and document-control failures

Root causes

The Project Lacked One Dependable Source for Current Information

Teams were using different platforms and manual registers to manage information. This made it difficult to confirm document ownership, revision status, approval history and whether a file had been superseded.

  • Documents were stored across separate systems and stakeholder-controlled folders.
  • File names, revisions and status information were not consistently structured.
  • RFI, submittal and change-control routes depended heavily on manual follow-up.
  • Project participants could access different versions of the same design information.
  • Sustainability evidence was not consistently connected to the relevant design records.

High-risk document groups

Control Issues Affected Both Technical and Compliance Information

The challenge extended beyond drawing storage. Each information type followed a different review path and carried its own risk when status, responsibility or approval history could not be confirmed.

Design drawings

Architectural, structural and building-services drawings required dependable revision and suitability status.

RFIs and responses

Outstanding questions and design responses needed clear ownership, due dates and closure records.

Technical submittals

Product data, shop drawings and technical approvals required traceable review and response stages.

BREEAM evidence

Materials, energy and sustainability records needed to remain connected to the relevant project requirements.

Information failure chain

One Uncontrolled Document Could Affect Multiple Project Decisions

The commercial and programme risk did not come from file storage alone. It came from teams acting on incomplete, outdated or incorrectly classified information.

Stage 01 Inconsistent source file A drawing, response or submittal enters the project without reliable naming or status.
Stage 02 Unclear review position Stakeholders cannot easily confirm whether the information is current or approved.
Stage 03 Incorrect project action Design, procurement or construction decisions may rely on the wrong information.
Stage 04 Delay or corrective work The project then faces clarification, resubmission, rework or programme disruption.

Why manual tracking was no longer sufficient

A spreadsheet-led process could not reliably control more than 500 multidisciplinary records across an 18-month programme. The project needed a structured information environment with consistent naming, status, review routing, version history and document-register control.

The documentation solution

A Centralised ISO 19650-Aligned System for Document Control and Approvals

Optimar Precon brought the project’s drawings, RFIs, submittals, change records and sustainability evidence into a controlled information environment. The structure supported multidisciplinary BIM coordination by giving stakeholders a more reliable way to identify current information, review status and outstanding responsibilities.

Delivery strategy

Replace Disconnected Files and Manual Trackers With a Structured Information Workflow

The approach combined document consolidation, ISO 19650-aligned metadata, controlled review routing, quality checks, sustainability-record integration and recurring team coordination. The objective was to make document status, responsibility and revision history visible throughout the programme.

01

Centralised Document Repository

More than 500 supplied project files were reviewed and brought into a controlled information structure.

  • Drawings, RFIs and submittals
  • Specifications and change records
  • Sustainability and compliance evidence
02

ISO 19650-Aligned Restructuring

Document identity and metadata were reorganised around the information-management requirements agreed for the project.

  • Naming and classification conventions
  • Revision and suitability status
  • Originator and discipline references
03

Controlled Approval Workflows

Defined routing stages reduced reliance on email chains, informal trackers and manual document follow-up.

  • Assigned reviewer and responder roles
  • Due-date and status visibility
  • Recorded review and approval history
04

Quality Assurance Reviews

Documents were checked for identification, completeness and status before progressing through the agreed workflow.

  • Metadata and file-name checks
  • Revision and status verification
  • Supporting-document completeness
05

BREEAM Evidence Integration

Supplied materials, energy-performance and sustainability records were linked to the relevant project information and review requirements.

  • Materials and product evidence
  • Energy-performance documentation
  • Requirement and submission tracking

Document-control workflow

From Incoming File to Controlled Project Record

Each document moved through a defined checking and review process before it became available as current project information.

The exact naming fields, suitability codes, review stages and approval responsibilities followed the project’s agreed information-management requirements.

Receive and register

Log incoming documents, identify the source and compare the file with the current project register.

Check identification

Review naming, classification, discipline, originator, revision and suitability information.

Route for technical review

Send the information to the assigned reviewer or response owner through the agreed workflow.

Record comments and status

Capture review comments, responses, approval conditions and the resulting information status.

Update the register

Record the current revision, issue date, suitability and superseded-document relationship.

Issue controlled information

Make the reviewed information available to authorised project participants through the controlled environment.

Quality-control gates

Checks Applied Before Information Progressed

The review process focused on information reliability rather than simply confirming that a file had been uploaded.

Identity check

Confirm file name, originator, discipline and document type.

Revision check

Confirm the current revision and relationship to superseded information.

Status check

Verify whether information is suitable for review, coordination, construction or record purposes.

Completeness check

Check required attachments, responses, supporting evidence and approval information.

Weekly coordination and user guidance

Weekly meetings supported document-status review, responsibility tracking and resolution of outstanding information issues. Project participants also received guidance on using the document structure, registers and review workflows relevant to their role.

Weekly review cycle

Responsibility clarification: Optimar Precon supported document control, information structuring, workflow administration and quality checks. The appointed project parties retained responsibility for technical design, formal approvals, regulatory submissions, BREEAM assessment decisions and authorisation of information for construction.

Reported project outcomes

Structured Information Control Improved Document Reliability and Approval Performance

The centralised documentation workflow gave the project team clearer visibility of current revisions, review responsibilities and outstanding information. Project records reported fewer document errors, shorter approval cycles and reduced exposure to rework and delay.

Document reliability 85% Fewer document errors reported Consistent naming, revision checks, status control and structured quality reviews reduced information-management errors across the project records.
Approval programme 5 weeks Reported approval time saved Defined routing, clear ownership and consistent document formatting reduced delays associated with manual follow-up and repeated clarification.
Reported commercial impact £800K+ Cost exposure reportedly avoided Earlier identification of document issues and more dependable information control reduced potential rework, approval delay and programme disruption.

Approval cycle reduced

Project information reported a 25% reduction in approval-cycle duration after the controlled workflows were introduced.

Clearer document status

Teams could more reliably distinguish current, superseded, under-review and approved project information.

Improved team coordination

A shared information structure improved visibility across architects, engineers, contractors and client representatives.

After controlled delivery

The Project Team Gained a More Reliable Basis for Review, Approval and Information Issue

The ISO 19650-aligned structure and recurring review process made document identity, status, revision and responsibility easier to confirm.

Controlled document register

Current revisions, issue dates, status and superseded records remained visible in one register.

Traceable review history

Comments, responses, reviewer responsibility and approval outcomes could be followed more consistently.

Improved information access

Authorised participants could locate the relevant current project records more efficiently.

Connected compliance evidence

Supplied sustainability records remained linked to the corresponding requirements and submissions.

ISO 19650 and BREEAM review outcome

Project records indicated that the information-management and sustainability-documentation reviews were completed without requests for document-control revisions. Formal certification and assessment decisions remained with the appointed auditors, assessors and project authorities.

No document-control revisions reported

Outcome context: The figures presented above are reported project outcomes based on the engagement’s document registers, review records, programme information and cost-risk assessments. Results on other projects will vary according to document volume, information quality, stakeholder response times, workflow adoption and the stage at which document-control support begins.

Project information outputs

Controlled Documentation Prepared for Review, Approval and Project Use

The engagement produced structured registers, controlled project records and traceable approval information. Deliverables followed the agreed project requirements, document responsibilities and available source information.

Core project deliverables

Records Issued for Information Control and Stakeholder Coordination

The exact file structure, metadata fields and approval stages followed the project’s agreed information requirements and stakeholder responsibilities.

Controlled document register

A current record of document identity, revision, status, issue date and superseded information.

Structured project repository

Organised drawings, RFIs, submittals, specifications and supporting records connected to the project’s BIM documentation workflow .

RFI status records

Question, responsibility, due date, response and closure information maintained for review.

Submittal review records

Submission history, review comments, response status and approval conditions.

Quality-review logs

Records of naming, metadata, revision, status and completeness checks.

Sustainability evidence records

Supplied materials, energy and compliance evidence organised against relevant requirements.

Current information

Revision and status checks helped users identify the latest controlled project records.

Traceable decisions

Review comments, responses and approval outcomes remained connected to the relevant information.

Clear responsibility

Reviewer, responder and approval responsibilities were visible through the workflow.

Controlled issue

Reviewed information was issued through the agreed environment rather than informal file sharing.

Testimonial attribution: Replace “Project Manager” with a person’s name, university name or organisation only when Optimar Precon has documented permission to publish the identity, role and quotation. Do not add Review or AggregateRating schema to this testimonial.

ISO 19650 documentation enquiry

Need Structured Documentation Support for a UK Construction Project?

Send the available information-management requirements, document register, naming conventions, workflow responsibilities, current project files and required review dates. Our team will assess the documentation scope before confirming the delivery process.

  • ISO 19650-aligned document structuring
  • Common Data Environment support
  • RFI, submittal and change-control workflows
  • Document-register and quality reviews

Project requirements

Request a Documentation Scope Review

Include the project type, document volume, current platform, required workflows and target dates.

Scroll to Top