Catch cross-unit transfers before they slip through
Every night, WebRun opens Care Logistics, checks every completed cross-unit transfer from the day against both units' current census, logs any mismatch to Google Sheets, and flags anything still unresolved to the bed control Teams channel before the next shift begins.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch cross-unit transfer errors before the next shift?
WebRun reconciles every cross-unit transfer from the day in Care Logistics against both units' current census each night, logs any mismatch to Google Sheets, and flags anything still unresolved to the bed control Teams channel before the next shift starts. Discrepancies get caught overnight instead of surfacing as a confusing count days later.
- Census mismatches are caught the same night, not days later
- Bed control starts the next shift with a clean, flagged list instead of a silent error
- Prior mismatches auto resolve in the log once Care Logistics is corrected
Built for bed control coordinators · hospital capacity managers · nursing administration · night shift supervisors
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.carelogistics.comin a real browser with your saved login - no setup, no API keys. -
1
Care Logistics - reconcile the day's cross-unit transfers
carelogistics.com How to Automate Care Logistics
WebRun opens Care Logistics to reconcile the day's cross-unit transfers. - Open the CareEdge transfer log for the day
- List every completed cross-unit transfer with its origin unit, destination unit, and timestamp
- Compare each transfer against both units' current census to confirm it is reflected correctly
- Flag any transfer where the origin or destination census does not match the transfer record
Done when Every cross-unit transfer today is checked against both units' census, with mismatches flagged.
-
2
Google Sheets - log any census mismatch
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log any census mismatch. - Open the Transfer Reconciliation Log
- Append a row for each mismatch with the transfer details and which unit's census disagrees
- Mark a prior night's mismatch resolved once Care Logistics shows it corrected
Done when The log has a row for every mismatch found tonight and a resolved mark for any prior mismatch now corrected.
-
3
Microsoft Teams - flag unresolved discrepancies
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to flag unresolved discrepancies. - Post any unresolved mismatch to the bed control channel before the next shift starts
- Name the origin unit, destination unit, and the discrepancy
- Skip the post entirely on nights with zero mismatches
Done when Bed control has every unresolved mismatch flagged before the next shift begins.
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
Does this reconciliation involve contacting any unit outside the hospital?
No. Everything stays internal between Care Logistics, your own Google Sheet, and the bed control Teams channel. No outside party is contacted.
What counts as a mismatch?
Any completed cross-unit transfer where the origin or destination unit's current census in Care Logistics does not match what the transfer record shows, checked fresh every night.
What happens to a mismatch found last night if it gets corrected today?
The next night's check reads the current Care Logistics census, marks that row resolved in the log, and it is no longer flagged in Teams.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.