The sick days nobody told HR about
A regional mental-health nonprofit in western Massachusetts is hiring someone to run every employee leave of absence. Here is how a leave goes wrong without anyone being careless, what went wrong for others who handed it off, and a build that keeps every decision with HR.
How to use this page
Read the story, then the map. If no one in your business holds the middle square, start there, not with the build. If someone does, read what went wrong for others, then copy the build kit into your AI agent.
On 24 September 2026 a regional mental-health and human-services nonprofit in Chicopee, Massachusetts posted for an HR Generalist (Leave Specialist) at $22 to $24 an hour. The line that carries the job: “Manage the full lifecycle of employee leaves of absence, including short-term, long-term, and intermittent leave, ensuring 100% compliance with company policy, state, and federal regulations (e.g., FMLA, ADA).” The same person also runs onboarding checks, the HR records and employee questions. The posting names Outlook, Word and Excel, and no leave software.
Here is how it goes today. On a Monday at 6:40 am a residential counselor texts her supervisor that her mother has had a stroke and she will not be in this week. The supervisor logs three sick days. Nobody tells HR. The federal clock has already started: the employer has five business days to tell her she is eligible for protected leave, counted from the day it knew, and a supervisor knowing counts.
On day 12 she asks the scheduler for two more weeks. HR hears of it from the scheduler and emails the federal leave paperwork, four business days late. The doctor's certification is due on day 27; nobody asks for it, and the leave is never put on record as protected leave. The state's paid-leave office sends its review on day 18, and it sits in a shared inbox past its 10 business days, so the state decides on her word alone.
She comes back after six weeks. On day 85 her manager writes her up for two late arrivals, and HR never sees it. In Massachusetts any negative change within six months of a return from the state's paid leave is presumed to be retaliation. The first jury verdict under that rule, in April 2026, came to about $75,000 in back pay alone.
Nobody here is careless. The deadlines run in three places at once (the federal law, the state, the employer's own policy), the first sign of a leave reaches a supervisor, not HR, and one person runs it all from a spreadsheet between everything else. Hand the whole job to an outside administrator and the chasing still comes back to HR, and someone who does not know the case can end a person's benefits for paperwork that was already on file.
The counselor, her hours, the days and the times are an example built from the posting and the federal and state deadlines; the posting gives no counts. The 400 employees, the 60 leaves a year, the 4 hours a leave and the $75,000 at risk are estimates from public figures.
The map: the same job as a system
The judgment it all runs on sits in the middle square, held by a person. Around it, the work in the order it moves, each square run by the machine or by a person. Along the bottom, what it runs on.
The middle is whether this absence is protected leave, and what the person on it needs. The HR generalist holds it, with the Director of HR.
The same job as a system. The middle is the judgment about whether an absence is protected leave and what the employee needs, held by the HR generalist. The absence comes in on the left; across the top the machine checks eligibility, chases the certification and keeps every deadline; on the right HR decides each leave and talks to the person. Along the bottom is what it runs on: the triggers and the switch, the counts, and the rules and the locked file.
- Runs on its own
- A person does it
- The judgment it all depends on
- What it runs on
Who holds the middle square
The HR generalist, with the Director of Human Resources. Whether an absence is protected leave under the federal and state leave laws, what the employee on it needs, and when an accommodation or a manager's action needs a careful conversation first.
Before you build, these must already be true in your business:
- Payroll holds each employee's hire date, hours worked and the site they report to.
- Leave medical papers are kept in a locked file apart from the personnel file.
- One person approves every leave, and the Director of HR sees any action on someone back from leave.
Still deciding whether to do this, or no one holds this judgment yet? See the verdict: what it costs today, what to hand over, the bill and the owner
What went wrong for others, and the rules it gives the build
Four things that went wrong for people who did this job, or that tripped them up, and the rule each one gives the build.
“We (field HR) are still tasked with nudging employees for documents, handling interactive process conversations, forwarding paperwork, etc.”
A multi-site HR manager in warehousing and trucking whose company outsourced leave to its disability insurer, November 2025. Read it
The rule: The machine drafts every request and reminder on the dates the law sets and puts it in HR's queue; HR's part is the read, the send and the decision, not the chasing.
“One of our owners went out on maternity leave, the LOA specialist terminated her benefits for failure to supply documentation. 1) Her documentation was already on hand.”
An HR reply in the same thread, about an outsourced leave specialist, November 2025. Read it
The rule: Never end benefits, deny a leave or close a case for missing paperwork; the machine lists what looks missing, and a person checks the file before anything happens.
“My understanding was that the majority of them were not eligible for FMLA, due to not being within 75 miles of a physical site.” After counsel: “Their ‘FMLA reporting site’ should be our HQ.”
An HR team setting up a leave administrator for four sites and many remote staff, August 2026. Read it
The rule: Count eligibility from the site the employee reports to, never a home address, and show HR the arithmetic on every case.
A change “occurring during a leave or within six months following the employee's return from PFMLA leave is retaliatory”: the presumption behind the first verdict, about $4.68 million in damages.
The first Massachusetts paid leave retaliation verdict, April 2026. Read it
The rule: Any write-up, pay change or schedule cut for someone back from leave within six months goes to the Director of HR before it is issued.
What it costs to run
About $0.20 in model use: about 60,000 tokens in ($0.12 at $2 per million) and 8,000 out ($0.08 at $10 per million) over the case. About $1 a month at 5 leaves, plus the runner ($20 a month, 2,500 workflow runs; this uses well under 500 a month: each logged absence, each document, each daily check) and the case table ($40 a month, two users). HR time: about 1.5 hours a leave, about $35 at $23 an hour, against about 4 hours, about $92, by hand.
Estimate. The token counts, the 1.5 hours a leave, the 5 leaves a month and the run count are assumed. The counted month replaces them.
The build kit
One prompt to paste into Claude, ChatGPT or any AI agent that can build. It checks the middle square before anything else, builds the map square by square, carries the 4 rules above, and has the whole build: what starts it, every step, the data, the review, the alerts, what to do when it breaks, and what to count before you switch it on.
Before you build
- It may never, on its own: Send a notice or letter to an employee; approve, deny, designate or close a leave; end benefits or pay; contact a doctor; decide an accommodation; or put anything from the medical papers in the personnel file or in front of a manager.
- Keep with a person: Approving and designating every leave; whether a certification is enough, and whether to ask for a second opinion; every conversation about the employee's health or her family's; the accommodation conversation the disability law requires, and every accommodation; what to do when someone has used up her protected leave; and the review of any action on someone back from leave.
- Not yet: Sending any notice without HR's read; denying, designating or closing a leave on its own; ending benefits or pay for missing paperwork; contacting a doctor; deciding an accommodation; and letting anything from the medical papers reach a manager or the personnel file.
Help me build this in my business: Running every employee leave of absence from the first sign of it to the return to work. That means five things. Spotting that an absence could be protected leave, because the federal clock starts when the employer knows, not when the employee fills in a form. Checking eligibility and sending the notices on time. Getting the doctor's certification back, complete. Keeping every deadline after that: the federal designation, the state's paid-leave review, the hours used on a leave taken a day at a time, the return date. And the return itself, including the six months after it. Before you build anything: this runs on one person's judgment, "Whether this absence is protected leave, and what the person on it needs", held by the HR generalist, with the Director of Human Resources. Ask me whether each of these is true in my business, one at a time: 1. Payroll holds each employee's hire date, hours worked and the site they report to. 2. Leave medical papers are kept in a locked file apart from the personnel file. 3. One person approves every leave, and the Director of HR sees any action on someone back from leave. If any is not true, stop and tell me which, and what I need in place first. Do not build around it. Rules from others who built this and got it wrong. Keep every one: - The machine drafts every request and reminder on the dates the law sets and puts it in HR's queue; HR's part is the read, the send and the decision, not the chasing. - Never end benefits, deny a leave or close a case for missing paperwork; the machine lists what looks missing, and a person checks the file before anything happens. - Count eligibility from the site the employee reports to, never a home address, and show HR the arithmetic on every case. - Any write-up, pay change or schedule cut for someone back from leave within six months goes to the Director of HR before it is issued. The map of this system, a 3x3: - The middle square, the judgment it all runs on: Whether this absence is protected leave, and what the person on it needs (The HR generalist, with the Director of HR). It stays with a person. - The work, in the order it moves: 1. Spot the possible leave (runs on its own: Every absence logged with a reason, every request); 2. Check eligibility and draft the notices (runs on its own: From payroll, the arithmetic shown); 3. Chase the certification (runs on its own: The due dates, the reminders, the missing fields); 4. Keep every leave deadline (runs on its own: The designation, the state's review, the hours left, the return, the six months after); 5. Decide each leave and talk to the employee (a person does it: HR reads and sends every letter, designates every leave, and has every conversation about health). - Along the bottom, what it runs on: Automation (The six triggers, the morning check and the off switch.); Measure (Business days to each notice, certifications on time, hours per case, actions held.); Build (The eligibility rules and qualifying reasons, the notice templates, the locked case file apart from the personnel file.). Build the squares in that order, and keep the person's squares with a person. The working set to build from: - Trigger: An absence logged with a reason in the scheduling or time system; a leave request (form or email to the leave inbox); a document arriving in the leave inbox (a certification, a doctor's note, a return note); the state's review email; a write-up, pay change or schedule cut entered in the HR system; a daily check at 7:00 am of every open case. - Steps: On an absence or request: read the reason against the list of reasons that can qualify (the employee's own serious health condition, a family member's, a new child, a military family need). If it could qualify, open a case. Pull hire date, hours worked in the last 12 months and the reporting site from payroll; compute eligibility for the federal leave and the state's paid leave; draft the eligibility and rights notice with the arithmetic beside it; put it in HR's queue with its due date (5 business days from the first sign). After HR sends it: set the certification due date (15 calendar days) and queue reminders for HR 8 and 13 days after the request. On a document: file it in the locked case file, never the personnel file; read a certification against the form's required fields and list what is blank; draft the letter giving seven calendar days to fix it; when complete, draft the designation notice (due 5 business days from a complete certification). On the state's review: pull wages and leave dates, draft the reply, due 10 business days from arrival. On a leave taken a day at a time: log each absence against it in hours and show what is left. Before the return: remind the manager five days ahead and ask what the return needs. On an HR action: if the employee returned from leave within six months, hold it and send it to the Director of HR. On the daily check: list every deadline in the next three business days and everything overdue. - Data: One record per leave case: employee, site reported to, reason (in words HR wrote, never the diagnosis), first sign at and from whom, eligibility arithmetic, notice drafted at and sent at, certification requested, due, returned, complete at, fix letter sent, designated at, state review arrived and answered at, leave type (continuous or a day at a time), hours used and left, return date, returned at, six-month window ends, actions held, decided by. - Review step: The HR generalist reads every notice and letter before it goes. The Director of HR reads every held action, and five closed cases a month against payroll. - Alerts: A notice due within two business days and not sent; a certification overdue; a state review due within three business days; a leave taken a day at a time with 80% of its allowed hours used; a return date in five days with no plan; any action held in the six-month window; a case with no update in 10 days; and the wrong-but-green count, the eligibility results or drafts HR changed after they looked complete. - If it breaks: What you see: absences with a reason and no case, a deadline passed with nothing in the queue, or a document filed in the wrong place. Check first: the absence log and the payroll export are still feeding (log a test absence); the leave inbox still forwards; the HR system still sends action records. Safe fix: pause the six triggers; the cases stay in the locked table, and the HR generalist works the morning list by hand. - Baseline to count before switch-on: One month of cases counted by hand: business days from the first sign to the eligibility notice (find the first sign in the absence log, do not ask), certifications returned on time, days to designation, state reviews answered on time, hours per case (time it), and any action on someone back from leave within six months. - Tools by name: The workflow runner n8n (Starter, $20 a month billed annually); the case table Airtable (Team, $20 a user a month billed annually, access limited to HR); the model Claude Sonnet 5.5 ($2 per million tokens in, $10 out); the HR and payroll system's export for hire dates, hours, reporting sites and actions (the posting names an HRIS without naming it; which one is not public); the Massachusetts paid leave employer portal, by a person. Standalone: Tilt ($2.50 to $3.50 per employee per month; leave specialists $1.50 more, $5,995 minimum). In-house leave systems: AbsenceSoft, Stiira (by quote). People: Sparrow (outsourced leave administration, by quote). It may never, on its own: Send a notice or letter to an employee; approve, deny, designate or close a leave; end benefits or pay; contact a doctor; decide an accommodation; or put anything from the medical papers in the personnel file or in front of a manager. Keep with a person: Approving and designating every leave; whether a certification is enough, and whether to ask for a second opinion; every conversation about the employee's health or her family's; the accommodation conversation the disability law requires, and every accommodation; what to do when someone has used up her protected leave; and the review of any action on someone back from leave. Not yet: Sending any notice without HR's read; denying, designating or closing a leave on its own; ending benefits or pay for missing paperwork; contacting a doctor; deciding an accommodation; and letting anything from the medical papers reach a manager or the personnel file. Ask me for the tools and numbers you need from my business before you start. Then build it one step at a time, and show me each step working before the next.
No one in your business holds this judgment?
Then the first step is the expertise, not the build. Konstellation, Nick's advisory firm, judges one of your jobs with you, free: what it costs today, the verdict, the bill and who owns it.
Get the verdict on one jobKnow someone doing this job by hand? Send them this page.
Free, for one email
One email opens every job and every system.
Everything on instig8.ai is free. Your email, once, unlocks all of it on this device, and you hear when the next job is out.
Unsubscribe any time.