Modifiers & precedence

When a member has multiple events on the same day, Temprix resolves capacity using one rule: the minimum modifier wins. This page is the canonical answer to “why does the timeline show X?”

Minimum modifier wins

If a member has Training (0.5) and a Holiday (0.0) on the same day, capacity is 0.0 — the holiday takes precedence because 0.0 < 0.5.

This applies regardless of which event was created first or which appears on top visually.

Visual stacking (zIndex)

Events stack on the timeline in a fixed order. Higher zIndex values render on top, but stacking is visual only — capacity always uses the minimum modifier.


Layer	zIndex	Typical modifier
Unplanned Time Off	50	0.0
Planned Time Off	40	0.0
Ops	30	0.5
Offsite	20	0.3
Holidays	10	0.0

Default dataset modifiers

The Default dataset ships with these category-level modifiers:

Category	Default modifier
Time Off	0.0
Holidays	0.0
Training	0.5
Offsite	0.3
Ops	0.5
Other	1.0

Individual event types within a category can override these defaults. See Event categories & types.

Edge cases

Multi-day recurrence overlap

When a recurring event series overlaps with a single-day event, the minimum modifier applies per day independently. Each day in the range is evaluated on its own.

Group event under a member event

A group holiday (0.0) applies to all targeted members. If a member also has a member event with modifier 1.0 on the same day, capacity is still 0.0 — the group event’s modifier participates in the minimum calculation.

Modifier 1.0 events

Events with modifier 1.0 do not reduce capacity. They can still appear on the timeline for visibility (e.g., “Working from home” logged for tracking purposes) without affecting the capacity total.

What to read next

• How capacity works — the fractional model and worked examples
• Timeline view — reading stacked events on the timeline