Deliverable guide

What this is

The 4% Bond Pathway Intake Memo is the first discipline check on whether the project is actually ready to be managed as a NY 4% / tax-exempt bond transaction. It should document the early assumptions that shape the map: issuer path, HFA/HCR route, bond-financing strategy, volume-cap questions, TEFRA responsibility, threshold evidence, good-cost evidence, and the branch decisions that remain open.

Why it matters

At intake, the danger is not that the team lacks activity; it is that the transaction is being treated like a generic LIHTC opportunity before the public-approval, issuer, bond-financing, and evidence path is real. This memo should make the earliest financing assumptions visible enough for leadership to know what is known, what is only assumed, and what needs counsel, tax, agency, issuer, or expert review.

Where this sits in the pathway

• Comes after: initial project intake, sponsor/borrower assumptions, and early NY4 applicability screening.
• Feeds into: issuer-path confirmation, volume-cap / TEFRA planning, HFA/HCR route decisions, capital-stack strategy, and the first Gate-readiness baseline.

Before you treat it as complete

• The memo names the likely issuer path, HFA/HCR route, tax-exempt bond strategy, TEFRA responsibility, and volume-cap question.
• Bond-financing threshold and good-cost assumptions are flagged for the proper reviewer rather than treated as settled.
• Open branch decisions have owners, dates, and a clear downstream consequence.

Watchouts

• Do not use this memo as proof that the issuer path, volume cap, TEFRA sequence, threshold evidence, or good-cost evidence is accepted.
• Escalate if the roadmap depends on a branch decision that has not been reviewed by the right counsel, agency, issuer, or tax reviewer.

Completion standard

The 4% Bond Pathway Intake Memo is complete when it captures the current transaction assumptions and makes the unresolved decisions explicit. The memo should identify the likely issuer path, HFA/HCR route, bond-financing strategy, volume-cap question, TEFRA responsibility, threshold-evidence status, good-cost evidence status, and review owners for any open branch. A polished intake memo is not enough if the issuer role, volume-cap path, TEFRA sequence, bond-test support, or counsel / tax / agency review status remains hidden. Keep the Deliverable open until unresolved assumptions are either confirmed, flagged for expert review, or carried forward with owner, due date, and Gate consequence.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Tax-exempt bond threshold assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Owner NY4 Applicability Decision Register is the control record for deciding which NY4 map content belongs in the first Owner import candidate. It is not a generic proof file. It is the place where Chris can see which Tasks, Deliverables, Documents, Gates, and guidance modules are included, held, excluded, conditional, expert-review required, or dependent on project facts.

Why it matters

This matters because the full NY4 bond map is broader than the first Owner import candidate. Without a decision register, the team can accidentally turn useful template logic into live scope before the project facts, issuer path, branch decisions, and expert-review posture support it.

Where this sits in the pathway

• Comes after: Owner project intake, initial applicability screening, and issuer-path assumptions.
• Feeds into: first-import Include / Hold / Exclude decisions, scope control, and Chris review.

Before you treat it as complete

• Current Owner intake facts, issuer-path assumptions, lifecycle stage, branch decisions, funding sources, construction type, environmental triggers, and expert-review flags are visible.
• Each affected row has an Include / Hold / Exclude decision with a reason and owner.
• Rows held for applicability are separated from rows ready for the first import candidate.

Watchouts

• The danger is treating “possibly relevant” as import-ready.
• A copied template row, a preliminary branch assumption, or a verbal understanding of issuer path does not prove that the row belongs in the first import candidate. The register must show the decision, the reason, the owner, and what would change the decision.

Completion standard

Complete only when Owner intake facts are current, each reviewed NY4 row has an Include / Hold / Exclude or conditional decision, every decision has a rationale, unresolved expert-review items are carried forward, and the import-candidate scope shows which Tasks, Deliverables, Documents, Gates, and guidance modules can safely move into the first project candidate.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Other assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Borrower / Sponsor Structure and Team Qualification Matrix is the evidence record for whether the development team story is financeable, reviewable, and internally coherent. It should show borrower entity, ownership and control, sponsor and affiliate structure, guaranty or support parties, entity readiness, team experience, disclosures, and questions that HFA/HCR, lender, investor, syndicator, or counsel reviewers are likely to ask.

Why it matters

This matters because a project can have a named sponsor and still lack a reviewer-ready borrower, ownership, support-party, capacity, or disclosure story. Entity structure and team qualification issues can become underwriting, investor, counsel, or closing problems if they are discovered late.

Where this sits in the pathway

• Comes after: project intake, borrower / sponsor scoping, and development-team qualification review.
• Feeds into: HFA/HCR application support, lender / investor diligence, disclosure review, and closing responsibility mapping.

Before you treat it as complete

• Borrower ownership, control, sponsor / affiliate structure, guaranty or support parties, and entity readiness are documented.
• Team experience, capacity, relationship disclosures, and support-party commitments are visible enough for reviewer reliance.
• Open HFA/HCR, lender, investor, syndicator, or counsel questions have owners and next steps.

Watchouts

• A roster of names, an org chart draft, or a development-team slide does not prove sponsor capacity.
• The file must connect team identity to ownership/control evidence, support-party commitments, qualifications, disclosures, and reviewer acceptance or unresolved questions.

Completion standard

Complete only when borrower entity, ownership/control, sponsor, GP/managing member, guarantor/support-party, affiliate, and development-team information is current, internally consistent, tied to qualification evidence, and any capacity, disclosure, support, or reviewer issue is assigned with a resolution path.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Other assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The NY4 Critical Path and Gate Readiness Baseline is the integrated management calendar for the deal. It should show how the NY4 pathway is sequenced, which Gates matter, which outside calendars control timing, and which workstreams can move or block the project.

Why it matters

This matters because a NY4 bond deal is controlled by external calendars as much as internal effort. Leadership needs a baseline that shows which Gates, dependencies, proof packages, and outside-party review cycles actually drive timing.

Where this sits in the pathway

• Comes after: early pathway intake, milestone sequencing, and branch-decision scoping.
• Feeds into: Gate readiness baseline, issuer / agency / counsel calendars, closing schedule, and PM execution cadence.

Before you treat it as complete

• Internal target dates are separated from outside-party dates and calendar constraints.
• Gate sequence, dependencies, and critical workstreams are visible across agency, issuer, diligence, closing, construction, cost certification, Form 8609, investor equity, and compliance handoff.
• Schedule risks have owners, next steps, and escalation paths for leadership review.

Watchouts

• A Gantt chart or list of target dates is not a critical path.
• The file must show what actually controls timing, what proof packages move each Gate, and which outside-party review cycles can change the schedule.

Completion standard

Complete only when an integrated schedule, Gate sequence, dependency map, outside-party review windows, closing-critical path, schedule-risk owners, and leadership acceptance of the baseline logic are documented and current.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Other assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Affordability / Set-Aside and Policy Fit Memo is the public-purpose and agency-positioning record for the project. It explains whether the affordability structure, set-asides, population served, preservation / new-construction / rehab strategy, financing sources, and agency narrative support the path being presented.

Why it matters

This matters because a project can look financially plausible and still have a weak public-purpose or agency-positioning story. HFA/HCR, leadership, lenders, investors, and community stakeholders need the affordability structure, set-asides, project facts, and policy narrative to agree.

Where this sits in the pathway

• Comes after: project concept review, affordability assumptions, set-aside strategy, and public-purpose narrative.
• Feeds into: policy-fit positioning, HFA/HCR application narrative, underwriting support, and leadership approval story.

Before you treat it as complete

• Affordability assumptions, set-asides, target population, project scope, and financing-source alignment are current.
• The policy-fit rationale ties the public-purpose story to actual project facts and agency positioning.
• Unresolved scoring, public-purpose, approval, underwriting, or leadership-confidence questions are documented.

Watchouts

• A general affordability narrative does not prove policy fit.
• The memo must connect the public-purpose story to real project facts, funding sources, agency positioning, and open questions that could affect approval, underwriting, or leadership confidence.

Completion standard

Complete only when affordability / set-aside assumptions, population served, preservation / rehab / new-construction strategy, financing-source alignment, HFA/HCR policy-positioning notes, and unresolved policy/scoring/public-purpose questions are current, reconciled, and assigned where open.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Other assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Site Control and Acquisition Path Checklist is the proof file for whether the project actually controls the site on terms the NY4 execution plan can rely on. It should show the site-control instrument, acquisition path, key dates, seller obligations, assignment or affiliate issues, title exceptions that affect control, and any conditions that could change closing or application posture.

Why it matters

A site can look available in a pipeline discussion and still be unusable for financing, agency review, or closing if the control right is weak, expiring, conditional, or inconsistent with the ownership structure. This checklist gives the PM and leadership a single place to see whether the site-control story is executable or only assumed.

Where this sits in the pathway

• Comes after: site screening, borrower / sponsor structure, and early site-control term review.
• Feeds into: title / survey / legal description clearance, application site-control evidence, and closing readiness.

Before you treat it as complete

• The operative agreement, amendments, extensions, and critical dates are current.
• Acquisition obligations, deposits, approvals, assignments, and closing conditions are tied to owners and deadlines.
• Any mismatch between borrower structure, seller terms, legal description, title, survey, or municipal approvals is flagged.

Watchouts

• Do not treat a signed LOI, stale PSA, verbal extension, or unresolved title condition as site control that can support the NY4 path.
• The checklist is complete only when the right to proceed is document-supported, calendar-controlled, and connected to downstream financing and Gate decisions.

Completion standard

