Project Documentation and Reporting

Construction projects in the District of Columbia generate binding legal and contractual obligations through every document produced on-site — from daily field logs to stormwater inspection reports. Federal contractors operating on GSA-managed or Army Corps of Engineers projects face layered documentation requirements under eCFR Title 48 that go beyond standard commercial practice. A single missing submittal can trigger contract disputes, withhold payment, or expose a contractor to debarment proceedings. Understanding exactly which records are required, who must sign them, and how long they must be retained is not administrative overhead — it is core project execution.

The District of Columbia sits within a dense overlap of federal procurement rules, EPA environmental permits, and OSHA construction safety mandates. A contractor working on a federally funded project in DC answers simultaneously to OSHA's 29 CFR Part 1926 construction standards, the Federal Acquisition Regulations at Title 48, and local DCRA permit requirements (according to DCRA). Failure to maintain compliant records under any of those frameworks can trigger independent penalties — meaning a single project can generate liability from three separate enforcement bodies at once.

Daily Field Reports and Activity Logs

The daily construction report (DCR) is the foundational document for any project. It must capture workforce headcount by trade, equipment on-site, work completed by location and phase, weather conditions, material deliveries, and any notable incidents or delays. On U.S. Army Corps of Engineers projects, the Construction Quality Management program requires DCRs to be completed by a certified Quality Control representative — not simply the superintendent. The QC manager's signature on the DCR is a contractual attestation that work completed that day met specified standards.

Format matters: vague entries like "framing work continued" are inadequate. A compliant DCR entry identifies the specific grid lines or room numbers where work occurred, the specification section governing that work, and any nonconformances identified and corrected. The Whole Building Design Guide identifies granular field documentation as the primary defense against claims disputes — projects with complete daily records resolve claims at lower cost and faster timelines than those with gaps.

Submittal Logs and Specification Compliance Records

Submittals — shop drawings, product data, material samples — must be tracked in a formal submittal register keyed to the project specification divisions. Every submittal entry should record the specification section number (e.g., 03 30 00 for cast-in-place concrete), the date transmitted to the architect or engineer of record, the revision number, the review action received, and the date approved or returned. GSA construction standards require contractors on federal building projects to maintain a complete submittal log as a contract deliverable, often required at substantial completion.

Unapproved substitutions — installing a product before the submittal receives a formal "Approved" or "Approved as Noted" action — are among the most common causes of contract disputes. Tracking submittal status in real time prevents installation of unreviewed materials, which triggers costly removal and replacement.

OSHA Recordkeeping: Forms 300, 300A, and 301

Under OSHA recordkeeping regulations, construction employers with 11 or more employees must maintain OSHA Form 300 (the injury and illness log), Form 300A (the annual summary), and Form 301 (the incident report) for every recordable work-related injury or illness. A recordable incident includes any case resulting in days away from work, restricted duty, medical treatment beyond first aid, loss of consciousness, or diagnosis of a significant injury by a healthcare professional.

Fatalities and hospitalizations carry separate immediate reporting obligations: a fatality must be reported to OSHA within 8 hours; an in-patient hospitalization, amputation, or eye loss must be reported within 24 hours (according to OSHA). On DC projects, 29 CFR Part 1926 governs the construction-specific safety standards that underlie those recordable determinations. OSHA Form 300A must be posted at the job site from February 1 through April 30 each year.

Stormwater Documentation Under the EPA Construction General Permit

Any construction activity disturbing 1 acre or more — a threshold exceeded by most DC commercial projects — requires permit coverage under the EPA Construction General Permit (CGP). The CGP mandates a Stormwater Pollution Prevention Plan (SWPPP) before ground disturbance begins, followed by routine inspection reports completed by a qualified person at a minimum frequency defined in the permit (according to EPA, at least every 7 days and within 24 hours after a 0.25-inch or greater rainfall event in most circumstances).

Inspection logs must document the condition of all best management practices (BMPs), identify any discharges observed, and record corrective actions with completion dates. Permit exceedances must be reported to the permitting authority. Incomplete CGP documentation is a primary trigger for EPA enforcement referrals on urban infill projects.

Federal Contractor Recordkeeping Under Title 10 and Title 48

Contractors performing work under federal contracts — particularly those with nuclear facility components or Department of Energy connections — face additional recordkeeping obligations under eCFR Title 10, which includes fitness-for-duty program records and audit trail requirements. Federal Acquisition Regulations at Title 48 establish baseline requirements for cost and pricing records, subcontractor correspondence, certified payrolls (on Davis-Bacon covered work), and project closeout submittals including as-built drawings and operation and maintenance manuals.

Retention periods under FAR typically run 3 years after final payment, but contracts with audit provisions can extend that obligation to 6 or more years depending on contract type and funding source.

Organizing a Document Control System

A functional document control system assigns a unique number to every document, tracks revision status, identifies the current revision as the active version, and establishes a distribution log showing who received each document. Digital platforms can automate version control, but the underlying discipline — no document gets superseded without a formal revision process — applies regardless of software. On projects with 4 or more active subcontractors, maintaining a single master register accessible to all parties reduces RFI response delays and prevents installation errors caused by superseded drawing revisions.

References

The law belongs to the people. Georgia v. Public.Resource.Org, 590 U.S. (2020)

Continue Reading

Next Client Communication Best Practices [standard]