Who this is for
School leadership, academics teams, and operations staff coordinating a new rollout or a term restart.
- Owners / principals
- Heads of department
- Admin and operations team
- IT/support champion
Fundokor
Fundokor
Menu
Guide
Rollout checklist
A practical checklist to align results, reporting, and finance access before term-end.
6 min read
Before you start
A smooth rollout happens when roles, term structure, and data sources are agreed upfront. Don’t skip alignment.
- Confirm the current term dates and publishing deadline
- List the roles that will post, review, and approve
- Decide the source of truth for students, subjects, and class lists
- Choose which optional modules you want this term (attendance, messaging, analytics)
Week 1: Structure and access
Set up the school structure so daily work matches reality.
- Create or verify class structure and subject mapping
- Confirm teacher-to-class assignments
- Set role permissions (teacher entry, HOD review, admin publishing)
- Confirm finance alignment rules (if applicable) for access gating
Week 2: Posting workflow
Turn term pressure into predictable weekly progress with a clear posting rhythm.
- Define the posting cadence (weekly/bi-weekly)
- Set review rules (what must be checked before it becomes “ready”)
- Agree on escalation: what happens when a class is behind
- Train teachers on the minimum set of actions they must complete
Week 3: Publishing readiness
Make publishing a controlled process, not an end-of-term scramble.
- Confirm what “ready to publish” means for your school
- Run a practice batch publish with a small group
- Prepare parent communication (timelines, expectations, support contact)
- Confirm the final sign-off role and the schedule for approval
Ongoing: Keep it clean
The goal is clarity every week: visibility, accountability, and fewer surprises.
- Do a 10-minute weekly check-in using the School Overview and Results Pipeline
- Resolve blockers early (missing entries, subject mapping issues, role access)
- Keep the term workflow consistent; avoid last-minute rule changes
- Document exceptions (late admissions, subject transfers) so reporting stays accurate
Want help applying this guide to your school’s term workflow?