"My Reservation Letter has a ‘date certain’ on it and DHCD's QAP actually spells out the federal 10 percent test in plain English — so what exactly happens if I miss it, and does my placed-in-service deadline run from a fixed calendar date the way some states set it, or from whenever my own Carryover Allocation happens to issue?"
The 10 percent test, stated directly in DC's own QAP text
DHCD's QAP states the requirement in its own words, not merely by cross-reference: “The Sponsor/Developer must incur more than 10% of the reasonably anticipated basis within 12 months of the tax credit Carryover Allocation date (the “10% Test”) and then place the Project in service no later than the end of the second year following the year of the Carryover Allocation. Failure to meet these requirements will result in the loss of the LIHTC for the Project.” To demonstrate compliance, DHCD requires “an owner's certification, which includes an itemized list of Project expenditures” and “a Certified Public Accountant (CPA)'s opinion documenting that the Project has met the 10% Test within 12 months of the date of the allocation of tax credits.”
That flat “12 months” framing is worth flagging against the federal statute it is meant to implement. IRC § 42(h)(1)(E)(ii) measures the 10% Test to the close of the calendar year following the calendar year in which the Carryover Allocation is made — a period that can run close to 24 months for an allocation made early in a calendar year, not a flat 12 months from the allocation date itself. This research could not determine from the QAP's own text alone whether DC's “12 months” language is a deliberate, DC-specific tightening of the federal timeline, an informal shorthand DHCD does not enforce literally, or simply imprecise drafting — DHCD's separate Carryover Allocation Agreement form, which is not part of this QAP and which this research did not independently obtain, may be the controlling document. Applicants should confirm the actual controlling deadline with DHCD directly rather than assume either the QAP's 12-month figure or the federal statute's own outer bound applies without checking.
The QAP defines “Reservation or Reservation Letter” as “a conditional commitment of LIHTC, which... does not meet the definition of a binding allocation as stated in IRC Section 42,” and separately states that “Reservation Letters will identify a date certain by which Sponsors/Developers must certify that: (1) Projects have been placed in service; or (2) at a minimum, that more than 10 percent of the reasonably anticipated basis of the Project has been incurred. If the Sponsor/Developer has not met either of these requirements, the Reservation may be cancelled.” Cancelled or otherwise unused credits become “Recovered Tax Credits,” available for redistribution to other projects or carryforward into the District's unallocated pool. For projects the DHCD Director deems “essential to the Mayor and/or DHCD's strategic plan or mission” but unable to meet a deadline for reasons outside the developer's control, DHCD may, at its sole discretion, substitute a Reservation from a future calendar year for the one that was missed.
Placed in service: a per-project clock, not a round-wide date
DC's placed-in-service deadline is expressed relative to each project's own Carryover Allocation year — “the end of the second year following the year of the Carryover Allocation” — rather than a single fixed calendar date shared by every award in a competitive round. Two projects selected in the same Consolidated RFP cycle can therefore carry different literal placed-in-service deadlines if their Carryover Allocations happen to issue in different calendar years, which is a materially different structure from a QAP that publishes one shared deadline for an entire funding round.
Once a building is placed in service, the QAP requires a defined document package before DHCD will complete its final evaluation and issue IRS Form(s) 8609: a revised Form 202 development budget and operating pro forma (Excel and signed PDF); the accountant's/owner's cost certification, including the 25% Test for tax-exempt-bond/4% projects; a draft Form 8609 per building; the project's DC business licenses; a DC Department of Buildings Certificate of Occupancy (or DHCD-acceptable equivalent); the recorded Land Use Restrictive Covenants (Extended Use Agreement); the project market study; the executed partnership/operating agreement and all amendments; a summary of development-team or management-group changes; evidence of LIHTC fees paid at closing; and the project's federal applicable-percentage rate-lock agreement. The final Tax Credit Allocation Amount is “the lesser of: (1) the tax credits necessary to make the development feasible; or (2) the amount of the earlier Carryover Allocation” — deferred developer fee is treated as a committed source at closing and reduced only under DHCD's standard right-sizing policies.
The fees that run on this clock
| Fee | Amount | Applicability |
|---|---|---|
| Extension Fee (late Carryover Allocation application) | $500 per calendar day past the due date | 9% and 4% |
| Allocation Fee (per-capita 9% Projects) | 50% of 1% of the total 10-year allocation, assessed at Carryover Allocation | 9% |
| Allocation Fee (tax-exempt bond-funded Projects) | 1% of the total 10-year allocation, paid in two installments — a portion at closing, the remainder when Form(s) 8609 issue | 4% and DC LIHTC |
| Compliance Monitoring Fee | $65/unit/yr ($80 for Average Income set-aside) for the first 15 years; $40/unit/yr ($45 for Average Income) from year 16 on, capped at $4,000/Project after the initial 15 years; due each February 15 | 9%, 4%, and DC LIHTC |
| Re-inspection Fee | $55/hour (min. $55) to re-inspect deficiencies; an additional $55/hour (min. $55) to review corrective tenant files/documents | 9%, 4%, and DC LIHTC |
| Allocation Modification Fee | $1,000 (where the Form 8609 modification isn't the result of a DHCD administrative error) | 9%, 4%, and DC LIHTC |
The Extension Fee is the QAP's only stated per-day monetary consequence in the post-award timeline — and it attaches specifically to a late Carryover Allocation application, not to a missed 10% Test or placed-in-service deadline, both of which the QAP says cost the credits outright rather than triggering a fee.
What actually triggers recapture, rescission, or a barred future application
DHCD's noncompliance process is direct: “DHCD will promptly notify Project owners in writing if its monitoring reveals that the Project is in noncompliance. This notice will provide a cure period of up to 90 days from the notice date for the owner to bring the Project into compliance. Failure to cure a condition of noncompliance may result in the recapture of the LIHTC.” Every noncompliance incident “must be reported to the IRS on Form(s) 8823 notwithstanding the resolution of compliance issues” — curing the problem does not cancel the filing. “For good cause, DHCD, in its sole discretion, may grant an extension of the cure period up to an additional six months.” Separately, any change in property management or ownership (including Managing Member or General Partner interests) requires the owner to give DHCD written notice “no less than 30 days prior” to the change.
The QAP's affordability floor runs well past any post-award closing milestone: Low-Income Units must remain rent-restricted for “a period of at least 40 years (the Compliance Period of 15 years and an extended use period of at least 25 years, for a total period of at least 40 years)” and every applicant “must agree to maintain the minimum 40-year extended affordability period by waiving their right to seek a qualified contract for the Project purchase after the 14th year of the Compliance Period,” unless the project instead presents an approved plan to transfer ownership to tenants at year 15. That QAP-mandated waiver forecloses, as a matter of DC policy, an early-exit option that IRC § 42(h)(6)(E)(i)(II) otherwise preserves nationally for owners who no longer want to remain in the program after year 14. The QAP goes further still: “Any application submitted by an applicant with a principal that was or is currently a principal in an Ownership Entity that has previously requested a Qualified Contract will not be considered for any reservation or allocation of credits at DHCD's discretion” — a prior Qualified Contract request anywhere can follow a principal into a future DC application.
For projects granting a Qualified Non-profit Organization a right of first refusal, that right “may be exercised anytime within a twenty-four (24) month period, or longer period, after the close of the Compliance Period,” after which “the Qualified Non-profit Organization shall have at least twelve (12) months to close on the purchase of the Project or the interests of the non-managing members of the Ownership Entity.” That clock runs from the close of the 15-year Compliance Period specifically — not from the award date, and not from Year 15 of the overall 40-year affordability term in isolation.
A parallel 6-month clock for 4% bond deals
As covered in Phase 8, a project selected through DCHFA's Readiness Review must close all project financing within 6 months of its DCHFA application date. That closing clock is not merely a DCHFA administrative preference — the QAP's own Evaluation Criteria make it a scored requirement: “Projects applying for 4% LIHTC in conjunction with a tax-exempt bond allocation must be able to close on all Project financing within six months of the submission of an application to DCHFA,” under the Readiness to Proceed criterion, meaning a missed 6-month window can cost scoring points under the QAP itself, independent of whatever consequence DCHFA separately attaches to it.
The preliminary bond inducement available to acquisition/rehabilitation projects — issued within 60 days of the project's acquisition date, solely to preserve IRS eligibility to finance acquisition basis with tax-exempt bonds — is explicitly not a substitute for any of this: DCHFA's own materials state a preliminary inducement “does not constitute a DCHFA commitment of Bond Cap” and “does not negate the project's requirement to secure a DHCD Threshold Review and Evaluation Score,” meaning the project must still separately compete through Readiness Review on its own twice-yearly calendar.
Where this goes wrong
- Assuming DC's QAP leaves the 10 percent test to federal law by silent cross-reference, the way some other states' QAPs do. DC's own text states the requirement directly, including the CPA-opinion and owner-certification documentation DHCD requires to prove it.
- Treating DC's stated “12 months” 10% Test window as identical to the federal statute's own outer bound. IRC § 42(h)(1)(E)(ii) measures to the close of the calendar year following the year of allocation — which can run close to 24 months for an allocation made early in the year — so DC's flat 12-month QAP language may be a tighter, DC-specific operational rule; this research could not resolve which controls without DHCD's own Carryover Allocation Agreement form, and recommends confirming directly with DHCD.
- Assuming DC publishes one fixed, round-wide placed-in-service date the way some other states do. DC's deadline runs per project, from that project's own Carryover Allocation year (“end of the second year following”), so two awards from the same competitive round can carry different literal deadlines.
- Assuming the $500/calendar-day Extension Fee is a general late fee covering any missed post-award deadline. The QAP ties it specifically to a late Carryover Allocation application; missing the 10% Test or the placed-in-service deadline itself costs the credits outright rather than triggering this fee.
- Assuming Qualified Contract remains an available exit strategy for a DC deal the way it does under plain federal law. DC's QAP requires applicants to waive the right to seek one after Compliance Year 14, absent an approved tenant-ownership transfer plan at Year 15 — a substantive, DC-specific narrowing of the federal IRC § 42(h)(6)(E)(i)(II) option.
- Missing that a principal's prior Qualified Contract request — even on an unrelated deal — can taint a future DC application. The QAP allows DHCD to refuse any reservation or allocation to an applicant with a principal previously involved in a Qualified Contract request, entirely at DHCD's discretion.
- Assuming the 90-day noncompliance cure period is DC's hard outer limit. DHCD may grant a further extension of “up to an additional six months” for good cause, at its sole discretion — there is no stated cap on how many times this discretion can be exercised.
- Assuming a cured noncompliance issue avoids IRS reporting. The QAP requires every noncompliance incident be reported on Form 8823 “notwithstanding the resolution of compliance issues” — curing the problem does not cancel the filing.
- Treating the 6-month bond-deal closing clock as only a DCHFA scheduling preference. It is also an explicit QAP Evaluation Criteria requirement (Readiness to Proceed) that can cost scoring points on its own, separate from whatever consequence DCHFA's own process attaches to missing it.
- Confusing a preliminary bond inducement (available within 60 days of acquisition, for IRS compliance purposes only) with an actual Bond Cap reservation or a substitute for Readiness Review. DCHFA's own materials state it does neither.
- Assuming the Right of First Refusal's 24-month exercise window starts at the award date or flatly at Year 15. It runs from the close of the 15-year Compliance Period specifically, and the nonprofit then has a further 12 months to close once it exercises.
- HUD
- LIHTC
- State QAPs
- IRS § 42
- Housing Finance Agencies