Contract Clause Library
Timeline clause
Sets the project schedule — key milestone dates, the final delivery date, and what happens if either side causes a delay.
This clause turns the project plan into contractually referenced dates, usually tied to specific milestones from the deliverables list, and states how delays are handled — particularly the distinction between a delay the agency caused versus one caused by the client's slow responses (see the Client Responsibilities clause). It's the clause most often referenced when a project is running behind and someone's asking why.
Sample wording
Sample language (illustrative, not legal advice)
Vendor will deliver the first draft within 4 weeks of kickoff and the final deliverables within 8 weeks of kickoff, subject to timely receipt of Client materials and approvals per the Client Responsibilities section. Delays caused by Client will extend these dates by a corresponding period.
Red flags
- Milestone dates stated as fixed calendar dates rather than relative to kickoff, which breaks the moment the actual kickoff date slips
- No explicit link back to the client responsibilities clause, making it hard to attribute a delay to the correct cause
- No process for formally documenting a timeline extension, leaving the "corresponding period" adjustment informal and easy to dispute later
How MarginFlow reads it
MarginFlow tracks each milestone date against actual project activity and flags a slip, then cross-references the Client Responsibilities clause to check whether the delay is attributable to a late client response — the evidence trail that supports (or undercuts) a timeline change order.