For an eligible employee's birth or placement, log three dates in the leave and pay file: event day, window expiry, and pay-change effective date. Write each one on the day you learn it, in the same block, in the same order.
Key takeaways
- Birth or placement date. The event day itself, not the announcement or paperwork date. It starts the twelve-month leave window.
- Window expiry. The day before the anniversary of the event date (for example, June 3, 2024 → June 2, 2025). Compute it as soon as the event date is known.
- Pay-change effective date. The day a new rate, classification, or scheduled hours take effect — what payroll codes to, not the approval date.
- One block, one file. Keep all three dates together in the leave and pay file, in consistent order, with the source document named next to the event date.
- Re-read quarterly. Confirm the event date matches the document, the expiry hasn't passed, and payroll is running on the current pay-change date.
Why three dates, not a folder full of paperwork
You set up a new hire's file. You collect the tax forms, the direct deposit slip, the signed handbook. Then the leave question shows up later, and the file has no date to answer it. That is where records go wrong.
Three dates solve most of it. One date starts a leave window. One date closes it. One date moves the pay. Write all three in the same place, and the file answers its own questions six months from now.
This post walks through each date: what it is, where it comes from, when you write it, and what breaks if you do not.
Date one: the day of birth or placement
The first date is the day the event happens. For a birth, that is the day the baby is born. For an adoption or foster placement, it is the day the child is placed with the family.
This date matters because it is the anchor. Under the federal Family and Medical Leave Act, the twelve-month window for a covered, eligible employee runs from this day. Everything else in the file counts from it.
The Office of Personnel Management's fact sheet gives a clean example: an employee's spouse has a baby on June 3, 2024. That single line sets the whole timeline. Nothing before that day starts the clock. The placement or birth day is day zero.
Two mistakes happen here. The first is writing the date you heard about the event instead of the event date itself. A manager says "congrats, the baby came last weekend." Ask for the actual date. The second mistake is using the due date, the court hearing date, or the placement paperwork signing date. Only the birth or placement day counts.
When do you write it? The day the employee tells you, ideally with a document attached. Birth certificate, placement letter, foster care notice. You need the date written down, and you need to be able to show where it came from if anyone audits the file later.
If the employee and a partner take the child in together, both share the same placement date. The fact sheet's second example: an employee and the employee's partner have a child placed with them for adoption on January 4, 2024. One date, one clock.
Write the date in plain format in the leave section of the file. Not in a note. Not in an email subject line. In the leave record itself, where payroll and HR both look.
Date two: the end of the twelve-month window
The second date is the expiry. For birth or placement leave, entitlement ends at the close of a twelve-month period that begins on the birth or placement day.
The OPM example shows how the counting works. Baby arrives June 3, 2024. The expiration date for use of FMLA for birth and care of the child is June 2, 2025. The window runs up to, but not through, the same calendar day one year later.
That is the rule you write into the file: the day before the anniversary of the birth or placement.
Here is the exact wording from the fact sheet, because the wording carries the rule: "The statute provides that entitlement to FMLA leave for birth or placement purposes expires at the end of the 12-month period beginning on the date of the birth or placement."
So when the employee asks "when do I have to use my leave by?", you look at the file and read the date. You do not re-count from today. You do not count from the return-to-work date. You count from the birth or placement day.
Why this date belongs in the file on day one rather than when the leave starts. Because the employee may not take leave right away. The fact sheet notes that the 12 weeks of paid parental leave may be used only on or after the birth or placement date for adoption or foster care. Some employees front-load. Some spread it out. Some use a few days now and the rest later. The expiry date tells you and them how much runway is left.
Miss this date and two things go wrong. An employee takes leave after the window closed, and payroll pays it as if it were still protected. Or an employee is told they have more time than they do, they plan around it, and the firm has to reverse the decision mid-year.
Use this format in the file: Event date: June 3, 2024. Window ends: June 2, 2025. Two lines, same block, no ambiguity.
| Event | Event date | Window ends |
|---|---|---|
| Spouse gives birth | June 3, 2024 | June 2, 2025 |
The same counting applies to a placement. For the child placed for adoption on January 4, 2024, take the day before the anniversary of that date. If you want the firm's own written confirmation of the computed date before you lock it into the file, ask your HR lead or your employment counsel to sign off on your counting method once, then use it consistently.
Date three: the day the pay rate changes
The third date is a pay date, not a leave date. It is the day a new hire's rate, classification, or scheduled hours change. On that day, payroll needs a new instruction, and the file needs a record that the instruction was given.
California's minimum wage page shows why this date has its own life. The state's schedule moves on its own: the Governor can no longer pause a scheduled increase, and the first adjusted increases may come faster if the adjusted CPI-W topped seven percent in that first year. Rates move whether or not your file is ready.
That is the state-level picture. Your firm's picture is simpler. A new hire starts at one rate. Three months in, they finish probation or the market shifts, and the rate changes. If the file has no date for the change, payroll either pays the old rate too long or the new rate too early. Both are problems you have to unwind. For the first pay run, see new hire pay checks before the first paycheck.
What to record: the effective date of the change, the new rate or schedule, and who approved it. Same block of the file as the leave dates, so one look at the file gives you the full picture of what this person earns and what leave they can draw, and when.
Write the effective date, not the approval date. Approvals can slip a week. The rate applies from the effective date, and that is what payroll codes to. If approval lands after the effective date, that is a conversation for your manager, not a reason to shift the date in the file.
Do the same when hours change. A move from full-time to part-time, or the reverse, changes pay, and may change leave accrual under your firm's policy. One date in the file covers both. If you leave it to memory, one side of the change gets updated and the other does not, and the mismatch shows up on the next pay run.
The three dates together: the event day starts the leave window, the day before the anniversary ends it, and the effective day of any pay change moves the money. Do not batch them. Files that get updated in batches are the files that miss a date.
What goes wrong when a date is missing
A missing birth or placement date means you cannot compute the expiry. You go back to the employee, who may not remember the exact day, and the longer the gap, the fuzzier the answer. A document fixes it, but you should not be hunting for a document at the moment payroll needs an answer.
A wrong expiry date causes the opposite failure. The employee is told they have until a date that is too far out. They plan a longer absence. The firm discovers the error after the leave has been taken. At that point you are having a difficult conversation with someone who has already made decisions based on your number.
A missing pay-change date causes payroll to guess. Payroll should never guess. The file exists so that nobody has to. The effective date is the instruction payroll follows, and it is the date an auditor will look for if they compare what was paid to what was approved.
All three failures share one cause: the date lived somewhere other than the leave and pay file. An email thread, a manager's calendar, a spreadsheet on someone's desktop. Move it into the file the day you learn it and the failure mode disappears.
Setting up the file: a working order
You are about to open a new hire's file. Here is the order that keeps the dates from getting lost. For a fuller handoff, see the family leave handoff worksheet.
Before day one. Record the planned start date as the pay record's baseline. This is not one of the three dates, but it is the reference point the pay-change date will later be measured against. If the start date shifts, update it before the first pay run.
On the day you learn the event date. Write the birth or placement date. Attach whatever document confirms it. Then compute the expiry, day before the anniversary, and write that on the next line. Both lines together, in the leave section.
On the day a rate or schedule change is approved. Write the effective date, the new figure, and the approver. Keep this in the same block as the leave dates, next to the original rate, so the history reads in order.
At each quarterly file review. Re-read the three dates. Confirm the event date matches the attached document. Confirm the expiry has not already passed. Confirm the most recent pay-change date is the one payroll is running on.
That last check is the one people skip. Files are written once and never re-read. A two-minute re-read each quarter catches the drift before it becomes a correction.
Common mistakes, and the fix for each
Using the announcement date instead of the event date. The employee tells you on Monday that the birth happened on Sunday. Sunday is the date. Always the event, never the announcement.
Counting the window from the return-to-work date. The window starts on the event date. Full stop. If the employee takes three weeks of leave first, the remaining balance still expires on the day-before-anniversary date. Starting the count later gives the employee time the rule does not give them.
Recording the approval date for a pay change instead of the effective date. The approval is a record of who said yes. The effective date is what payroll codes. Put both in the file if you like, but the effective date must be the one that sits in the pay record.
Leaving the expiry blank until leave actually starts. The expiry exists the moment the event date exists. Write it as soon as the event date is known. By the time leave starts, the file should already answer the question.
Scattering the dates across systems. One system holds the leave dates, another holds the pay rate, a third holds the manager's notes. Pick the leave and pay file as the home for all three, and treat the other systems as copies.
Filing conventions that survive an audit
Keep the three dates in one block, labelled, in a consistent order: event, expiry, effective pay change. Consistent order matters more than you think. An auditor opening forty files should not have to hunt.
Use the same date format across every file in the firm. Mixed formats are how June 3 becomes March 6 in someone's reading.
Record the source next to the event date: a short note naming the document you saw. You are storing the trail that says the date is not made up. For the wider records rules, see record retention rules for hiring and payroll files.
Do not overwrite a date. If a correction is needed, strike through, write the corrected date, initial and date the correction. Overwriting destroys the trail, and the trail is what protects you.
Keep the approver's name with every pay-change date. A rate that changed without a named approver is a rate that will be questioned later.
Illustrative example: one file, three dates
Take one new hire whose child is born on June 3, 2024. On the day the employee tells you, the leave section gets two lines: Event date: June 3, 2024, and Window ends: June 2, 2025. Your manager approves a rate change on June 5, 2024, effective July 1, 2024. The pay record shows July 1, 2024 as the change date, with the approval date beside it. At the first quarterly review, you confirm the birth certificate still matches June 3, 2024, the window has not closed, and payroll is running on the July 1 rate.
Quick reference for the three dates
The three dates in short, for the top of your file:
- Birth or placement date. The event day. Starts the twelve-month window. Record it the day you learn it, with the confirming document named.
- Window expiry. The day before the anniversary of the event date. Ends entitlement for birth or placement leave.
- Pay-change effective date. The day a new rate or schedule takes effect. What payroll codes. Record it with the new figure and the approver.
One file. Three dates. Each written on the day you learn it, in the same block, in the same order. That is the whole method.
Your next step today: Open one current leave and pay file and check that the event date, the window expiry and the pay-change effective date sit together in one block. If any of the three is missing, fix that file before the next pay run.
Related guides: EEOC ADA guidance: 3 dates and your own check date · I-9 name mismatch: 4 steps for a new hire's document · New hire benefits: 5 IRS rules and examples.
Frequently asked questions
Do I log these dates for every new hire?
No: the birth or placement dates apply only when an eligible employee has a birth or placement, while the pay-change date applies whenever a rate, classification or scheduled hours change.
When should I compute the window expiry?
Compute it as soon as the event date is known, since it is the day before the anniversary of that date.
Which date does payroll follow?
Payroll follows the pay-change effective date, not the approval date.