Scattered spreadsheets to streamlined systems.

Rugby School Group needed a better way to manage one of its most demanding processes: teacher reporting and student reviews. Cycles run multiple times throughout the school year, and often several run at once, each serving a different purpose across the school. Every student has multiple contributors feeding into a single report, from subject teachers to heads of year, and often SEND staff too. Coordinating that many inputs into one coherent document, whilst hitting deadlines, is hard enough for a single process. Managing several concurrent cycles, offline and across spreadsheets, made it harder still.

The school needed a system that could organise multiple reporting cycles independently, each with its own purpose and deadlines, whilst giving every contributor a structured way to add their input. It also needed to connect directly with ISAMS, the system already holding their student data. Parents needed a straightforward way to see their child's reports online, rather than waiting on a process with no visibility.

We worked closely with Rugby School Group to understand their exact processes, structure and reporting requirements before building anything. Off-the-shelf tools weren't going to fit a process this specific, so we designed Chronicle around how the school actually works, not the other way round.

We turned an archaic, scattered process into a streamlined system. Teachers now work through multiple reporting cycles in a structured way, with clear deadlines replacing the cumbersome mix of offline processes and spreadsheets, even when several cycles are running at once.

Parents and students gained visibility they didn't have before, with reports accessible online rather than locked away in an offline process. And with Chronicle now in place at both Rugby School and Bilton Grange, the platform is proving itself across more than one school in the group.