Site Control and Acquisition Path Checklist is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show site control, title, survey, zoning, municipal approvals, PILOT / tax exemption, and acquisition-path evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if borrower counsel, title company, surveyor, municipality, zoning counsel, or acquisition lead has not accepted the point it controls, if linked Documents are stale, or if a remaining real-estate diligence exception could affect site feasibility, closing readiness, lender diligence, and municipal approval timing. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Environmental / SHPO / SEQRA / NEPA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-020, Site Control, Due Diligence & Environmental Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Title / Survey / Legal Description Clearance Matrix is the control record for title, survey, legal-description, easement, encumbrance, endorsement, zoning-table, and closing-counsel issues that must be cleared or knowingly accepted. It should translate title and survey review into an operating matrix the PM can manage.

Why it matters

Title and survey problems can surface late as “legal” details, but they often control lender diligence, investor comfort, building permits, tax parcels, access, utility rights, insurance, and closing readiness. This matrix should show which exceptions are acceptable, which require correction, and which could block or delay closing.

Where this sits in the pathway

• Comes after: site control and acquisition path, title commitment / survey ordering, and legal-description review.
• Feeds into: closing due diligence clearance, lender / counsel review, and construction closing checklist.

Before you treat it as complete

• Current title commitment, survey, legal description, tax parcel, and endorsement requests are reconciled.
• Counsel comments, surveyor responses, and unresolved exceptions are logged with owners and due dates.
• Any item affecting access, use, zoning, affordability restrictions, financing, or construction start is escalated.

Watchouts

• A title commitment or survey upload is not clearance.
• The matrix is reliable only when exceptions have been reviewed, required endorsements are identified, legal descriptions are consistent, and unresolved matters are visible before the closing Gate.

Completion standard

Title / Survey / Legal Description Clearance Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show site control, title, survey, zoning, municipal approvals, PILOT / tax exemption, and acquisition-path evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if borrower counsel, title company, surveyor, municipality, zoning counsel, or acquisition lead has not accepted the point it controls, if linked Documents are stale, or if a remaining real-estate diligence exception could affect site feasibility, closing readiness, lender diligence, and municipal approval timing. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Closing / legal opinions assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-020, Site Control, Due Diligence & Environmental Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Closing Due Diligence Clearance Package is the clearance record for closing due-diligence items such as title, survey, zoning / permit evidence, insurance, legal documents, opinions, certificates, conditions, and reviewer exceptions.

Why it matters

This package helps leadership distinguish a closing file that is assembled from one that is actually clear enough for closing reliance. It should show what remains unresolved, who controls it, and whether any item can block the Construction Financing Closing & Start Gate.

Where this sits in the pathway

• Comes after: title, survey, permit / zoning evidence, insurance, legal-document review, and closing condition tracking
• Feeds into: closing checklist signoff, bond / construction closing readiness, and construction-start authorization

Before you treat it as complete

• Title, survey, insurance, permit, zoning, legal-document, opinion, certificate, and closing-condition items are tracked by status.
• Counsel, lender, investor, agency, title, surveyor, insurer, and borrower-side comments are separated from internal assembly work.
• Open exceptions show owner, due date, reviewer, waiver / acceptance status, and closing consequence.
• Documents are current enough to support the closing Gate and downstream construction start.

Watchouts

• Funds-flow and wire mechanics belong in the closing sources / escrow package; do not let them obscure due-diligence clearance.
• Do not mark this complete because documents were received; they must be cleared, accepted, or escalated.

Completion standard

Closing Due Diligence Clearance Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show title, ALTA survey, zoning, permits, insurance, bond documents, escrow, wires, counsel signoffs, and closing-condition evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if title company, surveyor, lender counsel, bond counsel, investor counsel, HFA/HCR, issuer, insurance broker, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining closing-condition exception could affect construction/bond closing readiness, funding mechanics, lender/investor approval, and title/counsel clearance. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive TEFRA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-070, Bond Issuance, TEFRA, Volume Cap & Construction Closing Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Zoning / Entitlement / Permit Strategy Memo is the proof artifact that summarizes zoning position, entitlement path, municipal approval requirements, permit sequence, and open land-use issues for the current plan set.

Why it matters

This memo should tell the team whether the project can proceed as designed, what approvals are still needed, and which municipal or zoning issues could affect schedule, underwriting, or Gate readiness. It is not a substitute for title or survey diligence.

Where this sits in the pathway

• Comes after: zoning / land-use analysis, preliminary design assumptions, municipal outreach, and permit-path review
• Feeds into: site-control diligence, design feasibility, application strategy, and the Site Control, Due Diligence & Environmental Readiness Gate

Before you treat it as complete

• The memo ties zoning district, use, density, height, parking, setbacks, lot coverage, and nonconformities to the current plan set.
• Entitlement, variance, special permit, site-plan, as-of-right, and building-permit steps are identified with owner and timing.
• Municipal, zoning counsel, or land-use reviewer comments are logged with status and next action.
• Open land-use or permit issues are linked to schedule, Deliverables, Documents, and Gate impact.

Watchouts

• A clean title commitment or ALTA survey does not prove zoning or permit readiness.
• Do not treat this memo as complete while the entitlement path is still a side conversation.

Completion standard

Zoning / Entitlement / Permit Strategy Memo is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show site control, title, survey, zoning, municipal approvals, PILOT / tax exemption, and acquisition-path evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if borrower counsel, title company, surveyor, municipality, zoning counsel, or acquisition lead has not accepted the point it controls, if linked Documents are stale, or if a remaining real-estate diligence exception could affect site feasibility, closing readiness, lender diligence, and municipal approval timing. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Closing / legal opinions assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-020, Site Control, Due Diligence & Environmental Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Municipal Approval / PILOT / Tax Exemption Tracker is the local-approval control record for municipal actions that can affect feasibility, closing, operations, or long-term affordability. It should track PILOT or tax exemption status where applicable, board or council steps, municipal agreements, approvals, filing dates, open conditions, and responsible parties.

Why it matters

Local approval risk is easy to underestimate because it often sits outside the core financing checklist. A PILOT, tax exemption, local consent, municipal agreement, or public approval can change underwriting, operating expenses, closing timing, political risk, and Gate readiness.

Where this sits in the pathway

• Comes after: zoning / entitlement strategy, local approval scoping, and tax / PILOT assumption review.
• Feeds into: operating underwriting, HFA/HCR application support, municipal condition tracking, and closing readiness.

Before you treat it as complete

• Required municipal actions and approval bodies are identified.
• Submission dates, hearing or board dates, resolutions, agreements, and conditions are tracked.
• Operating-budget assumptions reflect the current tax / PILOT position; Open municipal conditions have owners, next steps, and escalation paths.

Watchouts

• Do not treat a meeting, draft agreement, or informal municipal support as approval.
• The tracker is complete only when the required action is documented, conditions are understood, and downstream underwriting or closing reliance is updated.

Completion standard

Municipal Approval / PILOT / Tax Exemption Tracker is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show site control, title, survey, zoning, municipal approvals, PILOT / tax exemption, and acquisition-path evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if borrower counsel, title company, surveyor, municipality, zoning counsel, or acquisition lead has not accepted the point it controls, if linked Documents are stale, or if a remaining real-estate diligence exception could affect site feasibility, closing readiness, lender diligence, and municipal approval timing. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Environmental / SHPO / SEQRA / NEPA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-020, Site Control, Due Diligence & Environmental Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Phase I ESA and Environmental Diligence Package is the evidence file that tells the team whether the site has environmental conditions that could affect site control, HFA/HCR underwriting, lender or investor due diligence, closing timing, or the ability to start construction. It should not be treated as a passive report upload. It is the working record of environmental risk, reliance, follow-up scope, and clearance status.

Why it matters

In a NY 4% / tax-exempt bond transaction, environmental issues rarely stay isolated. A recognized environmental condition, stale report, missing reliance letter, unresolved Phase II question, SHPO/CRIS issue, SEQRA or NEPA trigger, or remediation scope can move directly into agency comments, lender conditions, investor diligence, budget pressure, and closing lag.

Where this sits in the pathway

• Comes after: Complete Phase I ESA and environmental due diligence path (NY4-T-010); Resolve Phase II; NY4-M-020, Site Control, Due Diligence & Environmental Readiness
• Feeds into: Environmental and Site Readiness Gate; related Task status; next reviewer / handoff

Before you treat it as complete
- The current Phase I is in hand, dated, and usable for the transaction.
- Reliance, user questionnaire, and report-recipient requirements are clear.
- RECs, controlled RECs, historical RECs, data gaps, or follow-up recommendations are logged with owners.
- Any Phase II, remediation, SHPO/CRIS, SEQRA, NEPA, floodplain, wetlands, noise, or similar branch decision is documented.
- HFA/HCR, lender, investor, and counsel comments are either closed or assigned with dates.

Watchouts
- A clean-looking executive summary is not the same as reviewer acceptance.
- A report can be received but still stale, non-reliance-ready, or missing a required branch decision.

Next dependencies
- Site control and due diligence readiness.
- HFA/HCR application and underwriting responses.
- Bond / construction closing due diligence and environmental conditions.

Completion standard

Complete only when the Phase I ESA and Environmental Diligence Package is current, transaction-usable, and linked to the environmental due-diligence workstream. Required proof includes the final Phase I, reliance or user documentation where required, an issue log for RECs or data gaps, and documented branch decisions for Phase II, remediation, SHPO/CRIS, SEQRA, NEPA, floodplain, wetlands, noise, or similar triggers if applicable.

Do not mark complete if the report is draft-only, stale, missing reliance, missing reviewer distribution, unresolved by environmental counsel or lender/investor diligence, or silent on a known branch issue. Open environmental conditions must have owners, due dates, budget/timing implications, and Gate impact before the package should be treated as ready.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Environmental / SHPO / SEQRA / NEPA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-020, Site Control, Due Diligence & Environmental Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Environmental Condition Resolution Plan is the action-oriented record for environmental issues that require follow-up beyond initial diligence. It should identify recognized environmental conditions, Phase II or remediation needs, reliance issues, mitigation steps, agency or lender review comments, budget exposure, and responsible parties.

