Cycle —
?— Viewer
Today
Where the cycle stands and the driver links.
Previous cycle · …
Derived from the orders table for the selected cycle.
Zone summary km = engine preview, est.
| Zone | Total | Morning | Evening | BF | First day | km M (est.) | km E (est.) |
|---|
Overnight changes 01:00 re-check vs 14:30 ingest
Loading…
Alerts
Driver links
Zones at a glance delivered · issues · pending
Morning vs evening per zone orders
Overall M/E split this cycle
M/E ratio per zone above 1 = morning-heavy · ideal 1.0–1.5
Breakfast % per zone share of morning orders
≥ 30% high20–30% medium< 20% fine
BF vs non-BF morning orders per zone
Breakfast risk assessment
| Zone | Morning | BF orders | % of morning | Pressure | Risk | Guidance |
|---|
Zones
One screen for all zones. The order shown is the one drivers received (DB seq); recompute is a preview only and never saves.
Morning : evening per zoneratio above 1 = morning-heavy · ideal 1.0–1.5
Map pins numbered by DB seq
Stops synced order · planned time
| # | Time | Customer | District | Plan | Source | Status |
|---|
LIVE DELIVERY TRACKING
Auto-refreshes every 60s
Notes are the driver's issue notes. Click a photo to see the order's full event history.
No deliveries logged yetDrivers will appear here as they submit.
| Pickup | Delivered | Zone | Customer | Source | Status | Notes | Photo |
|---|
Times shown in Riyadh time. The Pending view lists district, planned time, call and WhatsApp links.
History
Any past cycle, shown the way Live shows today.
Cycle
Zone
Shift
Source
Status
Loading…
Deliveries
| # | Zone | Planned | Pickup | Delivered | vs plan | In car | Customer | District | Source | Status | Photo |
|---|
Route map and zones
■ Kitchen (Dharat Laban)● delivered, zone colour● issue
Definitions
PickupTime the driver tapped "picked up from kitchen", one tap per shift.
DeliveredTime the driver marked the order delivered with a photo.
In carPickup → delivered, for that order.
vs planDelivered time minus the planned time from the route. Green ≤ 5 min late, amber ≤ 15, red over 15.
IssuesNobody home, access problem, wrong address, refused, not in kitchen.
Wrong pickupPickup outside 4:30–6:00 AM (morning) or 3:00–5:00 PM (evening).
Late startPickup → first delivery more than 60 min.
Wrong delivery timeOrder delivered morning before 6 AM or after 1 PM · evening before 5 PM or after 10 PM.
Map■ kitchen · ● delivered, zone colour · red ● issue. Line joins pins in real delivery order (straight, not road). Tap a zone card to show only its route.
StopsDeliveries within 50 m or less than 2 min apart count as one stop.
Performance
Driver shifts and days. Pick Day for one day; This month or All time turns every block into an average.
Period
Day
Zone
Shift
Days
Error details
Finish time
Orders per working hour
Shifts
| Date | Zone | Shift | Pickup | First delivery | Gap | Last delivery | Working hours | Orders | Stops | Orders / hour | Est. KM | Flags |
|---|
Borders and definitions
Wrong pickupPickup tap outside 4:30–6:00 AM (morning) or outside 3:00–5:00 PM (evening).
Late startPickup → first delivery more than 60 min.
Wrong delivery timeAn order delivered too early or too late: morning before 6:00 AM or after 1:00 PM · evening before 5:00 PM or after 10:00 PM. Counted per order.
Working hours (per day)Morning first → last delivery, plus evening first → last delivery. Example: 2h 30m + 3h 30m = 6h.
Orders / hourOrders delivered that day ÷ working hours that day. Example: 60 orders ÷ 6h = 10.
StopsDeliveries within 50 m of each other, or less than 2 min apart, count as one stop.
30 orders · 4 in one building + 2 in another → 26 stops
Est. KMKitchen → each customer pin in delivered order, straight line × 1.3 for roads.
Saturday ruleSaturday cycles are small, so they are left out of every average by default ("Without Saturday"). "Saturday only" shows them on their own. Orders always counts every day. Friday has no deliveries.
Scope lineUnder each block: the day, or "avg · N days excl. Saturday" for a bigger period. Flag blocks show "of N shifts / orders".
Per driver-dayWorking hours, Orders / hour and Est. KM are counted per driver per day, then averaged.
Late tapOrder marked delivered after the shift's day ended (e.g. evening order tapped next morning). Counted as delivered and as wrong time, but not in working hours.
FinishLast delivery of the shift. Pickup → first: pickup to first delivery.
ChartsDashed line = period average. Red dotted line = wrong-delivery border (1 PM / 10 PM). Day timeline: grey = pickup → first (red over 60 min), colour = first → last delivery.
Bigger periodsThis month / All time show averages in every block except Orders and the three flag blocks, which are totals.
Admin
Every change here goes through the ingest function, is checked against your role, and is logged in the ingest log below.
Ingest log v3_ingest_runs · last 60
| Started (Riyadh) | Type | Cycle | Rows | Added | Changed | Removed | Status | Duration |
|---|
Data actions current cycle
Removed orders dropped from a later sheet after a driver had started them
—
Re-run routing full engine for one zone and slot
Delete a cycle by date only · you type the date to confirm · no "all dates" button
Roles Admin: everything · Ops: upload, reorder, edit, restore, re-route · Viewer: read only
Jahez dispatch log v3_jahez_dispatch · last 50
| Time (Riyadh) | Order no. | Status | Result | Dispatch | Error | By |
|---|
Zone drivers v3_zone_drivers · sent to Jahez with PICKED / DISPATCHED
| Zone | Driver name | Phone | Last updated |
|---|
Phone: Saudi mobile, 9 digits (5XXXXXXXX). No driver for a zone → its Jahez pickups fail with "no driver for zone N".
Jahez sync v3_jahez_outbox · automatic status updates
Mode
| Time (Riyadh) | Order no. | Zone | Status | State | Error |
|---|
Last 50 rows · click a row for the exact body. Shadow = built and logged, nothing sent.