How capacity works
Each member has a daily capacity value from 0.0 (fully unavailable) to 1.0 (fully available). Temprix sums these fractions across a team to show real coverage — not just headcount.
Why fractional beats binary
Section titled “Why fractional beats binary”Binary availability (“in” or “out”) hides partial commitments. A team of four where one person is at half capacity is not a team of three or four — it’s 3.5.
Fractional capacity lets you model:
- Half-day training (0.5)
- Reduced on-call load (0.7)
- Full vacation (0.0)
- Normal working day (1.0, the default when no events apply)
Where modifiers come from
Section titled “Where modifiers come from”Every event carries a capacity modifier that determines how much availability remains. Modifiers can be set at three levels, from most specific to most general:
- Individual event override — set when creating or editing a specific event.
- Event type default — the modifier configured on the event type (e.g., Training defaults to 0.5).
- Event category default — the modifier shared by all types in a category.
When multiple events overlap on the same day, the minimum modifier wins. See Modifiers & precedence for the full resolution rules.
Worked example
Section titled “Worked example”A team of four members, all at full capacity (1.0 each), has a team total of 4.0.
One member logs a Training event with modifier 0.5 for Tuesday:
| Member | Tuesday capacity |
|---|---|
| Member A | 1.0 |
| Member B | 0.5 (Training) |
| Member C | 1.0 |
| Member D | 1.0 |
| Team total | 3.5 |
The Capacity Outlook and timeline reflect 3.5 — not 3, not 4.
What to read next
Section titled “What to read next”- Modifiers & precedence — overlap resolution and the zIndex stacking model
- Reading the capacity outlook — interpreting the report
- Event categories & types — configuring default modifiers