Report Header
Project identifiers, report number, author, submission date, and distribution list so recipients know scope and provenance immediately.
A consistent report creates a single source of truth for delays, helps determine responsibility, supports entitlement and cost recovery, and reduces disputes by documenting facts and timelines in a replicable format.
Project managers, contract administrators, and site supervisors commonly prepare the report to document delays and notify stakeholders.
Recipients often include the project controls team, client representatives, the commercial/legal team, and any subcontractors or suppliers directly affected.
| Field | Configuration |
|---|---|
| Report ID | Auto-generate using project code + counter |
| Attachments | Allow PDF, JPG, PNG, DOCX, XLSX with max size limits |
| Approval Path | Route to PM → Contracting Officer → Finance |
| Notifications | Send email/SMS alerts on submission and approval |
Choose delivery channels and eSignature settings that match contract and regulatory needs.
Ensure chosen methods preserve timestamps, author identity, and attachments; prefer platforms with audit trails and secure storage.
Issue initial report within 24–72 hours when feasible per contract notice clauses.
Submit supporting claim materials within the contractual claim notice period.
Incorporate delay into the baseline or recovery plan by the next reporting cycle.
Request cost recovery or time extensions within billing cycle requirements.
Keep records according to applicable retention rules in the project jurisdiction.
Detect and log the timing issue with initial facts and witnesses.
Analyze schedule effects, knock-on tasks, and preliminary mitigation options.
Send required contractual notice to owner and affected parties.
Agree corrective actions, update schedule, and close the report when verified.
Project identifiers, report number, author, submission date, and distribution list so recipients know scope and provenance immediately.
One-paragraph synopsis of what happened, the immediate schedule impact, and a short statement of required decisions or approvals.
Chronological statement of events that includes precise times, personnel, vendor actions, and relevant communications tied to the incident.
Quantified schedule impact using baseline tasks, float consumption, affected predecessors/successors, and estimated completion changes.
Factual analysis of contributing causes and an objective assignment of responsible party or force majeure classification where applicable.
List of mitigation steps, owners, deadlines, and monitoring metrics to restore schedule or claim compensating actions.
Use PDF for final signed reports and consolidated evidence bundles; PDFs preserve layout and are widely accepted for archives.
Attach baseline and updated CPM snapshots as PDF or XLSX showing impacted tasks, durations, and float calculations.
Include time-stamped JPG/PNG images with captions and GPS data when available to support site conditions.
Provide exported email threads or system logs (EML, PDF, CSV) showing communications and timestamps relevant to the event.
A mid-size property developer documented subcontractor delays to preserve the closing date
An operations director used structured reports to link a schedule variance to a procurement delay
Primary preparer and signer for routine timing reports; certifies factual accuracy and assigns corrective actions. The PM typically coordinates attachments and submits the report into the project control system.
Authorized to sign formal notices that may affect contract time or cost; signs claim submissions and approves sending formal notices to the client or subcontractors as required.