Capacity Planning: Clients and portfolios
Objective. Read the clients-and-portfolios structure and explain that a portfolio-level balance can hide a shortfall on an individual client.
This screen organises capacity by client and portfolio so a provider can plan and roll up across many clients - while still seeing each client's own requirement and commitments.
See it in the demo
What this screen answers
A Sales or CSM person opens this to answer 'how does capacity look across our book of clients, and for each one?' A provider serving many clients needs both the portfolio view and the per-client detail, because capacity and commitments differ by client. This screen is where that structure lives.
The task
Scope to the portfolio, read the rollup, then drill to an individual client to check its own required versus available. The move is to never stop at the aggregate: confirm each client is covered for its own commitments. Describe it as 'the portfolio rollup and per-client view', not invented labels.
How to read it
A portfolio balance is an aggregate that can hide per-client shortfalls. This is the app's core interpretation check applied to clients: net-balanced across the book does not mean every client meets its SLA - one client can be short while another is long. The misread is approving staffing on the portfolio total. Read per client, against each client's own KPIs and SLA, not the sum.
Honest limits
This screen shows structure and rollup; it does not prove each client's commitments are met - that depends on per-client KPIs, SLAs and coverage by skill and interval. Confirm the portfolio/client structure matches the customer's real book with product and the account team.
Interpretation check
A portfolio-level capacity balance can hide a shortfall on an individual client - read per client against each client's own commitments, never the aggregate alone.
In the field
A BPO/RCM provider managing a book of clients: approving seats on the portfolio total can leave a single client under-staffed against its SLA - the per-client drill is what prevents that.
Practical task
Read a portfolio rollup, then drill into one client and write a one-line finding: is that client covered for its own commitments, and does the portfolio total hide its position?
Self-check
The portfolio nets out balanced. Is every client covered?
No. One client can be short while another is long. A portfolio balance hides per-client shortfalls; read each client against its own KPIs and SLA.
Why keep both portfolio and per-client views?
Capacity and commitments differ by client. The rollup is for the book-level picture; the per-client view is where coverage against that client's commitments is actually checked.
What per-client detail must you check beyond the headcount total?
Coverage by skill and interval against that client's own KPI and SLA targets - the aggregate FTE total does not prove any single client is met.
Verified vs demo. Screen is live in the demo at /#/clients; exact controls and figures are SME-validation-pending.