Wellbeing Mark
ADEK
A national wellbeing framework, turned into a product a school can finish on its own and a team of validators can stand behind.
- Role
- Product designer, end to end
- Organisation
- ADEK, Technology & Smart Services
- Timeline
- 2025 to 2026, two phases
- Platform
- Web, inside ADEK's Compliance System
- Status
- Phase 1 shipped · Phase 2 designed

Overview
Every private and charter school in Abu Dhabi answers to ADEK. Its Compliance System could schedule inspections, but it had no way to see the thing ADEK now cared about most: how well a school actually looks after the wellbeing of its students and staff.
The answer was the Wellbeing Mark, a framework built on five SPIRE dimensions. On paper it was complete. In practice it was a rulebook: dimensions, elements, practice statements, each with minimum requirements, frequency and exposure. My job was to make it something a school could complete without a consultant, and something ADEK could validate without a spreadsheet.
What I owned
- The information architecture that turns SPIRE's nested rules into a navigable, one-level-at-a-time flow.
- The school journey in Phase 1: build the self-evaluation, evidence each practice, submit with confidence.
- The ADEK journey in Phase 2: plan a visit, split the checklist, validate across six stages, and produce a report.
- The role model and permission states for six roles, designed with the business analysts and engineers.
The framework was never the problem. Asking people to hold it in their heads was.
Objectives → Design framing
How might a school meet every SPIRE minimum without ever reading the rulebook?
How might every practice a school claims arrive already checkable?
How might a visit move through six people and six stages without losing a single decision?
Key constraints & tradeoffs
Wellbeing had to behave like the other visit types schools already knew, so I extended existing patterns instead of inventing new ones.
Principals are provisioned automatically and assign the coordinator in PASS. The product could not ask anyone to create an account.
At least two practice statements per element, minimum frequency and exposure per statement. The design had to enforce policy, not soften it.
Student, parent and teacher surveys run in a separate system, so the hand-off had to be a clean state change, not a new feature.
How objectives translated to features
A school can fail an element on a minimum it never saw. When the rules live in a PDF, the first person to discover a mistake is the validator, weeks later.
Design decisions- Progressive disclosure: dimension, then element, then practice statement, never all three at once.
- Guidelines, minimum requirements, frequency, exposure and limiting factors shown at the exact moment a school makes a claim.
- A live selection summary and a disabled Continue until each element has at least two practice statements.
- Physical is mandatory, so it is pre-selected and explained, rather than rejected at submission.
More steps than one long form. Each step asks for one decision, so the whole takes less effort, and nothing has to be redone.
Solution
Phase 1
The school side: build, evidence, submit.
A wellbeing coordinator opens the Wellbeing Mark like any other visit in the Compliance System. From there the product walks them through the framework one decision at a time, and does not let them submit anything ADEK would have to send back.

Start where they already are
Assessments appear as familiar cards, each with its window and deadline.
Coordinators do not learn a new tool. Each quarterly Wellbeing Mark assessment sits on the dashboard they already use, showing how many frameworks are open and when the window closes.
- Due date and status on every card
- One clear action per assessment
- Same shell as every other Compliance visit

One level at a time
Choose a dimension, then its elements. Nothing else competes for attention.
SPIRE's five dimensions are listed with a plain-language description. Selecting one reveals its elements in place, and a running summary counts dimensions, elements and practices as the school goes.
- Mandatory dimension explained, not enforced by an error
- Selection summary always visible
- Save draft and Continue fixed at the bottom

The rules, at the moment of choice
Practice statements appear under each element, ready to select.
When a coordinator picks a practice statement, the framework's requirements come with it. The minimum of two statements per element is checked live, so the form can only move forward in a valid state.
- At least two statements per element
- Add activities directly from the statement
- Invalid states never reach submission

A claim becomes evidence
Each activity records what, how often, for whom, and the proof.
The side sheet keeps the requirements at the top, the sample practices beside them, and the activity form below. Frequency, applicable cycles and evidence files are captured in one pass, with upload progress and a completion state.
- Requirements and limiting factors pinned above the form
- Multiple evidence files per activity
- Save and submit, or save and come back

Submit with confidence
A final review confirms everything required is in place.
Before anything goes to ADEK, the coordinator sees the whole self-evaluation in one read: dimensions, elements, practices and the evidence behind each. A single confirmation replaces the anxiety of wondering what might have been missed.
- Counts for dimensions, elements and practices
- Student and staff frameworks side by side
- Read-only view shared with ADEK after submission
Phase 2
The ADEK side: plan, validate, rate, report.
Once a school submits, the work moves to ADEK. An admin plans the visit, a manager splits the checklist, a lead validator and validators work through pre-visit, on-site and post-visit stages, quality assurance and a manager review the result, and the system produces the report.

Plan the visit
Dates, the wellbeing admin, the lead validator and the validator, in one form.
Planning is a short, ordered form with guidance under every field, so an admin can schedule a school in minutes and hand the visit to the right people.
- Date rules explained inline
- Self-evaluation closure date shown read-only
- Submit and continue straight to assignment

Split the checklist
Elements are assigned to validators, down to a single element.
The manager assigns each element to a lead validator or a validator. From that moment on, each person sees and edits only their elements, which keeps a multi-person visit focused and makes ownership obvious.
- Partial selection within a dimension
- Selected counts per dimension
- Lead can switch to the full checklist

Six stages, one place
Pre-validation, on-site, post-visit, quality assurance, manager review, report.
The validation hub shows where a school is, what is locked, and what can be submitted next. Progress bars per dimension tell the lead validator how much of the checklist is done before they open a single stage.
- Explicit state and next action per stage
- Self-evaluation locked once review starts
- Request changes at QA and manager level

Judge each statement
Achieved, not achieved or other, with a mandatory comment.
In pre-validation, validators work statement by statement. Status and comment sit side by side, and every statement links back to the school's evidence, so a judgement is never made in isolation.
- Three clear outcomes per statement
- Comment required, so every judgement is explained
- Statements grouped by element and dimension

Evidence, beside the verdict
The school's activity opens in a panel next to the statement.
Reviewers read the school's description, frequency, cycles and evidence file without leaving the form they are filling. It removes the tab-switching that makes long reviews slow and error-prone.
- Side panel keeps context
- Frequency and cycles as scannable tags
- Evidence files one click away

A conversation, on the record
Summaries, recommendations and threaded comments per statement.
When quality assurance or the manager sends work back, their comments land on the exact statement, stamped with name, date and time, newest first. The report is built on a trail anyone can follow.
- Comments anchored to statements, not pages
- Full history, latest on top
- Recommendations per dimension feed the report
Outcomes
Reflection
In a system this structured, the design work is mostly modelling. Once SPIRE was a clean hierarchy with its rules attached, the screens followed; the hard decisions were about where a rule should live and who should be allowed to change what. And because schools are rated on this data, clarity was not a style choice. It was the product.