Outcome → Data → Process → Test → Review → Export
Automation Workflows
Automate the routine, keep the judgement. Every output is tested on dummy data and approved by you before it can be downloaded. Nothing here is saved.
Automation litmus test
Three questions before you automate anything.
Run every task through the three questions below. Automate only when all three say yes — and even then, the output stays a draft until you approve it.
Can you state the outcome in one sentence?
YESYou know exactly what good looks like — that sentence becomes Stage 1 of the workflow builder.
NOVague outcomes produce vague automation. Talk it through with a colleague first.
Does it repeat the same steps with the same data, every time?
YESA workflow can follow your process — duty points, mark columns and thresholds all repeat.
NOOne-off tasks and judgement calls belong with a person, not a process.
Can you check the output before it matters?
YESEvery tool here stops at an approval screen — nothing downloads until you say yes.
NONever let an automated output land with staff or students unreviewed.
Three yeses → automate it. Any "no" → keep it human. The output is always a draft until you approve it.
Same process, different jobs
Progress trackers
Attainment and progress summaries with a class dashboard
Timetable reader
Pick a class from a dropdown and see its whole week
Staff duty rota
Fair allocation across duty points and time slots
Question Level Analyser
Matching students to subject groups by ID
Student login cards
Print-ready cards for every student, by year group
All built the same way, by a teacher, without writing code by hand.
Automate the admin, not the thinking
Context & constraints
Duties happen around break time. Each duty point belongs to a time slot — before break or after break — and each staff member marks which slots they are available for. The generator only assigns people to slots they can actually cover, so an unavailable colleague shows up as an uncovered position for you to resolve, not a silent clash.
Set each duty point's slot in the Duty points panel, and each person's availability in the Staff panel. Any change clears the rota and its approval.
Staff
6Duty points
4Number = people needed at that point. Slot = when the duty happens.
Working days
5How allocation works
- Pinned staff always go to their point, if available for its time slot.
- Staff only cover slots they marked themselves available for.
- No one covers two points on the same day.
- Flexible duties go to whoever has fewest so far.
This is a starting draft, not an optimal or guaranteed fair schedule. You make the final staffing decision.
Define the outcome
Start with what success looks like, not with the tool.
1 · Set up questions & class
2 · Enter marks
6 students in class · leave a box blank if a student was absent.
| Student | |||||
|---|---|---|---|---|---|