The Complete Guide to Tracking Employee PTO and Leave Balances

Paid time off looks like a simple benefit until you have to administer it. Someone asks how many vacation days they have left, and the answer depends on their hire date, the accrual rate, the days they already took, the holiday that fell on a Friday, and whether last year's unused balance rolled over. For a company with three people, you can hold all of that in your head. For a company with fifteen, twenty-five, or fifty, you cannot, and the moment a manager guesses wrong, trust in the whole system starts to erode. The employee who is told they have eight days and later learns they had five does not forget it.

This guide is the hub for everything we have written about PTO and leave balance tracking. It is organized around seven themes: why tracking matters, how to write a workable policy, how accruals are calculated, how to treat sick time and other leave types, how to run requests and approvals, how to choose a tracking method, and what to do at year-end. Each section summarizes the essentials and points to a deeper article where one exists. We build leave tracking software, so we have opinions, but we have tried to keep this guide useful whether or not you ever use our product. Most of what follows applies equally to a spreadsheet, a payroll module, or a dedicated tool.

Why leave tracking matters more than it looks

The obvious reason to track PTO is so that people take the time they have earned and no more. The less obvious reasons are the ones that catch small businesses off guard. Accrued but unused vacation is generally treated as a liability on the books, which means an inaccurate balance is an accounting error, not just an HR inconvenience. In several states, earned vacation is legally considered wages, so a balance that is off by a few days can turn into a wage claim when someone leaves. And every time a balance is wrong in the employee's favor, the company pays for time that was never earned; every time it is wrong against the employee, someone feels cheated and usually says so.

Tracking also shapes how people behave. When balances are opaque, employees hoard days because they are not sure what they have, then try to use them all in December. Managers approve requests without knowing who else is out, and a small team ends up with two of its four engineers gone the same week. Unplanned absences creep up because nobody notices that one person has called in sick eleven Mondays in a row. None of these problems are dramatic on their own, but together they are the difference between a team that runs smoothly and one that lurches from one coverage gap to the next.

Most companies start with a spreadsheet, and that is a perfectly reasonable place to begin. The trouble is that spreadsheets do not enforce rules. They do not stop a request from being approved when the balance is zero, they do not notify anyone, and they depend on a single person remembering to update them after every approval and every pay period. We have written about the specific ways spreadsheet tracking breaks down as a team grows, and about how better tracking helps reduce unplanned absences. The short version is that the tracking method should grow with the headcount, and the point at which the spreadsheet stops working usually arrives earlier than people expect.

Writing a PTO policy your team can actually follow

In the United States there is no federal law that requires private employers to offer paid vacation. That freedom means the policy is entirely yours to design, and it also means there is no default to fall back on when a question comes up. A written policy answers those questions before they are asked: how much time people get, how it accrues, when new hires can start using it, how far in advance requests should be made, what happens to unused time, and whether it is paid out when someone leaves. If any of those answers live only in a founder's head, the policy does not really exist yet.

The best time to write the policy is before you think you need it. Startups often wait until the first awkward situation, such as an employee asking for three weeks off in their second month or a departing engineer asking to be paid for the vacation they never took. By then, whatever you decide sets a precedent under pressure. A short policy written when there are five employees can be revised as the company grows; a policy improvised at twenty is harder to walk back. Our article on when a startup should formalize paid time off goes into the specific signals that tell you it is time.

Keep the document short and specific. A one-page policy that states the accrual rate, the cap, the request lead time, the carryover rule, and the payout rule will be followed. A twelve-page policy full of legal language will be ignored and then argued over. Decide early whether you want a single combined PTO bank or separate vacation and sick balances, because that choice affects everything downstream, from accrual math to state compliance. We cover that decision in detail in our article on tracking sick time and vacation separately.

One more principle: write the policy for the company you have, not the company you are imitating. Unlimited PTO sounds generous, but for small teams it often results in people taking less time because there is no number telling them what is normal. A clear allotment with a healthy minimum is easier to administer, easier to track, and, in our experience, more likely to result in people actually resting. If you do choose unlimited, still record every day taken, because you will want the data later.

Accruals, front-loading, and how balances are calculated

An accrual is simply the rate at which paid time off is earned. The two broad models are front-loading, where the full annual allotment is granted on a single date, and incremental accrual, where time is earned gradually across the year. Front-loading is simpler to explain and to track, but it creates a risk: an employee who takes all fifteen days in February and leaves in March has used time that was technically granted but not really earned. Incremental accrual avoids that problem at the cost of more arithmetic, and it produces balances that change every pay period, which is why people need somewhere to look them up.

