What our work placement system actually does in week one of term

Most software is sold on what its homepage looks like. School operations work tells you a different story. The real test of any system is what it does in the messy middle of an actual term.

Here is what our workplacements system did at one school during week one of Term 2 last year.

On the Monday morning, the placements coordinator opened her laptop and could see, on a single screen, that 84 students still needed placements for the May block. 27 host businesses had been confirmed. 12 had replied with conditional yeses. Six had not responded to the initial contact email she had sent in early March. The system had already drafted reminder emails to those six and was waiting for her approval before sending. She approved them.

The previous year, the same week meant a spreadsheet, the printed list of host businesses she keeps in a manila folder, and roughly four hours of cross-checking. This year, those four hours went to other things.

The Tuesday afternoon brought the first awkward case. A student had been placed at a site that had pulled out due to staffing. The system flagged it overnight, suggested three alternative hosts within the same industry and within an acceptable travel distance, and surfaced the student's previous responses about what kinds of work they were interested in. The coordinator reached the student in second period, sorted the alternative placement before lunch, and went back to her actual job.

Wednesday, the printed paperwork. Every host needs the standard set of documents: the school's induction information, insurance, the student's emergency contacts, the parental consent. In the old workflow this was a small printing project that took most of an afternoon. The system now generates the pack on demand, populated with the right details for each placement, and sends a digital copy to the host. The coordinator prints two physical packs a year now, mostly for sites that prefer paper.

By Thursday, the work had narrowed to actual relationship management. Phone calls to the harder-to-reach hosts. A coffee with one industry contact who had three new sites she wanted to offer. A short meeting with the assistant principal about which Year 11 students were not yet engaged with the program. None of these are tasks software can do. All of them are tasks the coordinator could only do because the rest of the system had cleared the way for her.

The point of operational software in a school isn't to replace the coordinator. It is to give her back the parts of her week that didn't need to be hers in the first place.