Team Capacity

Last updated: 2026-04-17 Owner: Product Writer Audience: manager, hr_admin, tenant admin, owner

Purpose

Explain how to read Team Capacity as a managerial view of availability, saturation, and operational margin across people in the selected period.

What you find here

The page combines in one place:

• usable availability per person
• planned load
• already reported load
• constraints from leave, travel, and on-call coverage
• project filter for the visible perimeter

It does not replace the source modules. It is meant to show very quickly who still has margin, who is at risk, and where you should drill down next.

How to read the view

The module is split into three levels:

1. Priority board
2. People list
3. Person detail

Priority board

The board groups people by risk state:

• Critical
• At risk
• Watch
• Balanced

Use it to see immediately where intervention should start.

People list

Each card shows:

• name and role
• risk state
• availability state
• available hours
• planned load
• actual load
• remaining margin

Person detail

The side panel shows:

• role and projects in the active perimeter
• nominal and available hours
• planned and actual utilization
• breakdown of leave, travel, and on-call coverage
• optional fallback signals when the system relies on secondary indicators

Contextual actions

From the person detail you can open the most useful source modules without losing context:

• Attendance
• Requests
• Travel
• Timesheet
• Professional profile

The return path back to Team Capacity preserves:

• horizon
• anchor date
• project filter
• person filter
• selected person

In the first pass some CTAs stay intentionally limited:

• Requests and Travel open a team view already focused on the selected person
• Attendance can focus another person only for owner, admin, and manager
• Timesheet and Professional profile still remain self-service, so for other people they are explicitly marked unavailable

Available filters

You can narrow the view by:

• Horizon: week or month
• Anchor date
• Project
• Find person

The person filter only works on the list already loaded, so it does not change the server-side aggregation logic.

Expected outcome

A manager should be able to understand within seconds:

• who is truly available
• who is saturated or close to the limit
• where load is consuming too much usable margin
• which people should be realigned first

Operational notes

• Team Capacity is a managerial reading surface, not a data entry page
• the project filter narrows the visible people, but each person load is still read honestly across the selected period
• this module does not replace Operational calendar: here you read saturation and margin, there you read coverage and day-by-day signals
• the CTAs do not fake permissions: if a source module does not yet support focus on another person, the detail panel says so explicitly

FAQ

Is this view for approvals?

No. Approvals stay in Approval Center.

Can I use it as a team timesheet?

No. Timesheet remains the hour-entry module. This view is for reading aggregated load and deciding where to intervene.