HR Notification Use Cases Across the Employee Lifecycle

Last updated: July 2026

What follows runs in lifecycle order, from before someone's first day to after their last. Nearly every notification in it has a manager-facing mirror, and that mirror is where HR products create most of their noise, so 2.10 handles it separately. Channels come in chapter 3.

2.1 Hiring and pre-boarding notifications

The defining constraint: there is no work email yet. Everything in this stage has to reach a personal address, and half of it is time-sensitive enough that a missed message delays a start date.

• Offer sent, offer viewed, offer accepted or declined
• Background check initiated, action needed, cleared
• Document requests and e-signature reminders (contract, tax forms, right-to-work)
• Equipment shipping and delivery confirmation
• Day-one logistics: where to go, when, who to ask for
• Manager and buddy introductions
• Visa, permit, and relocation milestones for international hires

The e-signature chase is the highest-value automation here, because an unsigned contract blocks everything downstream and the person chasing it is usually doing it by hand. A global employer-of-record platform running onboarding across 180 or more countries has the hardest version of this: the document set, the legal deadline, and the language all vary per hire inside a single customer.

2.2 Employee onboarding notifications

The defining constraint: the recipient doesn't know your product yet, and they're overloaded. Onboarding is where notification volume peaks and tolerance is lowest.

• Task checklist assigned, task due, task overdue
• Mandatory training and policy acknowledgement deadlines
• Benefits election window for new hires, with a hard deadline
• Probation checkpoints and 30, 60, 90 day check-ins
• Payroll setup confirmation and first payslip
• Manager-side prompts: your new hire hasn't finished X, their first 1:1 isn't booked

The pattern that works is one digest with everything outstanding, sent on a cadence, rather than a message per task. Twelve separate task notifications on day one is how you get an employee who ignores your product for their entire tenure.

2.3 Performance review and goal notifications

The defining constraint: cycles are deadline-driven, cascading, and bursty. Every manager in a customer's org hits the same deadline in the same hour, and each stage of the cycle gates the next.

• Cycle opened, self-review assigned, self-review due
• Peer and 360 nomination requests, nominations approved, peer feedback due
• Manager review due, manager review submitted
• Calibration session scheduled and prep required
• Cycle closing, cycle closed, results released
• Goal and OKR check-in prompts, goal at risk, goal overdue
• 1:1 agenda prep, action items outstanding from the last 1:1
• Weekly update prompts and continuous feedback delivery

Lattice runs this pattern across six channels from a single template library, which is roughly the shape it takes once you're past the first few customers: the events are stable, and the channels and timing are per-tenant.

Reviews and goals also produce the sharpest fan-out in HR. "Self-review submitted" is a confirmation for the employee, a to-do for the manager, a progress tick for the HR admin, and a data point in a completion dashboard. Sending all four every time is how a review cycle generates thousands of messages nobody reads.

2.4 Engagement survey notifications

The defining constraint: anonymity. You have to reach the people who haven't responded without revealing who has, which makes this the most technically interesting notification problem in HR tech. Section 4.2 covers the mechanism.

• Survey opened, invitation sent
• Non-responder reminders, usually two or three across the window
• Survey closing soon, survey closed
• Results published, to employees and to managers separately
• Action plan assigned, action plan step due, action plan overdue
• Anonymous comment received a reply, for platforms supporting two-way anonymous threads

Anonymous two-way threads invert the usual model: the platform has to deliver a reply to a specific person while neither party can identify the other, and the notification itself must not leak identity through timing, sender, or preview text.

Survey notifications also scale faster than teams expect, because volume is a product of headcount and cadence at once. Workleap's Officevibe went from sending dozens of surveys a month to over two million messages, which is the trajectory any pulse-survey product is on the moment its customers move from annual to weekly.

2.5 Recognition and rewards notifications

The defining constraint: recognition is social fan-out, and the audience is a per-tenant setting. One kudos can become a notification for the recipient, their manager, a whole Slack channel, and a company feed. It can also become a privacy problem if a customer expected recognition to be private and your default is public.

• Recognition received, recognition given confirmation
• Recognition posted to a public channel or company feed
• Manager and skip-level visibility of recognition for their team
• Nomination requests, nomination deadlines, award results
• Birthdays and work anniversaries
• Service award milestones, with a reward attached
• Points balance, points expiring, reward redeemed, reward shipped
• Wellness or challenge program updates

Milestone automation is the underrated piece. Birthdays and anniversaries are calendar-derived, high-volume, and delightful when they work, and they're also the notifications most likely to fire for someone who left last week if your event source and your employment status ever drift apart.

2.6 Compensation and payroll notifications

The defining constraint: sensitivity. Never put the figure in the notification. Section 4.3 covers why in detail.

