Student Activity Locator VIC: Your Excursion Guide

A familiar pattern plays out in schools every term. A teacher has venue confirmations in one inbox, transport details in another, student lists in a spreadsheet, risk paperwork in a shared drive, and parent updates still waiting to go out. Then someone asks whether the Student Activity Locator has been lodged, and the room goes quiet for a second.

That moment is why the Student Activity Locator matters. It isn't just another form to complete. For schools in Victoria, it sits at the centre of excursion visibility, emergency response readiness, and auditable compliance. Used well, it supports a clean, reliable operational picture before students leave the gate. Used poorly, it becomes a late-stage scramble that exposes gaps in supervision, records, and student support planning.

Table of Contents

• What Is the SAL and Why Is It Mandatory
• Why schools should treat it as a safety control
• Who must use it and who can access it
• Accessing and Navigating the Student Activity Locator
• First login and basic orientation
• What to look for on the dashboard
• Submitting Your Excursion Notification Step-by-Step
• School and timing details
• Location and route information
• Student and staffing data
• What a reliable verification pass actually looks like
• Integrating SAL into Your Broader Excursion Workflow
• Where SAL fits and where it doesn't
• The medical and dietary gap schools must manage
• What actually works in practice
• Record-Keeping Compliance and Post-Excursion Tasks
• Keep the audit trail clean
• Handling last-minute changes properly
• FAQ and Troubleshooting Common SAL Issues
• What happens if the 5 business day deadline is missed
• How should a multi-day camp with several locations be entered
• What if the student list changes after submission
• Who should be contacted for SAL support or questions

What Is the SAL and Why Is It Mandatory

The Student Activity Locator, often searched as Student Activity Locator Vic, is the Department of Education's notification system for approved school excursions and camps in Victoria. It exists so the department holds accurate movement and supervision details before travel occurs, not after a problem has already developed.

For Victorian government schools, this isn't optional. All Victorian government schools are mandated to use the Department of Education's Student Activity Locator to notify the department of any approved school excursion or camp, and the official guidance describes it as an operational “flight plan” that helps emergency services maintain accurate location data for student groups at all times, including during transit, under the Victorian Student Activity Locator guidance.

Why schools should treat it as a safety control

A lot of excursion paperwork feels administrative until something changes on the day. A bus runs late. A venue shifts the entry point. A student doesn't attend. A supervising adult is replaced at short notice. When those changes happen, schools need a dependable source of truth about who is travelling, where they're meant to be, and who is responsible.

That's the practical value of SAL. It anchors core excursion details in one official record. It also aligns closely with a school's duty of care obligations during excursions, because duty of care isn't just about supervision on the bus or at the venue. It includes planning, documentation, communication, and accountability before departure.

Practical rule: If a detail would matter during an emergency call, it belongs in the excursion workflow early, not in someone's notebook on the morning of departure.

Who must use it and who can access it

The mandatory requirement applies specifically to government schools. Non-government schools can also access the system to register camps and excursions, but the policy requirement sits with the government sector.

That distinction matters because many staff assume SAL is merely a universal excursion template for all Victorian schools. It isn't. It is a department-managed notification tool with a defined compliance role.

Schools that treat SAL as a final admin step usually create more work for themselves. Schools that treat it as the official record for movement and supervision planning tend to run cleaner processes, because the right questions are asked earlier: Who is attending? Which staff are confirmed? Is the route specific enough? Are return timings realistic? Those aren't software questions. They're operational ones.

Accessing and Navigating the Student Activity Locator

The first practical hurdle is simple access. The Student Activity Locator is available through the Salesforce-based portal at the SAL login page, and staff authenticate using an Edumail account under the department's guidance referenced earlier.

A surprising number of delays start here. The staff member coordinating the excursion often has the planning knowledge, but not always the login access or confidence with the portal. The fix is straightforward. Confirm access well before the excursion approval stage, not the day before the submission window closes.

First login and basic orientation

A clean first pass usually follows this sequence:

1. Open the portal early. Don't wait until the excursion pack is “almost done”.
2. Sign in with the relevant Edumail account. Shared access habits create confusion later.
3. Confirm the school profile. Make sure the correct school context is visible before any new record is started.
4. Locate existing notifications. Checking previous entries helps staff understand naming conventions and common fields.
5. Identify where help sits in the interface. That saves time when a coordinator is under pressure.

