Reporting and Closeout

The Data You Did Not Collect Cannot Be Reported

Every federal grant award contains a section titled “Reporting Requirements.” It specifies what reports are due, when they are due, what data they must contain, and in what format. This information is available on the day the award is signed — not at the end of the performance period, not at the quarterly deadline, and not when the program officer sends a reminder. The reporting requirements are known before a single dollar is spent or a single patient is served.

And yet, the most common failure pattern in grant-funded healthcare programs is discovering at reporting time that the required data does not exist. The program was implemented without building the data collection infrastructure that the reports demand. The result is a scramble — manual chart reviews, retroactive spreadsheet construction, financial crosswalks assembled from memory — that produces data of questionable completeness and uncertain reliability. This is not a reporting problem. It is a program design failure that manifests at reporting time.

The thesis is simple and non-negotiable: reporting requirements must be reverse-engineered into program workflows at the point of award acceptance. If the final report requires patient-level outcome data linked to specific grant objectives, then the intake process, the encounter documentation, and the data system must capture those linkages from the first patient encounter. Anything else is hoping the data will materialize, and it will not.

Reporting as Continuous Infrastructure

Federal grant reporting is governed by 2 CFR 200.328-200.329 (for non-federal entities) and shaped by agency-specific requirements from HRSA, SAMHSA, CMS, and others. The regulations establish a framework; the award terms specify the details. Together, they define a reporting obligation that runs continuously through the performance period.

Progress and performance reports are the narrative and quantitative account of what the program accomplished during the reporting period. They are typically required semi-annually or quarterly, depending on the agency and award terms. HRSA cooperative agreements commonly require semi-annual progress reports. SAMHSA discretionary grants often require quarterly Government Performance and Results Act (GPRA) data submissions. These reports ask specific questions: How many people were served? What services were delivered? What milestones were achieved? What barriers were encountered? The questions are not surprises. They are printed in the notice of award.

Financial reports use the SF-425 (Federal Financial Report), the standard form required by most federal agencies per 2 CFR 200.328. The SF-425 reports cumulative expenditures against the approved budget, broken out by federal share and recipient share. It is due quarterly or semi-annually, as specified in the award terms. The SF-425 requires expenditures reported by the budget categories established in the approved application — personnel, fringe, travel, equipment, supplies, contractual, other, indirect. If the grantee’s accounting system does not track expenses by these categories, producing the SF-425 requires a manual crosswalk from whatever cost structure the organization actually uses. This crosswalk is where errors concentrate.

Performance measure reports are program-specific data submissions tied to the agency’s performance measurement framework. HRSA’s Bureau of Primary Health Care requires Uniform Data System (UDS) reporting for health center grantees. SAMHSA requires GPRA/GPRAMA data, including the National Outcome Measures (NOMs) tool administered at intake, follow-up, and discharge. These instruments collect standardized data on demographics, service utilization, clinical outcomes, and functional status. The data elements are defined in the grant program guidance, and the instruments are available before the program launches.

The final report is the comprehensive account of the entire performance period — a synthesis of what was proposed, what was accomplished, what was learned, and what will be sustained. Per 2 CFR 200.344(a), the final performance report is due no later than 90 calendar days after the end of the period of performance. The final financial report (SF-425) is due on the same timeline. For HRSA awards, the final report is submitted through the Electronic Handbooks (EHBs) system. SAMHSA requires final progress reports through its own reporting portal. The final report is not a formality. Federal program officers review it, and it influences future funding decisions — both for the specific grantee and for the program as a whole.

The Data Retrofit Problem

The pattern is predictable enough to have a name in practice, if not in the literature: the data retrofit.

An organization implements a grant-funded program. Staff are hired. Services are delivered. Patients are seen. The program is, by most operational measures, running. Then the first progress report comes due, and the program manager discovers that the data required for the report was never systematically collected.

The mechanism is straightforward. Program implementation is driven by clinical and operational urgency — hire staff, stand up services, serve patients. Reporting requirements are perceived as administrative overhead, deferred to “when the report is due.” But the report requires data that can only be collected during service delivery: patient demographics linked to grant-specific categories, encounter data tagged to grant objectives, outcome measures administered at specific intervals, financial expenditures coded to grant budget lines. None of this data can be reconstructed accurately after the fact.

The retrofit attempt produces characteristic failures:

Incomplete data. Outcome measures that were supposed to be administered at intake were not. There is no baseline, making pre-post comparison impossible. SAMHSA’s GPRA tool, for example, requires administration at intake, six-month follow-up, and discharge. If the intake administration was skipped for the first cohort of clients, those clients cannot contribute to the outcome analysis. The data is not missing at random. It is systematically absent for the earliest participants — the ones who would demonstrate the longest follow-up.

Misaligned categories. The financial system tracks expenses by department or cost center. The grant requires expenses by budget category. A nurse’s salary is split across three cost centers (clinic operations, outreach, administration) but must be reported as a single personnel line item allocated proportionally to the grant. Without a cost allocation methodology established at the outset and applied consistently, the quarterly SF-425 becomes a forensic accounting exercise.