• Comp cycle opened for managers, budget and guidelines available
• Recommendation due, recommendation submitted
• Approval chain steps: submitted to skip-level, approved, sent back with comments
• Comp letter ready, comp change effective
• Payslip available, pay date reminder
• Bonus, commission, and equity events (vesting, grants, exercise windows)
• Off-cycle adjustments and corrections

Payroll notifications also carry the highest expectations of reliability in the whole category. People forgive a late review reminder. They don't forgive anything that looks like a problem with their pay, which means this event class needs delivery guarantees and an audit trail more than it needs polish.

2.7 Time off, leave, and approval notifications

The defining constraint: the approver is a person who might be unavailable. Every approval notification needs an answer to "what happens when this sits unread for a week."

• Request submitted, request approved, request declined with a reason
• Approver reminder, then escalation to a skip-level or delegate
• Delegation active while an approver is on leave
• Timesheet due, timesheet missing, timesheet approved
• Expense submitted, approved, reimbursed
• Accrual balance updates, use-it-or-lose-it warnings
• Return-to-work reminders and leave milestone check-ins
• Parental and extended leave: handover, keep-in-touch, planned return

Approvals are the one place in HR where the person you're notifying is blocking somebody else. A time-off request sitting unread is a holiday another person can't book, and a timesheet nobody approved is pay that doesn't run. That justifies escalation on a timescale that would feel aggressive anywhere else in this chapter.

2.8 Learning and compliance notifications

The defining constraint: someone is going to audit this. Compliance notifications need proof of delivery, not only delivery.

• Course assigned, course due, course overdue
• Certification or license expiring, then expired
• Mandatory annual training windows
• Policy updated, re-acknowledgement required
• Manager and admin views of who's outstanding ahead of an audit

Credential expiry is the pattern worth building carefully, because it's a scheduled series rather than an event: notify at 90 days, 30 days, 7 days, on the day, and then escalate. A healthcare staffing marketplace has the acute version of this, where an expired credential doesn't only fail an audit, it stops someone from being able to work a shift.

2.9 Offboarding notifications

The defining constraint: the work email is gone, and some of this is statutory. This is the highest-stakes channel fallback in an HR product.

• Resignation or termination workflow initiated, steps assigned
• Last-day checklist, equipment return instructions and reminders
• Access revocation confirmations to IT and the manager
• Final pay details and timing
• Benefits continuation notice (COBRA in the US), which carries a legal deadline
• Retirement account and equity deadlines, which often outlive employment by months
• Exit survey invitation
• Alumni and rehire communications

Two failure modes to design against. The first is a notice that bounces because it went to a disabled work address, which for a statutory notice is a compliance problem and not only a bad experience. The second is a review cycle reminder landing on someone who was terminated last week, which happens whenever your notification pipeline reads a cached employee list instead of live employment status.

2.10 Manager and HR admin notifications

Every section above has a mirror here, and this is where HR products earn their reputation for noise. A manager with eight reports in a review cycle can generate a hundred individually reasonable notifications.

• Your report hasn't completed X
• Your approval is waiting, and now it's overdue
• Your team's survey participation is below threshold
• An engagement risk was flagged on your team
• Cycle completion status for your org
• Exception reports: who's blocked, who's overdue, who's at risk
• Executive rollups, which should be exception-only or scheduled, never event-driven

The rule that fixes most of it: employees get events, managers get digests, admins get exceptions, executives get schedules. Managers almost never need to know the moment something happened. They need to know, once a day or once a week, what's outstanding and what they have to do about it.

Frequently asked questions

What notifications should an HR platform send?

At minimum: onboarding task reminders, performance review cycle deadlines, engagement survey invitations and reminders, approval requests with escalation, pay and compensation events, compliance and credential deadlines, and offboarding notices. Each of those also needs a manager-facing digest and an admin-facing exception view, which is usually the part that gets built last and matters most for adoption.

How many reminders should you send before a deadline?

Three is the common pattern for a multi-week window: one at the open, one at the midpoint, and one shortly before the deadline, then an escalation to the manager rather than a fourth reminder to the employee. More reminders to the same person produce diminishing returns quickly, while a single escalation changes who's responsible.

How do you notify a new hire before their first day?

Send to a personal email address collected during hiring, and treat that address as a first-class field on the profile rather than a temporary value. Pre-boarding notifications also need to be self-contained, because the recipient has no access to your product, no SSO, and no work account to authenticate with.

What happens to notifications when an employee leaves?

Discretionary notifications should stop immediately on termination, and statutory notices have to keep working through a personal channel after the work account is disabled. Getting the first part wrong sends review reminders to former employees. Getting the second part wrong means a legally required notice never arrives.