Student Activity Locator DET: 2026 Compliance Guide

The trip has been approved. Parents are chasing answers about departure time. Staff are checking medications, buses, venue contacts and attendance lists. Then someone asks the question that usually arrives too late. Has the Student Activity Locator DET entry been done, and does it still match what's happening on the day?

That's where many excursion processes start to wobble. Not because schools don't care, but because the SAL record often sits in a different workflow from approval, risk review, consent collection and day-of operations. When those steps drift apart, compliance risk rises and student visibility drops at the exact moment staff need clean information.

A workable Student Activity Locator DET process connects the department requirement to everyday school operations. It treats SAL as part of a live control system for student movement, supervision and emergency response, not as a form to complete at the end.

Table of Contents

• Understanding DET Compliance and the Student Activity Locator
• Why SAL matters operationally
• DET supervision ratio quick reference
• Building Your Pre-Excursion SAL Workflow
• Start SAL at approval, not at packing time
• A practical pre-excursion sequence
• What usually goes wrong before submission
• Live Day Operations From Departure to Return
• Departure control sets the tone
• During travel and at venue changes
• Return and handover
• Post-Excursion Audits and Record Keeping
• Reconcile the planned record with the real day
• What to retain in the final file
• Best Practices for a Flawless SAL Process
• Build time buffers into the operating model
• Use repeatable templates, but don't trust them blindly
• Treat changes as controlled events
• Your Student Activity Locator Questions Answered
• Can non-government schools use SAL
• What if the trip is cancelled or changed after lodgement
• How detailed should location information be
• Who should own SAL submission inside the school
• What usually causes last-minute SAL problems

Understanding DET Compliance and the Student Activity Locator

Most excursion problems don't begin on the bus. They begin earlier, when the school has approval in one place, parent consents in another, staffing in a spreadsheet, and SAL left as a final admin step. That separation is what makes the process fragile.

In Victoria, the Student Activity Locator (SAL) is mandatory for all Victorian government schools to notify the department of any approved school excursion or camp at least 5 business days beforehand, and guidance states schools must know the exact location of students at all times, including during travel. The same guidance sets baseline supervision expectations of 1:20 for day excursions, 1:10 for overnight base camps, and a minimum of 2 staff on all excursions according to the Victorian excursions policy and planning guidance.

Why SAL matters operationally

Those requirements make one thing clear. SAL isn't just a list of names and a destination. It sits inside the department's emergency-response and accountability framework.

That changes how schools should handle the Student Activity Locator DET process. The useful question isn't “Has someone lodged SAL?” It's “Does the SAL record reflect the approved activity, the actual itinerary, the staffing plan and the actual movement of students?”

Practical rule: If staff wouldn't rely on the record during a transport delay, venue change or welfare issue, the record isn't operationally complete.

A reliable process usually joins four things into one chain:

• Approval status: The excursion is formally approved before SAL entry starts.
• Movement details: Travel legs, venue sequence and timing are clear enough to support location awareness.
• Supervision planning: Staff allocation is built around the excursion type and the student cohort.
• Change control: Any late change is treated as a safety issue first and an admin update second.

Schools that want fewer gaps usually stop treating SAL as a standalone task and start treating it like part of broader school compliance software in Australia. The tool matters less than the discipline behind it. One source of truth beats scattered files every time.

DET supervision ratio quick reference

A quick reference table helps coordinators avoid mixing excursion categories.

The trade-off is straightforward. A lightweight process may feel faster at the planning stage, but it creates uncertainty later. A structured SAL process takes slightly more effort upfront and usually prevents the panicked phone calls, missing details and last-minute corrections that consume far more time.

Building Your Pre-Excursion SAL Workflow

The strongest SAL workflows begin the moment the principal or delegate approves the activity. They don't begin the week of departure. Once approval is in place, the school should open a working excursion file and move every related task through the same operational lane.

In Victoria, schools must use SAL to notify the department of any approved excursion or camp at least 5 business days beforehand so emergency services can have accurate activity data. The Victorian guidance also warns that treating SAL as a late-stage task creates compliance risk if lodgement happens after that threshold, as outlined in the Student Activity Locator guidance for schools.

Start SAL at approval, not at packing time

A common mistake is waiting for every small detail before opening the record. That sounds careful, but in practice it pushes SAL into the danger zone. The safer approach is to create the planning record as soon as the trip is approved, then work through a controlled checklist to complete and verify it.

That checklist should sit alongside consent collection, staffing confirmation and risk review. If each task lives in a different inbox, delays become invisible until the deadline is close.

A practical pre-excursion sequence

This sequence works because it mirrors how schools already make decisions.

