DOCK-TO-STOCK EVIDENCE REGISTER AND DEFINITION CENSUS Publisher: Cincinnati Dock Door Repair Research Verification date and dataset version: 2026-09-12 Canonical reference: https://cincinnatidockdoorrepair.com/research/dock-to-stock-time/ WHAT THIS IS A selected, source-annotated document register and original coding framework. It is not a warehouse survey, a national average, an industry prevalence study, a source of private receipt records, or a new measurement of provider performance. FILES - dock-to-stock-benchmark-ledger.csv/.json: 24 evidence records; 23 contain numerical time statements, including the historical APQC performer spread. The remaining record describes the 2026 WERC release without an hour value. Nine records are direct benchmark or producer/sponsor-summary records. Downstream attributed restatements are classified separately. The 2025 Yale white paper and infographic are grouped as one annual record. - dock-to-stock-definition-census.csv/.json: 20 selected definition passages. Endpoint coding: Yes 8; Implied 5; No 7. Explicit waiting: 2. Formula present: 8. Coding locators and notes are included. These are classifications of selected passages, not claims about every statement in an entire article or website. - dock-to-stock-receipt-log-template.csv: blank 13-field template; no observations. - dock-to-stock-receipt-log-data-dictionary.csv: one explanation per template field. - dock-to-stock-receipt-log-legend-and-example.csv: separate explanatory legend and fictional illustration; do not ingest this file as operational data. - dock-to-stock-worked-example.csv: one fictional receipt corresponding to the page's 08:00, 09:00, 11:00 and 13:00 timeline. Not a measured warehouse receipt. - dock-to-stock-ohio-cincinnati-context.csv/.json: seven context records grouped into the page's five geographic rows. Ohio employment is May 2022; Cincinnati metro employment/wages are May 2025; CVG's stated ranking is 2023. These are not dock-to-stock timing measurements and cannot be combined into a time trend. - dock-to-stock-system-and-regulatory-semantics.csv/.json: four official-source documentation/regulatory notes. Oracle's report excludes specified shipments, not just selected LPNs within an unchanged shipment denominator. - dock-to-stock-sources.csv/.json: source identifiers, descriptions, URLs and verification dates. Source IDs retain the draft's identifiers; gaps denote unused or superseded references, not missing files. - reproduce_dock_to_stock.py: standard-library Python script for record counts, CSV/JSON parity, cutoff arithmetic and example receipt calculations. PROVENANCE AND DATA FIELDS The value_as_published field concisely paraphrases the source while preserving its stated figures and qualifiers; it is not always a verbatim quotation. Numeric low/high fields must be read with numeric_relation and value_as_published. A median, a strict cutoff, a performer spread and a best-case statement are not commensurate bounds on one common distribution. Empty numerical fields are unknown/not applicable, not zero. Business days are not converted to hours. Multiple source URLs in one CSV cell are separated by ' ; '. Dates retain the source's precision: report year, document version, known publication date, or undated. verified_on is a reading date, not an observation vintage. VERIFICATION MARKS Star: the statement was checked against the issuer or original publisher. For an advisory/vendor statement, this verifies attribution, not its truth as a measured industry benchmark or any provider's compliance with a service window. Filled circle: the named summary/reproduction was inspected, but its underlying full benchmark report was not. No underlying survey raw data is included. DEFINITION CODING Use the selected dedicated definition and directly attached scope list named in selected_passage_locator. Yes: an inventory-system record, system availability, or recorded completion event is explicit. Implied: stock is available/pickable without an explicit computer event. No: a physical endpoint only in that passage. Read coding_note for later wording that differs within the same article. Waiting is Yes only when inclusion in the measured interval is explicit; an elapsed timestamp alone does not count. Formula presence is separate and covers an arithmetic expression anywhere on the inspected page. It is not a correctness score. APQC's 'average' and Oracle's 'daily average' descriptions are not counted as explicit arithmetic formulas. Oracle's example chart expresses time in minutes. REPRODUCTION From this directory, run: python reproduce_dock_to_stock.py This verifies CSV/JSON parity, all published classification counts, the 75% change in the numerical WERC cutoff, and the fictional 3.0/5.0-hour example. The code also checks missing completions, flow-through exclusions, invalid event order, duplicate IDs, later posting, earlier availability and UTC-offset arithmetic. It does not fetch current sources or reproduce the producers' underlying surveys. For a real, separately selected arrival cohort: python reproduce_dock_to_stock.py --receipts my_log.csv --cutoff 2026-10-01T00:00:00-04:00 --output results.json Use complete ISO 8601 timestamps with UTC offsets. The stored dock_to_stock_hours input is not trusted; durations are recomputed. The cutoff is required with a custom log. Report missing completion counts and inspect whether they represent unfinished work or missing records; the script cannot infer that distinction. Exception-flagged counts overlap other categories and are not additive. The default receipt is fictional and must never be represented as measured data. NAMED ENDPOINTS Recorded-and-put-away: max(physical putaway complete, receipt posted) minus dock arrival. Available-stock: max(those two events, explicit available status) minus dock arrival. Completion must cover all eligible quantity for that receipt. Partial receipts and different observation grains require separately named rules. These are this reference's proposed operational definitions, not an endorsement or mandated reporting form from APQC, WERC, Oracle, Microsoft or OSHA. RIGHTS AND SCOPE Original compilation/coding: Cincinnati Dock Door Repair Research. Underlying benchmarks, documentation, wording and reports remain attributed to their sources. This file does not grant rights to reproduce third-party underlying datasets or reports. No full third-party reports, private operational data or automatic attribution/backlink payloads are included.