# Design reference — fictional supplier review screen

## Purpose
Help an operations reviewer see what is ready, what is missing and who acts next.

## Existing design rules
- Reuse the project's type, colour, spacing and component tokens.
- Keep one page heading, a short introduction and a table or list of cases.
- Show supplier, status, evidence gap, owner and next action for every case.
- Use text labels as well as colour for status.
- Use at least 16px text for phone inputs and 44px targets for primary controls.
- At 390px, stack the case fields instead of shrinking the table's text.
- Preserve visible focus, meaningful labels and reduced-motion preferences.

## Sample cases
- Cedar Components: Needs evidence; coverage schedule missing; owner: Procurement.
- Harbour Supplies: Ready for review; evidence complete; owner: Reviewer.
- Elm Services: Needs evidence; certificate expired; owner: Procurement.

## Boundaries
- This screen prepares a review; it does not approve suppliers.
- Do not invent branding, metrics, testimonials or a working backend.
- Keep existing navigation and the current theme switch.

## Review before handing over
Check 390px and 1280px, both themes, long supplier names and keyboard use.
The next action should still make sense when colour is unavailable.