Guides · BR-04

Building Transfer Requirements: Extract the Real Board-Package Checklist

This page is for the people who open a deal by asking for the building's current application and transfer-requirements packet: buyer's agents, attorneys, and package coordinators / transaction coordinators. Listing-side agents who should request and share those materials early are the secondary audience. It is not another printable "every NYC co-op needs these documents" list.

The thesis: the checklist lives inside thisbuilding's packet. Blogs are orientation, not authority. BoardReady's first step is the same idea — upload the requirements, read the checklist out of that document — whether you use the product or a dated PDF and a spreadsheet.

This is not legal, financial, or tax advice. Do not treat a generic category list below as this building's requirements. Ask counsel whether Local Law 58 covers the transfer. Do not assert that a named building is covered or excluded.

Why generic board-package checklists fail

Requirements vary by building. Forms and fees change. A prior sale's package for the same address can be stale. SellWise says it directly: do not rely on a prior sale. Nacmias notes that buildings publish their own list and return incompletes. Hauseit treats the purchase application as building-specific.

Generic lists omit the things that actually bounce a file: portal slot rules, exact fee payees, recognition-agreement originals, pet or occupancy riders, copy counts, and "do not submit until" lines. The cost of the wrong source is a managing-agent bounce, wasted third-party letters, and contract timing pressure.

When a generic list is still useful

As a category map while you wait for the packet — financials, IDs, references, building acknowledgments. Buyer-facing tablesare useful for labeling folders. They are not the list you submit against. If you catch yourself checking boxes on a blog while the agent's PDF sits unread, stop.

What "transfer requirements" means

In plain English: the complete list of documents, forms, fees, disclosures, and procedural steps the co-op requires for the sale — including interview, authorizations, or third-party reports if the packet states them — plus how to submit.

Application vs transfer requirements (Local Law 58 vocabulary)

For covered cooperatives, Local Law 58 of 2026 distinguishes the standardized application (forms, authorizations, questionnaires, supporting documents) from transfer requirements (the complete list of requirements, plus submission instructions and any stated completeness standards). Covered co-ops must maintain both and provide them promptly upon request to the purchaser, the purchaser's agent, and the seller (§26-3702). That is a paraphrase — read the statute and ask counsel.

Not every New York City co-op is covered. The chapter's definition of cooperative corporation excludes, among other things, Article XI HDFCs, sales that need governmental housing-agency approval, and entities with fewer than ten dwelling units. Practitioner overviews (SellWise, CooperatorNews) discuss coverage the same way. Counsel confirms the building and the transfer. Do not assert a named address is in or out.

How to get the current packet

Ask the managing agent — and the listing side — for:

• The current application and transfer requirements.
• Fees and payees.
• Submission channel and format.
• Financial standards, if they are published in writing.
• Interview rules, if stated.
• Board calendar, if they will share it.

Request as soon as the building is serious, or at contract — not the day before the commitment letter. The living checklist cannot exist until the packet exists.

What "current" means

Date-stamp the PDF. If the agent sends an update mid-deal, replace the checklist. Do not merge from memory. Retain proof of what was provided — email plus attachments — for deficiency disputes later. Two people on the team with two versions of the application is a stop-work condition, not a "we'll reconcile at the end" item.

Extract a living checklist from the packet

This is a method, not a universal table of contents:

1. Skim for a published checklist, table of contents, or "submit the following."
2. Add every form in the packet as its own row, even if it is not listed twice.
3. Add fee lines (amount, payee, certified vs personal if stated).
4. Add format rules (portal, number of copies, bookmarks, originals).
5. Add procedural steps (interview, credit authorization, recognition-agreement timing).
6. Flag special riders (pets, renovations, pied-à-terre, guarantor, entity / trust) as conditional rows.
7. Assign an owner and a status: have / missing / N/A with a reason.

Hand off from there: classify incoming files against those rows (assembly workflow), treat the financial statement as the spine (tie-out), and run the completeness gate before send.

Common category buckets (orientation only)

Practitioner lists often group financials, purchase documents, references, and building acknowledgments. Those buckets help you label folders while the packet is in transit. They are not this building's list. Ending this page with a 25-row "ultimate checklist" would contradict the thesis — so there isn't one.

Local Law 58 — assembler angle only

The law takes effect 180 days after it became law and applies to applications made on or after that date. Practitioner sources commonly state July 28, 2026 (SGR reminder, CooperatorNews, SellWise; the statute's effective-date clause is the primary text). Ask counsel before you treat that date as controlling on a live file.

Why it matters for checklist work: covered co-ops must maintain and promptly provide the application and transfer requirements. Completeness acknowledgments identify missing items in writing. Starting from the wrong list wastes the whole clock story.

Assembler takeaway: get the written requirements early; submit against thatlist; keep a clean record of what you were given. Do not calculate a deal's deadlines in this article. Ask counsel about coverage, exclusions, and summer-recess tolling. The deeper assembler page is Local Law 58: what "complete" means.

How BoardReady extracts the checklist from the building packet

Product claims below match the homepage — nothing more.

1. You upload the building's requirements package — scanned or text. BoardReady reads address, managing agent, and the full checklist from that document, not a blank form you fill with guessed items.
2. Add client documents. Each is classified against those requirements. Missing items stay visible.
3. Output one PDF in the building's order, with divider pages. Balances are tied to the financial statement first.

Documents are encrypted so storage cannot read them. Models do not keep a copy. Details live on how BoardReady handles tax returns and bank statements.

That turns the packet into a working checklist faster than retyping it. It does not certify that the co-op's packet is lawful or complete under Local Law 58, and it does not fetch requirements from every managing agent without an upload. Humans still confirm fees, wet-ink rules, and judgment calls.

FAQ

The source of truth, once

• Get this building's current application and transfer requirements in writing.
• Date-stamp the packet; replace the checklist if the agent updates it.
• Extract a living list — forms, fees, format, procedures, riders — with owners.
• Submit against that list. Blogs are orientation. Counsel owns coverage and clocks.

Then assemble (BR-01), tie out the financial statement (BR-02), and clear the managing-agent gate. A wrong checklist is a common reason files get bounced. Prefer software? BoardReady reads the packet you drop in. It will not guarantee board approval.

Not legal, financial, or tax advice. Building requirements and counsel control the deal.

← All guides·NYC co-op & condo board package software