Summary
These examples show how Opries product screens should organise attention, records, workflow steps, and audit-friendly messages. They are practical patterns, not final screen designs.
Dashboard
Show the work that needs attention first: overdue obligations, reports due soon, documents awaiting approval, and recently updated records.
Use a clear grid with aligned summary metrics, task lists, and status tables. Avoid decorative dashboard cards that do not help users decide what to do next.
Document Register
| Column | Purpose |
|---|---|
| Document | Name and type |
| Owner | Person responsible |
| Status | Current, draft, review due, overdue, archived |
| Review date | Next required review |
| Last updated | Record freshness |
| Actions | View, edit, export |
Compliance Workflow
- User adds a funding agreement.
- Opries prompts for owner, due dates, reporting obligations, and evidence requirements.
- The workflow shows draft, review due, approved, lodged, and archived states.
- The audit trail records changes with user, date, and event.
For first-time users, include a short example funding agreement and a checklist of required fields before the form. This supports self-paced learning without interrupting experienced users.
Auditable Messages
Status change: "Report marked as lodged by Alex Nguyen on 13 Jun 2026."
Missing evidence: "This acquittal needs a signed committee approval before submission."
Export: "Document register exported by Casey Martin on 13 Jun 2026."
Checks
- Does the screen show what needs attention first?
- Are status, owner, dates, and evidence visible where relevant?
- Does the workflow include an auditable record of important changes?
- Does the screen support first-time users without slowing experienced users?