Capacity Forecast
The capacity endpoint produces an authenticated 90-day operational view by role category. It combines enabled-team profiles, open task estimates, the prior 30 days of time entries, and probability-weighted open-deal value.
It is a planning signal—not a staffing commitment, delivery forecast, or automated allocation engine.
How the signal is calculated
Section titled “How the signal is calculated”Each enabled team member is assigned a reference capacity of 160 hours per month. The forecast compares the sum of their open-task estimated hours with that reference capacity:
| Signal | Threshold |
|---|---|
| Green | Below 70% of reference capacity |
| Amber | 70% to below 85% |
| Red | 85% or above |
It also reports open-task count, committed estimated hours, and a trailing 30-day billable percentage. Pipeline demand is reported separately as probability-weighted value; it is not converted into staff hours by the endpoint.
Operating routine
Section titled “Operating routine”- Review red and amber roles at the weekly operating review.
- Open the contributing tasks and confirm their owners, estimates, due dates, and statuses.
- Compare the capacity signal with current timesheet utilization and real delivery commitments.
- Decide whether to re-estimate, reassign, defer, hire, or decline work—and record that decision in the normal CRM workflow.
Important boundaries
Section titled “Important boundaries”- Missing or inaccurate task estimates distort the signal.
- A 90-day window does not prove a project schedule or individual availability.
- The endpoint requires an authenticated CRM role, but it is a legacy role-gated REST surface rather than a substitute for the module permission matrix.
- Do not use the forecast as a payroll, performance, or compensation record.