How to document construction delays for claims
Document delays by giving written notice fast, recording the cause and impact in daily logs, updating the schedule to show the critical path effect, tracking delay costs on their own codes, and keeping all of it in one file per event.
To document construction delays for a claim, you need five things for every delay event: timely written notice, daily records of what happened and who was affected, a schedule update showing the effect on the critical path, separate cost tracking for the delay, and a clear link between the cause and the impact. Start the file the day the delay starts, not when the job is already late. A delay claim is won or lost on records made at the time, not on what people remember a year later.
Delays are the most common reason jobs lose money and the hardest to recover. The owner will ask three questions: did it really happen, was it your fault, and did it actually push out completion. Your documentation has to answer all three.
Know your delay categories first
| Category | Typical causes | What you may get |
|---|---|---|
| Excusable and compensable | Owner changes, late design answers, owner-caused access problems, differing site conditions | Time and money, subject to the contract |
| Excusable, not compensable | Unusually severe weather, strikes, some force majeure events | Time only, in many contracts |
| Non-excusable | Your own crew shortages, your sub's late work, your late submittals | Nothing, and possibly liquidated damages |
| Concurrent | Owner delay and contractor delay at the same time | Often time but no money; rules vary |
Federal fixed-price construction gives a useful model. FAR 52.249-10 treats delays from unforeseeable causes beyond the contractor's control and without its fault or negligence as excusable, listing examples such as acts of the government, fires, floods, epidemics, quarantine restrictions, strikes, freight embargoes, unusually severe weather, and qualifying sub and supplier delays. The contractor must notify the contracting officer in writing of the causes of delay within 10 days from the beginning of the delay, unless the contracting officer extends that. Private contracts set their own rules, and some include a no damages for delay clause that limits recovery to time.
Step-by-step: documenting a delay
1. Send written notice right away
Check the contract's notice clause for who, how, and how fast. Send notice even if you do not yet know the impact. Say what happened, when it started, the work affected, and that you reserve the right to request time and money. Follow up with updates as the impact becomes clear.
2. Record it in the daily log every day it continues
The daily log should show, for each day: the delay cause, the areas and activities affected, crews and equipment idle or reassigned, weather, visitors, and any direction received. One entry on day one and silence for three weeks does not prove a three-week delay.
3. Photograph and keep the communications
Dated photos of the blocked area, the missing information, or the flooded excavation. Save emails, RFIs and their response dates, meeting minutes, and submittal logs. An RFI log with sent and answered dates is some of the strongest delay evidence you can have.
4. Update the schedule and show the critical path impact
Owners grant time for delays to the critical path, not for delays to activities with float. Keep an approved baseline schedule, update it at regular intervals with actual dates, and insert a fragment for the delay event to show its effect. On federal work, FAR 52.236-15 (when included) requires a progress schedule within five days after work starts, or another period the contracting officer sets, and periodic updates, and the contracting officer can withhold progress payment approval until it is submitted.
5. Track delay costs on their own codes
Idle labor, standby equipment, extended supervision and site costs (extended general conditions), remobilization, and acceleration all need separate codes. Without them, delay costs blur into base work and are nearly impossible to prove.
6. Build the request
A clean request has a narrative (what happened, in date order), the contract basis, the notice letters, the schedule analysis, the cost summary with backup, and the specific time and dollars requested.
Worked example: a 15-day wait on a structural RFI
Here is an illustration. A GC on a $3.4 million two-story retail building finds a conflict between the steel connection details and the architectural layout. The PM sends an RFI on March 4. The steel erector cannot set the second floor until it is answered. The RFI is answered March 19. Steel erection is on the critical path.
| Record | What it shows |
|---|---|
| RFI log entry, sent March 4, answered March 19 | Owner-side delay of 15 calendar days |
| Notice letter, March 5 | Timely written notice reserving time and cost |
| Daily logs, March 5 to 19 | Steel crew demobilized, crane released, other trades resequenced |
| Schedule update with delay fragment | Substantial completion moves 11 working days |
| Separate cost code for delay | $18,400 for crane remobilization, extended super and trailer, and erector standby |
The owner's rep argues the GC lost two days of its own on a late crane booking. Because the schedule update shows that separately, the parties agree on 9 working days and the cost of the owner-caused part. Without the logs and schedule, the GC would likely have received a few days of time and no money.
What makes delay records believable
Records made at the time carry far more weight than summaries written later. Logs should be dated, signed or tied to a user, and never edited after the fact without a note. Photos should keep their original timestamps. Schedule updates should be saved as separate versions, not overwritten. If an owner's consultant later reviews the file, consistent and unedited records are what make your version of events the one they accept.
Mistakes to avoid
- Waiting until the end of the job. Many contracts bar late claims, and memories fade.
- Daily logs that say "worked on site." Generic logs prove nothing. Record what was blocked and why.
- No baseline schedule. Without an approved baseline, there is no starting point to measure delay against.
- Ignoring your own delays. Owners will find them. Show them honestly and separate them; it makes the rest of your claim credible.
- Mixing delay costs with base costs. Use separate codes from day one.
- Signing change orders that waive time. If a change order is silent on time or says no impact, you may have given up the extension.
Templates, terms, and tools
Use the construction daily report template, the RFI log template, and the construction schedule template. Subcontractors should also read how subcontractors should document delays, and for weather, how to handle weather delays in the schedule. Related terms: excusable delay and float. Smart Business Automator ties daily logs, RFIs, photos, and cost codes to the job, summarizes daily logs, and raises risk alerts when RFIs or submittals sit too long. See RFI and submittal tracking automation.
Frequently asked questions
How soon do I need to give notice of a delay?
Whatever your contract says, and often it is short. Federal fixed-price construction under FAR 52.249-10 requires written notice of the causes of delay within 10 days from the beginning of the delay, unless extended. Give notice as early as you can.
What is a concurrent delay?
A period where owner-caused and contractor-caused delays affect completion at the same time. Many contracts and decisions give time but no money for concurrent periods, so separating the causes in your records matters.
Do I need scheduling software to prove a delay?
Not necessarily, but you do need a baseline schedule and regular updates that show the critical path. Simple tools can work on smaller jobs if they are updated consistently.
Can I claim home office overhead for a delay?
Sometimes, depending on the contract and the law that applies. It usually requires showing the delay was owner-caused and that you were on standby without other work to absorb overhead. Get advice before including it.
