A sick leave tracker that keeps the right records separate
A sick leave tracker records sick-time eligibility, earned balances, requests, and usage separately from vacation. Use a distinct leave type and a clear hourly record so an unexpected sick day doesn't become a vacation deduction or an unexplained balance change.
$4 per user per month Β· No credit card
Keep the sick-time ledger clear and personal health details out of shared messages.
Request PTO
Leave type
Vacation
Start date
Nov 9
End date
Nov 13
Note
Sam is covering support
Cabana APP
New PTO request from Maya Patel
Employee
Maya Patel
Leave type
Vacation
Dates
Nov 9 to Nov 13
Days
5
Note
Sam is covering support
Cabana APP
π΄ Out today β Monday, Nov 9
- β’ Maya Patel
- β’ Chris Okafor
Posted each morning, plus a Monday digest of the week ahead. Names only β no notes or balances.
Start with the employee's sick-time record, not an attendance score. The useful questions are what they have earned, what they have used, and how to record the absence without broadcasting personal medical information.
Track sick days separately from PTO used for vacationΒΆ
Give sick time its own leave type when its rules differ from vacation. Keep the earning rule, available balance, carryover, and permitted usage together. A distinct ledger lets the person handling payroll explain a sick-time movement without reconstructing which entries in a combined vacation bank were actually taken for a protected purpose.
A combined PTO plan can satisfy a sick-leave law when it meets that law's conditions; separation isn't universally mandatory. New Jersey's labor department explains both approaches and the additional conditions that apply to a combined plan.
For everyday recordkeeping, collect employee, leave type, dates or hours, status, and balance movement. Keep diagnoses out of a general request note and out of the team availability channel.
State paid sick-leave accrual baselinesΒΆ
Use the state source to identify the standard accrual rate and the kind of limit involved before configuring a ledger. An annual earning limit, annual use limit, and total bank limit are different controls. The table separates them so a carryover balance doesn't accidentally stop earnings that the law still requires.
Checked October 27, 2026. Hours are used throughout. These are statewide baseline accrual routes for covered workers; eligibility exclusions, local ordinances, and alternative front-loading arrangements can change application.
| State / agency source | Standard earning rate | Baseline limits and paid-employer threshold |
|---|---|---|
| Alaska | 1 per 30 worked | Annual earn/use: 40 below 15 FTE; 56 at 15+ FTE. Carryover can increase the bank. |
| Arizona | 1 per 30 | Annual earn/use: 24 below 15 employees; 40 at 15+. |
| California | 1 per 30 | Annual use floor: 40 hours or five days, whichever is greater; bank cap may be 80 hours or ten days, whichever is greater. |
| Colorado | 1 per 30 | Annual earn/use: 48; carryover up to 48. All employer sizes. |
| Connecticut | 1 per 30 | Annual accrual: 40. Covered employers: 11+ Connecticut employees in 2026. |
| Maryland | 1 per 30 | Annual accrual: 40; total bank: 64. Paid at 15+ employees; smaller covered employers provide unpaid time. |
| Massachusetts | 1 per 30 | Annual earn/use: 40. Paid at 11+ employees; smaller employers provide protected unpaid time. |
| Michigan | 1 per 30 | Annual use: 40 for qualifying small businesses of ten or fewer; 72 otherwise. Usage caps aren't accrual caps. |
| Minnesota | 1 per 30 | Annual accrual cap may be 48; total accumulated bank cap may be 80. |
| Nebraska | 1 per 30 | Annual earn/use: 40 at 11β19 employees; 56 at 20+. No general mandate below 11. |
| New Jersey | 1 per 30 | Annual entitlement: 40. All employer sizes, subject to worker exceptions. |
| New Mexico | 1 per 30 | Annual use may be limited to 64; no accrual cap. |
| New York | 1 per 30 | Annual use: 56 at 100+; 40 at 5β99 or smaller employers with net income above $1 million; otherwise unpaid 40. |
| Oregon | 1 per 30 | Annual use: 40. Paid at 10+ Oregon employees, or six+ with a Portland location. |
| Rhode Island | 1 per 35 | Annual earn/use: 40. Paid at 18+ employees; smaller employers provide unpaid time. |
| Vermont | 1 per 52 | Annual accrual may be capped at 40; worker eligibility exceptions apply. |
| Washington | 1 per 40 | No annual accrual cap; carryover cap may be 40. Covered workers earn for all worked hours. |
Keep broader any-reason paid-leave programs distinct from sick-leave-specific laws:
| State / agency source | Rate | Baseline limit |
|---|---|---|
| Illinois | 1 per 40 worked | 40 per year under the statewide any-reason program; local regimes differ. |
| Maine | 1 per 40 | 40 earned per year, plus qualifying carryover; generally employers with more than ten workers for over 120 days. |
| Nevada | 0.01923 per worked hour | Carryover may be capped at 40; generally private employers with 50+ Nevada employees. |
This is general US information, not legal advice. The table isn't a complete eligibility, local-law, or payroll-administration guide.
Keep the statutory hourly ledger exactΒΆ
Use actual hours worked when the earning rule is tied to work, and keep sick hours earned and used in the same unit. For example, 120 worked hours at a one-for-30 rate earns four sick hours. That equals half an eight-hour day, but the underlying record is still four hours.
Keep the authoritative statutory-hours ledger in payroll or timekeeping. Cabana uses day-based balances; its period-based accrual isn't an actual-hours-worked feed.
Give sick day tracking a private, practical workflowΒΆ
Make reporting an unexpected absence easy and keep its medical explanation separate from shared availability. Employees need a way to notify the right person even when they cannot complete a detailed form immediately. The team needs to know who is unavailable; it doesn't need a public diagnosis or an absence-pattern score.
In Cabana, create a distinct category in Settings β Leave types. The policy control Hide this leave type from coworkers masks the category as Private leave in shared views. Use Private approver note on the web form for context intended for approvers and admins rather than coworkers.
Use Cabana for the request and availability recordΒΆ
Choose Cabana to keep sick requests separate from vacation and connected to manager messages and the team calendar. Employees can request from Slack or Microsoft Teams. Configure the approval process to reflect the applicable sick-leave rules rather than assuming ordinary vacation restrictions belong on every category.
Set up the sick leave type so it can't be refused for scheduling reasons: in its policy rule, leave Advance notice required, Maximum teammates away and the new-hire waiting period empty unless your state allows them, and consider Automatically approve requests. Blocked dates apply to every leave type, so keep them narrow.
Start with leave types, PTO tracking in Slack, PTO tracking in Microsoft Teams, and PTO tracking software for small teams. Use the PTO policy guide for small business and Free PTO policy generator for the written process.
One plan costs $4 per user per month, with a $20/month minimum. Try it free for 30 days with no credit card.
Frequently asked questions
Must sick leave always be separate from vacation PTO?
No. Some laws allow a combined PTO plan that meets every required sick-leave condition. Separate categories can make recordkeeping clearer when earning, usage, or carryover rules differ. New Jersey's labor department explains that a combined plan must preserve the required purposes and protections, not merely offer a larger total number of days.
Can a tracker decide whether sick leave is legally protected?
No. A request category or balance doesn't establish legal eligibility by itself. Use the governing rules and the employee's circumstances to determine the right treatment, then record the outcome. Cabana tracks the request and leave record; it doesn't replace the statutory decision about coverage, permissible notice, documentation, or protected use.
Does Cabana accrue statutory sick hours from actual hours worked?
No. Cabana's app accrual methods are period-based, and balances are stored in days. Keep the statutory hourly ledger in payroll or timekeeping and reconcile it with the request record. A state rate in this table describes the legal earning rule; it isn't a promise that the app automatically applies it.
Can coworkers see why someone is sick?
Coworkers may see general notes on non-private requests in the calendar feed, so keep medical explanations out of that field. Cabana can mask a private leave category as **Private leave**, while scheduled **Out today** announcements list names. Use **Private approver note** on the web form for context intended for approvers and admins.
Can employees request sick leave through Slack or Teams?
Yes. Employees can use `/pto request` in Slack or send `request` in their private Cabana chat in Microsoft Teams, then select the sick leave type. The chat forms contain dates and a note. Use the web form for partial-day options that aren't exposed in the current native chat forms.
Does a blackout rule automatically exempt sick leave?
No. Cabana's current blocked-date validation applies to every leave type within the affected scope, before the policy rule is resolved. Don't assume a sick category creates a protected-leave exemption. Establish the appropriate reporting and recordkeeping process before enabling a block, rather than relying on a form that rejects an employee's dates.
Related
A complete, state-aware policy in two minutes.
Small-business PTO benchmarks (2026 BLS data) βVacation days by tenure and leave access by workplace size.
PTO tracking software for small teams βWhat to look for, and how Cabana handles it.
PTO tracking in Slack βRequest, approve, and see who's out without leaving Slack.
PTO tracking in Microsoft Teams βRequest, approve, and see who's out without leaving Teams.