Skip to content

School workflow notes

Small ideas.
Useful changes to the school day.

Practical notes from the product’s everyday workflows, written to help school teams plan, review and introduce change.

Teaching & learning

A planned chapter is not a completed chapter

The monthly plan tells you what the class intends to cover. Teaching records tell you what happened. Both are useful, but they answer different questions.

Start a monthly review by comparing the planned chapter dates with the lessons recorded as taught. A chapter with one taught lesson may still need further explanation, practice or revision. Avoid treating the presence of a record as proof that the whole chapter is ready for an exam.

Keep the teacher’s judgement in the process. Use the records to suggest candidates, then confirm the chapter scope and learning objectives before assessment. When the class needs more time, adjust the next month’s plan rather than hide the difference.

Use the monthly planning checklist

Assessment

Automate the draft, keep the review

Preparing several tests for a month can save repeated setup. The useful result is a set of drafts with clear scope and visible gaps.

A unit test, a mid-term assessment and a competitive practice paper serve different purposes. Review each proposal’s subject mix, chapter coverage, questions, scoring and duration rather than accept one setting for every exam.

Question availability is part of readiness. If approved matching questions are missing, change the scope or prepare and review suitable questions. Creating a draft should make the remaining work visible; releasing it should remain a deliberate school decision.

Explore assessment planning

School operations

Begin a rollout with one complete routine

A long feature tour can leave staff unsure where to start. One complete routine gives people a clearer first experience.

Choose a routine your team repeats often: a teacher finds the class, checks the lesson, records attendance and sets homework. Prepare the roster and permissions needed for that routine, then practise it with a small group.

Collect the questions that appear in real use. Resolve the confusing steps, agree who supports staff, and review the first week before adding more modules. A defined starting point makes progress easier to judge.

Read the setup introduction

A conversation, then a plan

Have a workflow worth discussing?

Share the routine that takes your team the most effort. We can explore what a clearer process would look like.