Maryland employers may ask new hires for proof of sick leave in two situations: when leave spans more than two consecutive scheduled shifts, and when leave is used between day 107 and day 120 of employment — provided the employee agreed at hire to provide verification.
- Trigger one: leave covering more than two consecutive scheduled shifts (counted as shifts, not calendar days); no prior agreement needed
- Trigger two: leave used between day 107 and day 120 of employment; requires that the employee agreed at time of hire to provide verification under mutually agreeable terms
- Minimum increment for leave use cannot exceed 4 hours
- Rehires returning after a separation of less than 37 weeks must have their earned leave balances reinstated
What the two triggers are
Maryland's paid sick and safe leave law gives your new hires leave they earn over time. Most days, you do not ask for proof. You approve the request and move on. But there are two moments when you may ask the employee to show you something. Those are the two triggers this post covers.
Both triggers come from the Maryland Department of Labor's paid leave FAQ. The first trigger kicks in when the leave spans a long stretch of scheduled shifts. The second trigger kicks in during a specific window early in the job. Both are about documentation.
If you run a small staffing team, these rules touch your onboarding packet, your offer letters, and your day-to-day approvals. You need to know which request is legitimate and which one invites a complaint. The rest of this post walks through each trigger, the paperwork behind them, and the mistakes that get teams in trouble.
Trigger one: leave across more than two consecutive shifts
Your first trigger is a length test. If an employee uses sick and safe leave for more than two consecutive scheduled shifts, you may ask them to provide verification. The Maryland Department of Labor's paid leave FAQ states the rule plainly: "An employer may require verification for use of earned sick and safe leave if the employee (1) used sick and safe leave for more than two consecutive scheduled shifts…"
Read that carefully. The count is of scheduled shifts, not calendar days. Two consecutive weekday callouts in a three-day stretch hit two scheduled shifts. A Thursday callout followed by a Friday callout hits two. The third consecutive scheduled shift is where your right to ask begins.
This matters for staffing teams because many placements run five-day weeks. A new hire who takes Monday through Wednesday off is already past the line. You can request verification. A new hire who takes a single shift off cannot be asked for proof under this trigger.
The word "consecutive" does the work. Two shifts in a row, then a shift worked, resets the count. The employee returns, works a day, and calls out again. That new stretch starts from one.
Also note the leave must be earned. Sick and safe leave accrues over time under the law. A brand-new hire may not have a full balance yet. Asking for verification of leave that has not been earned yet puts you outside the rule.
Who this trigger covers: any employee whose sick and safe leave request spans more than two scheduled shifts in a row.
What you can request: verification for the earned sick and safe leave use. The FAQ does not list which documents count, so ask your labor contact what your team may accept.
Trigger two: the early-employment window
Your second trigger is a calendar window. The law lets you require verification when an employee wants to use leave between the first 107 and 120 calendar days of employment — but only if the employee agreed at the time of hire to provide that verification under mutually agreeable terms. The Maryland Department of Labor's paid leave FAQ spells this out.
Let's unpack the timing. Day 107 through day 120 is a fourteen-day stretch near the end of the employee's first four months. Outside that window, this trigger does not apply. Inside it, you may ask — if, and only if, the employee agreed to the arrangement at hire, under mutually agreeable terms.
That last part is the trap. If your offer letter says nothing about verification, you cannot invoke this trigger later. The agreement has to exist at the time of hire. Retroactive paperwork does not count.
The FAQ also notes a second condition that overlaps: you may require verification if the employee used leave during the 107-to-120 window and the employee and employer agreed to the verification at the time of hire. Same agreement, same timing, same result.
What happens if the employee does not provide it
The FAQ raises the question: what happens if an employee uses earned leave between the first 107 and 120 calendar days of employment, the employer requests verification, and the employee fails to provide the requested documentation?
In practice, your safest path is to ask your Maryland labor contact before you act on a refusal. A misstep here — docking pay, marking unexcused, or terminating — can turn a documentation dispute into a claim. The source does not give you a step-by-step answer, so get one before you need it.
Who this trigger covers: employees between day 107 and day 120 of employment who request sick and safe leave.
What you must have first: an agreement made at hire that the employee will provide verification under mutually agreeable terms.
Comparing the two triggers side by side
Here is the difference in one view.
| Trigger one | Trigger two | |
|---|---|---|
| Test | Leave spans more than two consecutive scheduled shifts | Leave requested between day 107 and day 120 of employment |
| Prior agreement needed? | No | Yes, agreed at time of hire |
| What you may ask for | Verification of the leave reason | Verification of the leave reason |
Both triggers let you ask. The first trigger turns on shift count. The second turns on calendar days and an agreement made at hire.
How leave accrues and what that means for new hires
Sick and safe leave is not a gift on day one. It builds over time. Your new hire's balance builds as they earn leave over time. That shape matters when you set expectations during onboarding.
Two practical consequences follow. First, a new hire who calls out in week one may not have leave to use yet. They may be asking for unpaid time instead. Your approval workflow should distinguish the two. Second, once a balance exists, the employee can spend it. Spending across three shifts in a row is where your verification right begins.
Staffing teams also deal with placement changes. An employee moves from one client site to another. Your accrual records should survive a site change. If your time system resets balances when a placement ends, fix that before it becomes a complaint.
Minimum increment: the four-hour cap
Your team can set a floor on how leave is used. The FAQ says an employer may establish a minimum increment for leave use, but that increment cannot exceed 4 hours. That comes from the Maryland Department of Labor's paid leave FAQ.
What this means on the floor: if an employee wants to leave two hours early for a doctor's visit, you can require they take a four-hour block instead. What it means: you cannot set a six-hour or full-shift floor. Four hours is the ceiling on any minimum increment.
Set this rule in your handbook once. Apply it everywhere. Mixed increments across teams is how you end up with inconsistent approvals and an angry employee who talked to a coworker.
Counting employees: the threshold question
The paid leave law applies to employers that meet the 15 employee threshold. The FAQ notes that seasonal employees are included in determining whether an employer has met the 15 employee threshold.
For staffing teams, this matters more than it looks. Your placement count, your bench, and your seasonal hires all roll up. Counting matters at the moment you ask whether the law applies.
If you are near the line, ask your labor contact how to count. The FAQ gives the inclusion rule for seasonal workers. It does not give the full counting method. Get that answer in writing before you design your policy.
Rehires and leave balances
Staffing teams see rehires constantly. The FAQ addresses one case directly: if an employee is separated for less than 37 weeks and returns to work for the employer, the employer has to reinstate any earned but unused sick and safe leave, whether paid or unpaid.
The practical read: when someone leaves your payroll and comes back within that window, their old balance comes back with them. Your system should store balances, not wipe them at separation.
This rule interacts with your verification triggers. The shift-length trigger still applies.
Building the onboarding packet
Your paperwork is where both triggers either work or fail. The second trigger depends entirely on what the employee agreed to at hire. Here is what your packet needs to include.
A verification agreement clause. If you want the right to ask for proof during days 107 through 120, the employee has to agree to it at hire. Put the clause in the offer letter or the acknowledgment form. Describe the terms as mutually agreeable. Leave room for the employee to raise concerns before signing.
A statement of the minimum increment. If you use a four-hour floor, say so in the handbook the employee receives on day one. Do not announce it later.
A clear accrual explanation. Tell the employee how leave builds. Do not promise a balance the law has not created yet.
A rehire note in your own records. Flag anyone separated for less than 37 weeks so their balance can be reinstated on return.
If your packet is a stack of generic forms with no Maryland clause, fix that before your next start date.
Common mistakes
Small teams get these four wrong most often.
Asking for proof too early. The shift-length trigger needs more than two consecutive scheduled shifts. A single sick day does not qualify. Asking anyway reads as suspicion.
Asking for proof without a signed agreement. The early-window trigger needs a hire-time agreement. No agreement made at hire, no right to ask under the early-window trigger. This is the mistake that generates complaints.
Setting an increment above four hours. The cap is 4 hours. A full-shift floor breaks the rule.
Wiping balances on separation. A rehire within the separation window brings the balance back. Wiping it in your system and refusing to restore it creates a violation.
Each of these is preventable with one policy pass and one system check.
A checklist before your next hire
Run this list before your next Maryland start date.
- Verify your headcount method and include seasonal employees in the count.
- Add the verification clause to your offer letter or acknowledgment form.
- Write the minimum increment into the handbook, at or under four hours.
- Train approvers on the more-than-two consecutive scheduled shifts test.
- Confirm your time system stores balances across separations under 37 weeks.
- Identify the day 107-to-day 120 window in your onboarding tracker.
- Ask your labor contact what verification documents are acceptable.
- Ask your labor contact what to do when an employee does not provide requested verification inside the window.
The first six you can do today. The last two are conversations. Both matter.
Related guides
- Interview Scorecard Example for Consistent Hiring Teams
- Hiring Decision Debrief: Notes to a Recorded Decision
- Conviction timing rules for 3 jurisdictions
FAQ
Do I need a signed agreement for both triggers? No. The shift-length trigger does not require one. Only the early-window trigger between day 107 and day 120 needs an agreement made at the time of hire.
Can I ask for proof on a single sick day? Not on the shift-length trigger alone — that one starts after more than two consecutive scheduled shifts. But a single sick day can be grounds for verification if it falls between day 107 and day 120 and the employee agreed at hire to provide verification. One shift off does not meet the test.
Does the four-hour minimum apply to every leave request? You may set a minimum increment, and it cannot exceed 4 hours. It applies to how the employee uses leave. It is not a rule that leave must be four hours.
What if my employee refuses to provide verification during the window? The FAQ raises the question but does not give a step-by-step answer. Ask your Maryland labor contact before you act on the refusal.
Does a rehire bring back old leave? If the employee was separated for less than 37 weeks and returns, yes. The employer has to reinstate the earned but unused sick and safe leave, whether paid or unpaid.
Does the headcount test include seasonal workers? Yes. Seasonal employees are included in determining whether an employer has met the 15 employee threshold.
Do these rules apply to a placement at a client site? Your team's obligations travel with the employee across placements. Keep accrual records tied to the employment relationship, not the site.
These two triggers sit inside a larger Maryland paid leave framework. The details in this post come from the Maryland Department of Labor's paid leave FAQ. Open questions remain that the source does not answer, including which documents count as acceptable verification, the full seasonal counting method, and the steps when verification is not provided inside the early window. Ask your Maryland labor contact for both before you need them.