Greater Sydney Adventist Schools

Phase 2: Ongoing management and sustainability

1. Focus on Contextual Interpretation: Train staff to look at the context and patterns of alerts (e.g., anime searches vs. actual distress) rather than reacting to every notification as an emergency, which reduces alarm and fatigue.
2. Have 'Champions': Identify early adopters to act as champions who can share success stories and demonstrate the benefits of the tool to their colleagues.
3. Maintain Transparency with Parents: Keep parents informed and provide them with tools (like the community app) to manage digital safety at home, creating a consistent partnership.
4. Safeguard Staff Wellbeing: Acknowledge that staff may find certain student alerts distressing; ensure they are supported and equipped to handle sensitive information without being 'triggered' themselves.

While these strategic principles provided the roadmap for the rollout, the actual success of the implementation depended on the deep, relational work that took place on the ground.

A defining feature of the rollout was the significant time invested in human connection before any technical features were activated. At the pilot school, the ICT Manager conducted five separate meetings directly with teachers rather than limiting discussions to the executive level. This approach prioritised the frontline users who would be most affected by the change.

By taking the time to understand the personal lives and individual contexts of the staff from their family dynamics to their specific classroom challenges, the ICT team transformed personal rapport into a foundational project management pillar. These connections ensured that when the time came for implementation, the staff were not just following a mandate, but were engaging with a team they trusted and respected. This shift from a technical deployment to a relationship-driven integration proved that human-centered management is a hard strategic asset, not merely a soft skill.

This strategy directly supports the overarching theme of prioritising people over technical specs. When staff trust the individuals introducing a new tool, the psychological barriers to adoption are significantly lowered. Conversely, without this human foundation, even the most sophisticated technology is likely to be met with resistance or neglect. Ultimately, the success of the rollout was predicated on the belief that technical systems are only as effective as the human relationships that support them.

Before rolling out to teachers or students, the ICT team did something unusual: they went straight to wellbeing staff. Thirteen counsellors and psychologists, plus a child protection officer covering all of New South Wales, were brought into the conversation before the product went live.

Together, they co-designed the parent communication templates, policy documents, student disclosure process, and the decision trees for when alerts were triggered, leaving wellbeing staff invested in the product's success, not blindsided by it.

Full disclosure to students was a legal obligation, and pushback was expected. Instead: "When I train students in the classroom and set expectations clearly, the behaviour just stops. They know if it's not educational, we'll know and there will be a consequence." One incident happened at 2:11pm; by 2:45pm, the student had been spoken to and sent home. It never happened again in that year group.

The ICT team also targeted the most vocal sceptics on staff rather than avoiding them. "I picked one guy who was quite difficult and had quite a reputation in the school. I trained him early, then asked him to speak for five minutes at a staff meeting about how he was using Classwize." Teachers, it turns out, listen to teachers far more than they listen to IT.

To ensure successful adoption, the speaker offered teachers personalized support options, including one-on-one assistance. The speaker also actively went into classrooms to demonstrate the technology, helping teachers log in and navigate the system.

Once the system was live, it surfaced things the school hadn't known about. Over one seven-day period, students on a single campus attempted to access ChatGPT 46,000 times a number that says less about the platform and more about how much of student life now runs through devices the school hadn't been able to see into before.

Filter alerts also picked up language among students that staff had no visibility into previously, including cases the wellbeing team was then able to step in on. In one instance, staff learned that a student was navigating questions about her gender identity, and were able to connect her with counselling support through the school's existing disclosure process. That's the kind of case the wellbeing partnership was built for: visibility paired with a trained, consent-aware team ready to respond, not surveillance for its own sake.

The school’s rollout model was built on awareness, buy-in, knowledge, ability, and reinforcement. It was a deliberately iterative process defined by constant check-ins and adaptation, including a daily 9:30 am coffee walk between the ICT manager and her systems engineer to candidly discuss what was working and what wasn't.

Underpinning this operational approach was a fundamental question: 'Why are we here, and who are we doing this for?' For Adventist education, the answer is found in the school’s core values nurture for today, learning for tomorrow, and character for eternity. Ultimately, this highlights a broader truth: digital safety tools only succeed when the people using them understand their purpose and feel supported. Technology is the easy part; the real work happens in the relationships.