<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/5c710f30d02a47b18c34280b6314c401&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5c710f30d02a47b18c34280b6314c401-982286badc61bbd2.gif</thumbnail_url><duration>276.339</duration><title>Transport Screen, Exceptions, and Risk Compliance</title><description>This Loom explains how to use the transport screen to identify and manage daily exceptions for each bus route and time period. It reviews five exception flags: off stop (scanned outside the geofence), wrong stop (used an approved stop but not the allocated one), not travelled (expected on the manifest but no tap on), casual traveller (booking exists but travel may not match), and not allocated (boarded without a booking). For off stop cases, it advises pressing the action pin to compare green and red scan locations against the blue expected stop, and then using stop guardian to check for patterns across the last 15, 30, or 60 days. It also covers the bus guardian check icons, noting green means the driver completed the check, grey or orange means it was not completed, and red means the check was intentionally skipped with a written reason required.</description></oembed>