Contract Clause Library
Client responsibilities clause
Lists what the client must provide or do — content, access, approvals, feedback — for the project to stay on schedule.
A project's timeline depends on the client holding up their end: providing brand assets on time, granting system access, turning around approvals within a stated window. This clause makes those dependencies explicit and, usually, ties a client delay to a corresponding timeline extension so the agency isn't penalized for someone else's slow response.
Sample wording
Sample language (illustrative, not legal advice)
Client will: (1) designate a single point of contact authorized to approve deliverables; (2) provide requested assets, access credentials, and feedback within 5 business days of request; (3) respond to scheduling requests within 2 business days. Delays in Client's performance of these responsibilities will extend the project timeline by a corresponding period.
Red flags
- Responsibilities listed with no corresponding timeline-extension consequence when the client is late
- No named point of contact, leaving approvals stuck between multiple stakeholders
- Response windows so generous (30+ days) that they don't actually protect the schedule
How MarginFlow reads it
MarginFlow extracts each numbered responsibility and its stated response window separately, so a slow client (a request sitting unanswered past the agreed window) can be flagged as the documented cause of a timeline slip — evidence that supports a timeline change order rather than the agency quietly absorbing the delay.