Proposal P6 · Daily Exception Briefing. Left: the briefing exactly as it arrives in Teams or email before the day starts. Right: the same findings with the drill-down a supervisor would use. Everything is read from states eHub already records — the AI changes nothing, ever.
Microsoft Teams · WMS Supervisors channel
✦
eHub Exception BriefingToday 07:00

Good morning — 3 items need attention, 1 is all clear.

12 orders due to ship today are still unallocated — last night's allocation for wave WAV/2609/000218 failed at 02:14. Suggested: re-run allocation for that wave first; all 12 are recoverable before cut-off.
3 orders are short on stock that exists but sits invisible to allocation — lot records missing expiry data. Suggested: correct the lot records; the stock is on hand.
2 overnight jobs neither completed nor reported failure — the work was silently dropped. Suggested: resubmit and confirm this morning.
Allocation queue is running normally this morning — no action needed.
Read-only briefing · generated 06:58 from overnight system states · illustrative only, not real data
✓ Read-only — the AI cannot modify inventory, orders or any record Arrives in Teams or email — no new tools to learn

This morning's findings — click to drill down

supervisor view
Ship today 12 orders unallocated — wave WAV/2609/000218 failed at 02:14 Cause and effect joined: this job failed at 2am; these orders ship today. ▼
Order NoCustomer RefShip DateLinesStatusAge
SO/2608/018231MG-770122026-09-016Unallocated4h 46m
SO/2608/018236MG-770192026-09-012Unallocated4h 46m
SO/2608/018240MG-770202026-09-0111Unallocated4h 46m
… 9 more orders on the same wave
Why the AI flagged it: the wave's allocation job recorded a failure state at 02:14 that appears on no screen — these orders would normally be found when the packing queue runs dry, hours from now. All 12 recorded ship dates are today.
Stock 3 orders short — stock on hand but invisible to allocation Lot records missing expiry data · the error P3 Inbound Capture prevents at source. ▼
Order NoSKUShort QtyOn-hand (blocked)Blocking issue
SO/2608/018219VITC-1000-B1224360Lot 240718B — expiry blank
SO/2608/018227PARA-500-B2412144Lot 240802A — expiry blank
SO/2608/018233VITC-1000-B1236360Lot 240718B — expiry blank
Why the AI flagged it: allocation skips lots with missing expiry on expiry-controlled products. The stock physically exists — correcting two lot records releases all three orders. No screen joins “short order” to “fixable lot record” today.
Overnight 2 overnight jobs silently dropped — neither completed nor failed No completion state, no error state — found today only by their consequences. ▼
JobSubmittedLast stateExpected byDownstream effect
Wave allocation — WAV/2609/00022101:40Processing (stale 5h)02:1018 orders not yet released
Billing sync — batch 2608-3103:05Queued (never started)03:30Invoices delayed, no operational risk today
Why the AI flagged it: both jobs hold a state that should be transient, aged far past the measured normal. “Still processing after 5 hours” appears nowhere — the queue screens only show work that finished or failed loudly.
All clear Allocation queue running normally Volume and pace within the measured baseline for a Monday morning. ▼
Also checked and clear: no waves stuck mid-allocation · no allocations built and discarded overnight · overnight receiving jobs all completed. Saying “no action needed” out loud is part of the briefing's job — silence should mean nothing was checked, not nothing was found.

How it works — every morning, before the day starts

read-only
Step 1Scan

Reads the states the systems recorded overnight. Changes nothing.

Step 2Detect

Two exception recipes, thresholds set from measured behaviour.

Step 3Prioritise

Orders shipping today come first.

Step 4 · Human decidesBrief

Plain language in Teams/email. Supervisors decide and act.

POC slice: exactly these two exception types — orders at risk and overnight work that failed or silently stalled. Put-away delays, receipt ageing and inventory mismatches are sequenced for later, by earned priority.

Prepared by Anchor Sprint Sdn Bhd · Proposal P6 · Draft v0.4 Interactive prototype · illustrative data only · not connected to any system