For trip leaders
Run the trip, not the clipboard.
Flock is small enough to explain to a substitute in ninety seconds. This is the playbook — what to do before the buses load, what to watch on the ground, and how to close out a trip so the next leader inherits a clean log.
— THE WEEK BEFORE —
Build the trip and the roster
Everything starts with the roster. Get it in once and it carries the medical context, contacts, and codes you will lean on all day.
- Create the trip. Set the start and end dates. Location sharing only turns on inside this window — never before, never after.
- Import the list. Paste from a spreadsheet, upload a CSV, or pull from PowerSchool. Names, grade, allergies, medications, and emergency contacts come in together.
- Check the medical column. Confirm allergies, plans of care, and over-the-counter consent with your nurse. This is what surfaces during an SOS — it has to be right.
- Assign groups and staff. Put students into groups and assign a leader or chaperone to each. Chaperones see critical alerts; nurses and leaders see full medical records.
— THE NIGHT BEFORE —
Print codes and brief the team
- Print join cards. Cards print four-up, one code per student, and expire when the trip ends. Hand them out at homeroom — no shared logins, no 6am PIN resets.
- Walk the team through SOS. Show every chaperone the one-tap SOS and where the live map lives. Ninety seconds is enough.
- Set up chat channels. Create a staff-only channel and a trip-wide channel so the day's coordination stays out of a parent group text.
— THE MORNING OF —
Load the buses with a headcount that holds
- Check in as they board. Members tap to check in. You see exactly who is on which bus, and missing students surface before the driver turns the key.
- Confirm the manifest. Each group leader confirms their group. The dashboard shows the gaps, not just the totals.
— ON THE GROUND —
Watch the map, work the alerts
Once the trip is live, your job is to read the map at a glance: who is reporting, who has gone quiet, and where any SOS is open.
- Read the pins. Profile-photo pins show each student. A quiet pin means a device has stopped reporting — check in before it becomes a problem.
- Work an SOS together. When a student opens SOS, location, the nearest leader, medical context, and contacts surface in one pane. The leader on the ground and you work the same case until it closes.
- Keep coordination in chat. Headcounts, detours, lunch moves — post them in the trip channel so everything is logged for the report.
— HEADING HOME —
Close the trip cleanly
- Final check-in by group. Confirm everyone is back on the bus. The final manifest is recorded automatically.
- Save trip notes. Add anything the next leader should know. SOS cases and chat are already logged.
- Let codes retire. Codes expire with the trip and location sharing stops. There is nothing to tear down.
Want to see the whole arc on one page first? Read a day on a trip, or reach us through the contact page for an onboarding session.