Failure PatternDecision layer
The Ghost Capacity Trap: Why Resource Planning Fails When Availability Data Lags Reality
Symptom: Schedulers show a designer at 60% booked while their actual week is full of unlogged client calls, Slack threads, and revision rounds. Root cause: Booked hours and worked hours live in separate systems. A schedule in Float or Resource Guru records intent, while Toggl or Everhour records what actually happened, and nothing reconciles the two on a weekly cadence.
By InnovaAI ResearchPublished
How do you recognize it?
- •Schedulers show a designer at 60% booked while their actual week is full of unlogged client calls, Slack threads, and revision rounds.
- •Delivery leads discover a missed deadline only after the fact, because the plan reflected a capacity number nobody had updated since the kickoff meeting.
- •Two agencies on the same retainer report wildly different utilization for the same team, and neither number survives a spot check against timesheets.
- •Account managers start keeping private spreadsheets of who is really free, which quietly becomes the real scheduling system.
- •New project intake gets approved against a capacity picture that is three weeks stale, so the work lands on people already at their limit.
Why does it happen?
- •Booked hours and worked hours live in separate systems. A schedule in Float or Resource Guru records intent, while Toggl or Everhour records what actually happened, and nothing reconciles the two on a weekly cadence.
- •Unplanned work (scope creep, ad hoc client requests, internal reviews) never gets entered as a booking, so the plan only ever sees the work someone remembered to schedule.
- •Capacity is treated as a static number set at project kickoff rather than a rolling estimate that shifts with holidays, sick days, and ramp time for junior staff.
- •Nobody owns the reconciliation step. Scheduling is assumed to be a manager's side task, so the update loop breaks the first week a deadline gets tight.
How do you fix it?
- •Run a one-week audit comparing scheduled hours against tracked hours per person, and publish the variance to the delivery team so the gap is visible rather than assumed.
- •Add a standing 15-minute Friday reconciliation where each project lead confirms next week's bookings against real availability before Monday intake.
- •Reserve a fixed percentage of every person's week as unbooked buffer (10 to 15% is a workable starting point) so unplanned client work has somewhere to land.
- •Require any request that adds more than four hours to a person's week to be entered as a booking the same day, even if the estimate is rough.