Why it matters

Environmental findings only become manageable when the team knows what must be resolved, who controls the resolution, and whether the issue affects underwriting, site control, closing, construction start, or cost. This plan turns consultant findings into a sequence of decisions and proof.

Where this sits in the pathway

• Comes after: Phase I ESA findings, environmental diligence, and condition discovery.
• Feeds into: remediation planning, HCR / lender / investor environmental review, and closing or construction-start readiness.

Before you treat it as complete

• Each environmental issue is tied to a recommended action, owner, due date, reviewer, and budget implication.
• Reliance letters, report currency, remediation proposals, agency comments, and lender / investor conditions are visible.
• Unresolved issues are mapped to the Gate or financing step they may block.

Watchouts

• A Phase I report does not resolve environmental risk by itself.
• The plan is complete only when follow-up items are accepted, waived, scoped, budgeted, or explicitly carried forward with an owner and consequence.

Completion standard

Environmental Condition Resolution Plan is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show Phase I reliance, REC follow-up, SHPO/CRIS status, SEQRA/NEPA applicability, floodplain / wetlands / resilience evidence, and reviewer acceptance, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if environmental consultant, HFA/HCR reviewer, lender, investor, SHPO, municipality, or counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining environmental clearance exception could affect feasibility, agency review, lender/investor diligence, and closing conditions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Environmental / SHPO / SEQRA / NEPA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-020, Site Control, Due Diligence & Environmental Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Historic / SEQRA / NEPA Clearance Matrix is the review-control record for historic preservation, environmental review, and federal or state clearance paths that may apply to the deal. It should show SHPO / CRIS status, SEQRA lead-agency or determination status, NEPA triggers where applicable, open comments, required evidence, and timing risk.

Why it matters

Historic and environmental-review clearance can become a hard external dependency even when the rest of the financing path appears ready. This matrix helps the team distinguish a normal consultant task from a clearance item that can delay application, board action, closing, construction start, or funding release.

Where this sits in the pathway

• Comes after: historic, SHPO / CRIS, SEQRA, NEPA, and environmental applicability screening.
• Feeds into: agency application support, environmental clearance evidence, Board / closing conditions, and construction-start readiness.

Before you treat it as complete

• Applicable review paths are identified and non-applicable paths are documented.
• Submissions, determinations, correspondence, clearances, mitigation commitments, and open comments are tracked.
• Any clearance that depends on an agency, consultant, municipality, or funding source is tied to the schedule.

Watchouts

• Do not count a draft submission, consultant assumption, or “no issue expected” note as clearance.
• The matrix is reliable only when the actual determination, correspondence, or waiver status is documented and linked to the next Gate.

Completion standard

Historic / SEQRA / NEPA Clearance Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show Phase I reliance, REC follow-up, SHPO/CRIS status, SEQRA/NEPA applicability, floodplain / wetlands / resilience evidence, and reviewer acceptance, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if environmental consultant, HFA/HCR reviewer, lender, investor, SHPO, municipality, or counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining environmental clearance exception could affect feasibility, agency review, lender/investor diligence, and closing conditions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Environmental / SHPO / SEQRA / NEPA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-020, Site Control, Due Diligence & Environmental Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Design Team Engagement and Coordination Protocol is the operating protocol that shows who is responsible for design decisions, deliverables, review cycles, coordination cadence, and issue escalation.

Why it matters

Design risk is not only whether plans exist. A NY4 deal needs clear design roles, consultant scopes, communication routines, and decision authority so cost, sustainability, accessibility, permitting, HFA/HCR exhibits, lender / investor diligence, and construction readiness do not drift apart.

Where this sits in the pathway

• Comes after: architect / engineering engagement, scope definition, sustainability and accessibility requirements, and preliminary design planning
• Feeds into: preliminary plans, development budget, permit strategy, design review, and the Design, Scope, Cost and Basis Readiness Gate

Before you treat it as complete

• Architect, engineer, consultant, sustainability, accessibility, cost-estimate, and owner-side roles are documented.
• Deliverable dates, meeting cadence, review cycles, issue logs, and escalation routes are clear.
• Design comments are tied to budget, basis, permitting, HFA/HCR exhibits, sustainability, accessibility, and lender / investor needs.
• Open consultant or scope questions have owners, dates, and downstream consequences.

Watchouts

• This protocol does not prove the budget is feasible or that the plans are approved.
• Do not let a signed proposal substitute for an operating cadence the PM can manage.

Completion standard

Design Team Engagement and Coordination Protocol is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive design / sustainability / construction assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Preliminary Plans and HCR Design Compliance Package is the plan-set and design-compliance proof package for the current NY4 submission stage. It should connect drawings, unit mix, building scope, design standards, HCR requirements, accessibility, sustainability, site constraints, and cost assumptions into one reviewable package.

Why it matters

Preliminary plans drive more than design review. They affect construction cost, eligible basis, marketability, accessibility, permit strategy, agency comments, lender / investor diligence, and whether the project narrative matches the actual building program.

Where this sits in the pathway

• Comes after: design-team engagement, site constraints, HCR design standards, and preliminary scope assumptions.
• Feeds into: HFA/HCR application exhibits, cost feasibility, accessibility review, and design compliance updates.

Before you treat it as complete

• The plan set is current, dated, and aligned with the development budget and pro forma.
• HCR design requirements, accessibility items, sustainability assumptions, and scope changes are flagged.
• Open design comments have owners, due dates, and cost or schedule consequences.

Watchouts

• A drawing set is not a compliant package merely because it exists.
• This package is complete only when the plans are internally reconciled, reviewer issues are logged, and design changes have been reflected in budget, basis, and Gate readiness.

Completion standard

Preliminary Plans and HCR Design Compliance Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The HFA / HCR Financing Application Submission Package is the assembled agency-facing submission package for financing, underwriting, project facts, and required exhibits. It should show the final package version, upload / delivery status, supporting documents, reviewer comments, and unresolved exceptions.

Why it matters

A submission is not useful just because it was uploaded. The package must present a coherent deal: sources and uses, design scope, site control, environmental status, ownership, market support, affordability, and financing assumptions must align.

Where this sits in the pathway

• Comes after: application form matrix, exhibit assembly, owner assignments, and final submission readiness review.
• Feeds into: agency completeness review, underwriting questions, clarification response log, and feasibility / Board readiness.

Before you treat it as complete

• The submitted package is dated, version-controlled, and reconciled to the current deal model.
• Required exhibits and supporting documents are complete or clearly flagged.
• Post-submission corrections, agency questions, and completeness items are tracked.

Watchouts

• Do not treat “submitted” as “underwritable.”.
• The package is complete only when the team can explain what was submitted, what remains open, and how agency comments will be managed.

Completion standard

HFA / HCR Financing Application Submission Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show HFA/HCR application exhibits, underwriting assumptions, clarification comments, completeness responses, and current supporting evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if HFA/HCR reviewer, underwriter, borrower counsel, architect, lender, investor, or internal application lead has not accepted the point it controls, if linked Documents are stale, or if a remaining agency comment exception could affect application acceptance, underwriting progression, feasibility review, and approval-calendar readiness. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-050, HFA / HCR Application, Underwriting & Due Diligence Submission Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Sustainability / Resilience / IPNA Compliance Matrix is the control record for energy, resilience, green-building, IPNA, and physical-needs requirements that apply to the NY4 deal. It should identify required standards, third-party inputs, design decisions, scope implications, costs, reviewer comments, and unresolved compliance items.

Why it matters

Sustainability and resilience requirements often look like technical design details until they affect budget, scope, agency scoring or eligibility, construction documents, lender / investor diligence, and long-term operations. This matrix makes those obligations visible before they become late design revisions.

Where this sits in the pathway

• Comes after: preliminary plans, energy / resilience assumptions, IPNA or capital-needs inputs, and HCR sustainability requirements.
• Feeds into: application exhibits, design compliance review, scope / budget reconciliation, and construction closing conditions.

Before you treat it as complete

• Required standards and applicability assumptions are documented.
• IPNA, energy, resilience, consultant, and design-team inputs are reconciled to scope and budget.
• Open compliance items have owners, reviewer paths, and cost / schedule implications.

Watchouts

• Do not treat a consultant memo, preliminary checklist, or design intent as compliance proof.
• The matrix is ready only when obligations are mapped to evidence, open items are controlled, and design / budget impacts are visible.

Completion standard

Sustainability / Resilience / IPNA Compliance Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Compliance assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Development Budget and Cost Feasibility Package is the current cost-control file for whether the project’s scope, sources, uses, contingencies, escalation, soft costs, reserves, and financing assumptions still hold together. It should show the budget logic leadership is actually relying on.

Why it matters

A NY4 deal can advance on paper while the budget is drifting underneath it. Cost feasibility affects application credibility, underwriting, bond sizing, investor assumptions, eligible basis, subsidy need, closing conditions, and construction-start confidence.

Where this sits in the pathway

• Comes after: preliminary design, sources / uses, cost estimate, basis assumptions, and value-engineering review.
• Feeds into: capital-stack sizing, HFA/HCR underwriting, Credit Committee readiness, and final basis reconciliation.

Before you treat it as complete

• The budget version is dated and reconciled to the latest plans, scope, sources / uses, and pro forma.
• Hard cost, soft cost, contingency, escalation, reserves, and financing cost assumptions are visible.
• Material variances have owners, explanations, and decisions about whether scope, sources, or timing must change.

Watchouts

• A balanced spreadsheet is not feasibility.
• The package is reliable only when cost assumptions are supported, reconciled to the current scope, and tied to the financing and Gate decisions they affect.

Completion standard

Development Budget and Cost Feasibility Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive design / sustainability / construction assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Change Order / Contingency / Budget Variance Control Log is the construction-phase control log for approved and pending change orders, contingency use, budget variances, scope changes, and unresolved cost exposure.

