Guides · BR-08

NYC Co-op vs Condo Board Package: What Changes for Deal Teams

NYC co-op and condo board packages share a core of financial and identity documents; the difference is the gate. A co-op board approves or rejects the buyer, so packages run deeper. A condo board typically decides whether to exercise or waive a right of first refusal, so packages are usually lighter — but always building-specific.

This page is for buyer's agents, real-estate attorneys, and package coordinators / TCs who run mixed inventory — a co-op this week, a condo the next — and need a side-by-side assembly map. It is not a buyer lifestyle FAQ on whether to buy a co-op or a condo. Those pieces already exist. This one assumes you know co-ops involve board approval and condos involve a purchase application and a waiver process.

The job is the same: pull thisbuilding's packet, chase the right third-party items, and deliver one complete file. The gate is not. Co-ops typically run board approval, often with an interview. Condos typically run a right-of-first-refusal (ROFR) waiver. Shared document patternsexist. Checklist weight, interview, and legal power diverge. Do not reuse last month's co-op table of contents on this month's condo — or treat every condo as a short form.

BoardReady is optional tooling for either package type: requirements in, documents classified, missing items left in view, one ordered PDF out. Use a spreadsheet if that is how the team already works.

This is not legal, financial, or tax advice. Building bylaws, the managing agent's current packet, and counsel control the deal. Unlawful discrimination is prohibited; nothing here is a substitute for an attorney on fair housing, contract contingencies, ROFR, or denial rights. Sponsor co-op sales and new-development condo transfers have their own documents — ask counsel and read the sponsoring papers; this page does not cover them.

Side-by-side comparison (patterns only)

Use the table to brief a mixed-inventory team. Then throw it out the moment this building's packet disagrees.

Same job, different gate — approval vs right of first refusal

Co-op (typical pattern). You assemble a purchase application / board package. The managing agent runs a completeness screen. The board reviews. An interview is common. For a non-sponsor sale, board approval is typically required to close. Hauseit's co-op package note and Nacmias describe that sequence as practice; they are not rejection-rate statistics. Sponsor sales are a different paper set — one sentence, then counsel.

Condo (typical pattern). You assemble a purchase / registration application plus supporting docs. The managing agent and board process is aimed at a waiver of the right of first refusal. ROFR is typically a bylaw or declaration right — not a citywide statute this page will recite — for the condominium to purchase on the same terms as the contracted buyer, or to waive that right. Hauseit's ROFR explainerdraws the contrast with a co-op board's approval power. That is a practitioner framing. Counsel and thisbuilding's bylaws control the deal. Do not treat "condo boards cannot reject" as a legal conclusion you announce on a live file.

Why incompleteness still hurts on condos

A lighter legal gate is not a lighter completeness job. Missing items can delay "complete application" status and push whatever waiver clock the bylaws and contract actually run. Brick Underground notes that an incomplete condo file can keep the waiver deadline moving and stall the closing. Hauseit describes incompleteness as a way a review window never cleanly starts. Assembler takeaway: completeness QC is not co-op-only. Run the same mechanical screen you would before a managing-agent review, and treat a bounce as assembly error, not "the condo is easy".

Shared document patterns (both property types)

Both packets often touch the same categories. Hudson Advisorylists the overlap at a high level: financials, taxes, employment, bank and brokerage statements, references, and the building's own forms. Co-op packages are typically more detailed; condo packages are often more streamlined. Categories that commonly appear on either side:

• Application or registration forms the building actually issued.
• Executed contract, plus riders the packet names.
• ID and credit-authorization forms.
• Employment or other income support.
• Bank and brokerage statements for the accounts the file will cite.
• Tax returns — years as the building requires, not as a blog default.
• Financing docs if mortgaged (loan application and/or commitment).
• Fees payable to the stated payees, in the stated channel.
• House-rules / bylaws acknowledgments.
• Lead, window-guard, pet, and other building-listed disclosures.

Do not assemble from this blog list. Extract thisbuilding's transfer / application requirements and treat that packet as the source of truth (how to pull the real checklist). SellWise and co-op checklists are useful for labeling folders. They are not the list you submit against.

Co-op-heavy extras assemblers should expect

A co-op file is typically heavier. Expect a fuller financial disclosure: a building or REBNY-style financial statement as the spine, with every material line mapped to statements (tie-out method). Do not invent a citywide reserve-month or DTI rule to "complete" the form.

