Capacity Planning: Seats and support
Objective. Read seat and support constraints as hard limits that can cap a people plan, so FTE alone is not treated as deliverable capacity.
This screen answers: do we have the seats, workstations and support capacity to host the plan? A non-people constraint can cap an otherwise balanced people plan.
See it in the demo
What this screen answers
The customer question is: even if we have the people, can the site physically and operationally host them - seats, workstations, support ratios. A CSM validates the constraint; a rep uses it to show the plan is grounded in real operating limits.
The task
Review the seat and support constraints for the scope and set them against the people plan. The job is to find where a seat or support limit caps the deliverable capacity below the FTE the plan assumes.
How to read it
Seats are a hard constraint that can cap a people plan. Having the FTE does not help if there is no seat at that interval or site - deliverable capacity is the minimum of people and seats, not the people number alone. The classic misread is ignoring seat limits and treating FTE as deliverable capacity. For a hybrid or multi-site operation this is where a plan that looks staffed can still fail because the physical or support capacity is not there.
Honest limits
Seat and support data and its source must be confirmed with the customer. This is a planning constraint view, not a facilities or desk-booking system - it flags the limit, it does not allocate the desk. Confirm support ratios reflect the customer's real operating model.
Interpretation check
Seats and support are hard constraints; deliverable capacity is the minimum of people and seats, so an FTE-balanced plan can still be capped by a seat limit.
Practical task
Review the seat/support constraints for a scope, find one interval or site where seats could cap the people plan, and write one line on the deliverable capacity there.
Self-check
The people plan is balanced but the operation still cannot deliver. How can a seat constraint cause that?
Deliverable capacity is the minimum of people and seats. If there is no seat at that interval or site, the FTE cannot be used - the plan is capped below its headcount.
Why does this matter especially for multi-site or hybrid operations?
Physical and support capacity varies by site and interval, so a plan that looks staffed overall can fail where the seats or support are not there.
Is this a desk-booking system?
No. It is a planning constraint view that flags the limit; it does not allocate specific desks.
Verified vs demo. Screen is live in the demo at /#/seats; exact controls and figures are SME-validation-pending.