Skip to main content
Skip to main content

Document Control Playbook

Overview​

Every construction project generates thousands of documents — contracts, drawings, submittals, RFIs, daily reports, change orders, inspection reports, and more. When documents are disorganized, people waste time searching, use outdated drawings, miss critical deadlines, and lose legal protection.

This playbook gives you a practical system for organizing, controlling, and managing construction documents from project start through closeout and retention.

Why Document Management Matters​

Construction disputes often come down to documentation. The party with better records usually wins. If you can't find the RFI that documented a differing site condition, or the submittal that showed the owner approved a material substitution, you've lost your proof — and potentially your claim.

Operational Efficiency​

The average construction professional spends 35-40% of their time on non-productive activities, and a significant portion of that is looking for information. A well-organized document system gives people the right information at the right time, which translates directly to better decisions and fewer mistakes.

The Cost of Poor Document Management​

  • Rework from using outdated drawings — a single instance can cost thousands or tens of thousands of dollars
  • Missed deadlines for submittals, RFI responses, and change order notices that result in denied claims
  • Failed inspections because the required documentation wasn't available
  • Closeout delays because as-builts, O&M manuals, and warranties weren't collected throughout the project
  • Unrecoverable costs from changes you performed but can't document

Document Types to Manage​

  • Prime contract and all amendments
  • Subcontracts and purchase orders
  • Insurance certificates
  • Bonds (bid, performance, payment)
  • Permits and licenses
  • Lien waivers (conditional and unconditional)
  • Notice documents (preliminary notices, stop notices)

Drawings and Specifications​

  • Original bid set
  • Issued-for-construction (IFC) drawings
  • Addenda and bulletins
  • Revised drawings (track all revisions)
  • Shop drawings
  • As-built drawings
  • Specifications (all divisions and sections)

Submittals​

  • Submittal schedule
  • Product data submittals
  • Shop drawing submittals
  • Sample submittals
  • Submittal review responses (approved, approved as noted, revise and resubmit, rejected)

RFIs (Requests for Information)​

  • RFI log
  • RFI submissions with supporting documentation
  • RFI responses from architect/engineer
  • Impacted drawings or specifications

Daily Reports and Field Documentation​

  • Daily reports (superintendent and foreman)
  • Progress photos (organized by date and location)
  • Inspection reports
  • Safety reports and incident documentation
  • Meeting minutes
  • Delivery tickets and material receipts

Closeout Documents​

  • O&M manuals
  • Warranty letters and certificates
  • Final lien waivers
  • Certificate of substantial completion
  • Certificate of occupancy
  • Final as-built drawings
  • Training records
  • Attic stock documentation

Document Organization System​

Folder Structure​

Use a consistent folder structure for every project. Here's a recommended structure:

PROJECT_NAME/
├── 01_Contracts/
│   ├── Prime_Contract/
│   ├── Subcontracts/
│   ├── Purchase_Orders/
│   ├── Insurance/
│   └── Bonds/
├── 02_Drawings/
│   ├── Bid_Set/
│   ├── IFC_Set/
│   ├── Addenda/
│   ├── Bulletins/
│   ├── Revisions/
│   ├── Shop_Drawings/
│   └── As_Builts/
├── 03_Submittals/
│   ├── Submittal_Log/
│   ├── Pending/
│   ├── Approved/
│   └── Rejected/
├── 04_RFIs/
│   ├── RFI_Log/
│   ├── Open/
│   └── Closed/
├── 05_Correspondence/
│   ├── Owner/
│   ├── Architect/
│   ├── Subcontractors/
│   └── Inspectors/
├── 06_Daily_Reports/
│   ├── 2024-01/
│   ├── 2024-02/
│   └── ...
├── 07_Photos/
│   ├── Progress/
│   ├── Safety/
│   └── Issues/
├── 08_Safety/
│   ├── Safety_Plan/
│   ├── Toolbox_Talks/
│   ├── Incident_Reports/
│   └── Inspections/
├── 09_Financial/
│   ├── Pay_Applications/
│   ├── Change_Orders/
│   ├── Lien_Waivers/
│   └── Budget/
├── 10_Meetings/
│   ├── OAC_Meetings/
│   ├── Subcontractor_Meetings/
│   └── Internal_Meetings/
├── 11_Inspections/
│   ├── Building_Dept/
│   ├── Special_Inspections/
│   └── Quality_Control/
└── 12_Closeout/
    ├── OM_Manuals/
    ├── Warranties/
    ├── Final_Lien_Waivers/
    ├── As_Builts/
    └── Training_Records/