Why it matters

This log shows whether construction cost movement is controlled enough to protect draw approvals, contingency adequacy, eligible basis, cost certification, investor confidence, and leadership visibility. It is not a preclosing feasibility file.

Where this sits in the pathway

• Comes after: construction start, GC contract setup, approved budget, draw workflow, and field-change management
• Feeds into: draw packages, cost certification, final basis review, equity-release conditions, and construction monitoring

Before you treat it as complete

• Approved, pending, disputed, and rejected change orders are listed with status and cost impact.
• Contingency balance, budget variance, allowances, savings, and scope changes reconcile to the current cost model.
• Required approvals from owner, architect, GC, construction manager, lender, investor, or agency are tracked.
• Open items show whether they affect schedule, draw approval, basis, or funding.

Watchouts

• An original budget or VE log does not prove construction-phase cost control.
• Do not close the log while pending changes are material to contingency, basis, or funding decisions.

Completion standard

Change Order / Contingency / Budget Variance Control Log is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show GC contract, notice-to-proceed, construction-start evidence, draw controls, change orders, monitoring, and property-management readiness, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if general contractor, architect, lender inspector, HFA/HCR construction staff, investor, property manager, or counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining construction-start or draw-control exception could affect construction monitoring, draw release, change-order exposure, lease-up preparation, and cost-certification evidence. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Compliance assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-080, Construction Start, Draws & Compliance Controls Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Eligible Basis and Ineligible Cost Working File is the working file that separates eligible basis, ineligible costs, acquisition basis, rehab / new construction treatment, reserves, soft costs, exclusions, and reviewer-sensitive assumptions.

Why it matters

This file supports the credit and equity model. It should make clear which costs support basis, which are excluded, where acquisition or rehab treatment matters, and which assumptions still need CPA, tax counsel, investor, agency, or accounting review.

Where this sits in the pathway

• Comes after: development budget, cost estimate, acquisition / rehab scope, sources and uses, and basis assumptions
• Feeds into: cost certification, final basis approval, investor review, Form 8609 / final allocation support, and equity delivery

Before you treat it as complete

• Cost categories reconcile to the latest development budget, contracts, acquisition documents, plans, and sources and uses.
• Eligible, ineligible, acquisition, rehab, new construction, reserve, soft-cost, and excluded-cost treatment is clearly identified.
• CPA, tax counsel, investor, HFA/HCR, or internal comments are logged with owner and status.
• Open basis questions show potential credit, equity, or final-allocation consequences.

Watchouts

• A cost estimate or acquisition file does not prove basis treatment.
• Do not mark this complete until the working file can survive reviewer questions about classification and support.

Completion standard

Eligible Basis and Ineligible Cost Working File is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive design / sustainability / construction assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Accessibility and Fair Housing Design Compliance Matrix is the proof record for accessibility, fair housing, visitability, adaptability, and design-compliance requirements that apply to the building program. It should connect code / program requirements, plan annotations, consultant review, open comments, and responsibility for corrections.

Why it matters

Accessibility gaps can become agency comments, construction changes, legal exposure, budget pressure, lease-up issues, or compliance findings. The matrix keeps design compliance from being treated as a vague assurance buried in plans or consultant emails.

Where this sits in the pathway

• Comes after: preliminary plans, accessibility standards, fair-housing review, and design compliance scoping.
• Feeds into: HCR design review, application exhibits, construction documents, and compliance handoff.

Before you treat it as complete

• Applicable accessibility and fair-housing requirements are identified.
• Plan evidence, consultant review, corrections, and unresolved comments are tracked.
• Any design change affecting units, common areas, site circulation, cost, or schedule is escalated.

Watchouts

• Do not rely on a general design-team statement that the plans are compliant.
• The matrix is complete only when requirements are traceable to the current plans and unresolved corrections are owned.

Completion standard

Accessibility and Fair Housing Design Compliance Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Compliance assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Sources / Uses and Operating Pro Forma Package is the current financing and operating model package that reconciles sources, uses, rents, expenses, reserves, subsidy, debt, equity, and operating assumptions.

Why it matters

This package supports underwriting and leadership decisions before final basis is settled. Its job is to show whether the deal still pencils under current assumptions and reviewer comments, not to prove cost certification or final allocation readiness.

Where this sits in the pathway

• Comes after: capital stack modeling, rent / operating assumptions, lender and investor diligence, and budget updates
• Feeds into: bond sizing, HFA/HCR underwriting, lender / investor review, closing readiness, and later final-basis reconciliation

Before you treat it as complete

• Sources, uses, operating pro forma, rent assumptions, expense assumptions, reserve assumptions, and funding gaps reconcile to the latest model.
• Lender, investor, syndicator, HFA/HCR, subsidy, and internal comments are tracked with status.
• Changes that affect bond sizing, debt capacity, equity, subsidy, reserve structure, or closing feasibility are visible.
• Open assumptions are assigned before the package is used for approval or Gate reliance.

Watchouts

• A balanced pro forma does not prove final basis or cost certification acceptance.
• Do not treat this as complete while major assumptions are still unsupported or disconnected from reviewer feedback.

Completion standard

Sources / Uses and Operating Pro Forma Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive lender / investor assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-040, Capital Stack, Bond Issuer & Equity Strategy Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Development Budget and Cost Feasibility Package is the current cost-control file for whether the project’s scope, sources, uses, contingencies, escalation, soft costs, reserves, and financing assumptions still hold together. It should show the budget logic leadership is actually relying on.

Why it matters

A NY4 deal can advance on paper while the budget is drifting underneath it. Cost feasibility affects application credibility, underwriting, bond sizing, investor assumptions, eligible basis, subsidy need, closing conditions, and construction-start confidence.

Where this sits in the pathway

• Comes after: preliminary design, sources / uses, cost estimate, basis assumptions, and value-engineering review.
• Feeds into: capital-stack sizing, HFA/HCR underwriting, Credit Committee readiness, and final basis reconciliation.

Before you treat it as complete

• The budget version is dated and reconciled to the latest plans, scope, sources / uses, and pro forma.
• Hard cost, soft cost, contingency, escalation, reserves, and financing cost assumptions are visible.
• Material variances have owners, explanations, and decisions about whether scope, sources, or timing must change.

Watchouts

• A balanced spreadsheet is not feasibility.
• The package is reliable only when cost assumptions are supported, reconciled to the current scope, and tied to the financing and Gate decisions they affect.

Completion standard

Development Budget and Cost Feasibility Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive design / sustainability / construction assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The HFA / HCR Financing Application Submission Package is the assembled agency-facing submission package for financing, underwriting, project facts, and required exhibits. It should show the final package version, upload / delivery status, supporting documents, reviewer comments, and unresolved exceptions.

Why it matters

A submission is not useful just because it was uploaded. The package must present a coherent deal: sources and uses, design scope, site control, environmental status, ownership, market support, affordability, and financing assumptions must align.

Where this sits in the pathway

• Comes after: application form matrix, exhibit assembly, owner assignments, and final submission readiness review.
• Feeds into: agency completeness review, underwriting questions, clarification response log, and feasibility / Board readiness.

Before you treat it as complete

• The submitted package is dated, version-controlled, and reconciled to the current deal model.
• Required exhibits and supporting documents are complete or clearly flagged.
• Post-submission corrections, agency questions, and completeness items are tracked.

Watchouts

• Do not treat “submitted” as “underwritable.”.
• The package is complete only when the team can explain what was submitted, what remains open, and how agency comments will be managed.

Completion standard

HFA / HCR Financing Application Submission Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show HFA/HCR application exhibits, underwriting assumptions, clarification comments, completeness responses, and current supporting evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if HFA/HCR reviewer, underwriter, borrower counsel, architect, lender, investor, or internal application lead has not accepted the point it controls, if linked Documents are stale, or if a remaining agency comment exception could affect application acceptance, underwriting progression, feasibility review, and approval-calendar readiness. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-050, HFA / HCR Application, Underwriting & Due Diligence Submission Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Bond Issuer and Volume Cap Strategy Memo is the decision memo for how the transaction will move through the bond-issuer and volume-cap path. It should capture the selected or conditional issuer route, volume-cap status, approval sequence, counsel responsibilities, key calendar assumptions, and open branch decisions.

Why it matters

Issuer path and volume-cap strategy shape public approvals, TEFRA timing, bond sizing, tax-exempt financing evidence, closing calendar, and who owns critical documents. Leadership needs this memo to show whether the deal has an executable bond path or only a financing assumption.

Where this sits in the pathway

• Comes after: 4% pathway intake, issuer-path assumptions, bond sizing, volume-cap questions, and TEFRA responsibility review.
• Feeds into: issuer / HFA/HCR decisions, TEFRA evidence, bond document drafting, and closing readiness.

Before you treat it as complete

• Issuer route, volume-cap source, approval sequence, and expected evidence are documented.
• Bond counsel, borrower counsel, issuer, HFA/HCR, lender, investor, and tax reviewer roles are clear.
• Unresolved branch decisions are tied to dates, owners, and downstream consequences.

Watchouts

• Do not treat a preferred issuer path, preliminary conversation, or model assumption as a settled strategy.
• The memo is usable only when the path is reviewable and open decisions are controlled.

Completion standard

Bond Issuer and Volume Cap Strategy Memo is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Volume cap assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-040, Capital Stack, Bond Issuer & Equity Strategy Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The 4% Bond Pathway Intake Memo is the first discipline check on whether the project is actually ready to be managed as a NY 4% / tax-exempt bond transaction. It should document the early assumptions that shape the map: issuer path, HFA/HCR route, bond-financing strategy, volume-cap questions, TEFRA responsibility, threshold evidence, good-cost evidence, and the branch decisions that remain open.

Why it matters

