Paid Leave Laws in DC, MD, and VA: A Multi-State Operator's Cheat Sheet

Paid leave compliance is the second-most-common audit finding we see in DMV restaurant operations — second only to tip-credit documentation gaps. The three jurisdictions in the region operate on fundamentally different paid leave statutes, and the operator running locations in all three has to maintain three parallel accrual systems with three different rule sets.

This post is the operating reference for DC, Maryland, and Virginia paid leave as of the most recent legislative cycle. It is not legal advice. It is the documentation framework we install when starting a compliance engagement for a multi-state DMV group.

The unifying principle

Every DMV jurisdiction now has some form of mandatory paid leave. The structural elements that vary are:

• The accrual rate (hours of leave per hour worked)
• The accrual cap (maximum balance an employee can carry)
• The annual usage cap (maximum hours that can be used in a single year)
• The waiting period before new hires can use accrued leave
• The qualifying reasons for leave use
• The carryover rules (year-end behavior of unused balance)
• The pay rate during leave (usually regular rate, but with tipped-employee nuances)
• The notice and documentation requirements (what the employee must provide; what the employer must record)
• The retaliation prohibitions and remedies

Each jurisdiction sets each element. There is no overlap and there is no shortcut. The multi-state operator has to build three accrual rules into the payroll system, or accept the noise of running the most generous of the three for the entire group.

District of Columbia — Accrued Sick and Safe Leave Act (ASSLA)

DC's ASSLA covers all employers and applies to every employee working in DC, regardless of where the employer is headquartered.

Accrual rate: For restaurants with 100+ employees, 1 hour of paid leave for every 37 hours worked, capped at 7 days per year. For 25–99 employees, 1 hour for every 43 hours worked, capped at 5 days per year. For fewer than 25 employees, 1 hour for every 87 hours worked, capped at 3 days per year. The restaurant industry typically falls into one of the lower-accrual tiers for an independent operator.

Accrual cap: Equal to the annual usage cap above (operators may set a higher cap voluntarily).

Waiting period: 90 days from date of hire before accrued leave may be used.

Qualifying reasons:

• Employee's own physical or mental illness or injury
• Care for a family member
• Reasons related to domestic violence, sexual assault, or stalking ("safe leave")
• Preventive medical care

Carryover: Unused balance carries forward into the next year, subject to the accrual cap.

Pay rate: The employee's regular hourly rate. For tipped employees in DC under Initiative 82 (the standard minimum wage equals tipped minimum wage now), this is the full DC minimum wage rate.

Notice and documentation:

• The employer must provide written notice of ASSLA rights at hire and post a notice in the workplace
• Pay stubs must show accrued leave balance, hours used during the pay period, and hours remaining
• Employees can be required to provide reasonable notice before using leave when foreseeable
• For absences of three or more consecutive days, the employer can require reasonable documentation

Recordkeeping: Records of hours worked, leave accrued, leave used, and current balance must be retained for three years.

Posting: The DC ASSLA notice (available in multiple languages from the DC Department of Employment Services) must be posted in a conspicuous workplace location.

Maryland — Healthy Working Families Act (HWFA), aka "Maryland Earned Sick and Safe Leave"

Maryland's HWFA covers employers with 15+ employees for paid leave; smaller employers must provide unpaid leave under the same accrual structure.

Accrual rate: 1 hour of leave for every 30 hours worked, capped at 40 hours per year.

Accrual cap: 64 hours maximum balance at any time.

Waiting period: 106 days from date of hire before accrued leave may be used.

Qualifying reasons:

• Employee's own physical or mental illness or injury
• Care for a family member
• Maternity or paternity leave (when not otherwise covered)
• Reasons related to domestic violence, sexual assault, or stalking
• Preventive medical care

Carryover: Up to 40 hours of unused balance carries forward into the next year. Employers may "front-load" 40 hours at the start of the year and avoid the carryover requirement.

Pay rate: The employee's regular hourly rate, calculated for tipped employees as the full Maryland minimum wage (not the tipped sub-minimum). This is the trap most operators miss — leave for tipped employees is paid at full minimum wage, not the tipped wage.

Notice and documentation: Pay stubs must show accrued leave balance and hours used in each pay period. Employees may be required to provide notice for foreseeable absences.

Recordkeeping: Records must be retained for three years.

Montgomery County: Note that Montgomery County has its own additional Earned Sick and Safe Leave Law, which in some elements is more generous than the state law. The county law applies in addition to the state law, and the more generous provision controls.

Virginia — Virginia Overtime Wage Act + limited paid leave

Virginia is the lightest-touch jurisdiction in the DMV. There is no general statewide paid leave mandate for private employers as of the most recent legislative cycle. However, Virginia does have:

• Public Health Emergency Leave (where applicable): During a declared public health emergency, employers must provide up to 80 hours of paid leave for COVID-19-related absences. This is dormant in non-emergency periods but can activate.
• Domestic Workers' Sick Leave: Effective for domestic workers, not restaurant staff.
• Localities: Some Virginia localities (notably Arlington and Alexandria) have considered or implemented additional protections; check the locality of each location.

For most Virginia restaurant operations, the practical answer is that there is no state-level paid sick leave accrual obligation. However, three caveats apply:

1. If your group is a federal contractor (including catering to federal facilities), federal contractor sick leave rules (Executive Order 13706) apply: 1 hour for every 30 hours worked, capped at 56 hours per year.
2. If you have an employee handbook that promises paid leave, the handbook can create a contractual obligation enforceable in Virginia courts even without a statutory mandate.
3. If you have an employee who normally works in DC or Maryland but occasionally works in Virginia, the hours worked in their home state continue to accrue under that state's law. The Virginia work hours typically do not generate accrual.

