Accurate Time Off Tracker for HR Teams 2027

Three people ask how many vacation days one employee has left. HR gives three different answers, from a spreadsheet, a payroll screen and a manager's email. A time off tracker exists to end that.
It holds one balance per employee, applies the right policy to it and keeps a record of every change. This guide shows the five places balances go wrong and the 2027 state leave dates that raise the stakes. It also gives you a scripted test to run on any time off tracker before you commit to it.
HR Cloud publishes this guide, so we hold ourselves to a strict rule. Every legal and labor statistic below comes from a government source we link. Every statement about HR Cloud comes from our own product pages or help center.
Examples are labeled as hypothetical, and we do not rank vendors here. If you need the difference between PTO and vacation first, our PTO vs vacation guide covers it. This guide answers the next question: how do you keep the numbers right?
Key Takeaways
- A time off tracker is accurate when five links hold: policy rules, accrual math, approvals against coverage, the payroll handoff and the audit record. We call these the five leak points, and the first table below pairs each one with a test you can run this week.
- Paid time off is a policy choice at the federal level. The U.S. Department of Labor says the Fair Labor Standards Act does not require time off for holidays, vacations or sick leave. State law and your own policy set the rules.
- Access is common but uneven. Bureau of Labor Statistics data for March 2026 show 80 percent of private industry workers had paid vacation and 81 percent had paid sick leave. Paid sick leave reached 74 percent of workers at establishments with 1 to 99 workers and 89 percent at those with 100 or more.
- 2027 adds dates to your calendar. Connecticut's paid sick leave law expands on January 1, 2027 to employers with one or more employees, down from 11 or more in 2026. Maryland FAMLI contributions begin the same day. Virginia's paid sick leave starts July 1, 2027 for employers with 50 or more employees.
- Test any time off tracker with your own awkward cases: a mid-year hire, a location transfer, a half day, a carryover cap. HR Cloud's time off tracking software page shows how it handles policies, and the eight-case test below gives you a fair way to compare.
What Makes a Time Off Tracker Accurate?
An accurate time off tracker returns the same balance no matter who asks, and it can show how that balance was reached. That sounds simple. In practice it depends on five links in a chain, and a break in any one of them produces a wrong number.
We call the five links the leak points. They are our own evaluation method, not an industry standard. The table pairs each leak point with a test that takes minutes, not weeks. Use it to find your weakest link before you shop for software.
| Leak point | What goes wrong | A test you can run | Usual owner |
|---|---|---|---|
| Policy rules | Rules differ by group, location or tenure, but they live in a handbook or in someone's memory. | Pick three employees in different groups. Write down each one's allowance, carryover cap and waiting period from two sources. Do the sources agree? | HR |
| Accrual math | Hand calculation, rounding and mid-year hires make balances drift. | Recalculate one employee's year-to-date balance from the written policy and compare it to the system. | HR and payroll |
| Approvals and coverage | A manager approves a request without seeing who else is out. | Ask a manager to name everyone away next Friday without opening a second tool. | Manager |
| Payroll handoff | Approved leave is typed into payroll a second time, or never arrives. | Trace one approved request to the pay record and count how many people touched it. | Payroll |
| Records | The system cannot show who approved, changed or denied a request. | Ask for the full history of one balance adjustment from last quarter. | HR and counsel |
Why this matters for HR: An error in any one link looks like a different problem. A wrong accrual becomes an employee complaint, a missed approval becomes a coverage gap, and a payroll mismatch becomes a pay dispute. Naming the link tells you who has to fix it, and it stops HR from absorbing every complaint as its own.
Why Does an Accurate Time Off Tracker Matter More in 2027?
Paid leave is now routine for most U.S. employees, which makes a wrong balance easy to notice and hard to explain. In March 2026, paid vacation was available to 80 percent of private industry workers, according to the Bureau of Labor Statistics. Paid holidays and paid sick leave each reached 81 percent.
Access is not even. In private industry, paid sick leave reached 74 percent of workers at establishments with 1 to 99 workers. At establishments with 100 workers or more it reached 89 percent. Paid vacation followed the same pattern, at 72 percent and 89 percent.
Smaller establishments are less likely to offer paid leave, so rules that reach them in 2027 will be new territory for some.
Federal law will not fill the gap. The Department of Labor's FLSA advisor says the law does not require time off for holidays, vacations or sick leave, with or without pay. It adds that state law determines whether such time must be granted. That makes your state list the thing to watch.
Four dated changes in the table below touch employers in 2027. We checked each against the government page linked in the last column on November 18, 2026. Rules change, so confirm the details with counsel before you set policy.
| Jurisdiction | Date | What changes | Source |
|---|---|---|---|
| Connecticut | January 1, 2027 | The paid sick leave law expands to employers with one or more employees in Connecticut, down from 11 or more in 2026. The count is based on payroll for the week containing January 1. | Connecticut Department of Labor FAQs |
| Maryland | January 1, 2027 | FAMLI contributions begin, with benefits available in January 2028. Employers with at least one Maryland employee must register. | Maryland Department of Labor FAMLI FAQs, April 2026 |
| Virginia | July 1, 2027 | Paid sick leave applies first to employers of at least 50 employees, then 25 or more on January 1, 2028, then one or more on January 1, 2029. Accrual is at least one hour per 30 hours worked. | Code of Virginia, Article 2.1:1 |
| New York | January 1, 2027 | A new Paid Family Leave eligibility standard takes effect for construction employees who work for several employers under a collective bargaining agreement. | New York Paid Family Leave |
A time off tracker does not run these programs. Maryland's FAMLI is a state insurance program funded by contributions, and Virginia's rule is an employer obligation. What the tracker does is record the leave your employees take, apply the accrual rule you set and show both on one record.
For example, a hypothetical Connecticut employer with 5 employees falls below the 11-employee threshold that applied in 2026. Before January 1, 2027 it would need three decisions. How does sick time accrue? Where do employees see the balance? How does it stay separate from vacation? A shared spreadsheet owned by one person can absorb that change only if that person hears about it in time.
What this means for your team: Do not wait for a complaint to learn which dates apply to you. List where your employees work and check each location against the sources above and your state labor department. Then decide who updates the tracker on each date.

