Capacity Planning - Application Overview

The customer problem

Workforce-driven operations live or die on getting headcount right ahead of demand, but most plan in spreadsheets built on last year's averages and a planner's intuition. The result is chronic mis-staffing: over-hire and carry idle cost, or under-hire and miss service, burn overtime and churn staff. Worse, the plan is a single number with its assumptions buried, so when it is wrong nobody can see which assumption broke.

The business impact is cost and service risk baked in months ahead. Hiring and training have long lead times, so a bad capacity plan cannot be fixed in-week - it locks in overtime, attrition and SLA misses. For an RCM or contact-centre operation, this also means being unable to defend a headcount ask to finance with anything better than 'we think we need more people'. The customer needs a requirement they can justify, with the assumptions on the table.

How Time Champ addresses it

Capacity Planning turns forecast demand into a defensible capacity requirement. The demo areas include Volume forecast, accuracy, seasonality and events, intraday and voice, what-if demand, capacity rules, standards, work drivers, workforce availability, skills, balancing, service levels, scenarios, and hiring and long-range plans.

The core move is to compute required capacity from forecast volume, handling standards, service goals and shrinkage, then set it against available capacity (workforce availability and skills) to expose the gap. Scenarios and what-if demand make assumptions explicit and testable - change the volume or the shrinkage and watch the requirement move. Skills and balancing matter because a plan is not just an FTE total; it is the right skills in the right intervals. Accuracy tracks how good past forecasts were, so the plan carries its own credibility.

Confirm with product how volume is sourced and which forecasting method applies for a customer; the demo shows the model on seeded data.

The value and how to measure it

The value is a staffing plan the customer can defend and act on in time - sized to real drivers, with assumptions visible, and expressed as skills-in-intervals rather than a headcount lump. That lets them hire ahead, challenge a forecast, and justify a number to finance with evidence.

Measure with the grounding's candidate measures: forecast bias/accuracy by an agreed method (is the volume forecast consistently over or under, and measured how - the single biggest driver of plan quality); unresolved skill gaps (intervals or skills where required exceeds available and no plan closes it); review cadence (is the plan revisited as reality moves, not set once); and plan approval (does a named owner sign off the plan and its assumptions). Honest framing: the value is a better, testable requirement with owned assumptions - not a promise of perfect staffing.

Sales task made concrete

Your task is to compare requirement and available capacity, and show one scenario with its assumptions. Concretely:

1. Open the overview (https://capacityplanner.demo.timechamp.io/#/overview) and the dashboards (https://capacityplanner.demo.timechamp.io/#/dashboards).
2. Show required capacity vs available capacity for a period and point to the gap - the shortage or surplus by skill, not just the total.
3. Run one what-if scenario: change a single assumption (volume up for a seasonal event, or shrinkage higher) and show the requirement move. Then say the integrity line: 'The plan is only as good as these assumptions - here they are, on the table, and here is how sensitive the answer is to them.'
4. Close on defensibility: 'This is the number you take to finance, with the drivers behind it, not a spreadsheet guess.'

Discovery to pair: 'How do you build your capacity plan today, and what assumptions sit inside it?' 'When the plan is wrong, can you tell which assumption broke?' 'Do you plan to an FTE total or to skills by interval?'

CSM task made concrete

Your task is to validate volume, handling standards, shrinkage, skills, service goals and forecast accuracy, then run a capacity review. A routine before the plan is trusted:

1. Volume: confirm the demand source and that seasonality and known events are reflected.
2. Handling standards and work drivers: validate the standards that convert volume into effort - defaults will be wrong for the customer's work mix.
3. Shrinkage: confirm the shrinkage assumption is the customer's real figure, not a placeholder; it swings the requirement heavily.
4. Skills and service goals: confirm required skills and the service levels the plan is sized to.
5. Forecast accuracy: review past forecast bias/accuracy by an agreed method so the customer knows how much to trust the number.
6. Then run a recurring capacity review with a named approver, and specifically check skill/interval coverage - not just the headline FTE balance (see interpretation check).

Objections and honest limits

'Our overall FTE looks balanced, so we are fine.' This is the core interpretation check: an overall FTE balance does not prove every skill and interval is covered. You can be net-balanced for the week and still be short of a skill at peak and long of another in the trough. Always inspect coverage by skill and interval, not the total.

'We already plan in Excel / we have a WFM tool.' Excel hides assumptions and cannot test them quickly; the value here is explicit, sensitivity-testable assumptions, skills-in-intervals, and forecast accuracy tracking. Against an incumbent WFM, qualify what it actually does for skills balancing and scenarios before positioning.

'Just give us the number.' A number without its assumptions is the problem you are solving, not the solution. The deliverable is the requirement plus its drivers.

Honest limit: output quality depends entirely on input validity (volume, standards, shrinkage). Forecasting methods and data sourcing for a customer must be confirmed with product.