Common Causes of Delays
Most delays fall into one of four categories: Late asset delivery from the client. Many projects depend on you providing content, data, credentials, brand assets, or approvals at key stages. When those materials arrive later than scheduled, the downstream work shifts accordingly. Scope changes. When the direction of a project changes mid-engagement — new requirements are added, original goals are revised, or new stakeholders introduce different priorities — the original timeline no longer reflects reality. Scope changes are welcome, but they require an honest conversation about what adjusting the scope means for the schedule. Unforeseen complexity. Some problems turn out to be harder than they initially appear. When that happens, the timeline is updated to reflect the actual work required rather than the original estimate. You’ll always be told why, not just told that more time is needed. External dependencies. Some projects rely on third parties — vendors, platforms, other contractors, or internal approvals on your end. When those external factors introduce delays, they are flagged as soon as they are identified, even if there’s no resolution yet.How Delays Are Communicated
You will never find out about a delay after the fact. As soon as a delay is identified — even if the full picture isn’t clear yet — you’ll receive a heads-up. That initial notification will include what’s known, what’s still being assessed, and when you can expect a revised timeline. Once the impact is understood, a revised timeline is provided in writing. That document includes the updated milestone dates, the reason for the change, and any actions needed from your side. Nothing moves forward on an informal understanding — written confirmation from both parties is required before the new schedule is considered agreed upon.Steps for Resolving a Delay
1
Identify the cause
Determine exactly what is causing the delay and whether it originates on the consulting side, the client side, or from an external dependency. This distinction matters because it determines what the resolution looks like.
2
Notify the client
Reach out proactively — don’t wait until the originally scheduled milestone has passed. Explain what’s happening clearly and avoid vague language. If the full picture isn’t available yet, say so and give a time by which you’ll have more information.
3
Agree on a revised timeline
Work together to establish a new schedule that is realistic given the current situation. Both parties need to actively agree — not just one side announcing a new date.
4
Document in writing
Capture the revised timeline, the reason for the change, and any new commitments from either side in a written record. This can be a simple email confirmation or an updated project tracker entry.
5
Resume
Once the revised timeline is confirmed in writing, work resumes under the new schedule. The delay is considered resolved and does not need to be revisited unless circumstances change again.
Client-Caused Delays
Delays aren’t always on the consulting side. If you are unresponsive to review requests, late delivering agreed-upon assets, or unavailable for required decisions for more than 5 consecutive business days, the engagement may be rescheduled to a later date. This isn’t a punitive policy — it’s a practical one. Holding open time in the schedule for a project that can’t move forward prevents other clients from getting help. When a client-caused pause extends beyond five business days, you’ll receive a written notice explaining that the project is being rescheduled and proposing a new start date once the blockers on your side are resolved.Timeline extensions — whether caused by the consulting side, the client side, or external factors — do not change the total project cost unless the scope of work has also changed. You will not receive a higher invoice simply because a project took longer than originally estimated.