Local Law 11 for NYC Co-op and Condo Boards the Full Guide

Local Law 11 is one of the most consequential compliance obligations a NYC co-op or condo board will ever manage. Understanding what it requires, when deadlines fall, and how to keep the right records can save your building from costly fines and last-minute scrambles.

This article is informational only and does not constitute legal advice. Boards should confirm all obligations against their governing documents, applicable regulations, and the guidance of qualified professionals.

What Local Law 11 Means for NYC Co-op and Condo Boards

Local Law 11 of 1998, officially administered today as the Façade Inspection & Safety Program (FISP), requires buildings taller than six stories to have their exterior walls inspected every five years by a licensed professional. The inspection results are filed with the NYC Department of Buildings (DOB) through the DOB NOW: Safety portal.

For a volunteer board, that means coordinating with engineers, tracking deadlines across multi-year cycles, and keeping records that survive board turnover.

The law has been continuously enforced since Local Law 10 of 1980, making it one of the oldest facade mandates in the country.

After a critical examination, the building's facade is classified as one of three statuses:

• Safe — No repairs needed; the facade is structurally sound for the next five years.
• SWARMP (Safe With a Repair and Maintenance Program) — Currently safe, but repairs are required within the cycle to prevent deterioration.
• Unsafe — Hazardous conditions exist; the owner must install a sidewalk shed immediately and correct the conditions within 90 days.

Boards overseeing NYC co-op and condo governance carry real responsibility here. The burden sits with the building owner — and in a co-op or condo, the board acts on behalf of the ownership collectively.

Which Buildings Need to Pay Attention to Local Law 11

The rule is straightforward: any NYC building taller than six stories is subject to FISP. The NYC DOB's FISP Universe Map lists every covered building by block number, and it is the building owner's responsibility to confirm whether the property qualifies.

Approximately 12,500 buildings across all five boroughs fall under this mandate — a number that grows each year as new construction clears its initial five-year window from the first Temporary Certificate of Occupancy (TCO).

For co-ops and condos, the question of who holds the compliance responsibility matters. In a co-op, the corporation owns the building; in a condo, the board of managers typically handles common areas including the exterior.

Either way, the board's role is to ensure the inspection happens, the report gets filed, and any required repairs are funded and completed on time.

Buildings six stories or shorter are generally exempt from FISP, but they may still face DOB enforcement if unsafe facade conditions are identified.

Since January 1, 2024, a separate annual parapet observation requirement under Local Law 126 of 2021 also applies to all buildings with parapets fronting a public right-of-way, regardless of height — an important detail for smaller co-ops and condos that might otherwise assume they have no facade obligations at all.

Building Type	FISP Applies?	Notes
Co-op or condo over 6 stories	Yes	Full FISP inspection every 5 years
Co-op or condo 6 stories or fewer	No (FISP)	Annual parapet observation may still apply
Newly constructed building	After 5-year TCO anniversary	First report due at applicable sub-cycle deadline
Building with parapet on public ROW	Parapet rule only	Annual observation, all heights, since Jan 1, 2024

---

Key Deadlines, Records, and Meeting Tasks to Track

FISP Cycle 10 began on February 21, 2025 and runs through February 21, 2030. Like previous cycles, it is split into three sub-cycles determined by the last digit of the building's block number:

• Sub-cycle 10A (block numbers ending in 4, 5, 6, or 9): Filing window February 21, 2025 – February 21, 2027
• Sub-cycle 10B (block numbers ending in 0, 7, or 8): Filing window February 21, 2026 – February 21, 2028
• Sub-cycle 10C (block numbers ending in 1, 2, or 3): Filing window February 21, 2027 – February 21, 2029

Missing a filing deadline costs $1,000 per month, plus an additional $5,000 annual failure-to-file penalty according to the NYC DOB FISP filing requirements.

An Unsafe condition that is not corrected triggers further penalties based on the linear footage of any required sidewalk shed. These costs add up fast.

For a board, the practical compliance calendar should include:

