The examples in this newsletter are drawn from real partnership experiences. Names and identifying details have been altered to protect privacy.
Who's This For
It's RPPR season. Or maybe you're writing a year-end narrative for a foundation grant. Either way, you're sitting in front of a partnership section that's supposed to capture what you accomplished together, and something feels hollow.
You know the work was good. You know the partnership moved forward. But the words on the page sound like... reporting. Generic. Distant. The kind of language that checks boxes but doesn't breathe.
Worse, you have this nagging suspicion that if your partner read it, they might not even recognize the collaboration you're describing.
This newsletter is for anyone who has written partnership content that technically satisfies requirements but fails to capture what actually happened. For PIs who want their partners to feel represented, not just mentioned. For project coordinators who know there's a better way but aren't sure how to find it.
Here's the uncomfortable truth: most partnership sections fail not because they lack information, but because they lack voice. Specifically, they lack your partner's voice. They describe what happened from a single perspective - yours - and that's exactly why partners read them and feel something is off.
The Partnership Moment
Picture this: You've submitted your annual report. It was a scramble at the end, as it always is, but you got it done. You described the partnership activities, listed the accomplishments, included some numbers. You even quoted your partner in one section.
A few weeks later, you get an email from your partner: "Thanks for sharing the report. A couple things looked a bit different from how I remember them, but I didn't want to make a big deal."
You read between the lines. They're being polite. But what they're really saying is: That wasn't quite our story.
Maybe you described their contribution in terms that felt like underselling. Maybe you framed an outcome in a way that made sense for the funder but didn't reflect how the partner experiences the work. Maybe the quote you attributed to them was something you paraphrased from a meeting six months ago, and it doesn't quite sound like them anymore.
This is the report that partners don't recognize. And it happens constantly - not because researchers are careless, but because the reporting process doesn't naturally include the partnership voice.
Under the Surface
Here's what's really happening: you're writing about your partnership without your partner's participation.
That sounds obvious when stated plainly. But think about how reporting usually works. Deadline approaches. You pull together documentation. You write sections. Maybe you send a draft to partners for "review" - often with a tight turnaround, often when the structure is already set, often framing it as "let me know if anything needs correction."
That's not partnership voice. That's editorial review of a document you authored.
Partnership voice requires something different: regular check-ins where partners record their own perspective in their own words. Not just triage of what needs to get done, but genuine portfolio recording where each partner's viewpoint is captured directly.
Without this process built into your grant management rhythm, you end up with what researchers call "hearsay representation." You're describing the partnership from what you remember, what you documented, what you interpreted - but the partner's actual voice isn't in the source material.
The risk: a slight organizational change at a partner institution can result in an ill-aligned report that surprises everyone. Your partner contact leaves or shifts roles, and suddenly the institutional memory on their side doesn't match what you've written. The report becomes a record of your perception rather than a shared account of what happened together.