Where Do Time Off Balances Go Wrong?
Each of the five leak points has its own cause and its own fix. Work through them in order, because an error early in the chain, such as a missing policy rule, spoils every number after it.
Leak point 1: Policy rules that live in someone's head
Most time off errors start before the first request. An employer has one rule for full-time staff, another for part-time staff and a third for a second location. A fourth applies to people past their fifth anniversary. When those rules sit in a handbook PDF and a manager's memory, every balance question becomes a judgment call.
A time off tracker needs each rule stored as a setting. The settings that matter most are:
- Annual allowance for each employee group
- Accrual schedule, whether per pay period, per hour worked or granted up front
- Carryover limit and the date it applies
- Waiting period before new hires can use leave
- Blackout dates
- Approval route for each group
HR Cloud's time off page lists these same settings, and its FAQ says policies can vary by location, department, group and leave type, including accruals, caps, waiting periods, carryover and approval chains. HR Cloud's help center shows the same building blocks in its policy setup article: a policy has a type, an accrual year start (the employee's anniversary or a date you choose), an accrued or up-front structure, an accrual cap, carryover and an optional new hire waiting period. Whatever tool you use, write each rule on one page per employee group before you configure anything. If you cannot write the rule in two sentences, it is not ready to become a setting.
Leak point 2: Accrual math done by hand
Accrual is where small errors compound. Our PTO accrual policies explainer covers the common methods. The arithmetic below shows why the method matters.
A hypothetical worked example. A policy grants a full-time employee 20 days a year on an 8-hour day, accrued per pay period over 26 pay periods. That is 160 hours a year, or 6.15 hours per pay period. A spreadsheet that rounds each period up to 6.2 hours credits 161.2 hours by year end, which is 1.2 hours more than the policy. After five years the gap reaches 6 hours, most of a working day, for one employee. Multiply that across a headcount and the balances look fine one at a time while the total is wrong.
Manual adjustments add another. HR Cloud's help center warns that an accrual added by hand should be assigned to a specific policy, because an accrual not linked to a policy does not follow policy rules and might not carry over to the next accrual year. Any tool with manual entry has this risk, so ask how it keeps adjustments inside the policy.
Mid-year hires add a second trap. A hire who starts at the beginning of pay period 14 has 13 periods left, which is half of the 26. If the policy prorates by period, the opening grant is 80 hours. A policy that prorates by days gives a slightly different number. Either rule is acceptable. The tracker must apply the same one every time.
Carryover caps add a third. With a 40-hour cap, an employee who ends the year with 52 hours carries 40 and loses 12. Whether an employer may remove those hours depends on state law and your own policy, so confirm that before the cap is enforced.
Some state laws set accrual by hours worked instead of by pay period. Virginia's paid sick leave statute, effective July 1, 2027, says employees accrue a minimum of one hour for every 30 hours worked. It also carries unused leave into the following year. A tracker that only knows "per pay period" cannot model that rule.
Pro tip: Once a quarter, pick one employee and recalculate the year-to-date balance by hand from the written policy. If the number differs from the system by even a fraction of an hour, find out why before the difference reaches a thousand rows.
Leak point 3: Approvals that ignore coverage
A manager who opens a request sees one name. The question that matters is who else is away. When absences sit in a separate calendar or email thread, the manager decides on partial information. The gap appears later as an uncovered shift.
HR Cloud's time off page describes a shared team calendar that shows coverage and upcoming absences in one view. It says the manager reviews a request with policy checks and team coverage shown up front. Its shared PTO calendar page adds customizable multi-level approval that can require two or more approvers.
For example, picture a hypothetical hospital unit of 12 nurses that needs nine on shift. Three approved requests for the same week leave no room for a sick call. A tracker that shows the other two requests beside the third lets the manager see the problem before approving, not after the schedule is posted.
Frontline teams add a second constraint: many approvers are not at a desk. HR Cloud's time off FAQ says employees can check balances and request time off, and managers can approve, on web or mobile. Test the approval step on a phone, not only on a laptop.
Leak point 4: The payroll handoff
Time off is paid through payroll, so the number that matters is the one payroll uses. If HR approves leave in one system and someone retypes it into payroll, you have two records and a person between them.
HR Cloud does not run payroll. It connects to the payroll you already run. Its time off page says approved leave moves automatically and duplicate payroll data entry is avoided, with ADP Workforce Now as the named example. Its ADP integration page says which fields sync depends on your ADP configuration. The second statement applies to any vendor and any payroll system: ask which fields move, in which direction and how often.
Payout rules are a second place the handoff matters. Virginia's statute states that it does not require reimbursement for unused accrued paid sick leave at separation. Whether vacation is paid out depends on your policy and applicable state law, so confirm yours with counsel. Make sure the tracker's balance matches the figure payroll uses on a final check.
Leak point 5: Records that cannot answer who approved what
When a balance is disputed, the first question is how it got there. A tracker that shows only the current number cannot answer.
The Department of Labor's FMLA advisor says covered employers must keep the specified records for at least three years. They must also make the records available for inspection. Those records include the dates FMLA leave is taken and, when leave is taken in increments of less than a full day, the hours. The leave must also be designated as FMLA leave in the records.
A time off tracker supports that record only if it logs each request, approval, denial and balance adjustment with a date and a name. HR Cloud's time off FAQ says it records requests, approvals, denials and balance adjustments and makes them reportable for compliance and planning. The tracker is one source among several, so ask counsel what else you must keep and where.
Why this holds up in an audit: An auditor or an employee's lawyer will not ask what the balance is. They will ask who changed it, when and on whose approval. A history that answers in one screen ends the question. A history spread across inboxes extends it.
How Do You Test a Time Off Tracker Before You Commit to It?
Ask every vendor to run the same scripted cases on their own screen, not a pre-built demonstration. Mark each row shown, partly shown or described only. Run the same eight cases against your current spreadsheet first, and you will learn where your own process leaks before any vendor does.
| # | Case to run | Evidence that counts |
|---|---|---|
| 1 | Enter a hire who starts at the beginning of pay period 14 on a 26-period policy. | The opening balance shows 80 hours or the proration your rule specifies, and the rule is visible on screen. |
| 2 | Move an employee from a location with one policy to a location with another. | The rule and balance change on the effective date, and the earlier history stays intact. |
| 3 | Set a 40-hour carryover cap and a year-end balance of 52 hours. | The system carries 40 hours, records the other 12 as your rule directs and logs the change. |
| 4 | Request 8 hours against a balance of 4 hours. | The system blocks or allows the request according to your overbook or negative-balance setting, and says which. |
| 5 | Request 2 hours on one day. | The balance drops by 2 hours and the record shows hours, not just a day. |
| 6 | Have three people in one department request the same Friday. | The approver sees the overlap before deciding. |
| 7 | Approve a request and follow it to your payroll system. | Nobody retypes it, and the vendor shows which fields move and when. |
| 8 | Pull the history of one balance adjustment. | The record shows who made the change, when, and the value before it. |
Why scripted cases work: A scripted case forces a vendor to show the rule, not describe it. It also makes vendors comparable, because every one of them answers the same eight questions. Rows 4, 7 and 8 deserve the most weight, because they touch money and records.
If you have a dozen employees, one policy and one payroll system, a well-kept spreadsheet may be enough. The test still helps, because it tells you how far you are from the point where it stops being enough.
Ready to pass your next audit—without the stress?
See how you can simplify compliance and eliminate gaps before they become problems.
Book Your Free Demo
How Does HR Cloud Run Time Off?
This section describes only what HR Cloud's own pages and help center state. Check each point in a demo against the eight cases above, because a page describes a product and a demo proves it.
The time off page groups the product into four areas: a time off calendar, accruals and policies, requests and approvals, and employee self-service. It describes a three-step flow. The employee requests leave on web or mobile with the balance visible before submitting. The right manager reviews it with policy checks and team coverage in view. Balances, shared calendars, history and connected systems then update.
Policy settings cover accruals, carryover limits, blackout dates and approval chains, and they can vary by employee group, location, department or tenure.
The help center adds detail on how a policy is built. In the policy article, an admin picks a time off type and an accrual year start, then chooses an accrued structure or an up-front structure. Accrued policies take an accrual schedule with one or more tiers, an accrual cap and carryover. The admin can also add rules that grant extra hours based on an employment detail, turn on auto assignment for new hires and set a new hire waiting period.
On balances, a separate help article lists the fields in the balance grid. Current Balance is the amount available today minus approved future use and pending requests for the current accrual year. Accrued, Used, Approved for Future Use and Pending appear as their own fields, with carryover from last year shown apart from current-year accruals.
Overbooking is a setting, not a surprise. The help center says an admin can turn on Allow Overbook for a time off type, which lets employees request more than their balance holds. A policy can also cap overbooking. Row 4 of the test checks how this behaves. The FAQ lists vacation, sick leave, personal days, parental leave, unpaid time off and custom types, each with its own policy, accrual schedule and balance.
For HR, the page describes a dashboard of balances, pending requests, upcoming absences and leave trends. It adds department and location filters and exportable time off reports.
The help center shows the request path in three steps. In the request article, the employee opens the Time Off application and clicks the plus sign under the Request tab. The employee then picks the time off type and enters the period. If approvals are set up, an email notification follows the review.
For a partial day, the partial-day article says to set the start and end dates, click Customize and adjust the hours. It adds that if Customize is missing, an HR admin may need to turn the feature on. That maps to row 5 of the test.
The approval article describes the other side. A manager or HR admin opens the Requests tab, clicks the requester's name, chooses Approve or Deny and can leave a comment. An approval email link can skip the first steps.
On payroll, HR Cloud does not run payroll. It connects to the payroll you already run, and the page names ADP Workforce Now as the connected example. Which fields sync for your payroll system is a demo question, as covered under leak point 4.
What to verify in a demo: Ask to see the overbook setting change what happens to a request that exceeds the balance (row 4). Then watch a request get approved on a phone (leak point 3), and pull the history of one adjustment (row 8). If a feature is on the page but missing from the screen, treat it as described only and score it that way.
What Does Accurate Time Off Tracking Look Like Across Shifts and Locations?
One time off tracker has to serve a nurse on rotating shifts, a plant worker in another state and a manager at a desk. The table shows where each setup can break and what to ask a vendor to show.
| Setup | What can break | What to configure | Ask a vendor to show |
|---|---|---|---|
| Hourly healthcare staff with round-the-clock coverage | Requests arrive by text or hallway conversation, and approvers cannot see coverage. | Mobile requests, a per-unit approver and a coverage view. | A request from a phone with the balance visible, and an approver who sees overlapping requests. |
| Multi-state manufacturer with several plants | Different state leave rules, and plant shutdown weeks that need blackout dates. | Policies by location and blackout dates for shutdowns. | Two employees in two states with different rules, and one report filtered by location. |
| Hybrid office team | Remote staff ask by chat, and the record lives in a message thread. | One request path with self-service balances. | A request and approval that never touch email. |
| Field or construction crews | Supervisors approve from job sites, and some crews fall under special state rules. | Delegate approvers and mobile approval. | A delegate approving while the primary approver is out. |
For example, a hypothetical 300-person home care agency with staff in Connecticut and Virginia could run two paid sick leave rules at once. Connecticut's law already reaches employers of that size, and Virginia's starts July 1, 2027, if the statute applies to it. A tracker with policies by location lets HR switch each rule on for its own date, not run both from one master sheet.
The construction row carries one dated item. New York's Paid Family Leave change for some construction employees takes effect on January 1, 2027. A contractor with New York crews should confirm whether it applies. Unionized crews can also be subject to rules written into collective bargaining agreements, which a tracker cannot read for you.
Why this matters on the floor: Frontline teams do not tolerate extra steps. If requesting leave means finding a desktop or a supervisor, people stop asking through the system and the record falls behind. Mobile requests and approvals are an accuracy feature, not a convenience.
What Should You Do This Week?
Each step below fits inside a working day, and together they show you which leak point to fix first.
- Sort your last three balance disputes (about 30 minutes). Pull the three most recent and label each one with a leak point from the first table. The leak point that appears most often is your first fix.
- Write one page per employee group (about 90 minutes). Record allowance, accrual schedule, carryover limit, waiting period, blackout dates and approver. Where two people give different answers, you have found a policy that needs a decision, not a setting.
- List the 2027 dates that touch your headcount (about 20 minutes). Check where your employees work against the table of dates above and your own state labor department. Then name the person who updates the tracker on each date.
- Run the eight cases against your current process (about 60 minutes). Mark each row shown, partly shown or described only, and keep the sheet. It becomes your script for every vendor demo.
Conclusion
An accurate time off tracker depends on five checks holding at once. They are written policy rules, correct accrual math, approvals that see coverage, a payroll handoff without retyping and a record that explains changes. A tool helps with each one, but only after you know which link is weakest in your own setup.
Start with the three disputes and the one-page policies. They cost no money, they take a day or two, and they tell you whether you need a better process, better software or both. Then run the eight cases against any time off tracker you consider, including ours, and score what you see on screen.
Discover how our HR solutions streamline onboarding, boost employee engagement, and simplify HR management
Book a DemoFrequently Asked Questions
What is the best way to track employee time off?
Use one system that stores each policy as a setting, calculates accruals itself, routes requests to the right approver and logs every change. That is what separates a time off tracker from a shared spreadsheet. With few employees and one policy, a spreadsheet can work. Once policies, locations or payroll connections multiply, balances start to drift.
What are best practices for time off tracking in HR?
Write each policy on one page, store it as a setting and recalculate one balance by hand each quarter to confirm the system matches. Show approvers who else is away before they decide. Keep a history of every request, approval, denial and adjustment. Review state leave dates each autumn for the coming year.
Can employees request time off from their phone?
Yes, with some systems. HR Cloud's time off page says employees can check balances and submit requests, and managers can approve, on web or mobile. For frontline teams without a desk, test this on a phone during the demo. Confirm that the balance is visible before the request is submitted.
Can payroll software track paid time off?
Some payroll systems carry a balance, but a payroll record is not the same as a time off workflow. Requests, approvals, coverage views and policy rules by group sit in the workflow, and the approved result goes to payroll. Ask any vendor which fields move and whether anyone re-enters data.
Does federal law require employers to give paid time off?
No. The U.S. Department of Labor says the Fair Labor Standards Act does not require time off for holidays, vacations or sick leave, with or without pay. State law may require paid sick leave, and employer policy or contract can add more. Check each state where you have employees.
How long should you keep leave records?
For leave covered by the FMLA, the Department of Labor says covered employers must keep the specified records for no less than three years. Other time off records may fall under state law or your own retention policy. Ask counsel for the period that applies, and keep the tracker history that supports each approval and balance.
Does HR Cloud include payroll?
No. HR Cloud does not run payroll. It connects to the payroll you already run, including ADP, UKG Pro, UKG Ready, Paylocity, Paycor, Dayforce and other payroll systems on its integrations list. The time off page describes approved leave moving automatically to ADP Workforce Now. Ask which fields sync for your payroll system.
Can time off policies differ by location?
Yes, if the tracker stores policies as settings. HR Cloud's time off page says policies can vary by location, department, employee group and leave type. They can cover accruals, caps, waiting periods, carryover and approval chains. Test this with two employees in different locations and compare their balances and rules side by side.
Is a spreadsheet enough for a time off tracker?
It can be, with few employees, one policy and one payroll system, as long as one owner recalculates balances and keeps a change history. It stops working when rules differ by group or location, when several managers approve, or when a state adds a leave law. The eight-case test shows where your sheet breaks.
About the author

Like What You Hear?
We’d love to chat with you more about how HR Cloud® can support your business’s HR needs.
Book Your Free Demo

