The Expedite Window
A workbook claims several warehouse-product pairs have less than 48 hours of cover. Audit the demand signal and choose the constrained actions worth taking now.
- ROLE
- Inventory Planning Analyst
- TIMEBOX
- 90–120 minutes
- COMPLEXITY
- Intermediate / 3 of 5
- ROTATION
- Brief 5 of 16
The decision has already reached your desk.
A supply workbook flags 30 warehouse-product pairs and reports claimed hours of cover. Planning wants immediate transfers and expedites before the morning freight window closes.
The physical movement ledger contains scanner replays. The daily position history is sampled rather than complete, and the workbook calculates demand only on days with issue events. Those choices can move a pair across the 48-hour threshold.
The source pack also contains approved budget, donor-reserve, transfer-lane and manual-review constraints. You have time to audit the watchlist and produce a small prioritized action portfolio—not build the full 21-day supply model.
Select the watchlist pairs for immediate transfer, expedite, substitution review or hold, subject to the published action constraints.
Use only evidence knowable by 01 Dec 2025 at 06:45 ET. Respect every hard constraint and keep uncertain pairs in manual review rather than forcing an action.
Run the brief as a controlled assignment.
The workbench mounts only the listed source neighborhood and supplies neutral starter worksheets. It does not grade the conclusion or reveal the mechanisms planted in the larger assignment.
- Open the dedicated brief workspace and confirm the brief ID in the queue.
- Establish table grain, cutoff and control totals before joining or modeling.
- Make at least two distinct evidence moves and test a credible rival explanation.
- Leave the requested polished artifact, then export the workspace or portfolio package.
The source files are shared; the draft workspace is not. Changing to another full assignment drops brief mode deliberately.
Real tables. A deliberately bounded neighborhood.
These Parquet files already belong to Meridian’s public 96-table estate. Use the mounted schema.table names in SQL or Python; download links are provided for learners working in a local DuckDB environment.
GRAIN / One selected warehouse-product pair at the decision snapshot.
CAUTION / Workbook cover calculations are claims to audit, not supplied answers.
GRAIN / One approved operational constraint.
CAUTION / Budget, donor reserve, transfer-lane and review limits are hard action constraints.
GRAIN / One controller-approved warehouse-product opening quantity.
CAUTION / Use these balances as the decision-time physical control rather than projecting a later position backward.
GRAIN / One technical inventory movement event.
CAUTION / Scanner replay rows are linked to original events and can double count demand if not reconciled.
GRAIN / One sampled warehouse-product-day position row.
CAUTION / The history is sparse; a missing row is not zero inventory and trailing fields require clock discipline.
GRAIN / One calendar date.
CAUTION / Use the date spine to preserve zero-issue days in demand estimates.
ANALYSIS CUTOFF / 01 Dec 2025 / 06:45 ET
Questions to pressure-test—not steps to copy.
These prompts define the analytical territory without prescribing an order, technique or conclusion.
- 01
How do replay reconciliation and inclusion of zero-issue days change the watchlist’s cover claims?
- 02
Which all-days baseline is supportable for intermittent demand, and how unstable is it across rolling windows?
- 03
Which actions remain feasible after donor reserve, lane, budget and review constraints are applied?
Leave work another analyst can review.
Artifact presence can be recorded; analytical quality remains a human judgment. A complete brief has evidence, reasoning and a decision—not merely executed code.
- 01Demand correction
Build a replay-safe, all-calendar-day demand profile and quantify which workbook cover claims materially change.
- 02Uncertainty view
Compare at least two rolling demand baselines or windows and identify pairs whose action is unstable.
- 03Action portfolio
Deliver a polished, constraint-checked list of actions, holds and manual reviews with a short planner note.
Review the reasoning after a real attempt.
The debrief does not contain an official answer. It identifies defensible analytical moves, common failure modes and questions a reviewer may use to challenge the handoff.
SPOILER-GATED REVIEW / REVEAL AFTER YOUR FIRST HANDOFF
DEBRIEF REVEALED / THIS MAY CHANGE HOW YOU APPROACH THE BRIEF
The threshold is only as credible as the movement reconciliation, time spine and demand definition beneath it. A useful action list must also survive operational constraints.
Defensible approaches
- Remove linked scanner replays under an explicit event rule, isolate issue movements and aggregate to warehouse-product-day.
- Cross the selected pairs with a complete calendar spine so zero-issue days remain in the demand denominator, then compare rolling-window estimates.
- Translate the revised risk view into a constrained action portfolio and preserve unstable or infeasible cases for manual review.
Common traps
- Treating every issue ledger row—including scanner replays—as new demand.
- Averaging only issue days and calling the result mean daily demand.
- Ranking risk without checking donor reserve, lane or budget feasibility.
Reviewer questions
- Can a planner reproduce why each pair moved relative to the workbook claim?
- Which modeling choice—not which decimal place—drives each action?
- Does every recommended action pass the supplied constraints?
CHALLENGE A COLLEAGUE
Pass the Brief
The link shares this spoiler-free briefing. It never includes your work, identity, or browser progress.SUGGESTED NOTEA 48-hour stock warning changed when zero-demand days and scanner replays entered the calculation. I worked The Expedite Window from The Analyst.