The portal tends to feel easier once staff stop looking at it as a form and start looking at it as a register. A register has to be accurate, current, and usable by someone other than the original author.

What to look for on the dashboard

Most users only need a few functions regularly, but they need to know where they are:

• New notification area for creating a fresh excursion or camp entry
• Submitted records view for checking what has already been lodged
• Editable drafts or in-progress entries for work that isn't ready to submit
• Support or help options for access or process issues

A good dashboard habit is to check whether the record is still a draft or already submitted before making assumptions about compliance status.

This is also where broader excursion systems can help internally. Many schools keep their planning, consent collection, staffing notes, and travel logistics in separate tools, then use SAL as the formal notification point. A platform focused on excursion management workflows can reduce double handling before details are entered into SAL, but the department record still needs its own verification.

Submitting Your Excursion Notification Step-by-Step

The cleanest SAL submissions are built from finalised operational details, not rough planning notes. The department expects the notification to be lodged at least 5 business days before the excursion, and the required information includes timing, location, student and staff participation lists, and emergency contact points. The same guidance also expects a reliable verification pass before departure so the record is accurate and auditable, as outlined in this Student Activity Locator DET Vic guide.

School and timing details

Start with the basic identifiers. That sounds obvious, but often, avoidable errors commence at this point.

The school entry should reflect the responsible institution, not just the organising faculty or campus shorthand used internally. Timing should be exact enough to be operationally useful. “Morning departure” or “back after school” doesn't help anyone trying to track a group or respond to a delay. Enter the planned start and return windows carefully and check them against transport bookings and the approved itinerary.

A strong timing entry usually does three things well:

• Matches the approved plan. If leadership approved one timetable and SAL shows another, someone has to reconcile that discrepancy.
• Reflects transport reality. Buffer time matters, but vague padding creates confusion.
• Includes the whole activity window. The record should account for the actual period of responsibility, including travel.

Location and route information

This field is more important than many staff realise. Emergency response needs usable location information, not broad destination labels.

A museum name on its own may be enough in one context and nowhere near enough in another. If the group is moving between a venue, a lunch location, and a pickup point, the details need to support operational clarity. Multi-stop days are where sloppy location entries become a problem.

Check this before submitting: If someone unfamiliar with the excursion had to identify the group's intended location and route from the record alone, could they do it confidently?

For camps and complex itineraries, schools should use the most specific information the form allows. Include the main venue accurately, but also make sure the route and movement pattern reflected in the entry align with the actual plan.

Student and staffing data

Coordinators need discipline. The record should reflect the final cleared participants, not a hopeful list created two weeks earlier.

Named staff need to match the adults who will attend. Student participation should line up with cleared permissions and current attendance decisions. This is also where schools often discover that their internal list, consent records, and teacher briefing sheet don't all agree.

A quick pre-submission check helps:

Schools that run a separate internal readiness review before touching SAL usually avoid rework. Some teams use tools such as an excursion readiness checker to confirm documents, approvals, and staffing before the official notification is lodged.

What a reliable verification pass actually looks like

A reliable verification pass isn't a quick skim. It means checking the final record against the approved excursion plan, transport bookings, staff attendance, and the cleared student list.

It also means someone is responsible for the comparison. When “everyone has looked at it,” no one has verified it. One coordinator should complete the entry, and one second person should validate it against the source documents. That small discipline catches most of the errors that create stress later.

Integrating SAL into Your Broader Excursion Workflow

SAL is important, but it doesn't run the excursion by itself. It sits inside a larger workflow that includes approvals, risk planning, parent consent, staffing, transport, venue liaison, and day-of-trip execution. Schools run into trouble when they expect one system to hold every operational detail.

The strongest approach is to position SAL as the formal department notification point, then build the school's internal workflow around it. That keeps the official record clean while still giving staff the detail they need to run a safe excursion.

Where SAL fits and where it doesn't

SAL works well as the place where the school confirms movement, timing, supervision, and contact details in a structured way. It doesn't replace internal approvals. It doesn't write the risk assessment. It doesn't brief staff. It doesn't manage family communications.

A practical school workflow usually looks more like this:

