Monitoring your outlets

Read the Overview home, the cross-outlet Checklists page, and each outlet's own page — including the real values and photos staff submitted.

The manager console is built so you can answer one question fast: which outlet needs me right now? — and then, once you’ve picked one, what actually happened there? Everything on these pages reads from the same live numbers, so a count you see in the sidebar always matches the page it opens, and a checklist’s status never disagrees between the Checklists page and an outlet’s own page.

Note: The compliance and analytics views need the reports-viewing permission (ops.reports.view); the Checklists page, an outlet’s checklist list, and opening a checklist’s submitted values need the checklist-approval permission (ops.checklists.approve) — the same permission that lets you resolve, waive, or reassign escalations. Managers and admins have both.

The Overview home

Overview is the console landing page — your first screen every morning. It opens with a greeting and a one-line summary of the day: “2 missed · 1 running late · 3 escalations”, or the far nicer “All clear across 4 outlets”.

Below that sit four stat cards, each of which taps through to the page where you fix it:

Missed today — tasks whose day closed without them being done.
Running late — tasks past their deadline but still open.
Compliance — the day’s percentage, with tasks done out of total.
Escalations — open control-point breaches.

The body pairs two columns: outlets needing you (your outlets ranked worst-first by compliance — click one to jump straight to that outlet’s own page) beside the top of the open escalations queue and a set of quick actions — New checklist, Assign task (jumps to the Checklists page), Outlets, Escalations.

The console sidebar carries live count badges so you can see trouble without opening anything:

Checklists — late plus missed, right now.
Escalations — open escalations across all outlets.
Outlets — how many outlets are in your cluster.
Tickets — open maintenance tickets across all outlets.
Templates and Assets — how many templates and registered assets you have.

Each badge is sourced from the same query as the page it opens, so the number on the badge and the number on the page never disagree.

The Checklists page

Checklists (under Operate in the sidebar) is the checklist-first cross-outlet view of today. Cards are one outlet’s copy of one checklist — a checklist run — collapsed by default and showing the template title, outlet, department chip, time window, and a status derived the same way everywhere in the console:

Done — every task done. Carries a · late mark when any task in it was completed after its own deadline; late work still counts as done, it just says so.
Missed · n/m — the day closed with tasks left undone.
Overdue — the checklist’s window has expired but the day hasn’t closed yet, so it isn’t final yet. It can still recover into “Done”.
In progress · n/m — some tasks done, window still open.
Pending — nothing done yet, window still open.

Click a card to expand it and see its individual tasks; click any task row to open the checklist’s submitted values and photos — see “Checklist submissions” below.

The KPI band is three tiles that add up to the day’s checklists — Completed, Missed, In progress — with an “of which N late” line inside Completed when any of today’s completions ran late. Late is never a fourth tile; it’s a quality note on the completed count, not a separate bucket.
The filter bar is the same true partition as segments — All / Done / Missed / In progress — plus a Late toggle chip beside them that narrows to late items within whichever segment is active, and outlet/department dropdowns.
The header button reads Open outlet overview once you’ve narrowed the outlet filter to exactly one outlet, or View outlets otherwise.

Today is the only day the Checklists page covers — for any other day, open the outlet’s own page.

Each outlet’s own page

Outlets (under Cluster in the sidebar) shows every outlet as a compliance card, ranked worst-first so the outlet that needs you leads the grid. Each card carries:

a compliance gauge and progress bar, colour-stepped green / amber / red;
a four-cell split: Done, Late, Missed, Escal;
its open-ticket count;
a red border and a Needs you pill when compliance drops below 75%.

An outlet with nothing scheduled today says No checklists today rather than pretending to be at 0%.

Click a card — or an outlet row from Overview’s “outlets needing you” — to open that outlet’s own page, a full screen (not a side panel) built around three clearly labelled time contexts:

Today, always. The header carries today’s compliance ring, no matter which day you’re browsing below it.
The day you pick. A date row (prev/next arrows, a picker capped at today — you can’t browse into the future, and a Today button reappears once you’ve stepped back) drives the checklist list right below it, and a day-by-day strip for that date’s whole week sits under the list so you can spot a bad patch at a glance.
A trailing range you choose. A Day / Week / Month toggle switches the analytics further down between today, the trailing 7 days, and the trailing 30 days — three sparklines (Compliance, Escalations, Maintenance spend) plus headline counts for Missed, Late, Open tickets, and Escalations over that same range.

Stepping through days never changes the analytics range, and changing the range never changes which day’s checklists you’re looking at — each zone loads and fails independently, so a slow analytics call never blocks the checklist list above it.

If your account only has reports access (no checklist approval), the checklist list and week strip are replaced with a quiet note pointing at the analytics below, which is still yours. The mirror case applies if you can approve checklists but don’t have reports access.

Checklist submissions

Clicking a checklist — from a task row on the Checklists page or a card on an outlet’s page — opens the one shared surface for what staff actually filled in: the checklist’s sections, each task’s status, who completed it and when, and the real submitted values, not a placeholder.

Readings, subtask ticks, multiple-choice, free text, and confirmations each render per their field type, straight from what was recorded.
Photo fields show a “Show N photos” reveal; opening it fetches short-lived signed download URLs for that task’s photos (nothing is signed until you ask). Click a thumbnail for a full-screen view with the capture time and, when the device recorded one, a GPS coordinate badge.
A waived task renders distinctly and stays excluded from the checklist’s completion count.
A task with nothing submitted (because the window is still open, or because the day closed with it undone) shows plainly as such.

This page reads the same date <= today data as everything else — open a checklist from three days ago exactly the way you’d open today’s.

Reading compliance

The day’s numbers come from a simple, honest model, and it’s the same model behind both the task-level Late/Missed figures above and the checklist-level Done/Missed/Overdue statuses on the Checklists page and outlet pages:

Late — a task past its deadline but still open while the day is running, or one completed after its deadline. Late work can still recover into “done late”.
Missed — final only once the day has closed with the task still undone. While the day is still running, a task or checklist past its window but not yet closed is Overdue, not missed.
Compliance % — tasks done out of tasks scheduled, per outlet and estate-wide.

Because late, overdue, and missed are all derived live against the current time — not from a stale flag — the Checklists page, an outlet’s own page, the Overview stat cards, and the sidebar badges all move together the moment a deadline passes, and never disagree with each other for the same outlet and day.

The deadline itself, and what a miss triggers, are covered in Scheduling checklists and Escalations; open maintenance work rolls up from Maintenance and tickets.

Press Cmd+K (Ctrl+K on Windows), or click the Search… pill in the top bar, to open the command palette. Type a page name — “checklists”, “escalations”, “reports” — press Enter to jump there, and Esc to close. Every console page you can see in the sidebar is reachable this way, which makes bouncing between Checklists, Outlets, and Escalations during a rough morning much faster than the mouse.

A few more shortcuts work anywhere in the console:

Cmd+B (Ctrl+B) — collapse or expand the sidebar.
g then o — jump to the Overview.
g then t — jump to the staff Today board.