Time off, done right.

Arizona mandates earned paid sick time on a two-tier cap that turns on a 15-employee headcount. Why crossing that threshold changes your obligation.

The eight questions that actually decide whether PTO software works for a small team, the red flags to walk away from, and when to skip it entirely.

Colorado treats earned vacation as wages that cannot be forfeited, and mandates paid sick leave. What Nieto v. Clark's Market changed for every handbook.

Connecticut's sick leave threshold drops each year until it covers every employer in 2027, and you may not ask for a doctor's note. What that changes.

The admin hours are the small part. The expensive failures are wrong balances, unlogged days and payouts calculated from a figure nobody checked.

Florida mandates no paid leave and bars cities from requiring it. With no state wage-claim process, your handbook is enforced in court instead.

Free tiers, free trials and genuinely free tools are three different things. How to tell them apart before you put your team's leave data in one.

A shared calendar is the best free way to make time off visible, and a poor way to track balances. Where the line falls, and how to set it up properly.

A step-by-step migration: reconcile first, pick a clean cut-over date, import rather than retype, and handle the requests already approved but not taken.

A full HR platform solves problems a ten-person team may not have yet. How to tell which category you actually need, and what each costs you.

Illinois requires 40 hours of paid leave usable for any reason, with no documentation. Chicago stacks a second entitlement on top. How the layers work.

Maryland lets you forfeit unused vacation only if you wrote it down first, and its sick leave waiting period is an oddly specific 106 days.