What NIH Reviewers Actually Look for in a Team Management Plan (And Why Most Miss It)

You really need to get a higher score this time, but something about what you're dreaming of doing just isn’t legible to the reviewers.

You've read the FOA three times, and you know you’re being responsive.

You've looked at funded examples. You feel like you’ve got the right formula.

You've written and rewritten the sections about the working groups. You're reasonably confident it checks the boxes.

But here's what nobody tells you:

Reviewers aren't just looking to see that you’re checking boxes. They're looking for evidence that your team has already solved the problem most multi-investigator grants fail to overcome - not weak science, but collaboration liability.

The team management plan is your chance to prove you've solved it before they fund you.

That you’ve already thought about where things are going to get tough and you’ve built the plan with that in mind.

I often work with teams all looking at the same phenomenon, but at different units of analysis. A geospatialist, an infectious disease scholar, a pathologist. The perfect mix for a study of malaria or coronavirus. Yet, what are the real barriers to combining data, finding an analytical pathway forward, or writing a paper together?

In other words, what is bubbling up beneath the surface that could take the team a year or two in?!?.

A visual showing what integrated team architecture actually looks like vs. a siloed multi-investigator structure. How the people fit together. Where the integration points are. This is your visual differentiator; no one else in this space is showing it.

Over the years, simple images and figures that make legible what collaboration will look like make reviewers trust what they’re investing in.

Convergence science scoring shoots up.

So, what’s the course correction here?

Prepare these five elements of a team management plan, even if its not an explicity request in the FOA:

1. Integration architecture. Not just who is on the team. How the disciplines actually connect. Where the knowledge exchange happens. What the handoff points look like.

2. Decision ownership. Who decides what. How disagreements get resolved. What happens when the science pulls in two directions at once.

3. Credit and authorship clarity. How contribution gets recognized. Whether junior team members are protected. Whether the structure incentivizes genuine collaboration or just parallel work.

4. Conflict protocol. Not conflict avoidance — conflict readiness. Evidence that the team has named the friction points in advance and built a path through them, sometimes in the form of an advisory board.

5. Leadership capacity: Not just a strong PI. Evidence that the team has the collective capacity to integrate across disciplines under pressure. A steering committee or a team science on staff can really help here.

Lastly, draw on the teaming language of Integrative Capacity as the organizing lens.

Capacity Within — the PI's individual leadership capacity.

Capacity Across — the team's integration infrastructure.

Both have to be present for a management plan to convince reviewers.

A diagram showing what Capacity Within + Capacity Across looks like in a funded team structure. Again, make it visual, make it specific, make it something a PI can hold up and say, "This is what we're building."

The team management plan that moves scores isn't longer. It isn't more detailed.

It's more honest about your readiness to deliver as a unit.

It shows reviewers a team that has already asked the hard questions — not the science questions, but the human ones. How do we make sure the collaboration is real and not just listed in biosketches and past publications?

That honesty reads as readiness. And readiness is what reviewers are actually scoring.

Ready to Construct Your Multiple PI Plan?

If your team management plan reads like a compliance document, it's not too late to make it an architecture document.

That's a different kind of writing. And it starts with a different kind of conversation with your team.

That conversation is exactly what I help teams have before the deadline, not after the subpar score.