Seniority Entitlement is the Automation that grants extra PTO days based on how long someone has been with the company. You define the milestones (for example: 3 extra days at 2 years of service, 5 at 5 years), and Vacation Tracker applies the bump automatically on each User's anniversary. No spreadsheets, no missed anniversaries, no awkward conversations about whether someone is owed more days.
What Seniority Entitlement Does
Adds days on top of the base quota: the bump sits on top of whatever the User's regular allowance is.
Triggers on the work anniversary: the system uses the User's Start Date to know when each milestone hits.
Per leave policy: you can apply it to Vacation, Personal Days, or any leave type that benefits from a tenure-based bump. Sick leave usually doesn't get the treatment.
Stacks cleanly: at year 5, the User keeps the milestones they earned at year 2 and adds the year 5 milestone on top.
How You Define Milestones
Pick a number of years of service.
Pick how many extra days that milestone grants.
Repeat for each milestone you want (2 years, 5 years, 10 years, etc.).
Choose whether the bump is cumulative (most common) or replaces previous milestones.
Why Use It
Recognition without a manual process: tenure is rewarded the day it lands, not when payroll remembers.
Fairness across the team: the same rule applies to everyone with the same Start Date math. No "I think you got an extra day; she didn't."
Less HR overhead: HR sets the rule once instead of editing balances by hand for every anniversary.
What This Means for Each Role
Administrator: turns on Seniority Entitlement, defines the milestones, and decides which leave policies it applies to. Owns the rule.
Approver: doesn't configure it, but seeing it on a User's profile explains why their balance jumped up on an anniversary.
User: sees the bump appear in their balance on the anniversary. If they're curious why, the profile shows the milestone that triggered it.
Common Patterns
Simple stepped tiers: +1 day at year 1, +1 more at year 3, +1 more at year 5.
Bigger milestones, fewer of them: +5 days at year 5, +5 more at year 10.
Hourly teams: the same logic, expressed in hours rather than days when Hourly Leave is in use.
Common Questions
The Automation uses the Start Date on the User's profile. If it's wrong, the milestones land on the wrong dates. Updating the Start Date on the profile is not enough, as the automation won't recalculate the changes. You can on the other hand change the amount on a Users individual profile.
Yes, subject to the Brought Forward Policy on that leave type. If the policy caps carry-over at, say, 5 days, the carry-over still caps at 5 regardless of how generous the Seniority milestones were.
Not through the Automation itself; it applies going forward. For a one-time catch-up, an Admin can adjust the User's quota manually on their profile, and from then on Seniority Entitlement takes over.
Book a Call