Last updated: June 2026
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.
You've probably read the political coverage — the veto override, the real estate industry opposition, the cost projections. What hasn't been covered is what this law actually demands from the scheduling and payroll systems that security employers rely on every shift. That's the part that matters most to operations, because the compliance requirements translate directly into system architecture problems that spreadsheets and generic tools weren't built to solve.
In this post:
What Does NYC's Security Guard Wage Law Require?
The Aland Etienne Safety and Security 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, and it passed the City Council overwhelmingly — 41 votes in favor, zero against — before surviving a mayoral veto override in January 2026.
Here's the compliance timeline that 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 — meaning the union-negotiated rates set annually for guards on city building service contracts:
| 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, which means office towers, retail complexes, residential buildings, and corporate campuses are all in scope. Only federal, state, and city government entities are exempt — along with union-represented guards under CBAs signed before October 30, 2025, but only if their total compensation package already meets or exceeds the law's standards.
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, from tiered rate calculations to a six-year audit trail with legal presumptions attached. Here's what each one means for your technology stack.
1. Rate-tier calculation per guard, per shift
The law creates a tiered wage structure based on both seniority and armed status, which means the correct rate for any given shift depends on who's working it. An unarmed guard with 18 months of experience earns $18.02 per hour under the prevailing wage schedule. 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, and the law gives employers flexibility in how they deliver it: health insurance, a cash equivalent, or a combination of both.
That flexibility creates a tracking problem most scheduling and payroll systems aren't designed for. Somewhere in your stack, you need to record what form of benefit each guard receives, calculate any shortfall between what's provided and what's owed, and document the result every pay period. Whether that lives in your WFM platform, your HRIS, or your payroll system — the data has to be accurate and auditable, because getting it wrong carries triple-damages exposure.
3. Six-year audit trail — with a presumption of non-compliance
Under Local Law 061, every wage paid, hour worked, benefit provided, and contract detail must be documented and retrievable for six years, and the enforcement mechanism is unusually aggressive. 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.
A scheduling system that doesn't generate auditable records for every assignment — rate applied, classification used, benefits tracked — isn't just operationally inefficient. Under the Aland Etienne Act's presumption-of-non-compliance framework, missing records become an automatic legal liability.
4. Annual rate reconfiguration
The NYC Department of Consumer and Worker Protection (DCWP) publishes updated wage and benefit levels every September, and those rates take effect the following January — creating a recurring annual compliance cycle rather than a one-time configuration.
Your system needs to support effective-dated rule changes, meaning the ability to stage new rates that activate on a specific date without disrupting current schedules. Miss the September DCWP update, and every shift scheduled at the old rate from January forward becomes a potential underpayment with triple-damages exposure.
5. Multi-jurisdiction compliance stacking
National security firms don't operate in NYC alone, and this is where the compliance architecture becomes structurally complex. Guards working across state lines face overlapping wage, overtime, and break rules — similar to the predictive scheduling laws that already vary by jurisdiction across U.S. cities and states.
As of 2026, California mandates daily overtime after 8 hours rather than just weekly. Washington State enforces the highest state minimum wage in the country at $17.13 per hour. Colorado applies a 12-hour daily overtime threshold under its COMPS Order. 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. A guard working Monday in Manhattan and Wednesday in Newark needs two different rule sets applied automatically, which 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 and isn't treating Local Law 061 as a symbolic measure. 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 within the agency to handle complaints and educate the workforce.
Guards can file complaints with their identity protected or go directly to court within a six-year statute of limitations, and prevailing workers recover attorney's fees. The penalty structure is steep: $500–$1,000 per violation, triple damages on any underpayment, and $2,500 for retaliation — including schedule changes made in response to a complaint.
When the city invests $18.6 million in enforcement before the law even takes effect, the question isn't whether you'll face scrutiny — it's whether your records will hold up when you do.
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, which cascades into contract renegotiations with every building owner in the portfolio.
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, and every benefit election needs tracking — at scale, across sites, without gaps.
NYC is the first city to mandate private-sector wage parity for security guards, but the sectoral wage model is being watched nationally as a potential template for other jurisdictions. Security employers operating in multiple states should be evaluating their system architecture now, not just their NYC compliance posture.
Here's what I notice when I read through laws like the Aland Etienne Act: the hard part is never the wage increase itself. It's the ongoing mechanics — the rate tiers that shift when a guard hits a seniority milestone, the annual DCWP rate publication every September that has to propagate into live schedules by January, the audit trail where a missing record doesn't just look bad but shifts the legal burden onto you.
Those mechanics are why I built WorkAxle the way I did. We run scheduling and compliance for enterprises with 18+ collective bargaining agreements in a single deployment, across operations that span five continents. 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. Not where the company is headquartered. Not a global default with local overrides. The jurisdiction selects the rules.
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. That's not a compliance module we added. That's how the system was designed from the first line of code.
Frequently Asked Questions
What is the Aland Etienne Safety and Security Act?
The Aland Etienne Safety and Security Act (NYC Local Law 061 of 2026) is a landmark law requiring all private security employers in New York City to match the wages, paid time off, and supplemental benefits that the city pays guards on public building service contracts exceeding $1,500. The law takes effect July 28, 2026, with wage requirements beginning January 1, 2027, and is named for a security officer killed during the July 2025 mass shooting at 345 Park Avenue.
How much must NYC security guards be paid under the new law?
Private security employers must match city-contract prevailing wage rates: $18.02 per hour for entry-level unarmed guards (0–2 years), $21.20 per hour for experienced unarmed guards (2+ years), and $32.70 per hour for armed guards. Employers must also provide supplemental benefits worth $8.12–$8.47 per hour, which can be delivered as health insurance, cash, or a combination of both.
What are the penalties for violating NYC's security guard wage law?
Violations carry civil fines of $500–$1,000 per incident, with triple damages on any wage underpayment — meaning a $10,000 shortfall becomes a $30,000 liability. Retaliation against guards who file complaints carries a $2,500 penalty per incident plus reinstatement and back pay, and the city has allocated $18.6 million for enforcement with 33 new staff at the Department of Consumer and Worker Protection.
What records must security employers keep under Local Law 061?
Employers must maintain detailed records of wages paid, hours worked, benefits provided, and contract details for every security guard, and these records must be retrievable for six years. The enforcement mechanism is unusually strict: if investigators request records and the employer can't produce them, the law presumes the employer violated it, shifting the burden of proof entirely to the employer.
Does the NYC security guard wage law apply to building owners or security companies?
The law applies directly to security guard employers — the companies that employ the guards — not to building owners or property managers. However, building owners will feel the cost impact through higher contract rates, because security providers must pass through the increased wage and benefit costs to maintain compliance with the prevailing wage standards.
If you're managing security guard scheduling in NYC — or across multiple jurisdictions with overlapping wage, overtime, and benefits rules — a 30-minute assessment can map your current compliance gaps, show you how effective-dated rule changes work at the jurisdiction level, and identify where your audit trail needs strengthening — before the July 28 deadline arrives.
