Guides · BR-01

How to Assemble a NYC Co-op Board Package: Workflow for Agents, Attorneys & TCs

To assemble a NYC co-op board package, start from the building's own transfer requirements, file every client document against a requirement, tie each financial-statement line to a dated statement, clear the missing items, and deliver one PDF in the building's order. This workflow is for buyer's agents, real-estate attorneys, and transaction coordinators who hold the checklist and the PDF. It assumes you know a co-op needs board approval and a purchase application. It is about assembling one complete file the managing agent will accept on the first pass.

The promise is a building-first process: take this building's transfer requirements, classify every incoming file against that list, keep missing items visible, tie the financial statement to supporting statements, and deliver one ordered PDF (or whatever format the agent actually requires).

BoardReady is optional tooling for the same sequence — requirements in, documents classified, missing items left in view, one PDF out. Use a spreadsheet if that is how your team already works. The steps do not change.

This is not legal, financial, or tax advice. The building's written requirements, the managing agent, and counsel control the deal. Unlawful discrimination is prohibited; nothing here is a substitute for an attorney on fair housing, contract contingencies, or denial rights.

Common co-op board package document categories (confirm against the building's packet)

Patterns only — the building's packet is the list. These categories show up on most NYC co-op purchase applications; they are not a substitute for this building's current transfer requirements.

Start with this building's transfer requirements — not a generic checklist

The authoritative list is the current application and transfer-requirements packet from the managing agent (or the listing side), not a blog list and not last year's file for the same address. Forms, fee amounts, copy counts, and portal instructions change. SellWise and other practitioner write-ups make the same point: start from the building, then gather.

Pull the packet and extract a living checklist before you chase the buyer for tax returns. How to turn that packet into rows is building transfer requirements. At minimum, capture:

• Required forms and questionnaires, including any REBNY-style financial statement the building uses.
• Fees, payees, and whether payment is a check, portal charge, or both.
• Copy count, binding rules, and the submission channel (portal, email, messenger).
• Recognition-agreement or bank-form requirements if the purchase is financed.
• Interview rules, if the packet states them — schedule later; do not let them bury document collection.
• Any stated completeness standard or "do not submit until" instruction.

Do not reuse a prior sale's package as the checklist for the same building. The last deal's PDF is a hint, not the source of truth. If two people on the team have two versions of the application, stop and get the current packet from the managing agent in writing.

Common document categories — application, contract, financial statement, income support, asset statements, references, IDs, disclosures, fee receipts — show up across buyer-facing checklists. Those categories are useful for labeling folders. They are not the list you submit against.

Local Law 58 and "complete" (assembler note only)

For covered New York City co-ops, Local Law 58 of 2026 applies to applications made on or after July 28, 2026 (180 days after the law became law on January 29, 2026). The statute requires covered cooperative corporations to maintain an application and transfer-requirements list, and to acknowledge materials in writing. Practitioner explainers describe a completeness acknowledgment — including a written list of missing items when the file is not complete — and a later decision clock once the application is complete or deemed complete.

Assembler takeaway only: submitting once, clean, reduces clock thrash. Each subsequent submission can restart acknowledgment. Ask counsel whether this building is covered. The statute excludes, among other things, HDFC cooperatives, sales that need governmental housing-agency approval, and entities with fewer than ten dwelling units. Condos are not what this chapter is written for. Do not run a DIY deadline calculator on a live deal from this page — counsel and the managing agent own applicability and dates. A longer assembler note is Local Law 58 for package assemblers.

Document intake — classify every file against a requirement

Open a living checklist whose rows are this building's requirements, not a generic template. As client and third-party documents arrive, label each file against the requirement it satisfies. A W-2 is not "financials." It is the income-support line the packet named. A June brokerage PDF is not "statements" — it is the specific account and period the financial statement will cite.

Keep missing items visible. A thread of "still waiting on the employer letter" buried in email is how packages get submitted short. The working file should show, at a glance, what is in, what is outstanding, and who owns the chase. If your team uses a shared sheet, the missing column is the only column that matters on Wednesday afternoon.

Third-party lag items

The documents that stall assembly are rarely the ones sitting on the buyer's laptop. Request these early, in the same week the requirements land:

• Personal and professional reference letters (and any form the building requires the writer to use).
• Employment or income-verification letters on letterhead.
• Loan commitment and, if financed, bank or recognition-agreement paperwork.
• Seller signature pages, lead disclosures, and seller-side fees the packet assigns to the outgoing shareholder.

Scanning two years of tax returns is work. Waiting ten days for a reference who is on vacation is calendar. Start the lag items first.

Special cases (flag only)

Gifts, self-employed buyers, guarantors, and entity purchasers expand the checklist. Flag the case as soon as you see it and ask the attorney which extra letters, returns, or entity docs this building wants. Do not invent a citywide gift-letter form from memory. A deeper special-case packet is future work — not this page.

The financial statement is the spine — every line traces to a statement

The building form — often a REBNY-style statement of assets, liabilities, income, and expenses — is the summary the board will read first. Everything else in the financial half of the file exists to support those lines. Line-item confusion on the REBNY formis a known source of bounce-backs; the assembler's job is not to invent a liquidity rule, it is to make every material number traceable.

Rule for assemblers: every material figure on the statement should map to a supporting bank, brokerage, retirement, or liability document (or a letter that explains a figure the statements cannot). Statement dates should align with the as-of date the form asks for. If the form says "as of the last day of last month," do not file a statement that ends six weeks earlier and hope no one notices.

Common traps — without treating any of them as a citywide underwriting rule:

• Missing pages in a multi-page statement (including the blank or "intentionally left blank" page).
• Large deposits that appear on a statement and nowhere in the explanation or gift paperwork.
• Liabilities that show on a credit report but not on the application.
• Retirement versus cash classification that this building may treat differently from the last one — ask the managing agent or the attorney for this building's written practice.

Do not apply a universal months-of-reserves or DTI cap you read on a blog. Buildings differ. If the listing agent or managing agent has stated a written standard, file to that standard. If they have not, do not invent one. The method for tying every financial-statement line to supporting statements is financial-statement tie-out.

Completeness QC before the managing agent sees it

Managing agents typically screen for completeness mechanically before the board reads substance. Nacmias Law describes that first gate in plain terms: incomplete files come back. Your QC pass is meant to clear that gate, not to underwrite the buyer. The full gate note is what managing agents check.

Walk the file once, with the building packet open:

• Blank fields filled or marked N/A the way the form allows — not left empty because "it did not apply."
• Names, addresses, unit numbers, and dates consistent across the application, contract, and statements.
• Signatures and notarizations present where the packet requires them.
• All pages present on every multi-page exhibit.
• Fee amounts and payees matching the current instructions, not last quarter's flyer.
• Sensitive files traveling only through the approved channel — not a personal Gmail thread with tax returns attached.

Hauseit and buyer-facing assembly notesboth stress consistency and order. Treat those as QC reminders, not as a substitute for this building's list.

Blank and "intentionally left blank" pages

Include every page of a multi-page bank statement or tax return, including blank pages and pages stamped "intentionally left blank." A missing "page 4 of 5" is a common reason a managing agent returns the file — that is industry consensus, not a ranked statistic. Milton Coste and other assembly notes make the same request: if the statement is five pages, the package contains five pages.

Assemble the deliverable — building order, dividers, bookmarks

Follow the building's stated section order exactly. If the packet says contract before financials, do not invert them because another building preferred it the other way. Formatting and order are how a reviewer finds the employment letter without hunting.

Digital default, unless the agent requires something else: one bookmarked PDF; clear divider or section pages; a cover sheet and a table of contents with agent and attorney contacts as practice allows. Confirm format with the managing agent before you bind anything.

If physical sets are still required, confirm copy count, tabbing, and binding with the agent. Some agents dislike permanent binding because they reshuffle sections. Phrase the question to the agent, do not assume a citywide rule. Hauseit-style assembly tips are useful prompts; the agent's current instruction wins.

There is no universal table of contents. A common pattern — not a template you should force — looks like:

1. Application and building forms
2. Contract / offer documents
3. Financial statement
4. Income support (returns, W-2s, letters)
5. Asset statements
6. References
7. IDs, disclosures, fee receipts, acknowledgments

If the building's packet orders those differently, the building wins. A deeper note on PDF order, dividers, and bookmarks is live.

Assembly bounce-backs vs financial weakness — keep them separate

Two different failures get called "the package was rejected." Only one of them is the assembler's to prevent. The taxonomy is why board packages get bounced.

Assembly / completeness issues — missing pages, incomplete forms, financial-statement figures that do not match the statements, wrong fee checks, late references, sections in the wrong order. These burn days and, on covered buildings after Local Law 58's effective date, can restart acknowledgment clocks. They are process failures. Assembly is deal risk; treat it that way.

Financial / board judgment issues — reserves, debt-to-income, credit, use of the apartment, interview impressions. Boards and counsel own those outcomes. A prettier PDF does not create post-closing liquidity. Do not promise an interview, an approval, or a closing date. Buyer-facing pieces that dwell on interview wardrobe or culture fit (for example) are a different job than assembly.

Interview answers should stay consistent with the file you submitted. That is a one-line reminder, not a coaching guide.

Resubmission cost

An incomplete first submission costs calendar. On covered co-ops, a new submission can mean a new completeness acknowledgment. That is why the QC pass exists. It is not a reason to invent deal-specific dates from the statute. Ask counsel how the clock works on this file.

Running this workflow in BoardReady (optional tooling)

If you would rather not run the sequence in a 40-tab spreadsheet, BoardReady follows the same steps the article just described. Product claims below match BoardReady — NYC co-op board package software — nothing more.

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.

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

BoardReady does not submit to the board, collect fees, or replace the managing agent's portal. It does not replace your attorney. It does not guarantee approval.

FAQ

The workflow, once

• Start from this building's current transfer requirements — not a generic list and not the last sale.
• Classify every incoming file against a requirement; keep missing items visible; chase third-party lag items first.
• Treat the financial statement as the spine: every material line traces to a supporting statement.
• QC for completeness before the managing agent sees the file, including every page of every statement.
• Assemble one deliverable in the building's order, with dividers and bookmarks, in the format the agent asked for.

Prefer software to a 40-tab spreadsheet? NYC co-op & condo board package software follows this same sequence. 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