Forecasting · Demand Room
Turn demand into hours the roster can use.
A forecast remains a presentation if it cannot become roles, headcount and a measurable staffing plan.
This is a capability inside Lightning Pharos, not a separate product.
Forecast demand by site and interval.
01 · What ships
The complete working surface.
Demand-driven staffing instead of last month's roster.
- 01
History import, patterns, assumptions, scenarios, versions, approval, and locking
- 02
Required hours translated into the roles and headcount to schedule
- 03
Moving-average or seasonal-naive forecasting with held-out algorithm selection
- 04
Planned-versus-actual comparison and an explicit feed-plan action into Scheduling
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Forecast demand by site and interval.
- 02 / 03
Governed event
Demand becomes required hours and roles for scheduling.
- 03 / 03
Connected result
Planned and actual coverage can be compared after the week closes.
03 · What it needs
Ready inside every Pharos workspace.
No additional module is required before this capability can be switched on.
04 · Where it stops
The boundary is part of the product.
Forecasting is statistical and deterministic, not generative AI. Insufficient history remains unknown or uses a disclosed pattern replay.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system