Unreliable aggregation. When data is collected retroactively — through chart reviews, staff recall, or manual tallies — it carries systematic bias. Staff remember successes more readily than failures. Charts contain what was documented, not what occurred. Aggregation from inconsistent sources produces numbers that are internally contradictory or that fail basic consistency checks (e.g., total patients served exceeds the sum of patients by service category).

The cost of the data retrofit is not just the staff time consumed by the scramble. It is the opportunity cost of what those staff could have been doing — delivering services, improving the program, preparing for sustainability. And it is the reputational cost: a final report built on retrofitted data is visibly weaker than one built on prospectively collected data. Federal program officers can tell the difference.

Closeout: The 90-Day Clock

Closeout is the formal process of concluding the federal award. It is governed by 2 CFR 200.344 and begins when the period of performance ends. The grantee has 90 calendar days to complete all closeout actions. This is not a suggestion. It is a regulatory requirement, and failure to complete closeout on time can result in enforcement actions under 2 CFR 200.339, including suspension of future awards.

The closeout checklist is defined in regulation:

Final SF-425. The final Federal Financial Report must account for all expenditures through the end of the period of performance. All costs must be obligated by the end date and liquidated within the closeout period (or within a longer period if the award terms specify one). Unliquidated obligations that cannot be completed must be de-obligated, and the corresponding funds returned. Per 2 CFR 200.344(d), the federal agency will recover unobligated balances — funds that were authorized but neither spent nor committed — as part of closeout.

Final progress report. The comprehensive narrative of program accomplishments, measured against the objectives and milestones stated in the approved application. This is where the quality of prospective data collection pays off. An organization that built reporting infrastructure into the program can generate the final report from existing data. An organization that did not faces weeks of reconstruction.

Equipment disposition. Per 2 CFR 200.313(e), equipment with a current per-unit fair market value in excess of $5,000 that was acquired with federal funds requires disposition instructions from the federal agency. The grantee may be required to return the equipment, transfer it to another federal program, or compensate the federal government for its share. This requires an equipment inventory — a list of items purchased, their acquisition cost, their current condition, and their fair market value. Organizations that did not maintain this inventory throughout the award period must create it during closeout, which means locating items that may have been moved, repurposed, or surplused without documentation.

Record retention. Per 2 CFR 200.334, financial records, supporting documents, statistical records, and all other non-federal entity records pertinent to the federal award must be retained for a period of three years from the date of submission of the final expenditure report. If any litigation, claim, or audit is started before the expiration of the three-year period, the records must be retained until resolution. This is not just financial records. It includes programmatic records, personnel records for grant-funded staff, procurement documentation, and any evidence used to support reported milestones.

Subrecipient closeout. If the grantee passed funds through to subrecipients, each subrecipient must also complete closeout — final financial and progress reports, equipment disposition, record retention. The prime grantee is responsible for ensuring subrecipient closeout is completed. Per 2 CFR 200.332(d), the pass-through entity must monitor subrecipient compliance, including during closeout.

Healthcare Example: The Telehealth Grant That Closed Badly

A 25-bed critical access hospital (CAH) in eastern Washington receives a three-year HRSA Telehealth Network Grant Program award for $900,000 to expand behavioral health and specialty care access via telehealth. The program launches on schedule. Equipment is purchased — telehealth carts, videoconferencing licenses, peripheral devices. A telehealth coordinator is hired. Clinical partnerships are established with a regional psychiatric group and an endocrinology practice. Patient encounters begin in month four.

At month 30, the program manager begins assembling the final report. Three problems surface immediately.

Problem 1: Outcome data exists but is not grant-aligned. The EHR captured every telehealth encounter — date, provider, diagnosis, duration. But the grant’s required outcome categories — “reduction in unnecessary emergency department utilization,” “improvement in PHQ-9 scores for behavioral health patients,” and “increase in specialty care access within 30 days of referral” — were never mapped to the EHR data fields. ED utilization data sits in a different system. PHQ-9 scores were administered inconsistently and not linked to the telehealth program flag. Referral-to-appointment intervals were never tracked. The encounter data is voluminous but cannot answer the questions the grant requires.

Problem 2: Financial tracking does not match grant budget categories. The hospital’s accounting system tracks expenses by department. The telehealth coordinator’s salary is in the “Administration” cost center. Equipment was capitalized under “IT Infrastructure.” Travel for training was coded to “Professional Development.” None of these map directly to the SF-425 budget categories in the approved grant application. The CFO’s office must reconstruct three years of expenses, re-categorize each transaction, allocate shared costs, and reconcile to the draw-down records in HRSA’s Payment Management System. This takes six weeks of a senior accountant’s time.

Problem 3: Equipment disposition was never planned. Three telehealth carts ($8,500 each) and two diagnostic peripherals ($6,200 each) exceed the $5,000 threshold requiring disposition documentation. No equipment inventory was maintained. One cart was moved to a satellite clinic. One peripheral was sent for repair and never returned. The current location, condition, and fair market value of each item must be established, and HRSA must be contacted for disposition instructions — all within the 90-day closeout window.

