What a CDFI Expects After the Check Clears: Covenant Reporting, Job-Count Attestations, and Site Visits
Most creators treat the wire as the finish line. For a CDFI-financed project, it is the start of a reporting relationship that runs for the life of the award or loan. The money arrives with covenants attached, and those covenants generate documents you will sign, numbers you will defend, and visits you will host.
This is not a compliance lecture. It is a map of what actually gets asked, when it gets asked, and what happens when the answer is late or wrong.
What “covenant reporting” means in practice
A covenant is a contractual promise. In CDFI lending and grant-making, covenants typically fall into three buckets: financial (maintain a minimum liquidity ratio, submit audited statements within 120 days of fiscal year end), operational (maintain insurance, keep collateral in good repair), and impact (create or retain a stated number of jobs, serve a defined geography or income band).
The CDFI Fund’s own program pages describe a formal “Compliance and Reporting” stage that follows closing and disbursement for Capital Magnet Fund awardees. That structure is the template: award, close, disburse, then report on a schedule the funder sets. The specific frequency and format are defined in your award agreement or loan documents, not in a generic public checklist. If you have not read those documents line by line, you do not yet know your reporting calendar.
Practical consequence: if your award agreement requires quarterly impact reports and you have been operating on an annual rhythm, you are already behind. Pull the agreement, find the reporting section, and build a calendar from it.
Job-count attestations: the number that gets audited
Job creation is the most common impact covenant and the most commonly mishandled. The problem is definitional. A “job created” can mean a full-time equivalent position, a headcount, a position filled for at least 90 days, or a position tied to a specific facility. Each definition produces a different number from the same payroll data.
An attestation is your signed statement that the number is accurate under the definition in your agreement. It is not a marketing figure. If your agreement says “permanent full-time equivalents employed at the project site as of the reporting date,” then contract workers, part-time staff, and employees at a different location do not count, regardless of how you described them in the campaign.
Three tradeoffs to weigh before you sign the attestation:
- Headcount versus FTE. Headcount is easier to document but inflates the number. FTE is defensible but requires hours data. If your payroll system cannot produce hours by employee by site, you cannot attest to FTE without manual reconstruction.
- Point-in-time versus cumulative. A point-in-time count (jobs as of December 31) is simpler to verify. A cumulative count (jobs created since closing) requires you to track attrition and backfill. Choose the definition that matches your recordkeeping, not the one that produces the larger number.
- Self-reported versus third-party verified. Some funders accept a signed officer attestation. Others require payroll records, W-2 summaries, or a CPA review. The cost of third-party verification should be priced into the project budget before you accept the covenant.
If you cannot produce the documentation the definition requires, the attestation is not a formality. It is a representation that can trigger a default finding.
Site visits: what triggers them and what gets examined
Site visits are not random. They are typically triggered by one of four events: a scheduled monitoring cycle, a material change in the project (new location, new ownership, construction delay), a covenant breach or late report, or a request for additional disbursement.
What gets examined depends on the funder, but the pattern is consistent. The visitor will want to see the physical asset or operation, match it against the representations in your application and reports, review records that support your impact numbers, and interview the person responsible for day-to-day operations. For a housing or facilities project, that means walking the site. For a job-count covenant, that means looking at payroll or personnel files.
The CDFI Fund’s impact blog has flagged compliance monitoring as a recurring topic for certified CDFIs, including the Annual Certification Report. That is a reminder that monitoring is not a one-time event. It is a cycle, and the site visit is one data point in it.
Preparation that actually helps:
- Have the reporting file assembled before the visit, not during it. Payroll summaries, lease or deed documents, insurance certificates, and the prior period’s attestation should be in one place.
- Know who will answer questions about the impact numbers. If the person who prepared the attestation is unavailable, someone else must be able to explain the methodology.
- Document any variance between the reported number and what the visitor observes. A written explanation prepared in advance is better than an improvised one.
If the visitor finds a discrepancy, the follow-up is typically a written finding with a cure period. The cure period is defined in your agreement. Missing it converts a finding into a default.
How this flows down to crowdfunding-backed ventures
If your project received capital from a CDFI, either directly or through an intermediary, the reporting obligations flow down. The intermediary’s loan agreement with the CDFI contains covenants. The intermediary’s agreement with you contains a subset of those covenants, often with tighter deadlines because the intermediary has to aggregate and report upward.
This is where community capital organizers get surprised. You may have run a Reg CF campaign, raised from your community, and then layered CDFI-originated capital on top. Ongoing reporting obligations may apply under Regulation Crowdfunding depending on the terms of your offering; confirm them with the offering documents and your counsel. Those obligations are separate from the CDFI covenant reporting. They are not substitutes. You can be current with the SEC and in breach of your CDFI covenant at the same time.
Practical step: build a single compliance calendar that lists every reporting obligation, its source document, its due date, and the person responsible. If the same number (jobs, for example) is reported to two different parties under two different definitions, note both definitions and produce both numbers. Do not assume one satisfies the other.
What happens when reporting slips
The consequences are graduated, but they are real. A late report typically triggers a notice and a cure period. A material misstatement in an attestation can trigger a default finding, which can accelerate repayment, freeze further disbursements, or disqualify you from future funding rounds.
For CDFI Fund awardees, the compliance and reporting stage is a condition of the award, not an afterthought. The Capital Magnet Fund page describes a ten-times investment requirement, meaning awardees must produce housing and community development investments at least ten times the size of the award. That multiplier is not a suggestion. It is a covenant, and it is measured through the reporting you submit.
If you are a sub-recipient or borrower, the consequence may be less visible but equally direct: the intermediary cannot report upward without your data, so your late report becomes their late report, which becomes their finding. The relationship damage is often more costly than the penalty.
Questions worth answering before you sign
These are the questions a CDFI expects you to have answers for, and the questions you should ask before accepting the capital.
- What is the exact definition of a “job” in this agreement, and what documentation satisfies it?
- What is the reporting frequency, and what is the format? Is there a template, or do I build one?
- What triggers a site visit, and who bears the cost of preparation?
- If I miss a reporting deadline, what is the cure period, and what happens if I miss that?
- Are the impact covenants measured at the project level or the entity level?
- If I raise additional capital from other sources, does that change the reporting?
None of these questions are adversarial. They are the questions that separate a project that can absorb CDFI capital from one that cannot. The check clearing is the easy part. The reporting is the work.
Legal and tax interpretation in this article is the author’s interpretation of publicly available program descriptions and standard lending practice. It is not legal advice. Your award agreement or loan documents control.