The cleanest Virginia posture is: clear written policy on what leave the operation provides, applied consistently across the workforce, with documented accrual and usage records.

The cross-jurisdiction problem

Operators running locations in two or three DMV jurisdictions face three structural challenges.

Challenge 1: Employees who work in multiple jurisdictions

A server who occasionally picks up shifts at a sister location across the state line generates accrual under each jurisdiction's law for the hours worked in that jurisdiction. The payroll system must track hours by location, not just by employee.

For most operators, the cleanest answer is to not schedule employees across state lines. The compliance cost of getting cross-jurisdiction accrual right is high; the operational benefit is usually low.

Challenge 2: Uniform policy versus jurisdiction-specific policy

Some operators choose to apply the most generous jurisdiction's policy across the entire group, simplifying administration. This is permitted everywhere — you can always offer more than the law requires. The cost is higher leave expense; the benefit is simpler administration and (often) better employee retention.

Other operators apply each jurisdiction's specific rules to each location. This minimizes leave expense but requires three accrual rules in the payroll system and creates internal pay-equity tensions when employees compare.

There is no universally right answer. The right answer depends on the group's size, the payroll system's capabilities, and the operator's view on retention versus cost.

Challenge 3: Pay rate for tipped employees

This is the highest-frequency trap. In Maryland (and other tip-credit jurisdictions), leave for tipped employees is paid at full minimum wage, not the tipped sub-minimum. Payroll systems default to the employee's "regular rate" which, for a tipped server, is often the sub-minimum direct wage. Using the direct wage as the leave pay rate is a violation.

The fix is a payroll configuration change. For every tipped employee, the leave-pay rate is set to the applicable jurisdiction's full minimum wage, not the direct tipped wage.

The leave-pay rate for tipped employees in Maryland is the single most-missed compliance item we find. The total exposure is usually small per employee — a few dollars per leave hour — but it accumulates across hundreds of leave hours per year per location.

The documentation discipline

Whatever the jurisdiction, the documentation requirements share a structure. For every leave event, the file should include:

• Date and amount of accrual (typically by pay period)
• Date and amount of usage
• Reason for use (recorded, not necessarily disclosed in detail — privacy protections apply)
• Pay period in which the use was paid out
• Pay rate applied to the leave hours
• Documentation requested or received (if any) for absences of three or more days

These records must be retained for three years (DC, MD) and producible by employee, by pay period, on demand. The records that cannot be produced are presumed against the employer in any dispute.

The pay stub disclosure is the documentation employees actually see. Every pay stub for every employee in DC and Maryland must show: accrued balance, hours used in the period, and current balance. Pay stubs that omit any of these fields are themselves a finding.

Common audit triggers

Paid leave audits in DMV jurisdictions are triggered by:

1. Employee complaint: Most commonly, a former employee who was denied a leave request or who believes their final paycheck did not include all accrued leave.
2. Wage-hour audit: A wage audit (often triggered by a tip-credit complaint) frequently expands to cover paid leave compliance.
3. Termination disputes: At separation, some jurisdictions require payout of unused leave; others do not. Disputes over termination payouts often trigger formal audits.

The first trigger is by far the most common. The second is the most expansive. The third is the most expensive because the dispute is often already in active litigation by the time the audit opens.

The 90-day setup

For a multi-state DMV operator who has not formally addressed paid leave compliance, the 90-day setup looks like this:

Days 1–30: Audit current state

• Map current accrual rules per jurisdiction (or lack thereof)
• Pull a sample of pay stubs and verify required disclosures appear
• Pull leave records for the last 12 months and identify documentation gaps
• Identify any tipped-employee leave events paid at the wrong rate

Days 31–60: Configure payroll

• Set accrual rules in payroll system per jurisdiction
• Configure pay rate for leave use, especially for tipped employees
• Configure pay stub disclosures
• Build the file structure for leave-event documentation

Days 61–90: Train and roll out

• Train managers on accrual and usage procedures
• Update the employee handbook with the jurisdiction-specific policies
• Communicate to staff the policies that apply to their location
• Begin the quarterly internal audit cadence

Quarterly internal audit

Each quarter, pull 20% of the leave-event records (rotating so every event is audited annually) and check:

• Accrual rate applied correctly for the jurisdiction
• Pay rate during leave correct, especially for tipped staff
• Documentation on file for events requiring it
• Pay stub for the affected period shows the required disclosures
• Carryover or year-end handling correct

The findings from each quarter produce a one-page memo, dated and signed. Same discipline as I-9 audit (see I-9 and E-Verify compliance).

What it costs

For a 3-location DMV operator with locations in two or three different jurisdictions, the setup cost for paid leave compliance is modest:

• Payroll system configuration: 4–8 hours of qualified time
• Handbook update: 2–4 hours
• Training: 4–6 hours
• Quarterly audit going forward: 2–3 hours per quarter

The biggest cost is not the setup. It is the back-paid leave for tipped employees who were paid leave at the wrong rate for years. That liability is typically $300–$1,200 per affected employee per year of error.

If you operate in more than one DMV jurisdiction and want a structured read on your current paid leave posture, book a discovery call. Bring a sample pay stub from each jurisdiction and a recent leave-event record. We will walk through the gaps on the call and tell you which to close first.

Paid leave law in the DMV is not going to converge. Multi-state operators who treat it as a one-time setup get expensive surprises. Operators who treat it as a quarterly discipline keep the exposure off the P&L permanently.