How availability works
Availability answers one question: how much of this person’s time is available on a given day?
It is a value from 0% to 100%, not a present-or-away flag. Coverage is a different question:
it adds every active member’s availability for that day and expresses the total in people.
That arithmetic lives on How coverage is calculated.
A value, not a flag
Section titled “A value, not a flag”Two states, present and away, are not enough.
- Someone in training is reachable but not on the queue. That is a fraction of their time, not “out”.
- Someone split across departments is permanently partial. That is their baseline, not an absence.
- Someone on call is fully available, and “present” does not tell you it is a rotation.
Most people, most days, are fully available or fully away (100% or 0%). The value of a
percentage is the exceptions. Half of a person’s time is a real quantity, and those shares add
cleanly when you sum them into coverage.
Availability is a share of the working day, not of a clock hour. A training event at 50%
means half of that day’s time remains available. Temprix does not split the day into morning and
afternoon slots.
Whole days
Section titled “Whole days”Temprix plans in whole calendar days. An event covers the days you give it, not 14:00 to 18:00. A one-day event is that day. A Monday to Friday event is those five days.
Working hours are recorded on a member and used for presence display. They do not change availability.
Baseline availability
Section titled “Baseline availability”Baseline availability is how much of a person’s time is available when no event covers the day.
It is set per member. Most people sit at 100%. A baseline below 100% describes a permanent
arrangement rather than an absence: a split role, regular training that takes part of the week,
an engineer who owes half their week to escalations.
| Member | Baseline | Ordinary working day, no events |
|---|---|---|
| Dana | 100% |
100% |
| Ben | 80% |
80% |
| Priya | 60% |
60% |
When you create an event, the form offers the lower of the event type default and the member
baseline, so a 100% on-call event on a 60% member is offered at 60%. That is a convenience
in the creation form. Once saved, the engine uses the value on the event.
Unscheduled time also has a baseline time type, set on the workspace and optionally on a team. That is reporting only. See Time type.
The working week
Section titled “The working week”The working week is the set of non-working days. New workspaces start with Saturday and Sunday off. That list is set on the workspace, and any member can overwrite it with their own set. They are part of who a member is, not a recurring event to maintain. A four-day contract is Friday off. You do not need to create a repeating Friday absence.
This is deliberately different from a reduced baseline. Both describe less available time over a week, and they answer a given Friday differently:
| Member | Arrangement | Mon | Tue | Wed | Thu | Fri | Week |
|---|---|---|---|---|---|---|---|
| Ana | Friday non-working | 100% |
100% |
100% |
100% |
0% |
4.0 |
| Ben | 80% baseline |
80% |
80% |
80% |
80% |
80% |
4.0 |
Same weekly total of available time, different Fridays. Baseline does not leak onto Saturday for either of them.
A 0% baseline on a working day is still a working day: the person is scheduled as fully
unavailable, and reports that count working days still include it. A non-working day is not a
working day.
Calendar days versus working days
Section titled “Calendar days versus working days”Time Distribution and Member Time Breakdown can count Calendar days or Working days.
- Working days follows the working week. Non-working days are omitted.
- Calendar days includes every day in the range. A member’s non-working days with no covering event are counted and attributed as Non-working.
A reduced baseline does not change which days count. Friday at 80% is still a working day.
Friday set as non-working is not.
Events
Section titled “Events”An event is a description of a period. It carries an availability value: how much of the person’s time remains available while it runs. The value is inherited from the event type, which inherits from its category, and either can be overridden on the individual event.
That value is availability remaining, not time consumed. Annual leave at 0% means fully
away. Training at 50% leaves half of the person’s time available.
Starting points from the default configuration (types inherit the category value unless you change them):
| Category | Event type | Availability | Time type |
|---|---|---|---|
| Planned Time Off | Annual Leave | 0% |
Non-working |
| Unplanned Time Off | Sick Leave | 0% |
Non-working |
| Internal Operations | Training | 50% |
Secondary |
| Core Operations | Standard Work | 100% |
Primary |
| Reactive Operations | On-call Duty | 100% |
Standby |
| Holidays | Public Holiday | 0% |
Non-working |
These are starting points, adjustable per workspace and per team. Other leave types in the
default set (Parental Leave, Personal Leave, Emergency Leave) also sit at 0% Non-working.
Offsite types sit at 50% Secondary. Team-specific demo types can differ.
An event does not have to reduce anything. On-call duty and standard work sit at 100%. The
event exists so the rotation is visible and reportable, not to move the number.
Creating, editing, recurrence, and confirmation live on Member events. Categories and types live on Event categories and types.
Recurring and unconfirmed events
Section titled “Recurring and unconfirmed events”Recurring events are expanded into individual dated occurrences before anything is calculated. The engine sees concrete days, never the rule.
Unconfirmed events do count. Confirmation state affects how an event is presented on the timeline, not the availability value.
Group events
Section titled “Group events”Group events apply by location match rather than by a list of names: public holidays, office closures, shutdown weeks. You pick a country when you create one. The app does not allow a group event without a country.
Matching, and members without a country, are covered on Group events. How a matching group event enters the team number is on How coverage is calculated.
Non-working time
Section titled “Non-working time”By default, a member event is a claim about working days. Training from Monday the 10th to Friday the 21st means the ten working days, not fourteen calendar days. The weekends inside the span stay at zero unless you say otherwise.
A member event can be set to count on non-working time. That is how Saturday on-call, holiday volunteer shifts, and approved weekend overtime get a non-zero availability. The setting lives on the event type as a default, and you can change it on the individual member event. If neither is set, the event does not count on non-working time.
Group events cannot carry that setting.
Time type never determines this. Reclassifying a category as Standby or Non-working does not decide whether weekends inside a span count.
In the default set, Standard Work, On-call Duty, and Stand-by Duty are set to count on non-working time. Other types are not, unless you change them.
How a non-working day, a public holiday, and a member event set to count on non-working time resolve for a person, including the worked examples, is on How coverage is calculated.
Time type
Section titled “Time type”Every event category carries a time type: Primary, Secondary, Standby, or Non-working. It classifies what a period counts as for time-attribution reporting (Time Distribution and Member Time Breakdown).
This is why Core Operations and Reactive Operations both sit at 100% and are still separate
categories: the same share of a person’s time, doing a different kind of work.
When no event covers a day, reports use the baseline time type. That is set on the workspace and can be overridden per team. Multi-team views use the workspace default.
Non-working as a time type is a reporting label (leave, rest). Non-working days are the working week. Whether an event counts on those days is the non-working-time setting on the member event. None of these three determines the other.
Where to go next
Section titled “Where to go next”- How coverage is calculated is how these values become a team number in people.
- Timeline is where you see and edit the days.
- Member events covers creating events, recurrence, and confirmation.
- Event categories and types is where default availability and time type are configured.
- Group events covers location-targeted holidays and closures.
- Time Distribution is the retrospective view, attributed by time type rather than availability.