If a driving school staff member loses a phone, run two jobs at the same time: contain access from the missing device and move today’s work to a verified person or replacement device. Do not cancel lessons automatically, share another employee’s password, or assume that changing one password has secured every app.
The phone, the mobile service, and each signed-in account are separate layers. Locking the phone protects the device. Suspending the SIM protects the phone number. Revoking a software session protects the school account. Removing a notification device stops future alerts. A complete response checks all four.
Use this 15-minute lost-phone response
| When | Account and device work | Keep the school day moving |
|---|---|---|
| First 15 minutes | Verify the report through a known contact method. Record whose phone is missing, when it was last seen, and which school apps were open. Lock the phone. Revoke active sessions and the lost device’s notification registration where each service supports it. | Identify the staff member’s next lesson, unread student conversations, keys or vehicle, and any office tasks due today. Give each item a temporary owner. |
| Within the hour | Review the login identifier, password, recovery methods, connected accounts, and phone number. Suspend the SIM with the carrier if the number may be misused. Replace access only after verifying the staff member. | Give the staff member least-privilege access on an approved spare or replacement device. Keep the same staff record and existing appointments. Confirm who will contact students. |
| Before closing | Review sign-in and account-change records that are available. Remove temporary access, check for unfamiliar recovery details, and document what was revoked or could not be verified. | Return messages and tasks to their normal owners. Confirm tomorrow’s schedule and write one short incident note for the manager. |
The identity check at the start matters. A caller who says, “I lost my phone; send a code to this new number,” may not be the employee. Use a contact route or manager-held detail that was already on file. Do not treat possession of a new phone number as proof of identity.
Locking the phone is necessary, but it is not the whole response
Apple says Lost Mode locks an iPhone or iPad with its passcode, and its guidance also tells owners to contact the carrier and review account security. Google says Android’s Find Hub can mark a device as lost or erase it, subject to the device being configured and reachable. Follow the owner’s platform instructions: Apple’s lost iPhone or iPad steps or Google’s lost Android steps.
Those controls protect the handset. They do not prove that every website session, calendar connection, messaging account, or browser on that device has been revoked. For each business system, look for a device list, active sessions, connected apps, notification registrations, and recovery settings. If a control is unavailable, record that gap and contact the provider rather than marking the job complete.
NIST’s digital identity guidance treats loss or theft as a reason an authenticator may need to be invalidated. It also warns against credential sharing. That supports a simple rule for a driving school: recover or replace the employee’s own access; never solve the incident by lending the manager’s login. See NIST SP 800-63B.
Check these four layers separately
- Device: Can the owner or school lock, locate, or erase it? If it is a personal phone, use the staff member’s Apple or Google controls; do not promise the school can remotely wipe a personal device.
- Mobile number: Is the SIM still active? If the number receives login or recovery codes, ask the carrier about suspending or replacing it. SIM action does not sign out apps that were already open.
- Account sessions: Which school, email, calendar, payment, and messaging sessions are active? Use an explicit “sign out other sessions” or session-revocation control where available. A password change may not end every existing session, so verify the result.
- Notifications: Can the missing phone still receive previews or push notifications? Remove that device’s notification registration where supported, and review what appears on a locked screen. Turning off push does not revoke an authenticated account session.
This is why a school needs a defined login and recovery policy before a phone disappears. The policy should name who can approve recovery, which identifiers may change, and what evidence staff must provide.
Keep lessons running without creating a second staff identity
A lost phone is an access incident, not a reason to rebuild the instructor. Keep the original staff record, lesson assignments, notes, and audit history. Restore verified access to that record on an approved device, or temporarily hand specific work to another named employee.
| Today’s item | Temporary decision | Do not do this |
|---|---|---|
| Upcoming lessons | Keep the bookings. Give the instructor a printed or approved replacement-device day sheet containing only what is needed. | Delete and recreate appointments merely to change who can see them. |
| Student messages | Assign one office worker to monitor and reply from their own account. | Share the missing employee’s password. |
| Pickup details | Provide only the next necessary pickup information through an approved channel. | Send the day’s entire student list to a personal email or chat. |
| Open tasks | Record a temporary owner and deadline, then return ownership after access is restored. | Rely on a verbal handoff with no record. |
This works best when every employee already has a separate account with a clear role. Our guide to adding a second instructor without losing control of access and handoffs explains why shared credentials become a bigger problem as a school grows.
A worked example
This is an invented example, not a report of a real incident.
At 7:20 a.m., instructor Maya tells the office from her partner’s phone that her own phone is missing. Her first lesson starts at 9:00. The office calls Maya back using the emergency contact method already recorded, notes the last confirmed use, and has her place the handset in Lost Mode. The manager revokes the school sessions and notification device that the software actually exposes, then records one connected service whose session status cannot be verified.
The office does not create “Maya 2.” It keeps her lessons on the existing record, assigns one administrator to watch student messages, and gives Maya temporary least-privilege access on a spare school device after verifying her identity. The administrator confirms the first pickup and checks the next two lessons. At closing, the manager reviews account changes, removes the temporary device, and documents the unresolved service for follow-up.
What to verify in RouteOS
RouteOS sells software for driving schools, so this is a commercial disclosure. The current RouteOS mobile app page says staff can view schedules, lesson details, and conversations, while available actions depend on account permissions and school settings. Its privacy policy also notes that accounts and sessions use security controls, but that is not evidence that every school has the same lost-device controls enabled.
Ask RouteOS—or any vendor—to demonstrate, in your configuration, how an administrator can view and revoke sessions, remove a notification device, recover the employee’s existing identity, and limit replacement access. Test the procedure with a non-production account. Record which steps require vendor support. A feature shown in code or a sales demo is not complete operational proof until the control works in the account your school uses.
The incident is closed only when both tracks are complete
Do not close the incident just because the phone was locked, and do not declare success just because the instructor reached the first lesson. Close it when the missing device and related access have been contained, today’s work has a verified owner, temporary access has been removed, and any unverifiable session is recorded for follow-up.