Automated Breathe HR Absence Pattern Reviews
Every Monday, WebRun opens Breathe HR, reads the sickness absence records from the last few months, looks for people with several short spells rather than one long one, drafts a private Gmail note to each line manager naming only their own team, and posts HR an anonymous Slack summary of how absence is trending overall.
How do I spot repeat short-term sickness absence patterns early?
WebRun reviews sickness absence every Monday. It reads Breathe HR absence records, finds people with several short spells rather than one long one, drafts a private Gmail note to each line manager about their own team, and posts HR an anonymous Slack trend, so support happens early.
- Repeat short absences surface within a week of meeting the trigger
- Managers see only their own team, never the whole company
- HR gets an absence trend without naming a single person
Built for HR managers · line managers · small business owners · people operations
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
breathehr.comin a real browser with your saved login - no setup, no API keys. -
1
Breathe HR - read sickness absence records
WebRun opens Breathe HR to read sickness absence records. - Sign in to Breathe HR and open sickness absence records for the rolling period you review on, commonly the last six months
- Capture each absence with the employee, the start and end dates, the number of days, and the reason recorded
- Apply your trigger rule, for example three or more separate spells in the period, and list who meets it with their line manager
Done when Everyone meeting the absence trigger is listed with their spells and their manager.
-
2
Gmail - draft a private note to the manager
WebRun opens Gmail to draft a private note to the manager. - Draft one email per line manager covering only the people who report to them, with the dates and the number of spells
- Keep the tone supportive and factual and suggest a return to work conversation rather than a conclusion
- Leave every email as a draft. WebRun never sends a message about someone's health record on its own
Done when A private draft is waiting for each manager who has someone meeting the trigger.
-
3
Slack - post the anonymous team trend
WebRun opens Slack to post the anonymous team trend. - Post the HR channel a trend summary: total absence days this period and the change against the previous one
- Break it down by team and by recorded reason, without naming any individual
- State how many manager drafts are waiting in Gmail so HR knows the private side has been prepared
Done when HR has this period's anonymous absence trend and the count of manager drafts.
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
Will it email managers about health records on its own?
No. Every note is left as a Gmail draft for HR to read and send. Absence data is sensitive, so a person always decides what goes out and to whom.
Does anyone get named in the Slack channel?
No. The Slack summary is counts and trends by team and reason only. Individual names appear solely in the private draft to that person's own line manager.
Can I set my own trigger rule?
Yes. Tell WebRun the rule your policy uses, such as three separate spells in six months, and it applies that rule instead of a default.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.