The Vendor Who Is Never Late
A supplier scorecard begins from receipts and rewards first arrivals. Rebuild it from obligations before selecting five vendors for remediation.
- ROLE
- Supplier Performance Analyst
- TIMEBOX
- 90–120 minutes
- COMPLEXITY
- Advanced / 4 of 5
- ROTATION
- Brief 13 of 16
The decision has already reached your desk.
The sourcing council will select no more than five vendors for remediation or dual-source review. Its draft scorecard reports timeliness and fill performance from the purchasing estate.
The calculation begins with received lines, measures delivery from the first receipt and treats gross received units as filled. Unreceived obligations, split receipts, rejected units and cancellations can therefore change both the denominator and the vendor ranking.
You must produce a scorecard that represents the purchasing promise and distinguish supplier performance from product, order-size and contract mix.
Select no more than five vendors for remediation or dual-source review and defend the scorecard used to choose them.
Aggregate receipts to purchase-order-line grain. Accepted quantity is received less rejected; cancelled quantity changes the remaining obligation; lines with no receipt must remain visible. Separate vendor performance from observable product and contract mix.
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 purchase-order header.
CAUTION / Vendor and order context live at header grain while quantity and promise live on lines.
GRAIN / One purchase-order line obligation.
CAUTION / Ordered and cancelled quantities must be resolved before measuring fill.
GRAIN / One receipt event for a purchase-order line.
CAUTION / Lines can receive in parts; gross and rejected quantities are not interchangeable with accepted fill.
GRAIN / One effective product-vendor sourcing relationship.
CAUTION / Contract lead time, cost, MOQ and primary status require an effective-date match.
ANALYSIS CUTOFF / 01 Dec 2025 / 06:45 ET; orders placed through 30 Sep 2025
Questions to pressure-test—not steps to copy.
These prompts define the analytical territory without prescribing an order, technique or conclusion.
- 01
What constitutes an on-time, complete and accepted line after split receipts and cancellations?
- 02
Which obligations disappear when the scorecard begins from receipts rather than ordered lines?
- 03
Are vendor differences robust within comparable product categories, order sizes and contract lead times?
- 04
Which vendors have enough evidence to support action rather than a small-sample review?
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.
- 01Receipt-obligation fact
Preserve unreceived, partial, rejected, cancelled and completed line obligations at one-row-per-line grain.
- 02Supplier scorecard
Report coverage, on-time completion, accepted fill, rejection and sample-size measures by vendor.
- 03Mix sensitivity
Test whether the action list survives material product, order-size or contract slices.
- 04Remediation slate
Recommend at most five vendors with an action, evidence boundary and follow-up condition for each.
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
Supplier performance begins with the obligation population. A receipt-first analysis can make unresolved work disappear and reward partial delivery.
Defensible approaches
- Start from eligible line obligations and left join a receipt rollup that derives accepted quantity and obligation-completing timing.
- Show unresolved and partial exposure separately rather than forcing every line into a completed performance rate.
- Compare vendors within product, size and contract slices and keep small-sample uncertainty visible in the action decision.
Common traps
- Inner joining to receipts or using the first receipt as the full-delivery date.
- Treating gross receipts as accepted units or ignoring cancelled obligation.
- Using vendor risk tier as observed performance and ranking small vendors on raw percentages alone.
Reviewer questions
- Can a vendor improve its score merely by leaving obligations unreceived?
- Are partial, rejected and cancelled units treated consistently?
- Would product or contract mix plausibly reverse the five-vendor action slate?
CHALLENGE A COLLEAGUE
Pass the Brief
The link shares this spoiler-free briefing. It never includes your work, identity, or browser progress.SUGGESTED NOTEA supplier looked punctual because unfinished obligations vanished from the scorecard. I rebuilt it in The Vendor Who Is Never Late from The Analyst.