At intake, the danger is not that the team lacks activity; it is that the transaction is being treated like a generic LIHTC opportunity before the public-approval, issuer, bond-financing, and evidence path is real. This memo should make the earliest financing assumptions visible enough for leadership to know what is known, what is only assumed, and what needs counsel, tax, agency, issuer, or expert review.

Where this sits in the pathway

• Comes after: initial project intake, sponsor/borrower assumptions, and early NY4 applicability screening.
• Feeds into: issuer-path confirmation, volume-cap / TEFRA planning, HFA/HCR route decisions, capital-stack strategy, and the first Gate-readiness baseline.

Before you treat it as complete

• The memo names the likely issuer path, HFA/HCR route, tax-exempt bond strategy, TEFRA responsibility, and volume-cap question.
• Bond-financing threshold and good-cost assumptions are flagged for the proper reviewer rather than treated as settled.
• Open branch decisions have owners, dates, and a clear downstream consequence.

Watchouts

• Do not use this memo as proof that the issuer path, volume cap, TEFRA sequence, threshold evidence, or good-cost evidence is accepted.
• Escalate if the roadmap depends on a branch decision that has not been reviewed by the right counsel, agency, issuer, or tax reviewer.

Completion standard

The 4% Bond Pathway Intake Memo is complete when it captures the current transaction assumptions and makes the unresolved decisions explicit. The memo should identify the likely issuer path, HFA/HCR route, bond-financing strategy, volume-cap question, TEFRA responsibility, threshold-evidence status, good-cost evidence status, and review owners for any open branch. A polished intake memo is not enough if the issuer role, volume-cap path, TEFRA sequence, bond-test support, or counsel / tax / agency review status remains hidden. Keep the Deliverable open until unresolved assumptions are either confirmed, flagged for expert review, or carried forward with owner, due date, and Gate consequence.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Tax-exempt bond threshold assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The TEFRA Notice / Hearing / Resolution Evidence Package is the proof file for the TEFRA sequence and related public-approval evidence. It should capture notice, hearing, approving resolution, issuer or governmental approvals, publication details, timing requirements, and open counsel or issuer comments.

Why it matters

TEFRA evidence is a discrete public-approval workstream, not a generic bond checklist item. If notice, hearing, resolution, or approval evidence is wrong or late, the bond path and closing calendar can be exposed.

Where this sits in the pathway

• Comes after: issuer-path confirmation, TEFRA calendar planning, public notice preparation, and approving-resolution coordination.
• Feeds into: bond counsel drafting, public-approval evidence, tax-exempt bond closing conditions, and final closing binder.

Before you treat it as complete

• Required notice, hearing, resolution, approval, and publication evidence is identified and tracked.
• Issuer, bond counsel, borrower counsel, and agency comments are logged.
• Timing assumptions are reconciled to the bond approval and closing schedule.

Watchouts

• A planned hearing or draft resolution is not TEFRA completion.
• The package is complete only when required evidence is in hand or open items are clearly owned and scheduled.

Completion standard

TEFRA Notice / Hearing / Resolution Evidence Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show title, ALTA survey, zoning, permits, insurance, bond documents, escrow, wires, counsel signoffs, and closing-condition evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if title company, surveyor, lender counsel, bond counsel, investor counsel, HFA/HCR, issuer, insurance broker, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining closing-condition exception could affect construction/bond closing readiness, funding mechanics, lender/investor approval, and title/counsel clearance. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive TEFRA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-070, Bond Issuance, TEFRA, Volume Cap & Construction Closing Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Tax-Exempt Bond Test and Good-Cost Tracker is the evidence tracker for bond-financing threshold assumptions, good-cost analysis, and related tax / bond counsel review items. It should show the numbers, source documents, reviewer comments, open questions, and timing needed to support the transaction path.

Why it matters

Bond-test and good-cost issues are not bookkeeping details. If the evidence is weak, stale, or reviewed too late, the deal can face closing risk, tax-certificate issues, investor concern, or final allocation complications.

Where this sits in the pathway

• Comes after: bond sizing, sources / uses, eligible-basis assumptions, and good-cost evidence planning.
• Feeds into: tax certificate preparation, investor / lender diligence, HFA/HCR underwriting, and final bond-financing evidence.

Before you treat it as complete

• Current calculations are tied to the latest sources / uses, eligible basis, draws, bond proceeds, and closing assumptions.
• Tax counsel, bond counsel, CPA, investor, and internal finance comments are logged.
• Open evidence gaps have owners and a clear effect on closing or final-basis work.

Watchouts

• A formula tab or preliminary schedule is not accepted evidence.
• The tracker is complete only when the relevant reviewers have a clear path to accept, revise, waive, or resolve the assumptions.

Completion standard

Tax-Exempt Bond Test and Good-Cost Tracker is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Tax-exempt bond threshold assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-040, Capital Stack, Bond Issuer & Equity Strategy Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Eligible Basis and Ineligible Cost Working File is the working file that separates eligible basis, ineligible costs, acquisition basis, rehab / new construction treatment, reserves, soft costs, exclusions, and reviewer-sensitive assumptions.

Why it matters

This file supports the credit and equity model. It should make clear which costs support basis, which are excluded, where acquisition or rehab treatment matters, and which assumptions still need CPA, tax counsel, investor, agency, or accounting review.

Where this sits in the pathway

• Comes after: development budget, cost estimate, acquisition / rehab scope, sources and uses, and basis assumptions
• Feeds into: cost certification, final basis approval, investor review, Form 8609 / final allocation support, and equity delivery

Before you treat it as complete

• Cost categories reconcile to the latest development budget, contracts, acquisition documents, plans, and sources and uses.
• Eligible, ineligible, acquisition, rehab, new construction, reserve, soft-cost, and excluded-cost treatment is clearly identified.
• CPA, tax counsel, investor, HFA/HCR, or internal comments are logged with owner and status.
• Open basis questions show potential credit, equity, or final-allocation consequences.

Watchouts

• A cost estimate or acquisition file does not prove basis treatment.
• Do not mark this complete until the working file can survive reviewer questions about classification and support.

Completion standard

Eligible Basis and Ineligible Cost Working File is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive design / sustainability / construction assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Tax / Regulatory / Good-Cost Closing Evidence Package is the closing evidence file for tax, regulatory, good-cost, bond, and related reviewer requirements that must be supportable at or before closing. It should gather the evidence reviewers need without mixing it into general closing noise.

Why it matters

Tax and regulatory evidence can control closing confidence even when business terms are settled. If good-cost support, tax certificate assumptions, regulatory obligations, or reviewer comments are unresolved, closing can be delayed or proceed with unacceptable uncertainty.

Where this sits in the pathway

• Comes after: bond document issue log, good-cost tracking, regulatory agreement planning, and tax-certificate evidence gathering.
• Feeds into: closing due diligence clearance, construction closing checklist, tax-exempt bond closing, and final good-cost evidence.

Before you treat it as complete

• Required tax, regulatory, good-cost, and bond evidence is identified.
• Counsel, CPA, investor, lender, issuer, and agency comments are logged.
• Open evidence gaps are tied to the tax certificate, closing checklist, or Gate consequence.

Watchouts

• Do not treat a generic closing binder as tax / regulatory clearance.
• This package is ready only when the relevant evidence can support the required reviewer reliance.

Completion standard

Tax / Regulatory / Good-Cost Closing Evidence Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show title, ALTA survey, zoning, permits, insurance, bond documents, escrow, wires, counsel signoffs, and closing-condition evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if title company, surveyor, lender counsel, bond counsel, investor counsel, HFA/HCR, issuer, insurance broker, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining closing-condition exception could affect construction/bond closing readiness, funding mechanics, lender/investor approval, and title/counsel clearance. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive 95-5 good costs assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-070, Bond Issuance, TEFRA, Volume Cap & Construction Closing Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Final Basis / Applicable Fraction / Sources-Uses Reconciliation is the final reconciliation file for eligible basis, applicable fractions, building-level allocations, final sources and uses, and the assumptions that feed final allocation and investor review. It should show how final numbers were derived and what changed from prior underwriting.

Why it matters

Final basis is where cost certification, tax credit calculation, investor assumptions, and agency review meet. If basis, fractions, sources / uses, or building-level data are inconsistent, the project can face Form 8609, final allocation, or equity-release delays.

Where this sits in the pathway

• Comes after: cost ledger closeout, CPA cost certification, investor basis review, and final sources / uses updates.
• Feeds into: final allocation request, Form 8609 owner review, final equity release, and permanent conversion conditions.

Before you treat it as complete

• Final costs, eligible / ineligible treatment, building allocations, applicable fractions, and sources / uses are reconciled.
• CPA, investor, tax counsel, agency, and internal comments are logged.
• Any unresolved variance is tied to final allocation or equity consequences.

Watchouts

• A final-looking schedule is not a final-basis position.
• The reconciliation is complete only when assumptions, supporting evidence, and reviewer comments are traceable.

Completion standard

Final Basis / Applicable Fraction / Sources-Uses Reconciliation is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show final cost ledger, CPA review, eligible basis, applicable fractions, good-cost evidence, and final sources / uses, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if CPA, investor / syndicator, tax counsel, HFA/HCR, lender, borrower counsel, or internal finance lead has not accepted the point it controls, if linked Documents are stale, or if a remaining cost-certification or basis exception could affect eligible basis, final allocation, Form 8609 inputs, equity adjusters, and investor final package readiness. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Cost certification assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-100, Placed in Service, Cost Certification & Final Basis Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Debt Commitment and Credit Enhancement Tracker is the control record for construction / permanent debt commitments, credit enhancement, lender conditions, rate / term assumptions, required approvals, and open financing requirements. It should show what is committed, what is conditional, and what can still move.

Why it matters