The final six months of this three-year program become a data remediation project. The telehealth coordinator, who should be optimizing workflows, training clinical staff, and planning for sustainability, instead spends 60% of her time reconstructing data. The CFO assigns a senior accountant to the crosswalk project full-time for six weeks. The IT department is pulled in to trace equipment. The final report is submitted on day 88 of the 90-day window, and the program officer notes that the outcome data is “limited” — a characterization that will appear in the grant program’s portfolio review and may influence the hospital’s competitiveness for future awards.

The fix: A reporting requirements matrix created during the first 30 days of the award. The matrix maps every required report to its data elements, identifies where each data element will be captured, assigns responsibility for collection, and establishes a verification cadence. For the telehealth grant, this means: EHR encounter templates that include a grant program flag and link to outcome measures; a cost allocation methodology established with the CFO’s office before the first expense is charged; an equipment log initiated at the point of purchase with annual inventory verification; and a quarterly dry-run of the progress report, testing whether the data actually exists to answer the required questions. The total cost of this infrastructure is approximately 40 hours in the first month. The cost of not building it is six months of remediation and a weakened final report.

Warning Signs

No reporting requirements matrix at award acceptance. If the program team cannot produce a document that maps every required report to its data sources, collection methods, and responsible parties within 60 days of award, the organization will be retrofitting data at reporting time.

Financial coding does not match grant budget categories. If the first SF-425 requires a manual crosswalk from the accounting system to the grant budget, the problem will compound with every subsequent report. The crosswalk should be built once, at award setup, and applied consistently.

Outcome measures not administered from day one. If the grant requires pre-post measurement and the baseline instrument is not administered at the first patient encounter, those patients are permanently excluded from the outcome analysis.

Equipment purchases not logged in a grant-specific inventory. If equipment above $5,000 is purchased and tracked only in the general asset system without grant-specific tagging, disposition at closeout will require forensic reconstruction.

No dry-run reports during the performance period. If the first time anyone attempts to produce a complete progress report is when the report is actually due, the gaps will be discovered under deadline pressure with no time to remediate.

Integration Hooks

Program Evaluation (PF Module 5 — Logic Models and KPI Design). Reporting data and evaluation data are the same data, collected differently depending on whether reporting infrastructure was designed into the program. When a logic model is built at program design and the KPIs are derived from it, the reporting requirements and the evaluation framework align naturally — the same data serves both purposes. When reporting is treated as a compliance exercise disconnected from evaluation, the organization collects data twice (once for the funder, once for the evaluator) or, more commonly, collects data only for the funder and has nothing for the evaluator. The integration point is at program design: the logic model should map directly to the reporting requirements, and both should map directly to the data collection plan. This is not extra work. It is the same work, done once, with two outputs.

Operations Research (OR Module 4 — Critical Path and Network Flow). The reporting timeline is a milestone dependency in the implementation plan. If the first progress report is due at month six, and it requires three months of program data, then the data collection infrastructure must be operational by month three at the latest — which means it must be designed and built in months one and two. Working backward from reporting deadlines through data collection requirements to infrastructure build-out is a critical path calculation. Programs that do not include reporting infrastructure on the critical path discover, at the first reporting deadline, that they have a data gap equal to the time between program launch and the point when someone finally set up the data collection. CPM applied to the grant lifecycle should treat “reporting infrastructure operational” as a predecessor to “first patient served,” not as a parallel task that can be deferred.

Product Owner Lens

What is the reporting/compliance problem? Grant reporting requirements are fully specified at award but are not reverse-engineered into program workflows, producing data gaps that are discovered at reporting deadlines and remediated poorly under time pressure.

What mechanism explains the bottleneck? Reporting is treated as a periodic administrative event rather than a continuous data collection function. The program generates activity; the reporting system requires structured data about that activity. Without infrastructure to bridge the two, activity occurs but reportable data does not accumulate.

What controls or workflows improve it? A reporting requirements matrix created at award acceptance that maps every required data element to a collection point, a responsible role, and a verification cadence. Quarterly dry-run report generation that tests data completeness before the actual report is due. Cost allocation methodology established at award setup and applied at the point of transaction, not reconstructed quarterly.

What should software surface? A report-readiness dashboard that shows, for each upcoming report, the percentage of required data elements that are currently populated, the data elements that are missing or incomplete, and the time remaining until the report deadline. For financial reports, a real-time view of expenditures by grant budget category (not by cost center) with variance from the approved budget. For closeout, a countdown with checklist status for each closeout requirement — final SF-425, final progress report, equipment disposition, subrecipient closeout, record retention confirmation.

What metric reveals risk earliest? Data completeness rate, measured continuously. If the grant requires quarterly encounter data tagged with outcome categories, and only 60% of encounters in the current quarter have the required tags, that is a leading indicator of a reporting gap — visible now, not at the reporting deadline. The second early metric is budget category alignment: the percentage of grant expenditures that are coded directly to grant budget categories at the point of transaction versus those requiring manual reclassification. A declining direct-coding rate signals that the cost allocation methodology is breaking down, and the next SF-425 will require increasing manual effort.