Skip to main content
Skip to main content

Documentation Standards

Document Type: Policy
Version: 1.0
Last Updated: February 2026
Distribute To: All Project Personnel


Purposeโ€‹

Establish company-wide documentation standards to ensure consistency, protect against disputes, meet compliance requirements, and support project success.


The Golden Rule of Construction Documentationโ€‹

"If it's not documented, it didn't happen."

In construction disputes, the party with better documentation wins. Every conversation, decision, delay, and issue should be documented.


Daily Documentation Requirementsโ€‹

Daily Reports (Field Personnel)โ€‹

Due: End of each work day
Who: Superintendent, Foreman, or designated reporter

Required Content:

  • Date, project name, report number
  • Weather conditions (start, end, temperature, precipitation)
  • Manpower by trade (company employees and subs)
  • Work performed (specific locations and activities)
  • Materials received and installed
  • Equipment on site
  • Visitors and inspections
  • Issues, delays, or impacts
  • Safety observations
  • Tomorrow's planned activities
  • Photos (minimum 3-5 per day)

Photo Requirements:

  • Overall site conditions (AM and PM)
  • Work in progress by each active trade
  • Concealed work BEFORE covering
  • Deliveries (especially for tracking purposes)
  • Any issues, defects, or damage
  • Weather conditions if impacting work

Time Documentationโ€‹

Due: Daily
Who: All employees and supervisors

Required:

  • Start and end times
  • Project/cost code allocation
  • Overtime justification
  • Supervisor approval

For Prevailing Wage/Certified Payroll:

  • Classification and wage rate
  • Fringe benefit allocation
  • Apprentice ratios verified
  • Certified payroll submitted weekly

Project Documentation Requirementsโ€‹

Submittalsโ€‹

Track:

  • Submittal number and revision
  • Date submitted
  • Date required for approval
  • Specification section
  • Current status
  • Reviewer and response date

File Naming: [ProjectNumber]_SUB_[SpecSection]_[Description]_Rev[#]


RFIs (Request for Information)โ€‹

Track:

  • RFI number
  • Date submitted
  • Response required date
  • Question/request
  • Response received
  • Schedule/cost impact

File Naming: [ProjectNumber]_RFI_[Number]_[Description]

Response Time Standards:

  • Routine RFI: 7 calendar days
  • Urgent RFI: 48 hours
  • Document delays when exceeded

Change Ordersโ€‹

Document:

  • Change order number
  • Description of changed work
  • Reason for change (owner request, field condition, design error, etc.)
  • Cost breakdown (labor, material, equipment, subs, markup)
  • Schedule impact (if any)
  • Approval signatures
  • Date work can proceed

File Naming: [ProjectNumber]_CO_[Number]_[Description]


Meeting Minutesโ€‹

Document:

  • Date, time, location
  • Attendees (name and company)
  • Agenda items discussed
  • Decisions made
  • Action items (owner, due date)
  • Next meeting date

Distribute: Within 24 hours
File Naming: [ProjectNumber]_MINS_[YYYYMMDD]_[MeetingType]


Photo Documentation Standardsโ€‹

Naming Conventionโ€‹

[ProjectNumber]_[Date]_[Location]_[Description].jpg

Example: 2024-001_20260201_Level2_Electrical-Rough.jpg

Minimum Requirementsโ€‹

Project PhasePhotos/DayFocus Areas
Mobilization10+Existing conditions, lay-down areas
Foundation5-10Excavation, rebar, concrete
Structure5-10Steel, decking, connections
MEP Rough-In10+Before close-up, penetrations
Close-Up5-10Insulation, drywall progress
Finishes5-10Quality, defects, progress
Punch ListAs neededEach deficiency
Closeout20+Final conditions, all areas

What to Always Photographโ€‹

  • Existing conditions (before work)
  • Underground work before backfill
  • Concealed work before cover-up
  • Test/inspection results
  • Defects or damaged materials
  • Delays (weather, access issues, etc.)
  • Safety hazards found and corrected
  • Deliveries (quantities, condition)

Filing Structureโ€‹

Digital File Organizationโ€‹

/Projects
/[ProjectNumber]_[ProjectName]
/01-Contract
/02-Drawings
/03-Specifications
/04-Submittals
/05-RFIs
/06-Change-Orders
/07-Meeting-Minutes
/08-Daily-Reports
/09-Photos
/10-Correspondence
/11-Safety
/12-Financial
/13-Closeout

Retention Requirementsโ€‹

Document TypeRetention Period
ContractsPermanent
As-Built DrawingsPermanent
Insurance certificatesLife of project + 10 years
Financial records7 years
Daily reportsLife of project + 6 years
Safety records5 years or per OSHA
Payroll records7 years (10 for prevailing wage)
General correspondence6 years

Email Documentationโ€‹

Subject Line Formatโ€‹

[Project Number] - [Topic] - [Action Required/FYI]

Example: PRJ-2024-001 - RFI #45 Response - Action Required

When to Use Email vs. Other Methodsโ€‹

Use Email WhenDon't Use Email When
Paper trail neededSensitive/confidential discussions
Non-urgent mattersComplex negotiations
Distributing documentsEmergency situations
Confirming verbal agreementsMatters requiring nuance
Formal noticesDelivering bad news

Important: Written Confirmationโ€‹

After any verbal discussion that includes commitments or decisions, send confirmation email:

Subject: Confirmation - [Topic Discussed] - [Date]

[Name],

Per our conversation today, I am confirming the following:
- [Key point 1]
- [Key point 2]
- [Agreed action items]

Please let me know if I have misunderstood anything.

Regards,
[Your name]

Quality Standardsโ€‹

Document Review Checklistโ€‹

Before submitting any document:

  • Correct project number/name
  • Date is current
  • All required fields completed
  • Spelling and grammar checked
  • Attachments included
  • Correct recipients
  • Appropriate tone

Common Documentation Mistakes to Avoidโ€‹

โŒ Backdating documents
โŒ Altering documents after signing
โŒ Vague descriptions ("worked on building")
โŒ Missing dates or signatures
โŒ Photos without context or labels
โŒ Informal language in formal documents
โŒ Storing documents only locally (no backup)


Tools and Technologyโ€‹

Software Optionsโ€‹

  • Daily Reports: BLDR Pro, Procore, Raken, or other mobile reporting tools
  • Document Management: Procore, BLDR Pro, cloud storage (Google Drive, SharePoint)
  • Photos: BLDR Pro, CompanyCam, or any app with auto GPS/timestamp
  • Time Tracking: BLDR Time, Procore, or your payroll system's time module

Backup Requirementsโ€‹

  • All project documents backed up daily
  • Cloud storage preferred
  • Local backup weekly
  • Test restoration quarterly

  • Daily Report Template
  • Photo Log Template
  • RFI Log Template
  • Change Order Form
  • Meeting Minutes Template

Template provided by support.construction. Customize with your company information.

Was this page helpful?