• Confirming your sub-cycle by checking the last digit of the building's block number
• Retaining a QEWI (Qualified Exterior Wall Inspector) at least 12 months before the filing deadline, since experienced inspectors book quickly
• Tracking SWARMP repair deadlines from the prior cycle — any Cycle 9 SWARMP conditions not resolved by February 21, 2027 automatically become Unsafe under Cycle 10A rules
• Logging the DOB report filing date and confirmation from DOB NOW: Safety
• Recording the parapet observation completion and keeping the report on file for at least six years
• Noting any amended reports filed after unsafe conditions are corrected

All of these dates belong on a compliance calendar that the full board can see, not just the managing agent's inbox.

---

How a Board Handles Local Law 11 Work Without Losing Track

Here is where many volunteer boards run into trouble. The inspection itself is handled by professionals, but the coordination — selecting a QEWI, reviewing proposals, approving vendor contracts, tracking repair timelines, and logging resolutions — falls squarely on the board.

A simple workflow helps:

1. Assign a compliance owner. One board member should be the point of contact for FISP in each cycle. That person confirms sub-cycle timing, manages the QEWI selection, and keeps the rest of the board updated.
2. Create a central document folder. All prior FISP reports, repair invoices, correspondence with the QEWI, DOB filings, and vendor contracts should live in one place. Not in someone's personal email, and not scattered across management reports.
3. Put it on the meeting agenda. The board should formally acknowledge FISP status at least once per cycle — either when approving the QEWI engagement or when reviewing the inspection report. The resolution and any vote should appear in the meeting minutes.
4. Track vendor commitments separately. If the QEWI identifies SWARMP conditions, the repair contractors and their deadlines should be logged with contract dates and completion confirmations.
5. Plan for handoffs. Board membership changes. A new treasurer or board president should be able to open the FISP folder and understand exactly where things stand without asking three people for context.

This kind of organized approach is what distinguishes boards that handle FISP smoothly from those that face fines because a deadline slipped during a transition year. Boardly is built specifically for this operational challenge — keeping NYC boards organized across multi-year compliance cycles without requiring a property management background.

---

Where Board Management Software Helps NYC Boards Stay Organized

Generic HOA tools and shared drives were not designed for New York City's specific compliance environment.

A board dealing with FISP alongside Local Law 97, Local Law 126, and annual shareholder meetings needs tools that match the actual workflow.

Boardly's features address each part of the FISP cycle directly:

Document storage and searchable records. Every FISP report, vendor contract, DOB filing confirmation, and repair invoice can be stored in a single searchable location. When a board member leaves and a new one joins, institutional memory stays intact.

Compliance calendar and deadline tracking. Rather than relying on a managing agent to send a reminder, the board can maintain a shared compliance calendar with FISP sub-cycle deadlines, parapet observation due dates, SWARMP repair milestones, and DOB report filing confirmations.

Meeting agenda and minutes. FISP approvals and vendor decisions should be reflected in board meeting records. Boardly's agenda tool makes it easier to add compliance line items and capture the resolution in a format that holds up over time.

Audit trail for board decisions. When the DOB asks whether the board authorized a specific repair or reviewed an inspection report, a timestamped record of the decision matters. Board management software creates that trail automatically.

Communication across turnover. Board governance depends on continuity. Boardly keeps FISP-related correspondence and decisions visible to every current board member, regardless of when they joined.

For a small co-op or condo that does not have a full-time property manager, this kind of structure makes the difference between a board that stays ahead of compliance and one that finds out about a missed deadline from a DOB violation notice.

---

Common Mistakes NYC Boards Make With Compliance Documentation

Based on the pattern of how FISP violations occur, a few documentation failures come up repeatedly.

Files scattered across personal email and shared drives. When the outgoing board president is the only person who knows where the 2020 FISP report lives, that is a governance problem waiting to surface. Centralized, access-controlled document storage is not optional for a building with ongoing compliance obligations.

