School data connections

Student movement integrations with school timetable data

LeaveLens uses school data to place each movement in the correct student, class, teacher, period and reporting context. Supported workflows include Wonde, Edval, Timetabling Solutions and structured imports.

Wonde

Connect supported school management data through the school’s Wonde permissions and source-system configuration.

Edval

Use timetable data to align teachers, students, classes, periods, days and locations with movement records.

Timetabling Solutions

Support direct timetable workflows and compatible data exchange from Timetabling Solutions environments.

Structured file imports

Schools can use validated timetable, student, class, staff and enrolment files where an automated connection is not used.

Why timetable integration matters

Student movement is only useful when it has the correct context. A record that says a student left at 10:14 am becomes more meaningful when the school can also identify the scheduled class, teacher, subject, period, day, location and student enrolment.

LeaveLens uses timetable and school data to make classroom logging fast and analytics reliable. Teachers can work from current classes, while reports can group movement by the organisational structures already used by the school.

Data commonly required

Core school data

  • Active students and school identifiers.
  • Staff accounts and school staff identifiers.
  • Classes, subjects and year levels.
  • Student-to-class enrolments.
  • Teacher-to-class allocations.

Timetable context

  • Day or timetable-cycle code.
  • Period or lesson identifier.
  • Class start and end times.
  • Teaching location where available.
  • Academic year and active status.

Optional parent names and email addresses are only required where the school chooses to use parent reporting workflows.

Wonde integration

Wonde can help LeaveLens connect with supported school management systems for student, class and staff data workflows. The exact data available depends on:

Where supported and enabled through Wonde, source systems may include platforms such as Compass, SEQTA, Sentral, TASS, Synergetic, Veracross, Daymap, SchoolPro and other Wonde-supported systems. Availability must be confirmed for the individual school.

View the LeaveLens application overview on Wonde.

Edval integration

LeaveLens supports direct timetable integration workflows for Edval. Timetable exchange can help align:

Edval supports timetable data exchange with a broad range of school systems. The implementation path for LeaveLens depends on the school’s Edval environment, available export or service method and local approval requirements.

Read Edval information about timetable integrations.

Timetabling Solutions integration

LeaveLens supports timetable workflows for schools using Timetabling Solutions. Timetabling Solutions provides several data-exchange options, including SIF, LISS and customised export files.

The appropriate method depends on the products and services enabled by the school. LeaveLens can use the resulting timetable and enrolment data to establish classes, staff, students, periods and movement-reporting context.

Review Timetabling Solutions data-exchange information.

Structured import workflow

Where a direct provider connection is not available, schools can supply validated files containing the required data. A typical upload package includes:

FilePurpose
timetable.csvClasses, subjects, days, periods, times, locations and teaching allocations.
students.csvStudent identifiers, names, year levels, status and relevant school grouping information.
studentclass.csvStudent membership of timetable classes.
parents.csv (optional)Parent contact information where the school enables parent reporting.

The school should validate identifiers, active status, timetable cycle and academic year before each import. LeaveLens can support implementation discussions about format and mapping.

Implementation sequence

1. Identify the source

Confirm the school management and timetable systems holding the authoritative data.

2. Approve access

Complete privacy, security, provider and school-system permissions.

3. Validate the first sync

Check students, staff, classes, memberships, days, periods and times.

4. Establish maintenance

Define how timetable changes, new enrolments and staff changes will remain current.

Questions to confirm before rollout
  1. Which system is authoritative for student, staff and timetable data?
  2. Which integration or export method is available to the school?
  3. Who approves data access and provider permissions?
  4. How often does the timetable or enrolment data need to refresh?
  5. How are timetable-cycle changes represented?
  6. Which identifiers remain stable across imports?
  7. Will parent contact data be included?
  8. Who checks sync failures or import validation results?
Related LeaveLens pages
See LeaveLens in your school context

Review the workflow with your timetable structure, school roles, data source and student movement procedures.