• Planning stage includes destination checks, educational purpose, preliminary staffing, and transport options.
• Preparation stage includes consent collection, final participant review, venue confirmations, and risk documents.
• SAL stage captures the official notification once the operational details are settled.
• Pre-departure stage includes last checks, roll confirmation, medication handling, and staff briefing.
• Day-of-trip stage relies on current lists, active supervision, and clear communication channels.

That order matters. Entering SAL too early often means duplicate work later because names, timings, or venues still change.

The medical and dietary gap schools must manage

One of the biggest practical gaps is student support information. While SAL captures participant counts, it doesn't link to individual medical or dietary databases. This forces trip coordinators to manually cross-reference student support needs, increasing administrative load by an estimated 35%, according to the cited 2025 School Operations Compliance Survey discussed in this procedure review context within the off-site supervision reference.

That gap has real operational consequences. The excursion coordinator may have one list in SAL, another in the school management system, a separate medication note from wellbeing staff, and a dietary update from a family email. None of that is unusual. It is, however, easy to mishandle if there isn't a disciplined process.

Schools shouldn't assume that because an excursion is visible in SAL, all student-specific support information is automatically aligned. It often isn't.

What actually works in practice

The most reliable workaround is a controlled internal cross-check before departure. That means one final participant list, one verified staff list, and one current support summary available to the adults responsible for the group.

Schools usually get better results when they assign ownership clearly:

• Excursion coordinator confirms the final attendance list and SAL accuracy
• Wellbeing or health staff confirm current medical considerations and required documents
• Business or operations staff confirm transport, venue, and timing details
• Lead teacher in charge carries the approved operational pack on the day

Some schools also use dedicated planning tools for school trip workflow management so consent, support notes, schedules, and communications are gathered in one place before SAL is completed. The key point isn't the software. It's the sequence. SAL should receive verified data, not be used as the place where unresolved questions are discovered.

Record-Keeping Compliance and Post-Excursion Tasks

Submitting the SAL entry isn't the end of the compliance job. Schools should retain the submission confirmation, related approvals, participant records, and supporting documents as part of the official excursion file. That record matters later if leadership reviews an incident, a parent raises a concern, or the school needs to demonstrate process compliance.

Keep the audit trail clean

A solid excursion file should include the SAL confirmation alongside the approval paperwork, risk documents, transport details, and final attendance records. The point isn't to archive more paper. The point is to preserve a traceable decision trail.

For many schools, the easiest discipline is simple:

• Save the confirmation promptly in the excursion folder
• Store the final version only so staff aren't relying on outdated drafts
• Keep related records together rather than spread across inboxes and local drives

Teams that already maintain structured legal and compliance documentation for school activities usually find SAL record-keeping much easier because the filing logic is already there.

Handling last-minute changes properly

Real excursions change. A student gets sick that morning. A teacher is replaced. A venue alters the arrival point. When that happens, staff should update the relevant records so the official picture remains accurate as close to departure as possible.

The practical standard is this: if the change affects who is attending, who is supervising, where the group is going, or how the day will run, it should trigger a record review. Schools shouldn't rely on verbal updates alone. If the written record stays wrong, the audit trail stays wrong too.

FAQ and Troubleshooting Common SAL Issues

What happens if the 5 business day deadline is missed

Treat it as a compliance issue, not a minor admin delay. The excursion coordinator should escalate internally straight away to the approver or school leadership responsible for excursions. The school then needs to decide whether the activity can still proceed under its internal governance and department requirements, or whether it must be amended or postponed.

How should a multi-day camp with several locations be entered

Use the most operationally useful location detail available in the record and make sure it reflects the actual movement pattern of the group. For camps, that means the main accommodation or camp site should be accurate, and the listed activity locations and route details should align with the approved itinerary held by the school.

What if the student list changes after submission

Review the record against the final cleared participants before departure. If a student withdraws or a new approval changes the attending group, the school should update its documentation and ensure the excursion records remain consistent. The key principle is that the named participants and supervising adults should reflect reality on the day.

Who should be contacted for SAL support or questions

For general support regarding the Student Activity Locator, the Department directs users to contact the SAL support email for emergency management queries.

Schools already juggle approvals, consent, transport, staffing, medical notes, and family communication across too many disconnected places. AnySchool brings those moving parts into one operational workflow so staff can manage excursions with clearer records, live visibility, and less manual cross-checking before the SAL submission is finalised.