Debt can appear “in place” while important conditions remain unresolved. Lender requirements, credit enhancement, counsel review, collateral terms, reserves, insurance, title, and closing deliverables can all affect schedule and sources / uses.

Where this sits in the pathway

• Comes after: capital-stack strategy, lender / credit-enhancement outreach, and underwriting support.
• Feeds into: Credit Committee readiness, HFA Board readiness, construction closing checklist, and final funding mechanics.

Before you treat it as complete

• Each debt source is tied to current commitment status, terms, conditions, approvals, and expiration dates.
• Lender / credit enhancer comments and counsel requirements are tracked.
• Material changes are reconciled to the development budget, pro forma, bond sizing, and closing checklist.

Watchouts

• Do not treat a term sheet, draft commitment, or verbal lender comfort as closed financing.
• The tracker is reliable only when conditions and reviewer paths are visible and controlled.

Completion standard

Debt Commitment and Credit Enhancement Tracker is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive lender / investor assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-040, Capital Stack, Bond Issuer & Equity Strategy Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Credit Committee Readiness Package is the approval-readiness file for the materials, conditions, underwriting conclusions, and open issues needed before Credit Committee action. It should show whether the deal is ready to be presented, not just whether a meeting is approaching.

Why it matters

Credit Committee readiness depends on agency staff confidence, underwriting support, financing assumptions, conditions, and unresolved comments. Leadership needs to know whether the package can support approval or whether the meeting date is masking open issues.

Where this sits in the pathway

• Comes after: HFA/HCR underwriting response, feasibility review, open agency issues, and internal capital-stack review.
• Feeds into: Credit Committee decision, HFA Board readiness, PACB / State Comptroller / 42(m) tracking, and closing conditions.

Before you treat it as complete

• Required materials, staff comments, conditions, and underwriting items are tracked.
• Any issue affecting approval recommendation, timing, or conditions is visible.
• Board / PACB / 42(m) and closing dependencies are updated if committee readiness changes.

Watchouts

• A calendar date is not readiness.
• The package is complete only when the team can show the evidence and open issues that control Credit Committee action.

Completion standard

Credit Committee Readiness Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show Credit Committee, HFA Board, PACB, State Comptroller, 42(m) letter, and approval-condition evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if HFA/HCR staff, agency counsel, PACB / State Comptroller process owner, bond counsel, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining approval-calendar exception could affect public approval readiness, closing calendar, conditions management, and leadership escalation. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive 42(m) assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-060, Agency Feasibility Review, Credit Committee, Board, PACB & 42(m) Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Closing Sources, Escrow and Wire Mechanics Package is the controlled record of how money moves at bond / construction closing. It ties the final sources and uses, closing statement, escrow structure, wire instructions, funding conditions, lender and investor requirements, and closing checklist together so the team can confirm that the closing is financially executable.

Why it matters

A NY 4% / tax-exempt bond closing can fail late if the sources and uses, cash-to-close, escrow deposits, bond proceeds, equity timing, subordinate funds, reserves, title charges, counsel fees, insurance costs, or wire approvals do not reconcile. This package is where the capital stack becomes closing mechanics.

Where this sits in the pathway

• Comes after: Finalize construction loan; equity; NY4-M-070, Bond Issuance, TEFRA, Volume Cap & Construction Closing
• Feeds into: Construction Financing Closing & Start Gate; related Task status; next reviewer / handoff

Before you treat it as complete
- Final sources and uses ties to the closing statement and funding memo.
- Escrow accounts, deposits, holdbacks, reserves, and wire amounts are documented.
- Wire instructions are verified through the required control process.
- Lender, investor, issuer, title, and counsel funding conditions are reflected.
- Unresolved funding gaps or approvals are assigned and escalated.

Watchouts
- A balanced pro forma is not a closing wire package.
- A wire instruction received by email is not verified unless the team’s wire-control process is satisfied.

Completion standard

Complete only when the Closing Sources, Escrow and Wire Mechanics Package reconciles the final sources and uses to the closing statement, escrow schedule, funding memo, and verified wire instructions. Required proof includes source approvals, cash-to-close calculation, escrow / reserve detail, wire verification, title or settlement statement tie-out, and evidence that lender, investor, issuer, title, and counsel funding conditions are resolved or exception-tracked.

Do not mark complete if wires are unverified, sources do not tie, escrow amounts are unresolved, investor or lender funding conditions remain open, or the closing statement is still changing without an assigned owner and impact analysis.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive TEFRA assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-070, Bond Issuance, TEFRA, Volume Cap & Construction Closing Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Investor / Syndicator Selection and Diligence Tracker is the record for investor selection, pricing assumptions, diligence requests, open conditions, underwriting comments, and sponsor / project evidence needed for equity commitment. It should show where the investor process actually stands.

Why it matters

Equity assumptions can make a deal look feasible before investor diligence is complete. Pricing, adjusters, reserve requirements, legal comments, document requests, and conditions can change sources / uses, closing timing, and final equity expectations.

Where this sits in the pathway

• Comes after: capital-stack strategy, investor outreach, pricing assumptions, and diligence planning.
• Feeds into: equity commitment, underwriting responses, closing conditions, final investor package, and equity release.

Before you treat it as complete

• Investor candidates, selection status, pricing assumptions, diligence requests, and open comments are tracked.
• Required sponsor, project, environmental, legal, design, financing, and compliance evidence is assigned.
• Any issue affecting equity pricing, commitment, closing, or release conditions is escalated.

Watchouts

• A selected investor or preliminary pricing indication is not equity readiness.
• The tracker is complete only when diligence status and open conditions are visible enough to support the next Gate.

Completion standard

Investor / Syndicator Selection and Diligence Tracker is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive lender / investor assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-040, Capital Stack, Bond Issuer & Equity Strategy Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Subordinate Financing / SLIHC / Subsidy Layering Matrix is the control matrix for non-senior funding sources, subsidy layering, SLIHC or other state / local resources, award conditions, timing, and compatibility with the NY4 financing stack. It should show which sources are real, conditional, pending, or at risk.

Why it matters

Subordinate funds can be essential to feasibility while also adding conditions, deadlines, approvals, compliance requirements, or layering review. If those conditions are not visible, the project may appear balanced while carrying hidden closing or underwriting risk.

Where this sits in the pathway

• Comes after: subordinate financing strategy, subsidy source identification, and project affordability / sources review.
• Feeds into: HFA/HCR financing application, subsidy layering review, closing sources, and final sources / uses reconciliation.

Before you treat it as complete

• Each subordinate source has status, amount, terms, deadlines, conditions, and documentation path.
• Subsidy layering, source compatibility, and award-condition issues are tracked.
• Changes are reconciled to sources / uses, pro forma, closing checklist, and Gate readiness.

Watchouts

• Do not treat a funding application, soft award, or assumed gap filler as committed capital.
• The matrix is reliable only when conditions and evidence requirements are controlled.

Completion standard

Subordinate Financing / SLIHC / Subsidy Layering Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive lender / investor assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-040, Capital Stack, Bond Issuer & Equity Strategy Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The HFA / HCR Application Form Matrix is the assignment and quality-control matrix for application forms, exhibits, uploads, narratives, certifications, and supporting schedules. It should show who owns each component, what source data it uses, and how it will be checked before submission.

Why it matters

Application risk often comes from inconsistency across forms rather than from one missing document. Budgets, rents, unit mix, ownership, financing, site facts, environmental status, design materials, and narratives must agree or the package becomes hard to underwrite.

Where this sits in the pathway

• Comes after: deal model, application owner matrix, exhibit list, and current project assumptions.
• Feeds into: HFA/HCR financing application submission, agency completeness review, and underwriting response workflow.

Before you treat it as complete

• Each required form or exhibit has an owner, reviewer, source data, status, and due date.
• Cross-form assumptions are reconciled before submission.
• Missing exhibits, unresolved comments, and inconsistent data are visible.

Watchouts

• A list of forms is not an application control system.
• The matrix is complete only when ownership, review status, and consistency checks are clear enough to support submission.

Completion standard

HFA / HCR Application Form Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-050, HFA / HCR Application, Underwriting & Due Diligence Submission Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The 4% Bond Pathway Intake Memo is the first discipline check on whether the project is actually ready to be managed as a NY 4% / tax-exempt bond transaction. It should document the early assumptions that shape the map: issuer path, HFA/HCR route, bond-financing strategy, volume-cap questions, TEFRA responsibility, threshold evidence, good-cost evidence, and the branch decisions that remain open.

Why it matters

At intake, the danger is not that the team lacks activity; it is that the transaction is being treated like a generic LIHTC opportunity before the public-approval, issuer, bond-financing, and evidence path is real. This memo should make the earliest financing assumptions visible enough for leadership to know what is known, what is only assumed, and what needs counsel, tax, agency, issuer, or expert review.

Where this sits in the pathway

• Comes after: initial project intake, sponsor/borrower assumptions, and early NY4 applicability screening.
• Feeds into: issuer-path confirmation, volume-cap / TEFRA planning, HFA/HCR route decisions, capital-stack strategy, and the first Gate-readiness baseline.

Before you treat it as complete

• The memo names the likely issuer path, HFA/HCR route, tax-exempt bond strategy, TEFRA responsibility, and volume-cap question.
• Bond-financing threshold and good-cost assumptions are flagged for the proper reviewer rather than treated as settled.
• Open branch decisions have owners, dates, and a clear downstream consequence.

Watchouts

• Do not use this memo as proof that the issuer path, volume cap, TEFRA sequence, threshold evidence, or good-cost evidence is accepted.
• Escalate if the roadmap depends on a branch decision that has not been reviewed by the right counsel, agency, issuer, or tax reviewer.

Completion standard

