Chicago CDBG Pass-Through Compliance: A 2026 Guide for Subrecipients

If your nonprofit holds a Chicago CDBG subrecipient agreement, you are operating at the intersection of three rule sets that don’t fully reconcile: HUD’s CDBG-specific regulations at 24 CFR Part 570, the federal Uniform Guidance at 2 CFR Part 200, and the City of Chicago Department of Planning and Development’s own subrecipient agreement and monitoring framework. Each rule set has its own evidence requirement. The audit posture that survives is one where the documentation is complete enough to satisfy HUD direct, DPD monitoring, and the Single Audit independently — and where they all reconcile.

This guide is the layer above what’s already in DPD’s subrecipient resources and your subrecipient agreement. It assumes you already know which CDBG-funded activity you operate, who your DPD project manager is, and what the activity’s national objective is. What it covers is the structure: how IDIS, environmental review, Davis-Bacon, Section 3, Uniform Guidance, and Single Audit fit together for a subrecipient.

The Three-Layer Rule Set

A CDBG subrecipient lives under three concurrent rule sets.

• HUD CDBG regulations (24 CFR Part 570). The program-specific rules. Eligibility of activities, national objectives, public service caps, planning and administration caps, financial management standards specific to CDBG.
• 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.
• DPD subrecipient agreement. Your specific contract with the City of Chicago. Activity scope, performance metrics, reporting cadence, special conditions, and the city’s own subrecipient monitoring framework.

Where the rules conflict, the more specific or more restrictive rule generally controls. In practice, the HUD CDBG rules tend to be more specific than Uniform Guidance for record retention, allowable activities, and beneficiary documentation; Uniform Guidance tends to be more specific for procurement, cost principles, and audit thresholds.

National Objectives: The Documentation You Cannot Miss

Every CDBG-funded activity must meet one of three national objectives at 24 CFR 570.208:

• Low- and moderate-income (LMI) benefit. Documented through one of three sub-criteria: area benefit (activities serving a defined geographic area where the LMI percentage exceeds the threshold), limited clientele (activities serving a presumed-LMI population such as homeless persons or migrant farmworkers, or where individual income certification is collected), or housing (LMI households occupying assisted housing).
• Elimination of slums or blight. Documented through area-wide blight designation or spot-blight criteria.
• Urgent need. Documented for activities responding to a serious and immediate threat where other resources are unavailable. A narrow category, rarely the basis for routine subrecipient activities.

The audit-relevant point: the national-objective documentation has to exist at the activity level, not aggregated to the program. A monitoring visit will pull individual files. For limited-clientele activities, the file needs the income certification per beneficiary, the eligibility documentation, and a documented connection between the service rendered and the activity scope. For area-benefit activities, the file needs the geographic area definition, the census-tract LMI calculation, and the documentation that activities are open to all residents of the area.

Weak national-objective documentation is the single most common HUD monitoring finding for CDBG subrecipients. It is also one of the most expensive — disallowed activities can result in repayment of the entire activity cost back to the city, and ultimately back to HUD.

IDIS and the Reporting Chain

The City of Chicago is the CDBG grantee; DPD administers the program. Subrecipient data does not flow directly into HUD’s IDIS — it flows through DPD into IDIS. The reporting chain works like this:

• The subrecipient executes activities and collects underlying data: beneficiary counts, income certifications, expenditures, accomplishments, demographics.
• The subrecipient reports that data to DPD on the contractually required cadence (typically quarterly).
• DPD enters the activity setup, accomplishment data, and drawdowns into IDIS.
• HUD monitors IDIS data and pulls subrecipient files when discrepancies arise.

The subrecipient’s exposure: data submitted to DPD has to be accurate at the point of submission, because DPD is reporting it upstream and HUD is reading it. A subrecipient that submits inflated beneficiary counts to DPD creates an IDIS data integrity finding that HUD attributes to the city, and the city, in turn, attributes back to the subrecipient. The remediation cost is high.

Environmental Review: Don’t Commit Before Clearance

CDBG-funded activities are subject to environmental review under 24 CFR Part 58. The City of Chicago, as the responsible entity, performs environmental review. The subrecipient cannot commit CDBG funds or undertake choice-limiting actions — signing a construction contract, executing a property purchase, beginning physical work — before the environmental review is complete and the city has obtained any required HUD release of funds.

This is one of the most common pre-clearance findings. A subrecipient eager to move on a project signs a contract before the environmental review concludes; HUD finds it during monitoring; the activity becomes ineligible.

The fix: have a written hold on commitments until the environmental review clears, with the project lead and the fiscal lead both signing off before any contract is executed.

Davis-Bacon, Section 3, and Other Cross-Cutting Requirements

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

