Boston CDBG and HUD Compliance: A 2026 Guide for Subrecipients

If your organization holds a subrecipient agreement with Boston’s Department of Neighborhood Development, the compliance load is dominated by HUD’s program rules layered on top of the federal Uniform Guidance, with DND’s program-year reporting cadence and the city’s CAPER submission to HUD setting the rhythm. Boston is a smaller entitlement city than Chicago or New York, but the rule structure is identical - HUD does not scale its monitoring expectations down for mid-sized cities.

This guide is the layer above what’s already on DND’s subrecipient pages and your subrecipient agreement. It assumes you already know which HUD program your funding draws from, who your DND project manager is, and what the activity’s national objective is. What it covers is the structure: how IDIS, environmental review, the program year, FY closeout, Davis-Bacon, Section 3, Uniform Guidance, and Single Audit fit together.

The Three-Layer Rule Set

A Boston CDBG subrecipient lives under three concurrent rule sets.

• HUD CPD program regulations. 24 CFR Part 570 for CDBG, 24 CFR Part 92 for HOME, 24 CFR Part 576 for ESG, and parallel parts for HOPWA. Each program has program-specific eligibility, beneficiary, and reporting rules.
• Federal Uniform Guidance (2 CFR Part 200). Cross-cutting administrative requirements, cost principles, and audit requirements that apply to all federal funds. The Uniform Guidance practical guide covers the structure end to end.
• DND subrecipient agreement. Specific contract terms, activity scope, performance metrics, reporting cadence, and city-specific special conditions including the program-year closeout cadence.

Where the rules conflict or differ in scope, the more specific or more restrictive rule generally controls. Subrecipients that try to apply only one rule set typically miss obligations from the others.

National Objectives and Beneficiary Documentation

Every CDBG-funded activity must meet one of three national objectives at 24 CFR 570.208: low- and moderate-income (LMI) benefit, elimination of slums and blight, or urgent need. The vast majority of subrecipient activities are LMI-benefit, documented through area benefit, limited clientele, or housing income certification.

The audit-relevant point: documentation lives at the activity and beneficiary level, not at the program level. A monitoring visit pulls individual files. Limited-clientele activities require per-beneficiary income certification or presumed-benefit documentation; area-benefit activities require the geographic boundary, the LMI calculation tied to current census data, and evidence that the activity is open to all area residents.

Weak national-objective documentation is the most common HUD monitoring finding for CDBG subrecipients in any city. In Boston, the program-year closeout package is the moment when documentation gaps surface, because DND has to report accomplishment data into IDIS for the CAPER on a hard deadline. Subrecipients who arrive at closeout with weak documentation create CAPER risk for the city, which produces tighter monitoring on the next agreement.

Boston’s Program Year and FY Closeout

Boston operates CDBG on the city’s program year, with subrecipient agreements typically aligned to that year. The closeout pattern:

• Final accomplishment data. Beneficiary counts by demographic category, activity completion status, project-by-project tally.
• Final beneficiary file. Per-person income certifications and eligibility documentation supporting the accomplishment counts.
• Final expenditure report. Reconciled to the general ledger, with allocation across funding sources documented.
• Drawdown reconciliation. Total drawn-down funds matched against total expenditures; unspent funds returned or rolled forward per the agreement.
• Program income reconciliation. Program income earned during the year, where it was deposited, and how it was used.
• Davis-Bacon and Section 3 closeout. Final certified payroll review, final Section 3 reporting.
• Subrecipient monitoring closeout. If the subrecipient further subcontracted, closeout of the downstream subrecipient files.

DND requires the closeout package on a hard timeline because the city has 90 days after program year-end to submit the CAPER to HUD. Late closeout submissions force DND to estimate or omit subrecipient data in the CAPER, which produces HUD findings against the city. The remediation cost flows back to the subrecipient.

IDIS and the Reporting Chain

The City of Boston is the CPD grantee; DND administers the program. Subrecipient data flows into IDIS through DND. The reporting chain:

• The subrecipient executes activities and collects underlying data.
• The subrecipient reports to DND on the contractual cadence (typically quarterly plus closeout).
• DND enters activity setup, accomplishment data, and drawdowns into IDIS.
• HUD reads IDIS data and pulls subrecipient files when discrepancies arise.

Subrecipient data accuracy is the foundation. A subrecipient that submits inflated or unsupported counts to DND creates an IDIS data integrity problem that surfaces in HUD’s risk analysis of the city. The fix is documentation discipline at the activity level - every reported beneficiary should have a file, every reported accomplishment should have evidence.

Environmental Review Discipline

CDBG-funded activities require environmental review under 24 CFR Part 58 before any commitment of funds or any choice-limiting action. The City of Boston is the responsible entity that conducts the environmental review. Subrecipients cannot:

• Sign a construction contract before the environmental review is complete and any required release of funds is obtained.
• Acquire property before environmental clearance.
• Begin physical work before environmental clearance.
• Commit funds for activities materially different from the activities the environmental review covered.

Pre-clearance commitments are a recurring HUD finding. The fix is procedural: a written hold on commitments, with both the project lead and the fiscal lead signing off before any contract is executed, and a process for re-running environmental review if the project scope changes.

Davis-Bacon, Section 3, and Cross-Cutting Rules

CDBG construction triggers Davis-Bacon labor standards above $2,000 in covered work. Subrecipient obligations:

