The Aland Etienne Act creates tiered wage requirements, a six-year audit trail with a presumption of non-compliance, and triple damages for underpayment, for more than 60,000 guards. Five scheduling system changes nobody is talking about.
This article is for general information and is not legal advice. Confirm obligations with qualified counsel.
The Aland Etienne Safety and Security Act (NYC Local Law 061 of 2026) takes effect on July 28, 2026, requiring every private security employer in New York City to match city-contract wage rates for more than 60,000 guards. The law creates tiered wage requirements, a six-year audit trail with a presumption of non-compliance for missing records, and triple damages for underpayment, making it the first private-sector wage law NYC has passed since 1964.
What does NYC's Security Guard Wage Law require?
The Aland Etienne Act establishes tiered minimum wage, paid time off, and supplemental benefit standards for all private security guards in New York City, phased in over three years starting July 28, 2026. The law is named for Aland Etienne, a 46-year-old security officer and 32BJ SEIU member killed while protecting others during the July 2025 mass shooting at 345 Park Avenue.
Here's the compliance timeline every security employer needs to track:
| Date | What takes effect |
|---|---|
| July 28, 2026 | Law effective, Notice of Rights must reach all existing guards within 30 days (in English and their primary language) |
| January 1, 2027 | Wage requirements begin, employers must match city-contract rates |
| January 1, 2028 | Paid time off, vacation and holiday benefits must match city standard |
| January 1, 2029 | Full supplemental benefits, health, retirement, and disability coverage must match |
The wage benchmarks security employers must meet, based on current prevailing wage schedules:
| Guard classification | Hourly wage | Supplemental benefits |
|---|---|---|
| Unarmed, entry-level (0-2 years) | $18.02 | $8.12/hour |
| Unarmed, experienced (2+ years) | $21.20 | $8.47/hour |
| Armed | $32.70 | TBD |
The law covers every private security employer in NYC with contracts exceeding $1,500. Office towers, retail complexes, residential buildings, and corporate campuses are all in scope. Only federal, state, and city government entities are exempt.
What scheduling system changes does the NYC guard wage law require?
The Aland Etienne Act creates five discrete compliance requirements that most security scheduling systems weren't designed to handle.
1. Rate-tier calculation per guard, per shift
The law creates a tiered wage structure based on both seniority and armed status. An unarmed guard with 18 months of experience earns $18.02 per hour. The same guard six months later, now past the two-year threshold, earns $21.20, while an armed guard at the same site earns $32.70.
Your system needs to assign the correct rate to every shift automatically based on each guard's current classification, because manual rate assignment across hundreds of guards and dozens of sites is where underpayment errors happen: and where triple damages start.
2. Supplemental benefits tracking
Employers owe $8.47 per hour in supplemental benefits for experienced guards starting January 2029. The law gives employers flexibility in delivery: health insurance, a cash equivalent, or a combination. That flexibility creates a tracking problem most scheduling and payroll systems aren't designed for.
3. Six-year audit trail, with a presumption of non-compliance
Every wage paid, hour worked, benefit provided, and contract detail must be documented and retrievable for six years. If investigators request your records and you can't produce them, the law presumes you violated it: shifting the burden of proof entirely to the employer.
"Missing records become an automatic legal liability under the presumption-of-non-compliance framework.", Local Law 061, enforcement mechanism
4. Annual rate reconfiguration
The NYC Department of Consumer and Worker Protection publishes updated wage and benefit levels every September, and those rates take effect the following January. Your system needs to support effective-dated rule changes: the ability to stage new rates that activate on a specific date without disrupting current schedules.
5. Multi-jurisdiction compliance stacking
National security firms don't operate in NYC alone. A guard working Monday in Manhattan and Wednesday in Newark needs two different rule sets applied automatically. As of 2026, California mandates daily overtime after 8 hours. Washington State enforces the highest state minimum wage at $17.13 per hour. NYC's new wage tiers now stack on top of all of these existing requirements.
The system must apply the correct jurisdiction's rules to every assignment, per guard, per site, per shift. This is not a spreadsheet problem but a system architecture problem that requires jurisdiction-aware scheduling at the platform level.
How will NYC enforce the Security Guard Wage Law?
The city has committed $18.6 million to enforcement infrastructure. The mayor's budget office projects 33 new staff at the Department of Consumer and Worker Protection, and a new Security Guard Advocate position has been created.
Guards can file complaints with their identity protected or go directly to court within a six-year statute of limitations. The penalty structure: $500-$1,000 per violation, triple damages on any underpayment, and $2,500 for retaliation, including schedule changes made in response to a complaint.
What does this mean for security operations?
For security employers not already paying prevailing wage rates, the cost impact is immediate: industry estimates suggest 24/7 security at a single building will cost $60,000-$70,000 more per year.
The operational burden compounds the cost because private security experiences 77% annual turnover, meaning new guards constantly enter the system and each one needs correct rate classification from their first shift. Every seniority milestone that triggers a wage tier change needs to be caught and applied correctly.
Those mechanics are why I built WorkAxle the way I did. We run scheduling and compliance for enterprises with multiple collective bargaining agreements in a single deployment. The rule engine treats each jurisdiction as its own configuration, California's daily overtime thresholds, Washington's $17.13 minimum, NYC's new prevailing wage tiers, and applies the correct rule pack based on where the employee is working that shift. When rates change, it's a dated configuration update, not a development ticket. When an auditor asks for records, every assignment, every rate applied, every override is already logged with who made the change and when.