Flag chronically underused OR blocks early
Every Monday, WebRun opens LeanTaaS iQueue, pulls the trailing four weeks of utilization for every block, flags any block that has stayed below your target utilization for two or more weeks running, logs each one to a Google Sheets tracker with its streak length, and posts the OR director a short list of blocks that need attention.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch chronically underused OR blocks before they become a bigger problem?
Every Monday, WebRun pulls the trailing four weeks of block utilization from LeanTaaS iQueue and flags any block that has run below target for two or more consecutive weeks. It logs the streak to a Google Sheets tracker and posts the OR director a short, ranked list in Slack, so chronically underused blocks surface early.
- Chronically underused blocks surface after two weeks, not two quarters
- The OR director opens Monday to a ranked list instead of pulling a report
- Single bad weeks are filtered out automatically so alerts stay meaningful
Built for OR directors · block time committees · perioperative services leadership · surgical services administrators
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.leantaas.comin a real browser with your saved login - no setup, no API keys. -
1
LeanTaaS iQueue - pull trailing four week utilization by block
WebRun opens LeanTaaS iQueue to pull trailing four week utilization by block. - Open LeanTaaS iQueue and go to the Block Utilization dashboard
- Pull each block's utilization for the trailing four weeks, by surgeon, service line, and room
- Identify blocks below your target utilization for two or more consecutive weeks
- Note the current streak length and the average utilization over the period
Done when Every block below target for two or more consecutive weeks is identified with its streak length.
-
2
Google Sheets - log the underused streak for each block
WebRun opens Google Sheets to log the underused streak for each block. - Open the block utilization tracker
- Add or update a row for each flagged block with this week's utilization and running streak
- Sort the tracker so the longest-running underused blocks sit at the top
Done when The tracker reflects every flagged block's current streak, sorted longest first.
-
3
Slack - alert the OR director to blocks needing attention
WebRun opens Slack to alert the OR director to blocks needing attention. - Post the week's flagged list to the OR leadership channel
- Lead with the blocks on the longest underused streaks
- Include a link to the full Google Sheets tracker
Done when The OR director has this week's underused block list in Slack with the full tracker linked.
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 one bad week trigger a flag?
No. A block only appears once it has run below your target utilization for two or more consecutive weeks, so a single slow week from a canceled case or a holiday doesn't trigger a false alarm.
Can I change the utilization target or the streak length?
Yes. Both the target percentage and how many consecutive weeks count as a streak are set when you configure the workflow, so it matches your facility's own policy.
Does it release or reassign the block itself?
No. It only flags the block and logs the streak. Any release, reassignment, or conversation with the block owner is still a decision your OR leadership makes.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.