Five Innovators, One Reporting Problem: Who Owns the Data When You Regrant?

In today’s competitive funding environment, you can build a strong regranting initiative and still struggle to explain its combined results. You often discover that each partner tracks progress differently just as your own funder needs one clear account of the work. This is where a pass-through reporting structure becomes invaluable: it connects partner-level information to a credible initiative-wide report. If you regrant funds, you are not only overseeing awards. You are also responsible for assembling the evidence behind the whole.

The intermediary sits in the middle

The structure is simple to describe: one funder, one intermediary, and five implementation partners. The funder needs an aggregate view of the initiative. The partners hold the day-to-day, participant-level reality. Between them, you must bring information from separate organizations together into one accurate, useful account.

Louisville Urban League’s February 20, 2026 announcement offers a local example of this structure. A Healthier Path Forward, funded by the Robert Wood Johnson Foundation and partnered with Render Capital, selected Attane Health, EnVue Health, Feed Louisville, Park DuValle Community Health Centers, and Rae’s Roots Mobile Market. Each team received $200,000 to pilot its solution over an 18-month period, with one or two projects potentially receiving an additional $425,000 to scale.

The initiative is a celebration of community-driven innovation. It also illustrates a practical reporting question for any intermediary: how do you make information from five distinct teams coherent without losing what each team is doing? The teams hold their own program records; the intermediary must make the shared story understandable.

Why this differs from a regular grant

A report from your own program draws on staff, systems, and definitions you can often manage directly. A pass-through report depends on separate organizations, each with its own software, fiscal calendar, data practices, and other funder commitments. Your partners are not employees you can simply instruct to change a field or adopt a new process.

That means alignment has to be negotiated, documented, and maintained. When the award terms leave reporting expectations vague, a partner may submit information that is accurate for its own program but difficult to combine with everyone else’s. Clear expectations help each partner understand what to submit, why it matters, and how you will use it.

Agree on the terms before funds move

Your sub-grant agreement is the place to define a workable reporting relationship. Keep requirements proportionate to the award, but specific enough that you can use the information consistently. Before signing, specify:

• Required data elements: Name each field the partner must report, such as reporting period, service type, outcome, and source of the information. Avoid broad requests like “send progress data.”

• Metric definitions: Explain shared measures in plain language, with a worked example. If you ask for “participants served,” clarify who counts, what qualifies as service, and how to handle repeat participation.

• Reporting frequency and internal due date: Set a schedule that gives you time to review, follow up, and prepare your funder’s report. An internal deadline should come before the funder’s due date.

• A named data contact: Record the person responsible for compiling and answering questions about the submission, not just a job title that may change.

• The consequence of non-reporting: Agree in advance on the response to missing or late reports, such as a correction request, escalation, or other action allowed by the agreement.

A short shared template and a clear data dictionary can make these terms practical. Your agreement should also explain how partners can flag an issue, correct a submission, or request help. That creates accountability without treating reporting as a paperwork exercise.

Make the totals mean something

Five partners reporting the same metric in different ways do not produce a meaningful combined result. If some count a participant at first contact while others count only after a completed service, adding those totals creates a number that looks precise but does not describe a shared measure.

Before collecting reports, decide what can be combined and how. For each metric, choose whether the initiative will report a sum, an average, or a per-partner range, and state the choice. A sum may make sense for a consistently defined count; an average can hide important differences between programs. A range may better show variation when partners deliver distinct approaches. If the underlying definitions do not align, explain the results by partner rather than presenting a misleading portfolio total.

Your shared KPI library should capture the measure’s definition, unit, reporting period, and calculation. For instance, it should distinguish people, households, and service encounters when those represent different things. This makes it easier to compare like with like while keeping each team’s work visible.

Keep the report traceable

Your aggregate report should be reconcilable to the partners’ individual submissions. Keep each original submission, the review notes, any requested corrections, and the final accepted version. Together, these records form the audit trail behind your reported totals.

When your funder asks how a figure was calculated, you should be able to point to a documented method and source records, not rely on someone’s memory of a spreadsheet change. A repeatable review step can check that required fields are present, totals follow the agreed definitions, and unexplained changes receive follow-up.

If your funding terms are governed by federal requirements, review the applicable pass-through duties in 2 CFR 200.332. Foundation and other awards may have different terms, so use the controlling award documents to set your actual obligations.

Protect the opportunity to scale

When future funding depends on demonstrated results, your ability to assemble compatible partner data becomes central to the scale-up case. In A Healthier Path Forward, one or two projects may be selected for an additional $425,000 after the 18-month evaluation period. That outcome makes clear why a well-organized reporting process matters: decision-makers need evidence they can interpret across participating teams.

Strong programs alone do not make a comparable portfolio story. If partners use incompatible measures, you may be unable to show what the initiative accomplished as a whole, even when each team has valuable results of its own. Consistent definitions and documented aggregation give your funder a fairer, clearer basis for understanding both the shared progress and the differences across approaches.

Build the system before signing

Your intermediary role calls for a reporting engine, not a last-minute spreadsheet merge. A practical system includes a shared KPI library, a sub-grantee data template, a monthly aggregation cadence, and one dashboard for both funder reporting and partner management. The same process can help you catch missing submissions, spot inconsistent figures, and give partners timely feedback.

Genesis Consulting helps grant-funded nonprofits structure KPI definitions, templates, dashboards, and reporting workflows through its Board + Funder Reporting System. You can build around your existing systems while making the shared reporting process clear and repeatable.

Final Thoughts

When you regrant, you carry two connected responsibilities: collecting usable information from each partner and reporting an accurate aggregate to your funder. Clear agreement terms, shared metric definitions, consistent aggregation, and a documented audit trail help you meet both obligations and present a stronger case for continued investment.

If you are preparing to issue sub-grants, request a Genesis Consulting Reporting Diagnostic before the agreements are signed. You can establish the reporting structure early, support your partners, and move forward with confidence in the story your data can tell.