Resources · Implementation playbooks

Make implementation part of the product

The rollout a school actually follows: a named lead, a roster, one routine, a week, then families.

Before rollout set goals, schools, roles, data and measures.
During rollout onboard users, train and track issues.
After launch review feedback, support needs and evidence.

Prepare people as well as records

A rollout needs more than access to software. Identify the staff who will maintain classes, support colleagues and review use. Check the starting records and choose a first routine that fits the school week. Agree a route for questions before asking everyone to adopt several new workflows at once.

Review the first cycle before expanding

After the first reporting or teaching cycle, discuss what staff completed, where records are missing and what support would help. Use that review to adjust training and responsibilities. Multi-site programmes should also consider local differences and escalation routes. Explore implementation support to scope migration, training and a staged rollout with Kurasa.

The rollout, in the order schools actually use

This is the playbook. There is no separate PDF behind it.

Name a lead. One person at the school owns the first week. They can answer “whose class is this?” without calling Kurasa.
Put the roster in. Classes, learners and staff roles. A class with no teacher, or a learner with no way to reach a parent, is a setup gap, not a failure of the teacher.
Pick one routine. Schemes and lesson plans, the morning register, or formative evidence. Not all three on the first Monday.
Run it for a week. Fix the missing records before you add another workflow. Write down what blocked people: a login, a class list, a phone that does not charge.
Release to families last. Assessments, attendance and reports go home by SMS, in the app, or on the guardian app when the plan includes it. A person releases them. They do not send themselves.

Start with onboarding