Protocol status: This page defines a study protocol, not a completed study or performance claim. The unit is one accepted order line with traceable event evidence.
Question and intended use
Measure the elapsed time between an accepted order event and the first visible reservation event in selected systems. Use the result to locate evidence gaps and test a process change, not to decide customer remedies or claim that staffing caused an outcome.
Declare the systems, locations, channels, and review window before inspecting values. Definitions of accepted and reserved must be stable enough that two reviewers can identify the same events.
Population and sampling
Freeze the eligible order-line population and assign study keys. Record exclusions, inaccessible records, duplicates, cancellations, and replaced samples. Do not remove records simply because a reservation event is absent.
Choose a sample that represents relevant channels and integration paths. If the study targets an incident window or one high-volume SKU, state that limitation instead of implying portfolio-wide coverage.
Data and event lineage
Collect source event, event time, source time zone, ingestion time, reservation event, location, retry history, and evidence link. Preserve raw labels before normalization.
Separate event time from observation time. Clock drift, batch ingestion, and platform-specific status definitions can create apparent lag that does not represent the same operational interval.
Analysis and review
Predeclare the primary summary, such as median and tail lag among records with reconstructable lineage. Publish counts for eligible, analyzed, missing, conflicted, and unresolved records beside every rate.
Use two reviewers on a blinded overlap sample. Report initial agreement, disagreement categories, adjudication, and codebook changes. A quality reviewer should be able to reopen evidence without private notes.
Privacy and limits
Replace customer identifiers with study keys, restrict raw evidence, and collect only fields needed for the declared question. Set retention rules before extraction.
This observational protocol can describe timing and evidence completeness. It cannot by itself establish why lag occurred or whether one person, vendor, or system caused the pattern.
Sources and boundaries
These sources provide public context for the protocol. Their inclusion does not mean they endorse this site or that the proposed study has been conducted.