The job of this console
Build a scenario, test a move, compare, then apply on the live planner if leadership agrees.
Resources · Simulation
Capacity Simulation
What-if staffing and bench moves before you commit the roster — Team capacity remains the live planner.
Scroll to Flowcharts. Scenario: Simulate a staffing move before committing.
Sandbox
Try the move before the roster is true
Capacity simulation models staffing and bench moves without writing the live roster. Commit stays on Team capacity.
Resources → Capacity simulation
Route
/resources/planner
Org flag plannerEnabled
Resource Manager · Project Manager
Seat at the table
Resource and project managers. Employees do not sandbox their own week here.
The working rhythm
Open sim, change, compare, commit elsewhere or discard.
Moments that bring you here
Before a big start date. Bench overflow. A what-if for a bid. After a resignation.
ⓘ
Not live assignments
Timesheet and delivery read Team capacity / assignments, not this sandbox.
Flowcharts
1 — Sandbox then commit
Model a move, compare, commit on live capacity if approved.
flowchart TD
A[Open Capacity simulation] --> B[Build scenario]
B --> C[Move people / demand]
C --> D[Compare to live]
D --> E{Commit?}
E -->|Yes| F[Team capacity]
E -->|No| G[Discard / save sandbox]
- 1OpenResources → Capacity simulation.
- 2ModelSandbox moves.
- 3CompareLive Team capacity.
- 4CommitOnly on the live planner.
Overview
Simulation is a sandbox. Team capacity writes live assignments on Employee and Project. Utilization is the demand/load lens.
How to use
1. Do not treat sandbox as roster
Finance and timesheet read live assignments.
2. Name scenarios
Or you will apply the wrong one.
3. Staffing requests
Fulfill from live capacity, not only the sim.