The Seventh Appointment
The morning roster, external signals and staffing records do not share one clean decision clock. Reconstruct what dispatch could know before authorizing scarce interventions.
- ROLE
- Dispatch Control Analyst
- TIMEBOX
- 75–105 minutes
- COMPLEXITY
- Intermediate / 3 of 5
- ROTATION
- Brief 9 of 16
The decision has already reached your desk.
The 07:30 dispatch packet lists the remaining BR0020 appointments and a controller-approved bulletin defines the morning action capacity. The packet is already being used to prepare customer contacts and emergency reroutes.
Business, warehouse and observation clocks do not align cleanly across the roster and external feeds. Traffic freshness varies by service area, provider revisions coexist, and workforce records contain final shift outcomes that were not approved for morning decisioning.
Dispatch needs an auditable action slate now. You must determine which records and signals belonged in the 07:30 packet, preserve any exceptions and keep every recommendation inside the published capacities.
Authorize the morning review, proactive-contact and emergency-reroute slate—or recall the packet—using only evidence that was supportable at 07:30.
Use only facts knowable by 20 Mar 2025 at 07:30 ET. The bulletin is the approved capacity authority: no more than four dispatcher reviews, three proactive contacts and two emergency reroutes. Do not use employee-level final shift outcomes.
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 appointment presented as remaining at the morning decision point.
CAUTION / Presented membership must still be reconciled against business and warehouse clocks.
GRAIN / One controller-approved morning capacity bulletin.
CAUTION / This is the authorized aggregate capacity source; it does not approve employee-level absence or final shift status for decisioning.
GRAIN / One privacy-minimized appointment-to-service-area record.
CAUTION / Use the effective operational geography without attempting to recover addresses or coordinates.
GRAIN / One scheduled employee shift.
CAUTION / Final shift_status is an eventual outcome and is not approved as a 07:30 employee-level feature.
GRAIN / One selected weather station mapped to the operating region.
CAUTION / Several stations can describe a region; station evidence is not appointment-level exposure.
GRAIN / One weather-station hour available to the assignment.
CAUTION / Observed, estimated and suspect quality states coexist and must remain visible.
ANALYSIS CUTOFF / 20 Mar 2025 / 07:30 ET
Questions to pressure-test—not steps to copy.
These prompts define the analytical territory without prescribing an order, technique or conclusion.
- 01
Which roster records existed in both business time and warehouse time at 07:30?
- 02
How fresh and comparable are weather and traffic observations across the service areas?
- 03
Which apparently useful workforce fields are eventual outcomes rather than approved morning evidence?
- 04
What action slate remains defensible after the evidence and all three capacity constraints are reconciled?
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.
- 01As-of packet audit
Classify roster and supporting fields as eligible, future-dated, stale, revised, quality-limited or prohibited at 07:30.
- 02Corrected dispatch view
Produce the supportable morning slate with evidence freshness and material limitations by appointment or service area.
- 03Capacity-checked action ledger
Name every review, contact, reroute and hold while proving that the published action limits are respected.
- 04Dispatch incident note
Deliver the operational decision and the minimum data-contract change required before the next morning packet.
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
A current-looking packet can contain future and revised facts. The work is to reconstruct the actual decision surface, not to use every field that later became available.
Defensible approaches
- Compare booked, created and warehouse-available clocks with the decision timestamp and retain excluded records as visible exceptions.
- Profile weather quality and traffic freshness by area, then distinguish recorded context from unsupported appointment-level inference.
- Use the controller bulletin for aggregate capacity and issue a conservative, explicitly capacity-checked action slate.
Common traps
- Trusting roster membership because the table is named current_appointment_roster.
- Using eventual worked or cancelled shift status to reconstruct morning availability.
- Treating the highest traffic revision as necessarily knowable at 07:30 or applying every action capacity independently to the same records.
Reviewer questions
- Can every acted-upon appointment be shown to exist at 07:30?
- Which recommendation changes if a stale or revision-ambiguous external signal is withheld?
- Did the final slate remain inside every authorized capacity without using employee-level outcomes?
CHALLENGE A COLLEAGUE
Pass the Brief
The link shares this spoiler-free briefing. It never includes your work, identity, or browser progress.SUGGESTED NOTEThe morning packet looked current until its clocks were reconciled. I audited the live decision surface in The Seventh Appointment from The Analyst.
