Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add cbrock84/headcount --skill benefits-and-leave --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Benefits And Leave?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cbrock84-benefits-and-leave)More formats (shields.io, HTML) on the badges page.
---
name: benefits-and-leave
description: Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
---
# Benefits and leave
Benefits are the second largest people cost after salary and the one employees judge most directly.
`people:compensation-and-leveling` covers pay bands and leveling; this covers everything else in the
package.
**Benefits and leave are heavily regulated and jurisdiction-specific — in the United States, ERISA,
COBRA, ACA, FMLA and their state equivalents, with state family-leave and sick-leave laws differing
substantially. Plan design and administration need a qualified benefits broker or employment
counsel. This structures the decisions and names what to ask.**
## Design for what people actually value
Benefits budgets are routinely spent on things that survey well and are used rarely, while the
things people quietly need are underfunded.
The reliable pattern: health coverage quality, retirement match, and real time off dominate
perceived value nearly everywhere. Beyond those, ask rather than assume — a young workforce and one
with school-age children value very different things, and the difference is large enough to be worth
measuring.
Watch utilization. A benefit nobody uses is either badly communicated or badly chosen, and the two
have different remedies.
## Cost, and the renewal you should not sleepwalk
Health costs rise faster than general inflation more or less every year, so a flat renewal is not
the baseline — the baseline is an increase you must actively negotiate down or absorb by design.
Start renewal months ahead, not weeks. Understand what drives your own experience rating, model plan
design changes against employee impact, and market the plan periodically even when you intend to
stay — a broker who knows you are not looking negotiates accordingly.
Cost-shifting to employees is a pay cut delivered indirectly. It may be the right call; describe it
honestly when you make it, because employees compute it correctly and describing it otherwise costs
more trust than the money saved.
## Leave: policy is the easy part
Write policy that a manager can apply without calling HR for every case — eligibility, notice,
documentation, pay treatment, and how it interacts with other leave types.
The failures are in administration: leave running concurrently under multiple entitlements, return-
to-work handled ad hoc, and accommodation requests treated as leave questions when they are legal
ones. Route anything touching disability, pregnancy, or accommodation through counsel via
`people:employee-relations`.
Track leave centrally rather than in managers' memories. The organization that cannot say who is on
what leave and until when is the one that mishandles a return.
## Never
- Change plan design without modeling the effect on the employees who use it most.
- Enter a renewal without having tested the market recently.
- Describe cost-shifting as a benefits enhancement.
- Handle an accommodation request as a leave administration question.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!