MosaicWatch one real school workflow run end to end
A Head of Science resigns. Below, a fictional school — Good Ambassadors Academy — runs the handover as a Mosaic playbook. Click through the three-minute tour to see the whole process, end to end.
| Task | Who | Done | Notes |
|---|---|---|---|
| Exam board logins | Peter?? | ✓ | ask Peter — he left Fri |
| Schemes of work | ??? | on his laptop somewhere | |
| Lab keys + safety | TBC | =VLOOKUP(#REF!) | |
| Coursework moderation | R. Menon | no | which folder?? |
| Budget / open orders | finance? | ||
| Handover meeting | — | ✓ | cancelled twice |
A file nobody owns, four copies, and the one person who knew the answers has left.
A prebuilt workflow: phased tasks, the right people, review gates, and a record — so the work survives the leaving date.
Press Next to step inside — the tour opens full screen.
Two ways to run a handover. One of them survives the person leaving.
Why schools outgrow task tools
Schools already have tasks in email, calendars, Planner, spreadsheets, meetings, inspections, reporting cycles, and informal follow-up lists. The problem is not the absence of task tools — it is that school work is fragmented from the academic calendar, evidence, responsibilities, deadlines, reporting cycles, and programme-specific obligations. Mosaic is school-native: a task is connected to a workflow, a cycle, a person or post, evidence, and a review.
vs Generic task tools
Planner, Trello, Asana
- A card has no idea who reviews it, what evidence it needs, or what a submission looks like.
- Assignment to a department is a label, not four tracked individuals.
- When a person leaves, their board dies with their account.
Mosaic tasks carry owner, assignee, and reviewer roles, typed response fields, and review gates — and work assigned to a post survives the person.
vs Spreadsheets
The handover tracker, v7_FINAL(2).xlsx
- Nobody owns a row; everybody edits the file.
- It is stale the day after the meeting.
- There is no history — only the current lie.
Mosaic keeps live status on a shared Control Centre, and every change lands in an append-only audit trail.
vs Email + meetings
The reply-all thread and the corridor promise
- A request in a thread is not an assignment — it is a hope.
- Knowledge leaves in someone's inbox on their last day.
- "It's handled" has no receipt.
Mosaic turns the process into a playbook: structured capture, visible blockers, and sign-off that leaves a record.
The school is fictional. The product is real.
Prebuilt playbooks, roles and review, structured responses, and a record that outlives the person who left. See how Mosaic could run this at your school.
Next up: the self-evaluation walkthrough — judgements, evidence tasks, and inspection-ready exports.