All templates

Automated iQueue Block Request Decision Drafts

Twice a day, WebRun opens LeanTaaS iQueue, reviews any new or pending block time requests against your facility's allocation criteria, drafts a recommended approve or deny decision with reasoning for each, logs every request to a Google Sheets decision log, and emails the OR director a draft memo in Outlook to review and finalize.

Runs on WebRun · Strict Lockdown policy
Twice a day, at 8:00 AM and 1:00 PM WebRunorchestrates each step
1 LeanTaaS iQueue pull pending block requests
2 Google Sheets log each request with a draft recommendation
3 Outlook draft the decision memo for the OR director
4 Slack alert the director that decisions are ready to review
In short

How can an OR committee speed up decisions on pending block time requests?

WebRun reviews pending block requests in LeanTaaS iQueue against your allocation criteria, drafts a recommended approve or deny decision with reasoning for each, and logs every request to a Google Sheets decision log. It emails the OR director a draft memo in Outlook to finalize, twice a day, so requests move faster without WebRun ever deciding anything on its own.

  • Pending block requests get a reasoned draft decision the same day they arrive
  • The director reviews a ready memo instead of re-reading every request from scratch
  • Every request and its outcome stays logged for the next committee meeting

Built for OR directors · block time committees · perioperative services administrators · surgical scheduling coordinators

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.leantaas.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    LeanTaaS iQueue - pull pending block requests
    leantaas.com
    WebRun in LeanTaaS iQueue: pull pending block requests
    WebRun opens LeanTaaS iQueue to pull pending block requests.
    • Open LeanTaaS iQueue and go to the Block Requests queue
    • Pull every new or still pending request with the requesting surgeon, service line, dates, and hours
    • Check each request's requested dates against current open time and utilization history
    • Note whether the request fits your facility's allocation criteria, such as prior utilization or waitlist standing

    Done when Every pending block request is pulled with the data needed to weigh it.

  3. 2
    Google Sheets - log each request with a draft recommendation
    google.com
    WebRun in Google Sheets: log each request with a draft recommendation
    WebRun opens Google Sheets to log each request with a draft recommendation.
    • Open the block request decision log
    • Add a row for each request with a draft recommendation of approve, deny, or needs discussion, and the reasoning
    • Carry forward any request still awaiting a director decision from the prior run

    Done when Every pending request has a logged draft recommendation and reasoning.

  4. 3
    Outlook - draft the decision memo for the OR director
    microsoft.com
    WebRun in Outlook: draft the decision memo for the OR director
    WebRun opens Outlook to draft the decision memo for the OR director.
    • Draft a short memo to the OR director summarizing each pending request and its recommendation
    • Leave the memo as a draft for the director to edit or finalize
    • Never submit or communicate a final decision on WebRun's own authority

    Done when A draft decision memo is waiting for the OR director covering every pending request.

  5. 4
    Slack - alert the director that decisions are ready to review
    slack.com
    WebRun in Slack: alert the director that decisions are ready to review
    WebRun opens Slack to alert the director that decisions are ready to review.
    • Post a short note to the OR leadership channel that new decision drafts are ready
    • List how many requests are waiting and the oldest request's age

    Done when The OR director knows decision drafts are ready to review in Outlook.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.leantaas.com
ScheduleRuns automatically on this cadence
Twice a day, at 8:00 AM and 1:00 PM
DeliveryHow each run's result reaches you
Decision drafts · Slack
OutputWhat each run produces - A decision log of pending block requests with a draft recommendation and reasoning for each, plus a draft memo in Outlook for the OR director.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Can WebRun approve or deny a block request on its own?

No. It only drafts a recommendation with reasoning and logs it for review. The OR director makes and finalizes every approval or denial, and nothing changes in iQueue until a person acts on it.

What criteria does it use to recommend a decision?

It weighs the requesting surgeon's or service's utilization history, waitlist standing, and whether the requested dates overlap open or released time in iQueue, the same factors most block committees already use.

What happens to requests the director hasn't decided on yet?

They carry forward to the next run and stay listed as pending, so nothing falls off the log until the director actually approves or denies it.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.