Define the baseline first
Agree on what counts as a supply-related delay, cancellation and coordination task. Record the source of each observation and use a comparable baseline period so a pilot does not mix unrelated disruptions with supply-readiness issues.
Track time and outcomes separately
Capture delayed or cancelled cases, delay duration and staff coordination time as separate measures. Record how a shortage was resolved and whether the relevant supply was confirmed available.
A resolved shortage does not, by itself, prove that a cancellation was avoided. Describe the evidence and uncertainty rather than attributing every improvement to the software.
Use an OR-minute estimate carefully
The ClinChek calculator combines editable assumptions to estimate avoided disruption, recovered OR time, coordination hours and gross OR-time value. Use a locally justified OR-minute cost where available.
Modeled OR-time value is not guaranteed cash savings, revenue or contribution margin. Capacity may not be reusable, costs may be fixed, and implementation costs must be considered separately. Do not add overlapping time measures together as if they were independent savings.
Report an honest pilot summary
Document the scope, observation period, baseline, data sources, assumptions and limitations. Compare observed results with the baseline and identify other changes that could explain the difference.
No verified ClinChek customer pilot results are presented here. These resources describe a measurement approach, not a customer case study or a promised outcome.