• Include the current Davis-Bacon wage determination in the construction contract.
• Conduct a preconstruction conference with the contractor.
• Collect certified payrolls weekly throughout the project.
• Review payrolls for accuracy and conduct periodic on-site labor interviews.
• Investigate complaints and document findings.
• Submit Davis-Bacon documentation to DND on the contractual schedule.

Section 3 obligations apply where HUD-funded activities generate economic opportunities. Subrecipients direct training, employment, and contracting to low- and very-low-income persons and Section 3 business concerns to the maximum extent feasible. Section 3 reporting flows through HUD’s SPEARS system via DND.

For broader procurement requirements that apply to subrecipient purchasing on the federal portion, see 2 CFR 200 Subpart D procurement standards and the federal procurement thresholds guide.

Single Audit Triggers

A Boston CDBG subrecipient that expends $750,000 in federal funds in any fiscal year ending before October 1, 2024 - or $1,000,000 thereafter - is subject to the Single Audit. The audit covers all federal funds, not just CDBG. The auditor selects major programs based on risk; large CDBG subawards are routinely selected.

The Single Audit produces a reporting package submitted to the Federal Audit Clearinghouse. Material findings produce HUD attention against the city, which produces tighter monitoring of the subrecipient. The single audit threshold guide and common single audit findings cover the federal angle in more depth.

Documentation Files to Maintain

The minimum file structure that withstands HUD and DND monitoring plus the Single Audit:

• Subrecipient agreement file. Original agreement, every amendment, signed cover letters.
• National-objective file. Per-activity national-objective documentation.
• Beneficiary file. Per-person eligibility documentation.
• Budget and expenditure file. Original approved budget, every approved amendment, working budget reconciled to the general ledger monthly, drawdown documentation.
• Procurement file. Procurement policy, conflict-of-interest disclosures, solicitations and contracts above the policy threshold, sole-source justifications.
• Davis-Bacon file. Wage determinations, certified payrolls, on-site interview records, complaint files.
• Section 3 file. Section 3 plan, training and employment records, contracting records.
• Environmental review file. Documentation that environmental review was complete before commitment.
• Program income file. Program income earned, deposited, and used.
• Closeout file. Per program year, the complete closeout package with sign-offs.
• Subrecipient monitoring file. If the subrecipient further subcontracts. The subrecipient monitoring guide covers the obligation flow-down.
• Audit file. Single Audit reports, corrective action plans, FAC confirmations.

The audit prep checklist and CDBG-specific compliance worksheet cover operating cadence.

Where Boston CDBG Subrecipients Get Caught

Recurring findings cluster in five areas.

• National-objective documentation thin. Income certifications missing, area-benefit calculations untied to current data.
• Pre-clearance commitments. Contracts signed before environmental review concluded.
• Late or incomplete FY closeout. Closeout submissions that arrive after DND’s CAPER timeline, or that lack reconciled data.
• Davis-Bacon failures. Missing certified payrolls, missing wage determinations, untimely back-wage corrections.
• Procurement undocumented. Purchases above the policy threshold without quotes, sole-source justifications written after the fact.

Software and Workflow Considerations

CDBG subrecipient compliance is a documentation and beneficiary-data integrity problem. Subrecipients that handle it well typically have:

• A grant management system that tracks budget, expenditures, and beneficiary records on the same record. The best HUD CDBG grant compliance software listicle covers the category.
• A beneficiary intake system that captures HUD-compliant income certification.
• A document repository organized to the audit file structure with retention rules at the HUD CDBG five-year minimum.
• A FY closeout calendar tied to DND’s program year so the closeout package is built progressively across the year, not retrofitted at year-end.
• A subrecipient monitoring workflow if the subrecipient further subcontracts.

Where to Start

If you’re picking up Boston CDBG compliance for the first time:

1. Read your subrecipient agreement, including all special conditions and the closeout schedule.
2. Verify environmental review status before any commitment.
3. Build national-objective documentation at activity setup.
4. Calendar every reporting deadline against Boston’s program year - quarterly progress, drawdowns, Section 3, Davis-Bacon, FY closeout, Single Audit.
5. If construction is involved, set up the Davis-Bacon workflow before the first construction contract.

DND does not renew agreements with subrecipients that produce repeated findings or late closeouts. Compliance is the precondition to staying in the portfolio.

For state-level context, see the Massachusetts nonprofit profile. For city-level context including DND and other Boston agencies, see the Boston nonprofit profile.

DEFINITION

DND

City of Boston Department of Neighborhood Development. Administers CDBG, HOME, ESG, HOPWA, and locally funded housing and neighborhood development programs. Manages subrecipient agreements for HUD CPD funding.

DEFINITION

CAPER

Consolidated Annual Performance and Evaluation Report. The annual report a HUD CPD grantee submits at the end of each program year, summarizing accomplishments, beneficiary data, and expenditures across CDBG, HOME, ESG, and HOPWA.

DEFINITION

IDIS

Integrated Disbursement and Information System. HUD's data system in which CPD grantees set up activities, track accomplishments, and draw down funds. Subrecipient data flows into IDIS through the grantee.

DEFINITION

Consolidated Plan

A five-year strategic plan a HUD CPD grantee submits identifying community needs, priorities, and intended uses of HUD CPD funds. Updated annually through the Action Plan and reported on through the CAPER.

DEFINITION

National objective

Each CDBG-funded activity must meet one of three national objectives under 24 CFR 570.208: benefit to low- and moderate-income persons, prevention or elimination of slums and blight, or addressing urgent needs.