The 4% Bond Pathway Intake Memo is complete when it captures the current transaction assumptions and makes the unresolved decisions explicit. The memo should identify the likely issuer path, HFA/HCR route, bond-financing strategy, volume-cap question, TEFRA responsibility, threshold-evidence status, good-cost evidence status, and review owners for any open branch. A polished intake memo is not enough if the issuer role, volume-cap path, TEFRA sequence, bond-test support, or counsel / tax / agency review status remains hidden. Keep the Deliverable open until unresolved assumptions are either confirmed, flagged for expert review, or carried forward with owner, due date, and Gate consequence.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Tax-exempt bond threshold assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The HFA / HCR Financing Application Submission Package is the assembled agency-facing submission package for financing, underwriting, project facts, and required exhibits. It should show the final package version, upload / delivery status, supporting documents, reviewer comments, and unresolved exceptions.

Why it matters

A submission is not useful just because it was uploaded. The package must present a coherent deal: sources and uses, design scope, site control, environmental status, ownership, market support, affordability, and financing assumptions must align.

Where this sits in the pathway

• Comes after: application form matrix, exhibit assembly, owner assignments, and final submission readiness review.
• Feeds into: agency completeness review, underwriting questions, clarification response log, and feasibility / Board readiness.

Before you treat it as complete

• The submitted package is dated, version-controlled, and reconciled to the current deal model.
• Required exhibits and supporting documents are complete or clearly flagged.
• Post-submission corrections, agency questions, and completeness items are tracked.

Watchouts

• Do not treat “submitted” as “underwritable.”.
• The package is complete only when the team can explain what was submitted, what remains open, and how agency comments will be managed.

Completion standard

HFA / HCR Financing Application Submission Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show HFA/HCR application exhibits, underwriting assumptions, clarification comments, completeness responses, and current supporting evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if HFA/HCR reviewer, underwriter, borrower counsel, architect, lender, investor, or internal application lead has not accepted the point it controls, if linked Documents are stale, or if a remaining agency comment exception could affect application acceptance, underwriting progression, feasibility review, and approval-calendar readiness. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-050, HFA / HCR Application, Underwriting & Due Diligence Submission Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Borrower / Sponsor Structure and Team Qualification Matrix is the evidence record for whether the development team story is financeable, reviewable, and internally coherent. It should show borrower entity, ownership and control, sponsor and affiliate structure, guaranty or support parties, entity readiness, team experience, disclosures, and questions that HFA/HCR, lender, investor, syndicator, or counsel reviewers are likely to ask.

Why it matters

This matters because a project can have a named sponsor and still lack a reviewer-ready borrower, ownership, support-party, capacity, or disclosure story. Entity structure and team qualification issues can become underwriting, investor, counsel, or closing problems if they are discovered late.

Where this sits in the pathway

• Comes after: project intake, borrower / sponsor scoping, and development-team qualification review.
• Feeds into: HFA/HCR application support, lender / investor diligence, disclosure review, and closing responsibility mapping.

Before you treat it as complete

• Borrower ownership, control, sponsor / affiliate structure, guaranty or support parties, and entity readiness are documented.
• Team experience, capacity, relationship disclosures, and support-party commitments are visible enough for reviewer reliance.
• Open HFA/HCR, lender, investor, syndicator, or counsel questions have owners and next steps.

Watchouts

• A roster of names, an org chart draft, or a development-team slide does not prove sponsor capacity.
• The file must connect team identity to ownership/control evidence, support-party commitments, qualifications, disclosures, and reviewer acceptance or unresolved questions.

Completion standard

Complete only when borrower entity, ownership/control, sponsor, GP/managing member, guarantor/support-party, affiliate, and development-team information is current, internally consistent, tied to qualification evidence, and any capacity, disclosure, support, or reviewer issue is assigned with a resolution path.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Other assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-010, 4% Pathway Feasibility & Intake Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Preliminary Plans and HCR Design Compliance Package is the plan-set and design-compliance proof package for the current NY4 submission stage. It should connect drawings, unit mix, building scope, design standards, HCR requirements, accessibility, sustainability, site constraints, and cost assumptions into one reviewable package.

Why it matters

Preliminary plans drive more than design review. They affect construction cost, eligible basis, marketability, accessibility, permit strategy, agency comments, lender / investor diligence, and whether the project narrative matches the actual building program.

Where this sits in the pathway

• Comes after: design-team engagement, site constraints, HCR design standards, and preliminary scope assumptions.
• Feeds into: HFA/HCR application exhibits, cost feasibility, accessibility review, and design compliance updates.

Before you treat it as complete

• The plan set is current, dated, and aligned with the development budget and pro forma.
• HCR design requirements, accessibility items, sustainability assumptions, and scope changes are flagged.
• Open design comments have owners, due dates, and cost or schedule consequences.

Watchouts

• A drawing set is not a compliant package merely because it exists.
• This package is complete only when the plans are internally reconciled, reviewer issues are logged, and design changes have been reflected in budget, basis, and Gate readiness.

Completion standard

Preliminary Plans and HCR Design Compliance Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Sustainability / Resilience / IPNA Compliance Matrix is the control record for energy, resilience, green-building, IPNA, and physical-needs requirements that apply to the NY4 deal. It should identify required standards, third-party inputs, design decisions, scope implications, costs, reviewer comments, and unresolved compliance items.

Why it matters

Sustainability and resilience requirements often look like technical design details until they affect budget, scope, agency scoring or eligibility, construction documents, lender / investor diligence, and long-term operations. This matrix makes those obligations visible before they become late design revisions.

Where this sits in the pathway

• Comes after: preliminary plans, energy / resilience assumptions, IPNA or capital-needs inputs, and HCR sustainability requirements.
• Feeds into: application exhibits, design compliance review, scope / budget reconciliation, and construction closing conditions.

Before you treat it as complete

• Required standards and applicability assumptions are documented.
• IPNA, energy, resilience, consultant, and design-team inputs are reconciled to scope and budget.
• Open compliance items have owners, reviewer paths, and cost / schedule implications.

Watchouts

• Do not treat a consultant memo, preliminary checklist, or design intent as compliance proof.
• The matrix is ready only when obligations are mapped to evidence, open items are controlled, and design / budget impacts are visible.

Completion standard

Sustainability / Resilience / IPNA Compliance Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Compliance assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Accessibility and Fair Housing Design Compliance Matrix is the proof record for accessibility, fair housing, visitability, adaptability, and design-compliance requirements that apply to the building program. It should connect code / program requirements, plan annotations, consultant review, open comments, and responsibility for corrections.

Why it matters

Accessibility gaps can become agency comments, construction changes, legal exposure, budget pressure, lease-up issues, or compliance findings. The matrix keeps design compliance from being treated as a vague assurance buried in plans or consultant emails.

Where this sits in the pathway

• Comes after: preliminary plans, accessibility standards, fair-housing review, and design compliance scoping.
• Feeds into: HCR design review, application exhibits, construction documents, and compliance handoff.

Before you treat it as complete

• Applicable accessibility and fair-housing requirements are identified.
• Plan evidence, consultant review, corrections, and unresolved comments are tracked.
• Any design change affecting units, common areas, site circulation, cost, or schedule is escalated.

Watchouts

• Do not rely on a general design-team statement that the plans are compliant.
• The matrix is complete only when requirements are traceable to the current plans and unresolved corrections are owned.

Completion standard

Accessibility and Fair Housing Design Compliance Matrix is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show plans, design scope, sustainability / resilience standards, accessibility / fair housing requirements, cost feasibility, and eligible-basis assumptions, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if architect, engineer, sustainability consultant, accessibility reviewer, cost estimator, HFA/HCR, lender, or investor has not accepted the point it controls, if linked Documents are stale, or if a remaining design-scope or basis exception could affect design readiness, budget control, eligible basis, HFA/HCR review, and construction closing assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive Compliance assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-030, Design, Scope, Sustainability & Cost Basis Feasibility Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

Sources / Uses and Operating Pro Forma Package is the current financing and operating model package that reconciles sources, uses, rents, expenses, reserves, subsidy, debt, equity, and operating assumptions.

Why it matters

This package supports underwriting and leadership decisions before final basis is settled. Its job is to show whether the deal still pencils under current assumptions and reviewer comments, not to prove cost certification or final allocation readiness.

Where this sits in the pathway

• Comes after: capital stack modeling, rent / operating assumptions, lender and investor diligence, and budget updates
• Feeds into: bond sizing, HFA/HCR underwriting, lender / investor review, closing readiness, and later final-basis reconciliation

Before you treat it as complete

• Sources, uses, operating pro forma, rent assumptions, expense assumptions, reserve assumptions, and funding gaps reconcile to the latest model.
• Lender, investor, syndicator, HFA/HCR, subsidy, and internal comments are tracked with status.
• Changes that affect bond sizing, debt capacity, equity, subsidy, reserve structure, or closing feasibility are visible.
• Open assumptions are assigned before the package is used for approval or Gate reliance.

Watchouts

• A balanced pro forma does not prove final basis or cost certification acceptance.
• Do not treat this as complete while major assumptions are still unsupported or disconnected from reviewer feedback.

Completion standard

Sources / Uses and Operating Pro Forma Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show sources and uses, bond sizing, volume cap, TEFRA, 95-5 good-cost evidence, investor / lender assumptions, and counsel review, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if issuer, HFA/HCR finance staff, bond counsel, tax counsel, lender, investor / syndicator, or borrower counsel has not accepted the point it controls, if linked Documents are stale, or if a remaining bond-path exception could affect capital stack confidence, public approval timing, construction closing, cost certification, and final allocation assumptions. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive lender / investor assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-040, Capital Stack, Bond Issuer & Equity Strategy Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The HFA Feasibility / Underwriting Response Package is the organized response record for HFA/HCR underwriting comments, feasibility questions, and due-diligence issues. It should show what the agency asked, what the team changed, which exhibits were updated, and which comments remain open.

Why it matters