Incremental accruals can run per pay period, per month, or per hour worked. Per-pay-period accrual lines up neatly with payroll and is the most common choice for salaried teams. Per-hour accrual is fairer for part-time and variable-hour staff, and it is the model many state sick leave laws are written around, often using a formula along the lines of one hour earned for every thirty hours worked. Whichever model you choose, decide on the details that trip people up: whether accrual starts on day one or after a waiting period, whether there is a maximum balance beyond which accrual pauses, whether balances can go negative, and how time is prorated for people who join or leave mid-cycle.

The math itself is not hard, but it has to be done consistently, on schedule, for every employee, forever. That is where manual tracking fails. A spreadsheet formula can calculate an accrual, but someone has to remember to run it every pay period, adjust it for the employee whose hours changed, and reconcile it with what payroll actually paid. Our deep dive on how PTO accruals work walks through the setup decisions step by step, and our article on year-end carryover covers what happens to accrued time when the calendar rolls over.

Sick time, vacation, and the other leave types

A single combined PTO bank is attractive because it is simple: one balance, one accrual rule, no need to judge whether a day off was for a cold or a beach. The drawback is that it quietly penalizes people who get sick, since every sick day is a vacation day they no longer have. It also collides with state law. A growing number of states and cities require employers to provide paid sick leave with specific accrual rates, carryover rules, and permitted uses, and a combined bank has to satisfy those rules for the entire balance, not just the sick portion.

Separate balances are more work to administer but easier to reason about. Vacation follows the company policy; sick time follows the applicable law where the employee works, which matters more than ever now that many small teams have remote staff in several states. The tracking system, whatever it is, needs to hold at least two balances per person, apply different accrual and carryover rules to each, and let employees see both. Our article on whether to track sick time and vacation separately lays out the trade-offs in detail.

Beyond sick and vacation, most companies eventually add leave types that do not accrue at all: bereavement, jury duty, voting time where state law requires it, military leave, and parental leave. Some are legally required, some are company choices, and some, such as parental leave, may be partly funded by a state program. These do not need a balance, but they do need to be recorded, both so that coverage can be planned and so that there is a clean record if a question comes up later. A good tracking setup lets you define a leave type in a minute and decide whether it draws down a balance or simply logs the absence.

Unpaid leave deserves a mention too. Larger employers are subject to the federal Family and Medical Leave Act, which provides job-protected unpaid leave for qualifying reasons, and some states have their own broader versions. Smaller companies are often outside those rules but still grant unpaid leave case by case. Whatever the situation, the policy should say how unpaid leave interacts with accruals, since many companies pause accrual during extended unpaid absences, and the tracking system should be able to reflect that. Our article on formalizing a first PTO policy suggests where these clauses belong.

Requests, approvals, and keeping the team covered

The request and approval flow is where most employees actually experience the leave policy. They do not read the accrual rules; they ask for a Friday off and notice how long it takes to get an answer and whether the answer feels fair. A good flow is fast, transparent, and consistent. The employee sees their balance before they ask, the manager sees who else is out before they answer, and the decision is recorded somewhere that both of them can find later. A request that sits in an inbox for a week is a small failure that people remember.

Fairness is the hard part. First-come, first-served rewards people who plan far ahead and punishes those whose lives are less predictable. Seniority-based approval is easy to explain but breeds resentment. Most small teams land on a hybrid: a lead-time rule for ordinary requests, a coverage minimum for each role or team, and a conversation when two people want the same week. The key is deciding the rules before the conflict rather than during it. Our article on approving time off fairly goes through the common models and when each one makes sense.

Coverage is easier when everyone can see the same calendar. A shared team leave calendar, whether it lives in a dedicated tool or is synced into the calendars people already use, lets employees pick dates that will not collide with a teammate's, lets managers spot a thin week before approving one more request, and cuts the number of back-and-forth messages dramatically. The benefits go beyond scheduling: people are more likely to take time when they can see their colleagues doing the same. We have a separate article on the real benefits of a shared leave calendar.

Two details make or break the workflow. First, approvals must update balances automatically. If a manager approves three days and someone else has to remember to subtract them, the balance will eventually be wrong. Second, the flow must handle changes gracefully: canceled requests, half days, requests that span a holiday, and a manager who is on leave themselves. These edge cases are exactly where manual systems accumulate errors, and they are worth testing before you commit to any method.

