Operational calendar

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

Purpose

Explain how to read the Operational calendar as a team-first view over people, days, coverage, and cross-module signals.

What you find here

The page unifies these modules in the same frame:

• Attendance and work location
• Requests
• Travel
• On-call
• Timesheet workload signals

It does not replace source modules. Its job is to show quickly where you have coverage, where people are unavailable, and where deeper review is needed.

How to read the view

The module is split into two levels:

1. Minimum daily coverage
2. Team grid

Minimum daily coverage

Each day card shows:

• visible people in the current scope
• available people
• people on leave
• people travelling
• people on on-call coverage

The day summary can be:

• Coverage ok
• Coverage at risk
• Coverage critical

In the first pass, coverage is estimated from the primary event of the day inside the filtered scope.

Team grid

Each row is a person. Each column is a day in the active range.

The cell shows:

• the primary signal for that day
• any secondary signals
• any overlays, for example Timesheet workload or missing hours

Available filters

You can narrow the view with:

• View: week or month
• Anchor date
• Module
• Project
• Find person

The person filter works on the already loaded list and reduces noise without changing the team-first logic.

Operational detail and quick actions

The view now includes an Operational detail panel alongside the team grid.

The panel shows:

• selected person
• selected day
• primary signal
• any additional signals
• Quick actions to source modules

Quick actions preserve calendar context:

• selected day
• selected person
• the minimum state of the calendar view

When you open a source module, you also get a Back to Operational Calendar link so the flow stays continuous.

Expected result

The reviewer or manager should understand within a few seconds:

• who is available
• who is absent or travelling
• which days have fragile coverage
• which source module should be opened next

Operational notes

• the view is intentionally team-first
• the calendar does not replace Approval Center
• Timesheet signals are supportive overlays, not the primary content of the day
• the project filter narrows the scope to assigned people

FAQ

Is this module used for approvals?

No. Approval decisions remain in Approval Center. This view is for reading the team’s operational situation.

If I see a signal here, can I close it directly from this page?

Not directly inside the calendar grid. The correct first-pass model is:

1. read the selected day in the detail panel
2. open the source module through the quick action
3. complete the work in the real module
4. return to the operational calendar if you need to continue team reading