1. Confirm the activity is approved SAL belongs after internal approval, not before it. The coordinator should verify the activity scope, dates, purpose, venue and lead staff member at this point.
2. Lock the planning spine Before entering SAL, staff should settle the core information that tends to cause rework later. That includes departure point, destination, transport mode, supervising staff, planned return and the current participant list.
3. Complete risk review and family permissions Risk assessment, consent, medical notes and dietary needs should feed the same excursion file. If a school uses digital permission slip workflows for excursions, the main benefit is traceability. Staff can see which students are cleared, what support they need and whether the operational list matches the approved group.
4. Enter the SAL record early enough to allow checking Early entry gives office staff and coordinators time to spot obvious problems such as the wrong date, an old venue detail or a staffing mismatch.
5. Run a final cross-check before the deadline The record should be checked against the latest staff roster, student list, transport booking and venue confirmation.

The schools that avoid last-minute SAL stress usually don't work faster. They make fewer disconnected decisions.

For off-site activities, the data model needs to be richer than a destination field and a calendar date. The planning record should support timing outside school hours, activity classification and approved-school-activity status. That's the difference between a compliant entry and a useful one.

What usually goes wrong before submission

Pre-excursion failure points are usually predictable:

• Approval drift: The trip is approved in principle, but the final activity scope changes and nobody refreshes the working record.
• Roster mismatch: The staff named for supervision aren't the staff who attend.
• Participant lag: Students are added or withdrawn after family communication closes, but the master list isn't updated everywhere.
• Transport edits: Bus or route changes happen late and stay buried in email.

The answer isn't more paperwork. It's a tighter handoff between the organiser, the approver, the office team and the staff leading the day.

A clean pre-excursion workflow should produce one operational pack containing the final itinerary, supervision structure, student support information, venue contacts, transport detail and the submitted SAL reference. If a school can't produce that quickly, the process is still relying too much on memory.

Live Day Operations From Departure to Return

The departure area tells staff whether the planning process was real or theoretical. If students are arriving and no one can instantly answer who is absent, who is late, which adult owns each group and whether the transport list matches the actual attendees, the weakness isn't on the day. It was built earlier.

Departure control sets the tone

A solid excursion departure follows a simple rhythm. Staff mark attendance against the final cleared list, confirm supervision groups, check medication ownership and verify that the transport manifest reflects who is boarding.

Paper rolls can work for small groups, but they break down when a late student appears, a parent passes on new information at the gate, or a staffing substitution happens ten minutes before departure. Digital tools are more useful here because they tie attendance, supervision groups and parent communication to the same excursion record.

One option schools use is AnySchool, which centralises approvals, logistics, staff group ownership, communications and on-day check-ins inside one excursion workflow. The practical value isn't branding. It's that day-of decisions stay attached to the same record staff used during planning.

During travel and at venue changes

The live-day discipline is simple. Every movement point gets an active check. That means headcounts at departure, arrival, group splits, venue transitions, rest breaks and return boarding.

In practice, the SAL principle of knowing the exact location of students becomes operational rather than theoretical. Staff need enough structure to know not just that the excursion is “at the museum” or “on the way back”, but who is where, with which staff member, and what the next transition point is.

A trip is easiest to control when each transition has one owner. Shared responsibility usually means nobody acts quickly enough.

A workable on-day pattern often looks like this:

• Before movement: Confirm all students are physically present and grouped.
• At each handover point: One staff member calls, one checks, one resolves discrepancies.
• If plans change: Update the school contact point straight away and document the variation for later reconciliation.
• During delay or disruption: Use the excursion communication plan rather than ad hoc messaging.

Schools that haven't built that communication path in advance should tighten it before the next trip. A structured school emergency response plan template helps define who contacts whom, what gets escalated, and how location or welfare updates move back to the school.

Return and handover

The final control point is return, not arrival at the school gate. Staff still need to confirm that all students are handed back through the school's expected process, that any welfare issue is noted, and that the actual finish aligns with what school leaders need to know.

That final handover often gets rushed. It shouldn't. A calm return check closes the loop between live supervision and the record that will later be audited.

Post-Excursion Audits and Record Keeping

The excursion file shouldn't be archived the moment the last student leaves. The school still needs to reconcile what was planned against what happened. That post-trip step protects the school if questions come later and improves the next excursion because the team isn't relying on memory.

A useful post-excursion audit is brief, but specific. It focuses on discrepancies, not on rewriting the whole day.

Reconcile the planned record with the real day

The first task is to compare the approved plan, the SAL record and the actual attendance and movement details from the day. If a student was absent, a return time shifted, transport changed, or a minor issue occurred, staff should note it while details are still fresh.

This doesn't need to become a burdensome narrative. A short reconciliation note is usually enough if it clearly identifies what changed, who was informed and whether any follow-up is required.

A practical review sequence is:

• Attendance reconciliation: Confirm who was approved, who attended and who withdrew or was absent.
• Itinerary check: Record any changes to locations, timing or transport.
• Incident and welfare notes: Attach any staff observations, first aid records or parent communications.
• Staffing review: Confirm whether supervision stayed as planned or shifted during the day.