References are typically formal letters — personal, professional, and often landlord — not just names and phone numbers. Brick Underground draws that contrast with condos, which often want contacts only. Phrase it as typically / often. Some condos ask for letters; some co-ops are lighter. Open the packet.

Interview prep should stay consistent with the submitted file. That is a one-line reminder, not coaching. Recognition agreements and other lender docs show up when the purchase is financed. Seller signature pages and seller fees are third-party lag — same chase discipline as the co-op assembly workflow.

Local Law 58 note (co-ops)

For covered New York City co-ops, Local Law 58 of 2026 applies to applications made on or after July 28, 2026. Completeness acknowledgments and written missing-item notices matter on that clock. Practitioner explainers exist; prefer the statute when a gloss and the text disagree. Assembler detail is Local Law 58 for package assemblers. Ask counsel whether this building is covered. This page does not invent a condo Local Law 58 duty. If someone on the deal asks whether LL58 applies to a condo package, that is a counsel question — not a blog conclusion.

Condo package patterns — lighter on average, never generic

Condo packets are often shorter: a registration or purchase-application form, a financing letter if mortgaged, selected financials, fees, acknowledgments, then a wait for the ROFR waiver letter before closing. Hauseit on the condo process treats that as a formality pattern, then flags the exception: some condo packets rival co-ops. Treat "condo = easy" as a myth. Open the building's packet every time. Do not skip a financial statement or interview because the last condo never asked.

ROFR clock language (assembler only)

Many bylaws and practitioner explainers describe a review window — commonly discussed as about 30 days after a complete application — after which waiver may be deemed issued. Hauseit and the condo-process note use that framing. Some packets also say a request for more information restarts a review window. Treat those as patterns you have seen in writing, not as law this page applies to a named building. Building bylaws and counsel control. Never calculate a deal-specific deadline from this article. Never publish a ROFR exercise rate. Whether a given board waives or exercises is a fact of that deal.

One assembly workflow for both — building packet first

Reuse the same sequence as the co-op assembly guide. The checklist changes. The workflow does not.

1. Ingest thisbuilding's requirements / application packet — not last month's TOC and not this article's category list.
2. Classify every client and third-party file against those requirements. Keep missing items visible.
3. If an FS is required, tie balances to statements before submit (BR-02).
4. Completeness QC as if the managing agent will bounce mechanical gaps (BR-03, BR-07).
5. Deliver one PDF in the building's stated order, with dividers and bookmarks as required (BR-06).

The anti-pattern is copying last month's co-op TOC onto this month's condo — or stuffing a short condo registration into a co-op spine because that is the folder template on the shared drive. Reuse workflow. Replace checklist.

Running both package types in BoardReady (optional tooling)

Product claims below match the homepage — nothing more. The same operational steps apply whether the gate is co-op approval or condo ROFR waiver. BoardReady does not invent building rules and does not submit to the board.

1. Upload the building's requirements package. BoardReady reads it for address, managing agent, and the checklist — scanned or text.
2. Add client documents. Each one is identified and classified against the requirement it satisfies. Missing items stay visible.
3. Output one PDF in the building's order, with divider pages. Balances are tied to the financial statement first when an FS is in play.

Documents are encrypted so storage cannot read them. Another account cannot open your package. Models do not keep a copy; labs that keep or train on documents are refused. Details live on how BoardReady handles tax returns and bank statements.

That helps mixed-inventory teams keep the right missing items visible. It does not replace your attorney, the managing agent, or a submission portal. It does not guarantee board approval, a ROFR waiver, an interview, or a closing date.

FAQ

The comparison, once

• Same assembly job; different gate — co-op approval (often with an interview) vs condo ROFR waiver.
• Shared document patterns (forms, contract, ID, income, assets, taxes, fees) — not a submit-against list.
• Co-op-heavy extras: FS spine, formal reference letters, interview consistency, LL58 completeness on covered co-ops.
• Condo path: often lighter, sometimes co-op-like; incompleteness still burns the waiver calendar.
• Building packet first. One workflow. Never copy last month's TOC onto the other property type.

Deep dives: the co-op workflow, extract this building's checklist, FS tie-out, PDF order. Mixed inventory this month? NYC co-op & condo board package software follows the building's checklist for either gate. It will not guarantee approval or a waiver.

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

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