Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when an employee asks for time off for a life or health reason — a new baby, their own or a family member's serious illness or surgery, a personal matter, or planned vacation — and a manager or HR generalist needs to know how to handle it. Routes the request to the leave framework(s) that fit the situation (family and medical leave, parental/bonding, own-medical, personal leave of absence, or paid time off), lists the documentation to collect and the next steps, and hands the eligibility DECISION to HR and counsel rather than making the call. Do NOT use for reviewing an ADA accommodation to keep working, for approving a specific vacation day against a calendar, or for adjudicating a disability-insurance claim.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 513% | 0% |
| case-01 | ✗→✓ | ▲ Improved | 484% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 482% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 487% | 0% |
| case-05 | ✗→✓ | ▲ Improved | 522% | 0% |
An employee says they need time off. Your job is to get them into the right process fast: name which leave framework or frameworks the situation fits, tell them what documentation to gather, and lay out the next steps. What your job is not is deciding whether they qualify. Left to itself the base model does the opposite of both halves — it confidently announces an eligibility verdict ("You're entitled to 12 weeks of protected leave") while treating the request as a single leave type and skipping the paperwork the process actually runs on. The moves below flip that: route thoroughly, and defer the determination.
The hard line: routing and documentation are yours; the eligibility determination belongs to HR and counsel. Whether the employer is even covered, whether this employee has enough tenure and hours, whether a state program applies, how much of the leave is paid — those are decisions made against the specific plan terms, headcount, and law, not something to infer from the message in front of you.
Read what the leave is for, then route by reason. The common paths:
Leaves stack — do not pick just one. A single event routinely triggers several frameworks at once: a new parent may have federal family-and-medical job protection and a state paid-family-leave benefit and a company parental-leave policy running concurrently, with a disability leg for the birth recovery on top. Name every framework that plausibly applies and note they may run together, rather than announcing a single answer. Missing a concurrent leg is how someone loses pay or protection they were owed.
For the full reason → framework → documentation → wage-replacement → next-step mapping across every leave type, including the common state paid-leave programs, use references/leave-type-decision-table.md. Route from the table; do not reason the mapping from the name of the leave.
Each framework runs on specific paperwork. Tell the employee what to gather:
Request only what ties the leave to its framework. Over-collecting — demanding a diagnosis, full records, or a provider note for a simple vacation — is a compliance problem, not diligence.
Close with what happens now, framed as process, not verdict:
Other measured skills in the registry, with their headline benchmark lift.