Naming Conventions​

Use a consistent naming format for all documents:

[TYPE]_[NUMBER]_[DESCRIPTION]_[DATE].[ext]

Examples:

DocumentFile Name
RFI #001 about site accessRFI_001_Site_Access_20240115.pdf
Submittal #023 for concrete mixSUB_023_Concrete_Mix_Design_20240203.pdf
Change Order #005 for added scopeCO_005_Added_Electrical_Scope_20240220.pdf
Daily Report for January 15DR_20240115_Main_Street_Project.pdf
Drawing revision for sheet A-101DWG_A-101_Rev03_20240301.pdf
Meeting minutes for OAC meeting #12MTG_OAC_012_20240215.pdf

Naming rules:

  • Use underscores instead of spaces (spaces cause problems in many systems)
  • Use dates in YYYYMMDD format (sorts chronologically)
  • Include the document type prefix for quick identification
  • Include revision numbers when applicable
  • Keep descriptions brief but meaningful
  • Never use special characters (&, #, %, etc.) in file names

Document Management Process​

Step 1: Receive​

When a document comes in (email, mail, hand-delivered, or uploaded):

  • Log it immediately — record the date received, who sent it, and what it contains
  • Assign a tracking number if applicable (RFI number, submittal number, etc.)
  • Acknowledge receipt — confirm with the sender that you received the document

Step 2: Review​

  • Determine who needs to review the document and by when
  • Route to the appropriate reviewer (PM, superintendent, engineer, etc.)
  • Track the review — set a deadline and follow up if it's not completed on time
  • Document the review decision — approved, rejected, revise and resubmit, etc.

Step 3: Distribute​

  • Send to all parties who need it — don't assume people will find it on their own
  • Use a transmittal for formal document distribution
  • Confirm receipt for critical documents (especially revised drawings)
  • Record the distribution — who got what, and when

Step 4: File​

  • Save to the correct folder following your naming convention
  • Replace outdated versions — move superseded documents to an archive folder, clearly marked as superseded
  • Update the log — mark the document as filed with its location

Step 5: Archive​

  • At project completion, organize the entire project folder for long-term storage
  • Create a project summary listing all key documents and their locations
  • Back up everything — maintain at least two copies in different locations
  • Set retention reminders — flag when documents can be disposed of per your retention schedule

Manual Process: Physical Files​

If you still use physical filing (or need to maintain physical copies):

Setup​

  • Use a filing cabinet or banker's boxes organized by project
  • Create tabbed dividers matching the folder structure above
  • Use color-coded folders for quick identification (red for contracts, blue for drawings, yellow for financial, etc.)
  • Keep a master log (spreadsheet or binder) that tracks every document received and filed

Daily Workflow​

  1. Collect all incoming documents at a central location
  2. Log each document in the master tracking sheet
  3. Route documents to the appropriate reviewer
  4. File reviewed documents in the correct folder
  5. Update the log with the filing location

Limitations​

  • Physical files can only be in one place at a time
  • No search capability beyond manual browsing
  • Vulnerable to loss, damage, fire, and water
  • Difficult to share with multiple parties simultaneously
  • No version control beyond manually marking documents as superseded

Digital Process: Cloud Storage​

Cloud storage (Google Drive, Dropbox, OneDrive, Box) provides significant advantages over physical files:

Benefits​

  • Access from anywhere — field and office teams can reach the same files
  • Search capability — find documents by name, content, or metadata
  • Version history — see previous versions and who made changes
  • Simultaneous access — multiple people can reference the same document at the same time
  • Automatic backup — cloud providers handle backup and redundancy

Best Practices​

  • Mirror the folder structure above in your cloud storage
  • Set permissions so people can view but not accidentally delete or move files
  • Use the sharing features instead of emailing copies (which creates version confusion)
  • Enable version history and train your team to use it
  • Establish a naming convention and enforce it — cloud search works best with consistent names

Digital Process: Project Management Software​

Platforms like Procore, PlanGrid, Fieldwire, and Autodesk Construction Cloud provide purpose-built document management:

Advantages Over Cloud Storage​

  • Workflow automation — submittals and RFIs follow defined review and approval workflows
  • Automatic numbering and logging — the system maintains logs automatically
  • Drawing management — hyperlinked drawing sets with automatic revision tracking
  • Mobile access — field teams can access current drawings on a tablet
  • Audit trail — every action is logged with who, what, and when
  • Integration — connects with other project tools (scheduling, cost management, etc.)

Best Practices​

  • Set up the project correctly at the start — folder structure, user permissions, and workflows
  • Train everyone who will use the system, including subcontractors
  • Migrate existing documents into the system early
  • Use the system as the single source of truth — don't maintain parallel copies elsewhere

Version Control​

The Problem​

Using the wrong version of a drawing, specification, or submittal is one of the most expensive mistakes in construction. A framer who builds from the Rev 2 drawings when Rev 4 has been issued will likely have to tear out and redo the work.

The Solution​

Implement a version control system that ensures everyone always works from the latest documents:

Best Practices​

  1. Clearly mark revisions — every document revision should include the revision number and date in the file name and on the document itself
  2. Issue drawing logs — maintain a log that shows the current revision of every drawing. Distribute updated logs whenever new revisions are issued
  3. Retrieve superseded copies — when new drawings are issued, physically collect or digitally archive the old versions to prevent accidental use
  4. Notify all parties — when a new revision is issued, send a notification to everyone who has the previous version. Don't assume they'll notice on their own
  5. Date-stamp everything — every document should show when it was created, revised, and distributed
  6. Controlled copy distribution — maintain a distribution matrix showing who has copies of controlled documents. When revisions are issued, update every copy holder

Common Mistakes​

1. No Standard System​

Every project manager sets up their own folder structure. Every superintendent names files differently. When someone leaves or a new person joins a project, they can't find anything. Pick one system and use it everywhere.

2. Filing by "I'll Do It Later"​

Documents pile up on desks, in email inboxes, and on desktops. "Later" never comes. File documents the same day they're received — make it part of the daily routine, not a weekly catchup task.

3. Email as a Filing System​

Email is a communication tool, not a document management system. Important documents buried in email threads are effectively lost. Save documents to the project folder and use email only for the transmittal.

4. No Version Control​

Three different versions of the same drawing are in circulation, and no one knows which is current. This leads to rework, disputes, and claims. Always track and control document versions.

5. Ignoring Closeout Until the End​

Waiting until the project is 95% complete to start collecting closeout documents means you're chasing subcontractors who've already moved on to other projects. Collect closeout documents throughout the project — start at the beginning.

6. No Backup​

A single copy of critical project documents — whether physical or digital — is a disaster waiting to happen. Hard drives fail, offices flood, and laptops get stolen. Maintain redundant copies and verify your backups regularly.

Document Retention​

How Long to Keep Documents​

Document TypeRetention Period
Contracts and legal documents7-10 years after project completion (or longer per legal counsel)
Drawings and specificationsProject duration plus retention period (typically 7-10 years)
Financial records7 years minimum (IRS requirement)
Safety records5-7 years (OSHA requires 5 years for injury/illness logs)
Daily reports and photosProject duration plus statute of limitations (varies by state)
Insurance certificatesDuration of coverage plus 7 years
Employee recordsDuration of employment plus 7 years
CorrespondenceProject duration plus statute of limitations

Best Practices​

  • Check your state's statute of limitations for construction defect claims — this often drives your retention period (can be 10+ years in some states)
  • Consult your attorney for specific retention requirements based on your project types and jurisdictions
  • Create a retention schedule and review it annually
  • Don't destroy anything related to a project with an active or potential dispute
  • Digital storage is cheap — when in doubt, keep it

The Bottom Line​

Document control isn't glamorous, but it's one of the most impactful things you can do for your construction business. Good document management protects you legally, saves your team hours of searching, prevents costly mistakes from outdated information, and makes closeout faster and smoother.

Pick a system — any system from this playbook — and commit to it. A simple system that everyone follows beats a sophisticated system that nobody uses. Start with the folder structure and naming conventions, then build from there. The key is consistency: same structure, same names, same process, every project, every time.

ResourceLink
Document Control GuideDocument Control
Submittal Management PlaybookSubmittals
RFI Process PlaybookRFI Process
Transmittal GeneratorCreate Transmittal
BLDR Probldr.pro

Was this page helpful?