Capacity Report
Managers and financial admins only.
The daily PO capacity report: who has free capacity, who is over-committed, and what is planned for everyone in the upcoming two-week window (next Monday → following Friday). Generated every day at 10:00 from Tempo (teams, schedules, plans) and Jira (unscheduled work) — teams and membership are discovered from Tempo automatically.
Summary metrics
Total free hours, over-allocated count, needs-work count, and no-schedule count — each person counted once even if they are in several Tempo teams.
Per-team tables
One row per person (part-timers show their FTE %):
| Column | Definition |
|---|---|
| Capacity h | Working hours in the window from Tempo’s schedule. |
| Planned h | Hours scheduled in Tempo plans. |
| Unscheduled h | Remaining estimates on assigned, undated Jira stories. |
| Planned+Unsched h | The committed total. |
| Capacity left | Capacity − committed, as hours and %. |
| Flag | 🔴 OVER (+overload %) · ⚠️ UNDER · ✅ OK · ⚪ NO_SCHEDULE (no Tempo workload scheme — not vacation). |
Under each table, a collapsed expander per person lists their planned work (story, dates, window hours, logged, remaining) with a link to the team’s Tempo Planner view.
Detail sections
- Over-allocated — who is over and why (a note marks overloads that are invisible in Tempo because undated stories cause them).
- Needs work planned — most free capacity first.
- Unscheduled queue — per person, the committed-but-undated stories.
- Report date selector — browse previous days’ reports.
A Slack summary of the report is DM’d to the report owner every Friday morning. All other days the report just refreshes silently.