Job Description for Document Controller in Construction

STANDARD OPERATING PROCEDURE: CONSTRUCTION DOCUMENT CONTROLLER (CDC)

Document ID: SOP-TR-ENG-409
Effective Date: October 24, 2023
Version: 3.2
Review Cadence: Semi-Annual

---

1. EXECUTIVE SUMMARY & PURPOSE

1.1 Purpose

This Standard Operating Procedure (SOP) defines the operational scope, technical competencies, and procedural workflows for the Document Controller in Construction role at Template Registry. The purpose of this document is to establish an institutional-grade framework for managing engineering drawings, contracts, submittals, Requests for Information (RFIs), and project correspondence to prevent site rework, eliminate contractual disputes, and ensure strict compliance with ISO 19650 Information Management standards.

1.2 Objective

To maintain a single source of truth across all active construction lifecycles, ensuring zero latency between site execution teams and engineering design offices regarding design revisions and contractual directives.

---

2. SCOPE & PREREQUISITES

2.1 Scope

This procedure applies to all capital construction projects, civil infrastructure developments, and design-build initiatives managed by Template Registry. It governs all project documentation phases from pre-construction feasibility through procurement, construction execution, and closeout/handover.

2.2 Software & Technical Toolchain

• Common Data Environment (CDE): Autodesk Construction Cloud (BIM 360), Bentley ProjectWise, or Aconex.
• Enterprise ERP: Procore, Oracle Primavera P6 (for schedule-linked submittals).
• Productivity Suite: Microsoft 365 Enterprise (Advanced Excel, SharePoint, Teams).
• PDF Manipulation & Markup: Bluebeam Revu eXtreme (Required for batch overlay, stamp automation, and OCR).

2.3 Physical Prerequisites & Safety (PPE)

When visiting active construction sites or material testing laboratories, the Document Controller must adhere to Template Registry Site Safety Protocol (SOP-SAF-001):

• Hard hat (ANSI Z89.1 Class E).
• High-visibility safety vest (ANSI/ISEA 107 Class 2).
• Steel-toe safety boots (ASTM F2413).
• Safety glasses with side shields (ANSI Z87.1).

---

3. ROLES & RESPONSIBILITIES (RACI MATRIX)

Legend:

• R = Responsible (The role that performs the activity)
• A = Accountable (The role with final approval and fiduciary ownership)
• C = Consulted (The role providing advisory input)
• I = Informed (The role kept updated on progress)

---

4. STEP-BY-STEP PROCEDURE

Phase 1: Common Data Environment (CDE) Setup & Ingestion

• Establish project folder structures within the CDE adhering strictly to BS 11652 / ISO 19650 naming conventions (e.g., [Project]-[Originator]-[Volume]-[Level]-[Type]-[Role]-[Number]).
• Configure metadata taxonomy, custom attributes, and automated workflow triggers for drawing revisions and submittal reviews.
• Audit incoming transmittals within 2 hours of receipt against the contractor’s Master Document Register (MDR).
• Validate native file formats (e.g., .dwg, .rvt) alongside flat formats (.pdf) to ensure editable and immutable files are correctly cataloged.

Phase 2: Processing RFIs and Technical Submittals

• Receive formal RFI/Submittal packages via the CDE ingest portal.
• Perform a pre-screening quality check using Bluebeam Revu to verify completeness, contractor signatures, and alignment with technical specifications.
• Log the submission in the Master Log, assigning a unique sequential tracking number (e.g., RFI-STR-042).
• Route the submittal to the designated Lead Engineer or Architect based on the engineering discipline matrix.
• Monitor review durations against contract SLAs; issue automated escalation notices at 48 hours prior to contractual deadlines.

Phase 3: Revision Control & Distribution Management

• Upon approval/rejection, apply standardized institutional stamps (Approved, Approved as Noted, Revise and Resubmit, Rejected) via Bluebeam.
• Supersede previous drawing revisions in the CDE, moving superseded files to the restricted archive directory with a SUPERSEDED watermark.
• Distribute latest revision packages to field operations via mobile CDE sync, notifying the Site Superintendent via automated push alerts.
• Generate a weekly Delta Log detailing all drawing and specification changes made during the preceding 7-day window.

Phase 4: As-Built Compilation & Project Handover

• Collect daily red-line markups from the Site Superintendent and Quality Control Managers bi-weekly.
• Coordinate with the design team to ensure all Field Change Orders (FCOs) and Request for Deviations (RFDs) are formally drafted into CAD/BIM as-built models.
• Compile the final Operations & Maintenance (O&M) manuals and As-Built deliverables into a searchable, hyperlinked digital archive.
• Execute formal handover of the digital CDE archive to the client asset management team within 30 days of Practical Completion.

---

5. QUALITY ASSURANCE & PRO-TIPS

5.1 Key Performance Indicators (KPIs) & Metric Thresholds

• Processing Velocity: 100% of incoming documents logged and routed within 4 hours of receipt.
• RFI Turnaround Compliance: Maintain an on-time review rate of $\ge 95%$ across all engineering disciplines.
• Version Integrity Error Rate: $0%$ tolerance for field teams working off superseded drawing revisions.

5.2 Pro-Tips

• Automate Metadata Extraction: Leverage Bluebeam Batch Processing and OCR plugins to automatically harvest drawing numbers and titles from title blocks, reducing manual data entry errors by up to 70%.
• Rigorous Naming Protocols: Never allow manual file renaming by external subcontractors. Enforce CDE upload scripts that reject files failing naming-convention regex parsing.

5.3 Common Pitfalls to Avoid

• Orphaned Submittals: Accepting physical paper or unlogged email attachments without generating an official CDE transaction ID.
• Inadequate Superseding: Failing to immediately lock superseded revisions, which directly results in costly site rework due to construction occurring on obsolete designs.

---

6. FREQUENTLY ASKED QUESTIONS

Q1: What is the exact protocol when a subcontractor submits a file with a non-compliant naming convention?
A: Reject the transmittal immediately through the CDE portal using the preset rejection code ERR-NAM-01. Do not manually rename the file on their behalf, as this breaks chain-of-custody and accountability. Return the document with an automated system notification citing Section 4 (Phase 1) of this SOP.

Q2: How should urgent site RFIs that bypass standard CDE workflows be handled?
A: Emergency verbal instructions or site sketches must be logged retroactively as an "Emergency RFI" within 24 hours. The Document Controller must secure a retroactive sign-off from the Project Manager and Lead Engineer to maintain contractual validity and liability coverage.

Q3: What actions are required when a drawing revision changes structural or life-safety parameters?
A: Immediately flag the transmittal for "High Priority Impact." The Document Controller must manually email the Site Superintendent, Lead QA/QC Manager, and Safety Officer, and ensure the previous revision is hard-locked in the mobile field viewer within 1 hour of ingestion.