All templates

Automated RLDatix Daily Safety Huddle Brief

Every morning before huddle, WebRun opens RLDatix, pulls yesterday's new incidents, any open high-risk items, and overdue actions, and posts a short, ready-to-read brief to the unit's Slack channel so the team walks into huddle already informed.

Runs on WebRun · Strict Lockdown policy
Every day at 6:45 AM, ahead of the 7:00 AM huddle. WebRunorchestrates each step
1 RLDatix pull yesterday's safety data
2 Slack post the huddle brief
In short

How do I brief my team before the daily safety huddle?

Every morning before huddle, WebRun opens RLDatix, pulls the last 24 hours of incidents plus any open high-risk items and overdue actions, and posts a short brief to each unit's Slack channel. Teams walk into huddle already knowing what happened, what's still open, and what needs attention first, instead of compiling it live.

  • Every unit walks into huddle with the last 24 hours already summarized
  • High-severity items are flagged first, every single morning
  • Huddle prep time drops from a manual RLDatix search to zero

Built for nursing unit managers · patient safety officers · charge nurses · clinical quality teams

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.rldatix.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    RLDatix - pull yesterday's safety data
    rldatix.com
    WebRun in RLDatix: pull yesterday's safety data
    WebRun opens RLDatix to pull yesterday's safety data.
    • Open RLDatix RLD360 and pull incidents logged in the last 24 hours
    • Add any open high-risk items and actions now overdue
    • Group everything by unit

    Done when Yesterday's incidents, open high-risk items, and overdue actions are compiled by unit.

  3. 2
    Slack - post the huddle brief
    slack.com
    WebRun in Slack: post the huddle brief
    WebRun opens Slack to post the huddle brief.
    • Post a short brief to each unit's Slack channel before huddle time
    • Lead with the highest-severity item first
    • Keep it to a few bullet points the team can read in under a minute

    Done when Every unit has its huddle brief in Slack before huddle starts.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.rldatix.com
ScheduleRuns automatically on this cadence
Every day at 6:45 AM, ahead of the 7:00 AM huddle.
DeliveryHow each run's result reaches you
Huddle brief · Slack
OutputWhat each run produces - A short bullet-point brief of new incidents, open high-risk items, and overdue actions by unit.
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

How far back does the brief look?

It pulls the last 24 hours of new incidents plus anything still open from before, so nothing gets lost between huddles.

Can each unit get its own brief?

Yes. It groups everything by unit and posts to that unit's own Slack channel, so teams only see what's relevant to them.

Will it replace the actual huddle conversation?

No. It only prepares the talking points. Your team still runs the huddle and makes the calls; WebRun just saves the time spent compiling the data.

Put this on autopilot.

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