A visible Cleaning | Security toggle shows one discipline at a time. Cleaning is the initial view for staff; selecting Security replaces the work queues and charts rather than adding another section. Their choice stays in page links; supervisors remain in their own discipline.

Tradeoff to test

The role controls which tools are available; the discipline filters the work. These are different choices, so the role switch stays in the preview toolbar.

10. Put incoming work on the front page

Today groups Zones & Tasks and Jobs & requests inside one Work overview panel. Scheduled cleaning work lives under Zones & Tasks, reached through Tasks in the left menu. Jobs & requests holds additional Slack requests and pending approvals. Jobs is always available in the left menu for both disciplines; full lists and individual details live there so Today stays compact.

Tradeoff to test

These are sample queues, not live Slack integrations. These mock navigation changes do not move or modify production records. Security requests are separate from patrols and incidents. All open work is separate from chart date ranges.

1. One place to choose the property

Keep Justin’s consistent header picker. The building remains visible on every page, and changing pages keeps that choice. This reduces the chance of reviewing or assigning work at the wrong building.

Tradeoff to test

A global choice must always be visible. Only permitted properties appear. There is no All properties option. Restore the last permitted choice at login; otherwise use the first available property. The mock remembers this browser’s choice per preview role; production must store it per signed-in user.

2. One menu and one starting page

Today is the single landing page; Summary is consolidated into it. A collapsible left menu holds labeled icons for the tools each role needs. Collapsing it preserves accessible names and hover labels. Property and Discipline stay together in the header.

Tradeoff to test

Some secondary tools take one extra click. Primary work stays visible; nothing should exist only inside an unlabeled icon.

3. Show what needs action first

Keep overdue cleaning tasks inside Zones & Tasks and pending approvals inside Jobs & requests. Today has no separate Needs attention block. Counts link directly to a focused queue, so a supervisor can act without interpreting a dashboard or scrolling to another section.

Tradeoff to test

Live queues and historical results are different. The mock labels queues as current; date ranges apply only to the result charts.

4. Separate requests from routine work

One panel provides visual structure, while two sections retain the meaning. Zones & Tasks measures cleaning timetable completion; Patrols measures patrol completion for the selected period. Jobs & requests counts open Slack requests and pending approvals right now. A divider, separate labels, and local date controls make these different measures explicit; there is no combined total. Sections stack on smaller screens. Keep the visual summaries and Justin’s consistent discipline colors: blue for cleaning and olive for security. The whole card is clickable, and numbers, labels and arrows explain the result without relying on color.

Tradeoff to test

Charts provide orientation, not the complete record. Each opens a dedicated page with the underlying rows.

What we kept from each approach

Justin: a consistent property picker, discipline colors, and a single navigation map.

Our approach: one Today page, clickable summaries, and focused detail pages.

Read all design decisions →

Try these review tasks

Switch to Cleaning supervisor and approve a sample task.
Switch to Security supervisor and find a request.
Change property and check that its name stays visible.
Hide notes and compare against the sidebar version.

Today

Work overview

Zones & Tasks →

Jobs & Requests →

Zones & Tasks

Jobs & Requests