Practical answers for Australian and New Zealand schools reviewing LeaveLens, including how it works during lessons, what data is captured, where data is hosted, how privacy is handled, what reporting is available and how setup, integrations, demos and trials work.
Looking for something specific? Use the sections below, or contact us here for a walkthrough, trial activation or school-specific discussion.
LeaveLens is a school-focused student movement tracking platform. It helps staff record when students leave class and when they return, then turns those movements into useful visibility around time out of class, lost learning time, repeated patterns and duty-of-care awareness.
Most schools already have student movement during lessons, but the information is often spread across paper books, informal notes, hallway passes, memory or disconnected spreadsheets. LeaveLens gives schools a consistent way to see who is out, how long they have been away and where repeated movement patterns may need follow-up.
LeaveLens can act as a digital alternative to hall pass processes, but it is designed to go further than simply issuing a pass. The main value is the data produced from the exit and return workflow: lost learning time, repeated exits, student patterns, class pressure points, subject trends and leadership reporting.
LeaveLens is designed for schools that want better visibility over students leaving lessons. It supports classroom teachers, heads of department, year level teams, wellbeing teams, student services, administration, support staff and school leadership.
No. LeaveLens does not replace roll marking or whole-day attendance systems. It complements those systems by focusing on temporary out-of-class movement during scheduled lessons. Attendance systems usually answer whether a student attended school or class. LeaveLens helps answer how often a student left during class and how much learning time was affected.
LeaveLens can support everyday lesson-time movement such as toilet breaks, drink breaks, visits to student services, wellbeing support, IT desk visits, administration, support staff follow-up and other short movements during class. The system focuses on time, frequency and patterns rather than turning every movement into a behavioural judgement.
The core workflow is designed to be fast: find the student, record the exit, then capture the return. Staff can search for a student or work from their current class list, helping the process fit into real classroom conditions without lengthy forms.
Yes. Schools can request a demonstration, use the demo environment and discuss a school trial. The demo is intended to give staff and leaders a practical understanding of how the logging workflow, live view and analytics operate before a broader rollout.
A teacher can locate the student through search or the current class view and record the exit. When the student returns, the return is captured so the time away from class can be calculated. The intent is to make the process quick enough to use while teaching.
The return time is recorded against the original exit. LeaveLens then calculates the duration of the movement so the school can see the lost learning time associated with that record.
Yes. Where appropriate, staff can adjust a return time so the record reflects what happened accurately. This is useful when a student returns while the teacher is managing the class and updates the record shortly afterwards.
LeaveLens is designed to help staff see students who are currently out. Depending on school configuration and workflow, schools can use live views, end-of-lesson awareness and reporting to identify records that need attention. If a student has not been returned, the record should be reviewed so the school has accurate information.
LeaveLens is intentionally privacy-conscious. The focus is on when students leave, when they return, how long they were away and whether patterns are emerging. Schools do not need every toilet visit, drink break or support visit to become a stored sensitive reason.
Categorising every exit can turn ordinary student needs into sensitive records and can shift the discussion towards consequences rather than support. LeaveLens keeps the emphasis on learning time, movement patterns and duty-of-care visibility, while still allowing schools to have informed conversations when repeated patterns appear.
Yes. LeaveLens can support live visibility for authorised staff, including leadership, student services, support teams or roaming staff using mobile-scaled web access. This helps schools know who is currently out of class and how long they have been away.
Yes. Toilet break tracking is a common use case, but LeaveLens is broader than that. It supports student movement tracking across many school contexts, including student services, support visits, IT desk visits, administration and repeated out-of-class movement during lessons.
LeaveLens reporting can help schools review lost learning time, frequency of exits, current and historical movement patterns, student trends, class trends, subject trends, faculty-level patterns, year level patterns, day and period heatmaps and repeated movement concerns.
Lost learning time is the time a student spends away from their scheduled lesson. LeaveLens calculates this from the exit and return times so schools can see the cumulative impact across students, classes, subjects, faculties, year levels and date ranges.
Yes. LeaveLens helps schools identify repeated exits, prolonged absences and patterns across time. This can support earlier conversations with students, parents, carers, wellbeing teams or leadership before the pattern becomes more difficult to address.
LeaveLens can help schools review student movement overlap and peer crossover patterns by comparing exit and return windows. This supports schools that are trying to understand whether repeated movement is individual, social or linked to particular times, classes or locations.
Yes. LeaveLens can support reporting by class, subject, faculty, year level, teacher context and date range, depending on the school’s timetable and data configuration. This helps leaders distinguish between individual student patterns and broader timetable or classroom pressure points.
Yes. LeaveLens is useful because it gives staff a calm, evidence-informed view of time away from class and repeated patterns. It can support conversations with students, parents and carers without relying on anecdotal memory or informal notes.
Yes. LeaveLens includes live visibility so authorised staff can see students currently recorded as out of class. This supports day-to-day duty of care and helps staff follow up when a student has been away longer than expected.
Yes. Reporting can be viewed across selected date ranges, such as a day, week, fortnight, term or other period, depending on the report and the school’s data set.
Yes. LeaveLens is designed around a privacy-conscious movement record. It focuses on time, frequency, duration and repeated patterns rather than requiring staff to store private reasons for each exit.
LeaveLens uses the information required to support the school workflow, such as student identity, class membership, timetable context, staff context and the exit and return records created during use. The specific dataset depends on the school’s integration or import process.
The standard LeaveLens workflow is not built around storing sensitive reasons for leaving. The system is designed to help schools monitor time away from learning and duty-of-care visibility without requiring staff to record private explanations for every movement.
LeaveLens supports role-based access so users only see the areas appropriate to their role. For example, classroom teachers, coordinators, heads of department, administrators and leadership users can have different levels of access depending on the school’s configuration.
LeaveLens can support teacher-focused views such as current class and my students workflows, while authorised leadership and support users can have broader visibility where the school requires it.
LeaveLens has been assessed through the Safer Technologies 4 Schools program. This helps schools and education bodies review privacy, security and procurement considerations as part of their own approval process.
LeaveLens is hosted through Microsoft Azure. Schools can discuss hosting, data handling, access and implementation requirements during onboarding or procurement review.
No. LeaveLens is not designed to turn toilet breaks, drink breaks or support visits into automatic consequences. It is designed to show time away from class, repeated patterns and duty-of-care concerns so schools can respond proportionately and supportively.
Yes. LeaveLens is suitable for both Australian and New Zealand schools that want a clearer way to record student movement during lessons, understand time away from class and review repeated patterns. The core workflow is not tied to a single state or jurisdiction: it is based on timetable data, classes, students, staff and exit-and-return records.
LeaveLens application data is stored in Australia. This is important for schools that need to consider regional hosting, privacy review, procurement expectations and school-system approval processes before adopting a cloud platform.
Yes. LeaveLens is designed around school timetable structures, class periods, student enrolments, staff roles and lesson-time movement. The same core workflow can support Australian and New Zealand schools because the platform focuses on who left, when they left, when they returned and how much learning time was affected.
No. Australian hosting is a strong starting point for regional review, but each school, education department, independent school system or governing body may still need to complete its own privacy, security, procurement and data-governance assessment. LeaveLens can support those discussions with relevant information about hosting, privacy-conscious design and product workflow.
LeaveLens uses school timetable and enrolment information so exit records can be linked to the correct class, period, day, teacher and student. This can be configured through supported integrations or data uploads depending on the school’s systems.
LeaveLens supports direct timetable integration workflows for Timetabling Solutions and Edval. These integrations help align classes, periods, days and reporting structures with the school timetable.
Yes. Wonde can help LeaveLens connect with supported school management systems for student, class and staff data workflows, depending on the school’s Wonde connection, permissions and source system configuration.
Where supported and enabled through Wonde, schools may be able to connect data from systems such as Compass, SEQTA, Sentral, TASS, Synergetic, Veracross, Daymap, SchoolPro and other Wonde-supported platforms. Availability depends on the school’s system, Wonde permissions and configuration.
Yes. LeaveLens can support structured data uploads where an automated integration is not available. This allows a school to provide timetable, student, enrolment and related data in an agreed format.
That depends on the school’s timetable changes, enrolment changes and integration method. Automated integrations can reduce manual work, while file-based uploads may be updated on a schedule that suits the school’s operational needs.
LeaveLens can support student photos where a school chooses to provide them and where the school has appropriate permissions and internal processes. Photos can make classroom logging faster, but they are not the central purpose of the platform.
LeaveLens relies on accurate source data. When the school’s timetable, enrolment or staff data changes, the LeaveLens data should be updated through the chosen integration or import workflow so reporting remains accurate.
LeaveLens supports access through the web platform, a mobile-scaled web interface and desktop app workflows. This helps schools use LeaveLens in classrooms, staffrooms, leadership offices and mobile supervision contexts.
Yes. LeaveLens supports a Windows desktop app workflow for schools that want quick desktop access for lesson-time logging.
Yes. LeaveLens supports a macOS desktop app workflow for Mac users who want a dedicated LeaveLens experience.
Yes. LeaveLens includes a mobile-scaled web interface designed for phone and tablet workflows. This is useful for staff who move around the school or need live visibility away from a desktop computer.
LeaveLens is designed for modern HTML5 browsers, including Chrome, Edge, Safari, Firefox and other current browsers used by schools.
Yes. The mobile-scaled web interface can support leadership, support teams and staff who need quick access to current movement information while moving around the school.
Setup time depends on the school’s data source, integration method, timetable complexity and approval process. A demo or trial can usually be used to understand the workflow before a full school rollout.
A school generally needs to confirm its timetable source, student and staff data workflow, user access requirements, privacy and approval requirements, and any reporting priorities. LeaveLens can then be configured around those operational needs.
LeaveLens is designed to be simple for classroom staff, but short onboarding is recommended so staff understand when to use it, how to return students, what live views show and how the school intends to use the data.
Yes. Schools can start with a small group, faculty, year level, leadership team or pilot cohort before moving to wider implementation. A staged rollout can help schools refine expectations and staff workflow.
Support can include onboarding guidance, configuration assistance, data import or integration support, troubleshooting and help with interpreting reports. Schools can also request walkthroughs or school-specific advice.
LeaveLens includes configurable settings such as school-specific thresholds, timezone, role access and integration or data workflows. Some requirements may be handled through configuration, while more specialised requests can be discussed separately.
Schools can use the enquiry page to request a walkthrough, trial activation or school-specific discussion. The demo registration page can also help prospective users see the product workflow before a broader conversation.
LeaveLens is generally offered as a school software service. Pricing can depend on the school context, rollout scope, support requirements and licensing arrangement. Schools should enquire for current pricing and trial options.
Yes. The demo environment is available so prospective schools and visitors can explore the workflow without using live school data.
Yes. Schools can discuss trial options, including how long the trial should run, what data should be included and what success measures the school wants to review before deciding.
Schools should consider their current student movement process, privacy expectations, staff workflow, data source, integration options, leadership reporting needs and how the school wants to use repeated movement patterns to support students.
Useful stakeholders often include school leadership, timetable or data staff, wellbeing and student services teams, heads of department, teachers, IT support and privacy or procurement contacts where required.