The Kit Before the Call
Field Operations wants standard pre-call parts kits. Turn historical parts usage into a bounded pilot without confusing recorded use, availability, geography or causal impact.
- ROLE
- Service Parts Analyst
- TIMEBOX
- 90–120 minutes
- COMPLEXITY
- Advanced / 4 of 5
- ROTATION
- Brief 16 of 16
The decision has already reached your desk.
Field Operations believes a small standard parts kit prepared before selected calls could reduce avoidable return visits. The enablement team wants a six-week pilot recommendation by the morning planning review.
Part lines, work-order histories and visits have different grains and clocks. Parts are usually recorded around or after service, final repair outcomes are later facts, and the service-area reference maps areas to default branches without locating each service site to one unique area.
You must identify a compact, testable kit policy from historical usage while making clear what the estate can establish about coverage, cost and geography—and what requires a prospective pilot.
Approve, modify or withhold a six-week pre-call parts-kitting pilot and define the eligible work, kit contents, operating scope and evaluation plan.
Aggregate part use before joining status histories. Design on service history through 30 Sep 2025 and evaluate on Oct–Dec 2025 without using final outcomes as predictors. Do not claim current inventory availability, infer an exact service area from default branch alone or present historical association as causal pilot impact.
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 service work order.
CAUTION / Current status, completion, first-time-fix and final resolution are later outcomes relative to a pre-call kit decision.
GRAIN / One work-order status event.
CAUTION / The one-to-many history must be reduced before it is joined to work orders, visits or part lines.
GRAIN / One physical service visit.
CAUTION / Arrival, departure and visit outcome are realized after the kit decision and cannot be selection features.
GRAIN / One product quantity recorded against a work order and visit.
CAUTION / recorded_at is not necessarily pick, load or use time; several part lines belong to one job.
ANALYSIS CUTOFF / 19 Jan 2026 / 08:30 ET; design on 2024–2025 service history
Questions to pressure-test—not steps to copy.
These prompts define the analytical territory without prescribing an order, technique or conclusion.
- 01
What should one historical kit-opportunity row represent, and where can the source joins multiply part demand?
- 02
Which pre-call attributes may define an eligible kit without using eventual repair or visit outcomes?
- 03
How much held-out job and unit coverage can a compact kit achieve, and at what historical carrying-cost proxy?
- 04
Which proposed geographic scopes are supported by the available bridge and which require new operational data?
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.
- 01Grain-safe service-parts fact
Aggregate historical part quantity and cost by work order and product before attaching eligible pre-call context.
- 02Candidate kit matrix
Recommend compact kit contents for declared service segments with historical job, unit and cost coverage.
- 03Held-out policy evaluation
Evaluate the rule on Oct–Dec 2025 and show coverage, unused-kit burden and instability across material slices.
- 04Pilot operating plan
Define scope, exclusions, logistics assumptions, success measures and the evidence needed for a causal rollout decision.
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
Historical part use can support a candidate kit policy, but it cannot prove stock availability or the causal effect of pre-positioning. The professional handoff preserves that boundary.
Defensible approaches
- Reduce part lines to work-order/product facts and status histories to only the milestones needed before any multi-table join.
- Define candidate kits from a time-bounded design period using only pre-call service and appointment attributes, then evaluate unchanged rules on a later holdout.
- Report job coverage, quantity coverage, historical cost and unused-kit burden while treating branch-level geography as coarser than service-area assignment.
Common traps
- Joining raw part and status rows and ranking products from multiplied quantities.
- Using first-time-fix, visit outcome or final resolution to decide which future jobs receive a kit.
- Equating recorded part use with inventory availability or mapping a branch appointment to every service area that names that default branch.
Reviewer questions
- Could the policy be executed using only information available before the appointment?
- Does held-out coverage survive a reasonable change in kit size or service mix?
- Does the pilot distinguish descriptive historical fit from the causal effect it is designed to learn?
CHALLENGE A COLLEAGUE
Pass the Brief
The link shares this spoiler-free briefing. It never includes your work, identity, or browser progress.SUGGESTED NOTEA useful parts kit is a bounded operating policy, not a list of historically popular SKUs. I designed The Kit Before the Call from The Analyst.
