Net of every shift a conductor has ever submitted — same gap formula as Shift Reports/CSV export, using ticket-verified revenue where tickets exist and falling back to the conductor's own self-report only when no tickets can be matched — not scoped to the date range above, so a shortfall from months ago never quietly drops out of view. Any single shift with an implausibly large gap is excluded from the net and listed separately below it for manual review, instead of silently distorting the total.

Fare or luggage recorded under the $1 USD / R20 ZAR floor — enforced app-side and by a database constraint, so any row here predates that fix or bypassed it directly.

For the selected date range — a day this low is worth a look, not necessarily a problem.

Tickets exist but no shift report was ever submitted, 24+ hours later.

Unregistered devices, or one device used by more than one conductor.

Tickets issued before 05:00 or after 22:00 Zimbabwe time, for the selected date range.

Ordinary conductor/manager access can't UPDATE or DELETE these tables — every row below is a privileged write (admin tooling, migrations, corrections), for the selected date range. Review anything you don't recognise.

A ticket number was assigned on a device but never reached the database.

Lock-task exits, owner-PIN dialog attempts, and boot events, for the selected date range above.

Counts across all the signals above, per conductor, for the selected date range.

Separate from the manager login PIN — this one gates the offline shift-handover approval step on a conductor's phone, so it has to stay downloadable to their device. It still uses the legacy security password as its own extra confirmation step, independent of your IT sign-in above — this is a deliberate second gate on a sensitive write action, not an oversight.