Failure PatternDecision layer
The Frozen Roster Trap: Why Resource Planning Stalls When Capacity Data Lags Demand
Symptom: Schedules are rebuilt in a spreadsheet every Monday because the planning tool's bookings no longer match what delivery leads actually promised clients. Root cause: Planning data is entered manually and asynchronously, so the schedule reflects intentions rather than committed work; tools like Float and Resource Guru only stay accurate if bookings are updated the moment a scope change is agreed.
By InnovaAI ResearchPublished
How do you recognize it?
- •Schedules are rebuilt in a spreadsheet every Monday because the planning tool's bookings no longer match what delivery leads actually promised clients
- •Utilization reports show 85% billable across the agency while two senior designers are quietly working 55-hour weeks and a strategist sits at 40%
- •New project kickoffs get staffed by whoever the account lead remembers is free, not by who the capacity chart says has room
- •Time entries land in the tracking system three to five days after the work happens, so the forecast is always describing last week
- •Freelance spend spikes in the final two weeks of a quarter even though the capacity plan predicted a surplus
Why does it happen?
- •Planning data is entered manually and asynchronously, so the schedule reflects intentions rather than committed work; tools like Float and Resource Guru only stay accurate if bookings are updated the moment a scope change is agreed
- •Capacity is modeled in whole-person units instead of hours by skill, which hides the difference between a team that is 90% booked on the right work and one that is 90% booked on work nobody can deliver
- •Time tracking sits in a separate system from scheduling, so actuals never feed back into the forecast; Everhour and Toggl capture hours that planners rarely reconcile against the plan
- •Approval authority for overbooking is unclear, letting account leads commit delivery dates without a capacity check, which pushes the correction cost onto the delivery team
How do you fix it?
- •Pick one source of truth for bookings this week and delete every competing spreadsheet; if the schedule lives in Runn or Float, the Monday spreadsheet stops existing
- •Add a 15-minute Friday reconciliation where actual hours from Hubstaff or Tempo are compared against planned hours, and flag any person above 90% or below 60% for the coming week
- •Convert capacity from headcount to hours by discipline so a 40-hour week for a junior developer and a 40-hour week for a creative director stop looking identical on the heatmap
- •Require a named approver for any booking that pushes a person past 85% utilization, and log the exception so patterns of overcommitment become visible at the retainer review