No clear owner for the compliance task. If everyone assumes the managing agent is tracking FISP and the managing agent assumes the board treasurer is handling it, the deadline can pass without either party acting. Explicitly assigning one board member as the FISP point of contact removes that ambiguity.

Weak handoffs during board elections. Annual elections mean regular turnover. A board that does not formally transfer institutional knowledge — including FISP cycle status, outstanding SWARMP conditions, vendor contracts, and prior DOB filings — risks losing months of progress. This is especially dangerous mid-cycle.

No record of meeting votes or resolutions. A board vote to engage a QEWI or approve a repair scope should appear in the minutes. Without that record, the decision lives only in someone's memory, which is not useful if a dispute arises later.

Treating SWARMP as optional. Some boards see a SWARMP classification and assume there is no urgency. There is. Any SWARMP condition from Cycle 9 that is not repaired by February 21, 2027 automatically converts to Unsafe under Cycle 10A — triggering fines and mandatory sidewalk sheds.

None of these mistakes require legal missteps to be costly. They are operational failures, and they are exactly what organized board governance is designed to prevent.

A Practical Local Law 11 Checklist for Board Members

Use this checklist before any FISP-related meeting, vendor review, or new cycle begins. Confirm details with your QEWI, legal counsel, and property manager before acting.

Before the inspection cycle opens:

• Confirm your building's block number and assigned sub-cycle (A, B, or C)
• Check whether any SWARMP conditions from the prior cycle are still open
• Begin QEWI selection at least 12 months before your filing window closes
• Verify that parapet observation is up to date for the current calendar year

When engaging the QEWI:

• Request proof of QEWI registration with the NYC DOB
• Confirm the QEWI carries professional liability insurance
• Document the board's authorization to engage the QEWI in meeting minutes
• Store the signed contract in your central document folder

After the inspection report is filed:

• Save the DOB NOW: Safety filing confirmation
• Log the filing date on the compliance calendar
• If classified SWARMP, record each repair item and its deadline
• If classified Unsafe, confirm sidewalk shed installation and 90-day repair plan
• File the amended report within two weeks of completing any unsafe repairs

For ongoing governance:

• Add FISP status as a standing item on the annual meeting agenda
• Confirm the full board knows where all FISP documents are stored
• During board elections, formally brief incoming members on active compliance items

Keeping this checklist current is easier when it lives alongside your other board records in one place. If your board is managing FISP files across multiple email threads and folders, now is a good time to get started with Boardly and consolidate everything.

Wrapping Up

Local Law 11 is not going away, and the penalties for disorganized compliance are real. Boards that treat FISP as a governance task — with assigned owners, centralized records, and clear meeting documentation — consistently handle it better than those that treat it as a one-time administrative chore.

If your board is entering Cycle 10 without a clear system, Boardly gives NYC co-op and condo boards a focused home for compliance tracking, document storage, and meeting records. Get started with Boardly and bring structure to your building's compliance workflow before the next deadline arrives.

Questions about how Boardly supports FISP governance? Talk to the Boardly team and we can walk you through how it fits your building's specific setup.

Frequently Asked Questions

Does Local Law 11 apply to all NYC buildings? No. Only buildings taller than six stories must comply with FISP inspections. Shorter buildings may still face parapet observation requirements under Local Law 126 of 2021.

What happens if a board misses the FISP filing deadline? The penalty is $1,000 per month past the deadline plus a $5,000 annual failure-to-file fine. Unsafe conditions carry additional monthly penalties tied to sidewalk shed footage.

Who actually files the FISP report with the DOB? Only a Qualified Exterior Wall Inspector (QEWI) — a DOB-registered licensed engineer or architect — can file the technical report through DOB NOW: Safety.

What is a SWARMP classification and why does it matter to the board? SWARP means the facade is safe now but needs repairs within the cycle. Unresolved SWARMP items automatically become Unsafe when the next cycle report is filed.

How does board management software help with Local Law 11 compliance? It centralizes documents, tracks deadlines on a shared compliance calendar, logs board decisions, and preserves institutional memory through board member turnover.