Choosing a tracking method: spreadsheet, HR suite, or dedicated tool

There are broadly four ways to track leave: a spreadsheet or shared document, a leave module bundled with your payroll or HR platform, a dedicated leave tracking tool, or a calendar with a loose process around it. Each can work at a certain size, and the honest answer is that the right choice depends on headcount, how many leave types you run, how many states you operate in, and how much of the administrator's time you are willing to spend on it. Nobody needs the most powerful option on day one.

Spreadsheets win on cost and flexibility. They lose on enforcement, notifications, self-service, and history. A bundled payroll module usually gets accruals right and syncs balances to pay, but the request experience is often clunky and the configuration can be rigid. A dedicated tool is built around the request flow, the calendar, and self-service, and typically integrates with payroll rather than replacing it. Calendar-only tracking is fine for a team of four with an unlimited policy and no legal sick leave obligations, and poor for almost everyone else. We have written a full comparison of these approaches, and our article on spreadsheet tracking explains where the breakdown usually happens.

Whatever you choose, prioritize self-service. When employees can see their own balance, submit a request, and check its status without asking anyone, the administrator stops being a bottleneck and the number of balance disputes drops sharply. But self-service only works if people trust the number on the screen. That trust comes from balances that match what payroll paid, from a visible history of every accrual and deduction, and from a system that never silently changes a figure. Our article on what makes employees trust a self-service system covers the details.

Finally, think about the switch itself. Migrating from a spreadsheet means picking a cutover date, loading opening balances for every employee, and reconciling them against the old records. Do it at a natural boundary such as the start of a pay period or a new year, tell employees what their opening balance is and how to dispute it, and keep the old spreadsheet read-only for a few months. A clean migration prevents the new system from inheriting the old system's errors, and it is the single best moment to correct balances that have drifted.

Year-end carryover, payouts, and what the data can tell you

December is when weak tracking gets exposed. Employees suddenly discover balances they did not know they had, managers face a wave of last-minute requests, and the administrator has to work out who carries over what. The policy should already say whether unused time carries over, how much, and by when it must be used. Common approaches include a hard cap on carryover, a grace period into the first quarter, and a rolling maximum balance that simply stops accrual once it is reached. Each is easy to administer once the rule is written down and the system applies it automatically.

State law constrains these choices. Some states, California being the best-known example, treat earned vacation as wages that cannot be forfeited, which makes a pure use-it-or-lose-it rule unlawful there, though a reasonable cap on accrual is generally permitted. Payout at separation likewise depends on the state and on what the written policy says. This is one of the strongest arguments for tracking that is accurate to the day: when an employee leaves, the final paycheck may need to include an exact figure, and reconstructing it from a stale spreadsheet is painful. Our article on handling carryover at year-end walks through the options and the planning calendar we recommend.

Once tracking is reliable, the data becomes useful in its own right. You can see which teams are not taking time off, which is often an early sign of burnout or understaffing. You can see patterns in unplanned absences, such as a cluster of sick days around specific dates or people, and address them with a conversation instead of a policy change. You can forecast coverage for the busy season and plan hiring around it. None of this requires anything fancy, just balances and absence records that are complete and correct. Our article on reducing unplanned absences shows how a few simple reports change the conversation.

Treat the year-end review as a policy checkpoint. Look at total accrued liability, average unused balance, and how many people hit the cap. If large balances are piling up, the problem is usually cultural rather than mathematical, and the fix is managers who model taking time off, not a tighter carryover rule. If people are running out of time by October, the allotment may be too small for the work you are asking of them. Either way, the numbers should drive the conversation, and the conversation should happen before the new year starts rather than after.

More guides on this topic

Further reading from the LeaveLedgr blog, each answering one specific question in depth.

Leave tracking is one of those operational chores that nobody thinks about until it goes wrong, and by then it has usually gone wrong for a while. The good news is that getting it right is not complicated. Write a short policy early. Choose an accrual model you can explain in one sentence. Keep sick time separate where the law or fairness calls for it. Give people a self-service view of their balance and a shared calendar. Pick a tracking method that enforces the rules rather than merely recording them, and revisit the policy every year with the data in front of you. The articles linked throughout this guide go deeper on each step. If you have a question we have not answered, tell us; the next article usually comes from a reader.