What to retain in the final file

Schools should retain the documents that show the excursion was properly planned, communicated and supervised. The exact storage method varies, but the file should be easy to retrieve and readable by someone who wasn't on the trip.

That usually includes the approval trail, family permissions, risk material, staff allocation, final participant list, communication log and any post-trip variation notes. If records are scattered across email chains, paper folders and staff devices, the audit trail is weak even if the trip itself was well run.

Records matter most when the people involved are busy, absent or no longer at the school.

The emphasis of centralised record keeping shifts, becoming less about convenience and more about defensibility. A well-structured file helps school leaders answer questions from families, leadership or auditors without reconstructing the excursion from fragments.

For schools tightening this part of their process, clear legal documentation practices for education settings help define what belongs in the file, what should be linked to the original excursion record and how changes should be recorded.

The hidden value of post-excursion review is operational learning. If the same venue creates timing problems, if the same consent question keeps coming back from families, or if the same staffing handoff fails on transport days, the school can fix the process before the next trip instead of repeating it.

Best Practices for a Flawless SAL Process

The schools that handle SAL well don't usually have fewer excursions. They build stronger habits. Those habits reduce omissions, keep the approval chain visible and give staff time to fix problems before departure week.

One practical benchmark from Victorian school policy practice is to prepare SAL earlier than the minimum notice window. One school excursion policy references completing the online notification 3 weeks prior to the excursion date, which shows how some schools build lead time above the department minimum to reduce omissions and rework, as noted on the Victorian schools systems and logins page.

Build time buffers into the operating model

The biggest improvement most schools can make is simple. Set an internal SAL deadline that's earlier than the department threshold.

That buffer gives staff room to deal with ordinary disruption: venue confirmations that arrive late, transport adjustments, staffing substitutions, family follow-up, or risk treatments that need another review. Without that buffer, one delayed input can push the whole process into reactive mode.

A practical model is to anchor internal tasks to the excursion date, not to the compliance deadline. Approval, risk review, family permissions and SAL preparation should move on a school calendar that creates breathing room.

Use repeatable templates, but don't trust them blindly

Templates save time for recurring excursions, sports travel, camps and repeat venues. They reduce typing, preserve known contacts and help schools standardise staff expectations.

But template use creates a different risk. Old information stays hidden in copied records.

The fix is a short verification pass before each submission:

• Venue details: Check current address, access points and contact names.
• Transport assumptions: Confirm actual departure and return arrangements for this trip.
• Staffing and group ownership: Verify the adults named in the record are the adults attending.
• Student-specific needs: Refresh medical, dietary and support information rather than assuming last term's data still applies.

Treat changes as controlled events

Scheduling drift is one of the most common causes of SAL weakness. Approval happens on time, but the risk review slides. The risk review completes, but the student list changes. The SAL entry goes in, then transport or staffing shifts and no one updates the master record.

That's why effective schools treat changes as controlled events. Someone owns the update. Someone confirms whether the change affects the operational plan. Someone checks whether the school office, lead staff and families need the revised information.

A simple communications protocol helps here. Schools that define who escalates changes, who approves updates and who informs families avoid the messy version of excursion management where every adjustment becomes a chain of phone calls and contradictory messages. Clear school communication protocols support that discipline.

The trade-off isn't between speed and compliance. It's between visible work and hidden work. Strong SAL habits make the work visible early, when fixes are cheap and calm.

Your Student Activity Locator Questions Answered

Can non-government schools use SAL

Yes. Victorian guidance states that non-government schools can access SAL to register camps and excursions. That doesn't make their internal process identical to a government school's process, but it does make the platform relevant beyond the public sector.

What if the trip is cancelled or changed after lodgement

The safest approach is to treat any material change as something that must be updated promptly in the school's records and communicated through the school's approved process. A lodged record that no longer matches the actual activity becomes less useful in an emergency and weaker in an audit.

How detailed should location information be

Detailed enough that the school can identify where students are during the full excursion, including travel and transitions. A vague destination name isn't much help if the group is in transit, split across activities, or delayed between stops.

Who should own SAL submission inside the school

One named role should own submission, but that person shouldn't be the only person holding critical information. The most reliable model is shared input with single-point accountability. The organiser, office staff and approver all contribute. One responsible role verifies that the lodged record matches the final approved plan.

What usually causes last-minute SAL problems

Not one big mistake. Usually it's drift between approval, risk review, family permissions, participant changes and transport updates. When those threads sit in separate places, the final record becomes harder to trust.

AnySchool gives schools one place to manage excursion approvals, digital permissions, logistics, communications and day-of tracking so the operational record stays aligned with the trip itself. For schools reviewing their Student Activity Locator DET process, it's one option for reducing paper-based handoffs and keeping a cleaner audit trail through the full excursion lifecycle.