• Including the current Davis-Bacon wage determination in the construction contract.
• Conducting a preconstruction conference with the contractor.
• Collecting certified payrolls weekly throughout the project.
• Reviewing payrolls for accuracy and conducting periodic on-site labor interviews.
• Investigating complaints and documenting findings.
• Submitting Davis-Bacon documentation to DPD on the schedule the agreement specifies.

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, with subrecipient data submitted through DPD.

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 and Prep

CDBG dollars count toward the federal Single Audit threshold. A 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. Single Audit prep for a CDBG subrecipient typically includes:

• A Schedule of Expenditures of Federal Awards listing CDBG and any other federal expenditures by funding source and Assistance Listing number.
• Auditor selection of major programs based on risk; large CDBG subawards are routinely selected.
• Compliance testing across the applicable Compliance Supplement areas: activities allowed/unallowed, allowable costs, cash management, eligibility, equipment and real property, matching, period of performance, procurement, program income, reporting, subrecipient monitoring, special tests and provisions.
• Submission of the SF-SAC and reporting package to the Federal Audit Clearinghouse.

A clean Single Audit is the price of admission for the next year’s CDBG funding. Material findings produce HUD-attention findings against the City of Chicago, which produces tighter monitoring of the subrecipient. The single audit threshold guide and common single audit findings cover the federal angle.

Documentation Files to Maintain

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

• Subrecipient agreement file. Original agreement, every amendment, signed cover letters.
• National-objective file. Per-activity documentation of national-objective compliance — area-benefit calculation, limited-clientele certifications, or housing income documentation.
• Beneficiary file. Per-person eligibility documentation as required by the activity type.
• 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 contractor’s quote threshold, sole-source justifications.
• Davis-Bacon file. Wage determinations, certified payrolls, on-site interview records, investigation files for any complaints.
• Section 3 file. Section 3 plan, training and employment records, contracting records with Section 3 business concerns.
• Environmental review file. Documentation that the city’s environmental review was complete and any required HUD release of funds was obtained before commitment.
• 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, Federal Audit Clearinghouse confirmations.

For broader audit prep, the audit prep checklist and the CDBG-specific compliance worksheet cover the operating cadence.

Where Chicago CDBG Subrecipients Get Caught

Recurring findings cluster in five areas.

• National-objective documentation thin. A limited-clientele activity with income certifications missing for some beneficiaries; an area-benefit activity with the LMI calculation undocumented.
• Pre-clearance commitments. Contracts signed or work commenced before the environmental review concluded.
• Davis-Bacon failures. Missing certified payrolls, missing wage determinations on covered contracts, untimely back-wage corrections.
• Procurement undocumented. Purchases above the policy threshold without quotes, sole-source justifications written after the fact.
• Public service cap. CDBG public service activities are capped at 15 percent of the entitlement allocation; subrecipient programmatic creep into public-service-coded activities can push the city over the cap.

Software and Workflow Considerations

CDBG compliance is a documentation-management problem and a beneficiary-data integrity problem at once. The 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 income certification with HUD-compliant documentation.
• A document repository organized to the audit file structure above with retention rules enforced for at least five years past the program-year reporting deadline.
• A subrecipient monitoring workflow if the subrecipient further subcontracts.

Spreadsheets work for a single small activity. They do not scale to a multi-activity CDBG portfolio plus Davis-Bacon, Section 3, and Single Audit prep.

Where to Start

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

1. Read your subrecipient agreement, including all special conditions. The activity scope, national objective, and reporting cadence are in there.
2. Verify the environmental review status before you commit any funds or sign any contract. If the city hasn’t completed it, do not move.
3. Build the national-objective documentation pattern at activity setup, not after the first beneficiary is served.
4. Calendar every reporting deadline — quarterly progress, drawdowns, Section 3, Davis-Bacon, Single Audit, closeout.
5. If your activities involve construction, set up the Davis-Bacon workflow before you sign the first construction contract. Retrofitting Davis-Bacon mid-project is expensive.

DPD does not renew agreements with subrecipients that produce repeated monitoring findings. Compliance is the precondition to staying in the CDBG portfolio.

For state-level context, see the Illinois nonprofit profile. For city-level context including DPD and other Chicago agencies, see the Chicago nonprofit profile.

DEFINITION

CDBG

Community Development Block Grant. Annual formula grant from HUD to states and entitlement cities to fund community development activities benefiting low- and moderate-income persons, eliminating slums and blight, or addressing urgent needs. Governed by 24 CFR Part 570.

DEFINITION

DPD

Chicago Department of Planning and Development. The city department that administers CDBG, HOME, ESG, and other HUD CPD funds for the City of Chicago and manages subrecipient agreements with implementing nonprofits and other entities.

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

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.

DEFINITION

Section 3

HUD requirement at 24 CFR Part 75 that, where economic opportunities are generated by certain HUD-funded activities, recipients direct training, employment, and contracting to the maximum extent feasible to low- and very-low-income persons.