This package is where a 4% / tax-exempt bond deal moves from “submitted” to “underwritable.” Agency feasibility review can expose gaps in sources and uses, rents, operating assumptions, development budget, design, environmental status, site suitability, ownership structure, or subsidy layering. If the response package is weak, the deal may lose time in repeated clarification cycles and may not be ready for Credit Committee, Board, PACB, 42(m), or closing-condition work.

Where this sits in the pathway

• Comes after: Prepare HFA feasibility / underwriting response package (NY4-T-030); Assemble HFA / HCR financing and underwriting application exhibits (NY4-T-026); NY4-M-060, Agency Feasibility Review, Credit Committee, Board, PACB & 42(m) Readiness
• Feeds into: Agency Feasibility Review Readiness Gate; related Task status; next reviewer / handoff

Before you treat it as complete
- Every agency comment is logged with response status, owner, due date, and supporting exhibit.
- Sources and uses, pro forma, design, environmental, market, appraisal, disclosure, and site-suitability materials are reconciled to the latest response.
- Revised exhibits are version-controlled and tied back to the comment they resolve.
- HFA/HCR follow-up comments are closed or clearly assigned.
- Gate impact is updated for unresolved conditions.

Watchouts
- A response sent by email is not the same as an accepted underwriting response.
- Updated numbers that are not reconciled across the pro forma, application, and capital stack can create new comments.

Completion standard

Complete only when the HFA Feasibility / Underwriting Response Package is current, organized by agency comment, and usable as the record of how underwriting questions were resolved. Required proof includes the HFA underwriting response memo, updated sources and uses, updated pro forma, revised design/environmental/report responses, and a comment log that shows closed, open, and escalated items.

Do not mark complete if the package is merely submitted, missing revised exhibits, inconsistent with the current capital stack, not reconciled across application materials, or still waiting on agency acceptance. Open comments must have owners, dates, next actions, and Gate impact before leadership should rely on the status.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive 42(m) assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-060, Agency Feasibility Review, Credit Committee, Board, PACB & 42(m) Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Market / Appraisal / Operating Underwriting Support Package is the evidence file for demand, value, operating assumptions, rent levels, expenses, reserve assumptions, and other underwriting inputs that support the NY4 application and feasibility review.

Why it matters

Market, appraisal, and operating assumptions can quietly drive feasibility. If they are stale, inconsistent, or unsupported, they can affect HFA/HCR questions, lender sizing, investor diligence, operating budget confidence, and leadership’s view of whether the project is financeable.

Where this sits in the pathway

• Comes after: market study, appraisal, operating pro forma, and underwriting support request workflow.
• Feeds into: HFA/HCR underwriting, Credit Committee readiness, investor / lender diligence, and application clarification responses.

Before you treat it as complete

• Market study, appraisal, rent, expense, reserve, and operating assumptions are current and traceable.
• Changes are reconciled to the pro forma, application, lender materials, and investor materials.
• Reviewer comments and open diligence questions have owners and due dates.

Watchouts

• A received report is not underwriting support if its assumptions are not reconciled to the deal model.
• The package is ready only when the evidence can support reviewer reliance.

Completion standard

Market / Appraisal / Operating Underwriting Support Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show HFA/HCR application exhibits, underwriting assumptions, clarification comments, completeness responses, and current supporting evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if HFA/HCR reviewer, underwriter, borrower counsel, architect, lender, investor, or internal application lead has not accepted the point it controls, if linked Documents are stale, or if a remaining agency comment exception could affect application acceptance, underwriting progression, feasibility review, and approval-calendar readiness. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-050, HFA / HCR Application, Underwriting & Due Diligence Submission Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Site Suitability / Team Qualification / Disclosure Package is the evidence package for whether the site, sponsor, development team, disclosures, and execution capacity are credible enough for agency, lender, investor, and internal reliance. It should connect site facts with the people and entities responsible for delivering the deal.

Why it matters

Site suitability and team qualification can be treated as narrative sections, but reviewers rely on them to judge whether the project is feasible, responsible, and manageable. Weak disclosures, unclear control, missing qualifications, or unsupported site claims can create underwriting questions that slow the application or approval path.

Where this sits in the pathway

• Comes after: site suitability review, sponsor / team qualification materials, and disclosure collection.
• Feeds into: HFA/HCR application review, underwriting questions, Board readiness, and agency disclosure conditions.

Before you treat it as complete

• Site suitability evidence, team experience, ownership / control facts, disclosures, and qualifications are current and internally consistent.
• Any reviewer question about capacity, conflict, site facts, or disclosure status has an owner and response path.
• The package reconciles with borrower / sponsor structure, application materials, and agency-facing narratives.

Watchouts

• Do not treat a biography list or site narrative as a qualification package.
• The package is reliable only when the claims are supported, current, and tied to reviewer expectations.

Completion standard

Site Suitability / Team Qualification / Disclosure Package is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show HFA/HCR application exhibits, underwriting assumptions, clarification comments, completeness responses, and current supporting evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if HFA/HCR reviewer, underwriter, borrower counsel, architect, lender, investor, or internal application lead has not accepted the point it controls, if linked Documents are stale, or if a remaining agency comment exception could affect application acceptance, underwriting progression, feasibility review, and approval-calendar readiness. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-050, HFA / HCR Application, Underwriting & Due Diligence Submission Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The Agency Clarification and Completeness Response Log is the working log for HFA/HCR questions, completeness comments, clarification requests, response owners, submitted answers, and unresolved issues. It should make the agency response cycle visible instead of burying it in email.

Why it matters

After submission, the deal can stall because the team cannot see which agency questions are open, who owns the response, which assumptions changed, and whether the answer has been accepted. This log keeps the underwriting response cycle controlled.

Where this sits in the pathway

• Comes after: HFA/HCR submission, completeness review, and agency question routing.
• Feeds into: underwriting response package, Credit Committee readiness, Board readiness, and approval-to-closing conditions.

Before you treat it as complete

• Each agency comment has an owner, due date, response status, supporting document, and acceptance status.
• Responses are reconciled to the application, budget, plans, underwriting, and legal assumptions.
• Open items that affect Gate readiness are escalated.

Watchouts

• Do not treat a drafted response or sent email as resolved.
• The log is complete only when the agency response status and remaining consequences are clear.

Completion standard

Agency Clarification and Completeness Response Log is complete when the file is current, dated, version-controlled, and usable by the party that must rely on it. The evidence should show HFA/HCR application exhibits, underwriting assumptions, clarification comments, completeness responses, and current supporting evidence, the related Documents should be marked with current received / reviewed / approved / pending / waived status, and open comments should have an owner, due date, reviewer path, and decision consequence. A drafted, assembled, or internally balanced file is not enough if HFA/HCR reviewer, underwriter, borrower counsel, architect, lender, investor, or internal application lead has not accepted the point it controls, if linked Documents are stale, or if a remaining agency comment exception could affect application acceptance, underwriting progression, feasibility review, and approval-calendar readiness. Keep the Deliverable open until those exceptions are resolved, waived, or carried forward visibly.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive HFA/HCR process assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-050, HFA / HCR Application, Underwriting & Due Diligence Submission Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.

Deliverable guide

What this is

The HFA Feasibility / Underwriting Response Package is the organized response record for HFA/HCR underwriting comments, feasibility questions, and due-diligence issues. It should show what the agency asked, what the team changed, which exhibits were updated, and which comments remain open.

Why it matters

This package is where a 4% / tax-exempt bond deal moves from “submitted” to “underwritable.” Agency feasibility review can expose gaps in sources and uses, rents, operating assumptions, development budget, design, environmental status, site suitability, ownership structure, or subsidy layering. If the response package is weak, the deal may lose time in repeated clarification cycles and may not be ready for Credit Committee, Board, PACB, 42(m), or closing-condition work.

Where this sits in the pathway

• Comes after: Prepare HFA feasibility / underwriting response package (NY4-T-030); Assemble HFA / HCR financing and underwriting application exhibits (NY4-T-026); NY4-M-060, Agency Feasibility Review, Credit Committee, Board, PACB & 42(m) Readiness
• Feeds into: Agency Feasibility Review Readiness Gate; related Task status; next reviewer / handoff

Before you treat it as complete
- Every agency comment is logged with response status, owner, due date, and supporting exhibit.
- Sources and uses, pro forma, design, environmental, market, appraisal, disclosure, and site-suitability materials are reconciled to the latest response.
- Revised exhibits are version-controlled and tied back to the comment they resolve.
- HFA/HCR follow-up comments are closed or clearly assigned.
- Gate impact is updated for unresolved conditions.

Watchouts
- A response sent by email is not the same as an accepted underwriting response.
- Updated numbers that are not reconciled across the pro forma, application, and capital stack can create new comments.

Completion standard

Complete only when the HFA Feasibility / Underwriting Response Package is current, organized by agency comment, and usable as the record of how underwriting questions were resolved. Required proof includes the HFA underwriting response memo, updated sources and uses, updated pro forma, revised design/environmental/report responses, and a comment log that shows closed, open, and escalated items.

Do not mark complete if the package is merely submitted, missing revised exhibits, inconsistent with the current capital stack, not reconciled across application materials, or still waiting on agency acceptance. Open comments must have owners, dates, next actions, and Gate impact before leadership should rely on the status.

Key risks / failure points

• Treating a file upload as proof without checking review/approval status. - Letting multiple versions circulate without naming the current version. - Separating the proof package from the Task, Action and Gate it supports. - Closing comments in email without updating the issue log and blocking reason. - Treating sensitive 42(m) assumptions as final without expert review.

Gate impact

This Deliverable supports NY4-G-060, Agency Feasibility Review, Credit Committee, Board, PACB & 42(m) Readiness Gate. Its leadership value is to answer whether the proof is ready or merely talked about, which reviewer controls timing, and whether unresolved evidence should block advancement.