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. In the real app, only permitted properties would appear.

2. Stable tabs, shaped around the role

Keep the simplicity of our top tabs. Supervisors see their own work; managers begin with Summary. Labels do not change because someone selected a discipline elsewhere. Less-used tools move into a named More page.

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

Group urgent work above the charts. 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. Charts are doors to the details

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: role-based top tabs, 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.