NYC Local Law 11 Facade Projects: A Board Documentation Guide
A practical documentation guide for NYC condo and co-op boards managing Local Law 11 facade inspections and repairs—from engineer selection through final closeout.
Why facade compliance becomes a records problem
New York City's Facade Inspection and Safety Program, commonly called Local Law 11 or FISP, requires owners of buildings taller than six stories to have exterior walls and appurtenances inspected periodically by a qualified exterior wall inspector. The technical inspection belongs with the engineer. The board's job is to make sure the resulting decisions, filings, repairs, and costs form one complete record.
A facade cycle can involve an architect or engineer, property manager, contractor, expeditor, attorney, insurance broker, and several generations of board members. Reports arrive as attachments, recommendations change after probes, and change orders are approved in email. When the record is fragmented, a new director cannot tell what condition was found, which work was required, what the board authorized, or what remains open.
This guide focuses on the operational record a condo or co-op board should maintain. It is not legal or engineering advice. Confirm current requirements, cycle dates, and technical decisions with qualified professionals and the NYC Department of Buildings.
Open the project record before the inspection
Do not wait for the final report. Create a dedicated facade project record when the board begins selecting an inspector. Include:
- Prior FISP reports and filing confirmations
- Earlier repair scopes, permits, warranties, and closeout documents
- Inspector proposals and engagement letters
- The resolution approving the selected professional
- Insurance certificates and credentials
- Known leaks, cracks, loose materials, and resident complaints
- Current deadlines and responsible parties
Prior reports show how conditions developed. Without them, the board and its engineer lose context that may distinguish a stable condition from an accelerating one.
Document the inspector selection
Compare candidates on relevant experience, inspection methodology, scope exclusions, fee structure, availability during repairs, and references from similar buildings. Preserve the comparison and final approval.
The board should be able to explain why it selected the firm, what services were included, which fees were approved, and who was authorized to sign. This is useful governance even when the selected proposal is the lowest.
Keep the inspection evidence together
The filed report is only one part of the record. Preserve:
- Field notes and marked-up elevations
- Photographs with dates and locations
- Drop or scaffold inspection logs
- Probe recommendations and results
- Access limitations
- Draft reports and material revisions
- The filed report and proof of submission or acceptance
Ask the engineer to use consistent location labels across photographs, reports, drawings, and repairs. "Crack near window" is difficult to track. "North elevation, floor 8, window stack B" can be connected to a repair item and closeout observation.
Turn findings into an action register
Translate the technical findings into an operational list. Each item should have a unique identifier, location, condition, engineer-assigned priority, recommended action, owner, target date, status, and supporting documents.
The engineer remains responsible for technical judgment. The register gives the board visibility into execution. If temporary safeguards are recommended, record installation, inspection, monitoring, and the plan for permanent correction.
Build a defensible procurement file
Require contractors to price the same issued scope and list exclusions, allowances, alternates, and unit prices. Keep:
- Issued drawings and specifications
- Bid invitations, questions, and addenda
- Complete proposals
- The engineer's bid comparison
- Interview notes and references
- Insurance and licensing documents
- The approval resolution
- Signed contract and baseline schedule
If the board chooses a bid that is not the lowest, document the actual reasons, such as relevant experience, staffing, completeness, safety record, or fewer exclusions.
Control change orders
Facade work often uncovers concealed conditions. That does not mean changed work should bypass governance.
Every change request should identify the condition, explain why it was outside the original scope, include the engineer's recommendation, show cost and schedule impact, and record the required approval. Avoid approvals that exist only as "looks fine" inside a long email chain.
Maintain a live cost log with the original contract, approved changes, pending changes, invoices, retainage, contingency, and forecast at completion. For a broader planning framework, see How to Create a Capital Improvement Plan for Your Building.
Record resident communications
Preserve notices about sidewalk sheds, window access, noise, terrace restrictions, dust precautions, entrance changes, and complaint handling. When the schedule changes, explain what changed, why, and what residents should now expect.
Consistent updates reduce confusion and create evidence that the board considered resident impact throughout the work.
Close the project deliberately
Before treating the project as finished, collect:
- Engineer punch lists and completion confirmation
- Final inspection photographs
- Contractor warranties and product information
- Permits, sign-offs, and filing records
- Final change-order and payment reconciliation
- Lien waivers where counsel advises them
- As-built drawings or marked-up repair locations
- Ongoing maintenance and monitoring recommendations
The closeout package should be understandable to a future board with no prior involvement. Store it with the building's permanent capital-project records, not in one officer's personal inbox.
The board's final test
Confirm that a new director can answer:
1. What condition did the engineer identify?
2. Which work did the board authorize?
3. Which document is the latest approved scope?
4. What is the final cost after approved changes?
5. Which filings and sign-offs closed the cycle?
6. What monitoring or maintenance remains?
A facade project is complete when the building has a coherent record of the condition found, decision made, work performed, money spent, and professional confirmation that closed the cycle.
BoardRecord organizes project email, documents, decisions, and vendor communication into a searchable building record. Start a free pilot.
Get board governance guides in your inbox
We publish practical guides for condo, co-op, and HOA boards every week. No spam, unsubscribe anytime.