Build Gallery, example type, read 8 Nov 2026
A reorg scenario: who can model one, and what the model holds
The trap is the live record: a scenario built by editing the org chart is a reorg, not a model. The view needs a copy of the reporting line, the cost per person or band, the location and the span policy, and a way to compare two versions.
HiBob's workforce planning scenarios are a delivered model and Rippling's headcount planning is the nearest delivered view; Workday's sandboxed what-ifs are the enterprise form; a Shapes Vibe View on a copied reporting-line table is the built form.
Who can build it, and how
| Platform | How | Source |
|---|---|---|
| HiBob | Workforce planning scenarios, delivered | www.hibob.com/platform/core/analytics/ |
| Rippling | Headcount planning report; a scenario view is built from a prompt | www.rippling.com/platform/analytics |
| Workday | Scenarios in a sandbox, delivered | www.workday.com/en-us/ai-platform/analytics-report |
| Shapes | A Vibe View on a copied reporting-line table | shapes.co/vibe-views |
Where Shapes is weak
Questions that need payroll or ATS data are answered through integrations, not from Shapes's own records.
Sources
- HiBob, read 8 Nov 2026
- Rippling, read 8 Nov 2026
- Workday, read 8 Nov 2026
- Shapes, read 8 Nov 2026
- Shapes Vibe Views library, read 8 Nov 2026
Last reviewed 10 Nov 2026.