Connecting Financial Aid and Advancement: The Org-Structure Gap Behind Most Stewardship Failures

Most donor stewardship failures don't look like failures from the inside. They look like everyone doing their job.

The Director of Financial Aid is awarding scholarships against criteria, watching application volume, and trying to spend the dollars the institution committed to spend. The VP of Advancement is cultivating donors, reporting on impact, and protecting the relationships that fund the next gift. Each function is running its own playbook competently. The problem is that at most institutions, the donor lives in Advancement and the fund lives in Financial Aid, and the two functions barely share a system.

That gap is where stewardship breaks. Not because anyone is failing at their job. Because nobody owns the seam between them.

What the data shows about the seam

In our 2026 Donor Stewardship Benchmarking Report (125 higher education foundations), three numbers describe this gap with uncomfortable clarity.

Seventy-one percent of foundations had at least one scholarship fund go unawarded last year, and 37 percent had no protocol for telling the donor it happened. That is the seam, measured. The fund didn't perform, the awarding side knew, and the donor side either didn't know or didn't have a process for saying anything.

Forty-six percent of stewardship programs operate on one full-time equivalent or less. Half of advancement teams are experimenting with AI to extend capacity, but only 15 percent are using it consistently. The capacity to manually stitch FA and Advancement together, fund-by-fund, donor-by-donor, doesn't exist at most institutions. It hasn't existed for years.

Only one in three foundations could confidently report on the impact of donor-restricted funds across their portfolio. The other two thirds had pieces of the picture: awarded amounts in the SIS, donor history in the CRM, fund balances in Finance, narrative reports in someone's drafts folder. The information existed. It just wasn't connected.

These aren't separate problems. They're the same problem looked at from different angles. The org chart has two functions. The donor's experience has one.

Why the structure produces the gap

The organizational logic is reasonable on its own terms.

Financial Aid is built around the student-fund match. Eligibility, compliance, packaging, disbursement, satisfactory academic progress. The work is high-volume and high-stakes, and the team is measured on awards completed on time and in compliance.

Advancement is built around the donor relationship. Cultivation, solicitation, recognition, retention. The work is long-cycle and relationship-intensive, and the team is measured on dollars raised, donor retention, and reportable impact.

A donor-restricted scholarship fund sits in the middle. The donor side cares about whether the fund honored intent. The aid side cares about whether the dollars were awarded compliantly. Neither side, on its own, owns the question of whether the donor knows what the aid side did with the donor's gift.

At a small foundation, the seam gets stitched manually by one or two people who happen to talk to each other. At anything larger, the stitching doesn't happen at all unless someone built a process for it, and the process tends to live as a spreadsheet that gets out of date inside a quarter.

The handoffs that actually close the loop

The institutions doing this well aren't the ones with the largest teams. They're the ones who treat the FA–Advancement seam as its own operational surface and define the handoffs explicitly.

A few patterns show up consistently across the foundations in the benchmark who reported high confidence in their donor-restricted impact reporting.

A shared view of the fund, not the function. The high-confidence institutions had stitched together a single read-only view of each fund: award status from the SIS, donor history from the CRM, fund balance and restrictions from Finance, recipient outcomes where available. The view didn't replace the source systems. It made the fund the unit of analysis, not the department.

A monthly or cycle-aligned check-in with both teams in the room. The check-in is short, fund-level, and operational. Which funds are tracking under-utilization. Which donors are due for an interim communication. Which restrictions need a conversation before the next cycle. The output is a small list of fund-specific actions with owners. The institutions running this had cut the unawarded-with-no-communication number close to zero.

One protocol per fund state, owned at the seam. Awarded in full, partially awarded, unawarded with explanation, criteria-modified, held intentionally. Each state has a template, a turnaround time, and an owner who isn't fully in FA or fully in Advancement. At some institutions that owner is a stewardship coordinator. At others it is a foundation operations role. The title matters less than the fact that the seam has a name on it.

Donor-aware criteria conversations. When a fund consistently tracks under-utilization, the protocol triggers a conversation about widening the criteria. The conversation includes the donor early. Most donors understand the operational reality once it is explained. The institutions that bring donors into the conversation early reported the strongest renewal patterns.

None of this is new. All of it is hard to maintain without infrastructure that holds the seam together.

Where AwardSpring fits in

AwardSpring's role here is to make the awarding side of every donor-restricted fund visible in one place. Application volume, eligibility match, awards made, dollars disbursed, criteria notes, recipient outcomes — the operational record of how each fund performed each cycle lives in the system the Financial Aid team already uses to run the cycle.

When that record is shared with Advancement on a consistent cadence — fund by fund, with utilization and applicant context attached — the monthly check-in stops being a manual data pull and becomes a working session against a current view. Both functions can have the conversation about which funds are tracking under-utilization, which donors are due for an interim communication, and which criteria need a look before next cycle, against the same numbers.

That shared operational surface is the practical starting point for closing the FA–Advancement seam. It doesn't replace the stewardship relationship or the FA team's compliance work. It gives both functions one place to meet on the fund itself.

Where to start before the platform conversation

If your foundation is sitting on this gap, the most useful starting point is not software. It is a one-page inventory.

For each donor-restricted scholarship fund, list four things. Who in Financial Aid owns the awarding side. Who in Advancement owns the donor side. What was communicated to the donor about last cycle's outcome, and on what cadence. What needs to change about the criteria or the timing before the next cycle.

The inventory is rarely complete on first pass. The gaps it surfaces are the map of where the FA–Advancement seam is doing the most damage, and they are the right starting point for a platform conversation, an org-structure conversation, or both.

Recently we presented the 2026 Donor Stewardship Benchmarking Report. If you missed the live session, the recording and full data set are available.