Guides · BR-07

Why Board Packages Get Bounced: Assembly Errors vs Financial Weakness

This page is for agents, transaction coordinators, and attorneys who are about to hit send — or who just got a "please resubmit" email. Buyers who caused the gap (missing pages, late letters) can use the punch list. It is not interview coaching, and it is not "will my DTI pass."

Most early stalls are completeness and consistency. The file never reaches a board vote. Separating a bounce from a rejection changes how you QC. BoardReady, if you use it, is built to reduce preventable assembly bounce-backs. It is not approval insurance.

This is not legal, financial, or tax advice. Practitioner "most common" lists below are attributed to those writers — not BoardReady research, and not rejection-rate statistics.

Bounce vs board rejection — keep them separate

Bounce / return / incomplete. The managing agent or processor will not treat the file as ready — missing item, wrong format, inconsistent figures. Not a final "no" from directors. Nacmias describes a mechanical bounce on a single missing item. Milton Coste notes that incomplete packages are returned rather than queued; the agent is not your document chaser.

Board rejection / denial / conditions. Substance and judgment after a complete (or deemed complete) file — finances, use of the apartment, interview. A prettier PDF does not fix thin reserves.

Why the mix-up hurts clients

Teams rewrite the cover letter when they needed page 5 of 5. Or they panic about "rejection" when the email is a fixable bounce. Name the failure correctly and you fix the right thing.

Local Law 58 nod

Covered buildings may send written missing-item lists. That is still a completeness process, not a board vote. Assembler detail lives in Local Law 58: what "complete" means. Not legal advice; ask counsel about coverage and clocks.

Common assembly errors that get packages returned

Milton Coste's "mistakes that stall packages" is one practitioner list — his experience, not a BoardReady census. Paraphrased:

Partial statements (missing pages, including blank).
Unexplained large deposits.
Late reference letters.
A financial statement that does not reconcile to the statements.
Wrong fee checks or payees.
An overselling cover letter (more a board-tone issue than an agent bounce — keep it brief).
Waiting on the loan commitment and submitting incomplete anyway.

Themes that show up in Hauseit, Anthony Park, Gina Sabio, and Yeo as well:

Blank application fields not marked N/A.
Wrong section order / no navigation (PDF assembly).
Stale statements after a long commitment wait — refresh.
Over-redaction.
Missing schedules on tax returns.
Seller signature pages and seller fees not coordinated.

Missing pages

"Page 3 of 5" without pages 4–5 returns the package. Milton treats that as a reason the whole file comes back; Yeomakes the same request. Some product guides call missing pages the "#1 reason" for resubmission. If you see that language elsewhere, it is theirclaim. BoardReady does not publish a ranked "top reason" and does not invent one.

Financial-statement mismatch as a completeness / consistency issue

Treat a financial statement that does not match the statements as something agents flag early. Hauseit says the form must correspond to supporting documents. Milton uses a worked mismatch example (his numbers, not a client of ours). The deep method is tie every line to a dated statement.

Here: date alignment matters; unexplained deposits belong in the package before anyone asks; do not invent a liquidity-month or DTI rule to "fix" a mismatch. Clearing the mismatch prevents a consistency bounce. It does not underwrite the buyer.

Forms, fees, order, and third-party lag

Forms. Every blank handled — filled or marked N/A the way the form allows.

Fees. Exact amounts and payees from the current instructions (Milton flags wrong checks).

Order and format. Building order, divider pages, bookmarks as the agent wants them (BR-06). Confirm physical versus digital rules. Starting from the wrong checklist — last year's sale, a blog list — is its own bounce reason (extract this building's packet).

Third-party lag. References, employment letters, commitment — the package is incomplete until they are present. Nacmias on timing: missing items stall the clock. The full gate narrative is what managing agents check.

Pre-submit QC — run the bounce checklist yourself

Checklist = current building transfer requirements.
No row "missing" without an owner and ETA — ideally zero missing before send.
All multi-page statements and returns complete.
Financial statement tied to dated statements.
Large deposits explained.
Forms signed; N/A where needed.
Fees and payees correct.
Order / dividers / bookmarks per the agent.
Commitment and references in hand.
Proof of delivery retained.

QC before submit is the habit. Visible missing items beat hoping the agent does not notice.

How BoardReady reduces assembly bounce risk (not approval risk)

Product claims below match the homepage — nothing more.

Missing items stay visible against the extracted building checklist.
Balances are tied to the financial statement first.
One PDF in the building's order, with divider pages.

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 helps catch assembly gaps before managing-agent review. It does notguarantee no bounce, no rejection, or an approval. It does not fix weak finances, DTI, or reserves. It does not invent a "#1 reason packages fail."

QC before the managing agent does

Keep missing items visible and balances tied to the financial statement on BoardReady. Built to reduce preventable bounce-backs — not to promise a board yes.

NYC co-op & condo board package software →·Walk through the demo

FAQ

Why was my board package returned?

Usually incompleteness or inconsistency — missing pages, forms, fees, a financial-statement mismatch, or format. Ask for the written deficiency list. That email is not a director vote.

Is that the same as board rejection?

No. A bounce means the file was not treated as ready. A rejection is substance and judgment after a complete (or deemed complete) file. Do not collapse the two.

Do bank statements need every page including blank ones?

Yes, when the statement is multi-page. Include every page the issuer produced, including blank or "intentionally left blank." Missing pages commonly trigger a return.

What if the financial statement doesn’t match the statements?

Fix the tie-out before you resubmit. Agents and boards question mismatches. Use the line-by-line method. Do not invent a liquidity rule to paper over the gap.

What mistakes are most common?

Practitioner lists — Milton Coste and others — cite missing pages, unexplained deposits, late references, unreconciliation, wrong fees, and submitting while the commitment is still out. Those are their observations. BoardReady does not publish a ranked "top reason."

How do I prevent bounces?

Start from this building's checklist. Keep missing items visible. Tie the financial statement to dated statements. Assemble an ordered PDF. Do not submit early on third-party lag.

Will BoardReady stop rejections?

No. It targets assembly completeness and consistency risk. A clean package improves process odds and guarantees nothing — including whether finances meet this building's standards.

Name the failure, then fix it

Bounce ≠ board rejection. Completeness first; substance later.
Missing pages, mismatches, fees, order, and third-party lag are assembler problems.
Thin reserves and interview judgment are not solved by a prettier PDF.
QC against this building's list until missing items are visible and then gone.

Deep dives: the agent gate, tie-out, PDF order, and the full workflow. Prefer software? BoardReady keeps gaps visible. A clean package improves process odds and guarantees nothing.

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

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