Reconcile scanned specimens against the manifest every run
As runs complete, WebRun opens CXT Software, compares the barcodes scanned on each run against that run's manifest, logs any specimen that was manifested but not scanned or scanned but not manifested to a Google Sheet, and posts a reconciliation summary to Slack for follow-up.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I reconcile scanned specimens against the manifest for each run?
As each run completes, WebRun opens CXT Software and matches the run's scanned barcodes against its manifest. It logs any specimen that was manifested but not scanned, or scanned but not manifested, to a Google Sheet with the run and driver, then posts a reconciliation summary to Slack so your team can chase every discrepancy.
- Every run is reconciled against its manifest automatically
- Missing or extra specimens surface with route and driver
- Recurring gaps by route or driver become visible
Built for medical courier operations · lab logistics quality · specimen transport teams · courier compliance leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.cxtsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
CXT Software - compare scans against the run manifest
cxtsoftware.com How to Automate CXT Software
WebRun compares each run's scans against its manifest in CXT Software. - Open CXT Software and select each recently completed run
- Pull the run manifest and the list of barcodes actually scanned during the run
- Match scans to manifest entries, one specimen at a time
- Flag any manifested specimen with no scan, and any scan not on the manifest
Done when Every completed run has a clear match between its manifest and its scans, with discrepancies flagged.
-
2
Google Sheets - log missing and extra specimens
google.com How to Automate Google Sheets
WebRun logs each run's missing and extra specimens to the reconciliation sheet. - Open the Run Reconciliation sheet
- Append a row per run with the manifested count, scanned count, and any discrepancies
- List each missing or extra specimen ID with its route and driver
- Keep the log so recurring gaps by route or driver become visible
Done when The reconciliation sheet records every run's counts and lists each discrepancy.
-
3
Slack - post the reconciliation summary
slack.com How to Automate Slack
WebRun posts a reconciliation summary for any run with a discrepancy. - Post a reconciliation summary to the operations channel for runs with a discrepancy
- Name the missing or extra specimen IDs, the run, and the driver
- Skip a full post for runs that reconciled cleanly and just note them as clear
Done when Operations sees a Slack summary for every run with a scan-to-manifest discrepancy.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Is the reconciliation summary internal?
Yes. WebRun posts the summary only to your internal operations channel in Slack and logs to your own sheet. It reports specimen IDs and counts for your team and never notifies the patient, clinic, or lab directly.
What does it flag as a discrepancy?
Any specimen that was on the run manifest but never scanned, and any barcode that was scanned but is not on the manifest. Each discrepancy is listed with its run and driver for follow-up.
Does it act on the discrepancies itself?
No. WebRun surfaces the missing and extra specimens for your team to investigate. Resolving a discrepancy, such as locating a specimen or correcting a manifest, stays a human task.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.