Skip to main content

Operations

The Operations page (/operations) handles two cross-cutting workflows: cross-site borrows for moving capacity around, and incidents for declaring and managing disruptions.

Cross-site borrows​

When one site is short and another has slack, a borrow request moves capacity. The New borrow request dialog captures:

  • Requesting site
  • Source site (where the agents come from)
  • Number of agents
  • Date range
  • Reason

Each borrow needs sign-off from both site managers — the source manager (yes, we can spare them) and the destination manager (yes, we can take them). The card shows decision badges per side: Pending / Approved / Rejected. Action buttons render contextually only when the current user can act.

If neither side responds within the SLA, an escalation timestamp on the card shows when the request will auto-escalate.

Incidents​

The Declare incident dialog captures:

  • Type — SITE_OUTAGE, NETWORK_OUTAGE, SYSTEM_FAILURE, PUBLIC_HEALTH, FORCE_MAJEURE
  • Scope — SINGLE_SITE or MULTI_SITE
  • Estimated duration
  • Description

Once declared, the incident card shows status (ACTIVE / RESOLVED / CANCELLED), type, scope, affected site, declared timestamp, estimated duration, the count of affected shifts, and the description.

Click into the detail drawer for:

  • The full incident timeline (immutable — every status change is appended)
  • Shift reallocation summary (cancelled, rerouted)
  • Mark resolved and Cancel actions (only while ACTIVE)

The timeline is the audit trail for after-action reviews — what happened, when, and what we did about it.

Pairs with​