NSF Collaborative Proposal Guidelines

When a research project involves investigators at more than one organization, NSF’s Proposal & Award Policies & Procedures Guide (PAPPG, NSF 24-1, Chapter II.E) gives proposers two distinct ways to structure the submission: a single proposal from a lead organization that subawards funds to the collaborating institutions, or a collaborative proposal from multiple organizations, in which each participating organization prepares and submits its own proposal and NSF links them together for joint review. This guide covers the mechanics of the second option — the “separately submitted” collaborative proposal — since it is the one that trips up research offices most often: it looks like several independent proposals but has to behave, procedurally, as one coordinated submission.

For the related but distinct mechanism where a collaborator provides only a signed statement of intent rather than a full separately submitted budget, see NSF Letter of Collaboration: What It Must (and Must Not) Say. For the general institutional and governance issues that arise once a multi-institution project is underway, see Managing Multi-Institutional Research Collaborations. This page focuses narrowly on what NSF’s PAPPG requires at the proposal-preparation and submission stage.

Two Ways to Structure a Multi-Institution NSF Proposal

PAPPG Chapter II.E recognizes two mechanisms for involving more than one organization in an NSF-funded project:

Subawards under a single proposal. One organization submits the entire proposal, including a subaward budget and budget justification for each collaborating organization. NSF makes a single award to the lead organization, which then executes subaward agreements with the others. This is the more common structure when one institution is clearly the intellectual and administrative lead.
Collaborative proposal from multiple organizations (separately submitted). Each participating organization prepares and submits its own complete proposal through Research.gov. NSF links the linked proposals for joint merit review and, if funded, issues a separate award to each organization rather than a single award with subawards. This structure is typically used when each organization has significant intellectual and administrative independence in the project — for example, when co-PIs at different universities each need their own award for internal accounting, effort reporting, or funder-relations reasons.

Neither mechanism is inherently required or preferred by NSF; the choice is the proposing team’s, made in consultation with each institution’s sponsored programs office. See the comparison section below for the practical tradeoffs.

How the Separately Submitted Mechanism Works in Research.gov

Under the separately submitted model, every proposer identifies, during proposal setup in Research.gov, whether the submission is “a collaborative proposal from multiple organizations.” Doing so exposes a linking step: the lead organization’s proposal generates an identifier that each non-lead organization enters into its own proposal so Research.gov associates the submissions with one another for programmatic and review purposes. All linked proposals must be submitted to the same NSF program and the same target date or deadline; NSF reviews them as a single, coordinated project rather than as unrelated submissions that happen to share a title.

Because the system depends on that linkage being entered correctly by every participating organization’s Sponsored Research Office (SRO) before submission, a mismatch or omission is one of the most common reasons a collaborative proposal set is flagged during NSF’s compliance check — sponsored programs offices should confirm the link status with every collaborating institution before final submission, not just before the lead institution’s own deadline.

Title, Timeline, and Program Must Match Across Every Linked Proposal

PAPPG requires every proposal in a separately submitted collaborative set to carry:

The same project title, and that title must begin with the words “Collaborative Research:” followed by the shared project title — this is a literal, checked requirement, not a style suggestion.
The same requested start date and project duration across all linked proposals.
Submission to the same NSF program, so that all linked proposals are reviewed together by the same panel.

A mismatch on any of these — a co-PI’s institution using a slightly reworded title, or requesting a different start date than the lead organization’s proposal — can cause NSF’s system to fail to recognize the proposals as linked, which risks the non-lead proposal being reviewed (or returned) independently of the rest of the project.

What the Lead Organization Submits

The lead organization’s proposal in a separately submitted collaborative set carries the full project narrative and is expected to include, per PAPPG Chapter II.E and Chapter II.D’s standard content requirements: the cover sheet, project summary, project description, references cited, a biographical sketch and current-and-pending-support disclosure for its senior personnel, a budget and budget justification for its own portion of the work, a data management and sharing plan, a mentoring plan where required by the funding mechanism, and a facilities/equipment/other-resources statement describing the resources it is contributing. The project description must explain the roles each participating organization will play, the overall managerial and coordination arrangements across institutions, and why the work genuinely requires a multi-organizational effort rather than being structured as a single-PI project with subawards.

What Each Non-Lead Organization Submits

A non-lead organization’s proposal within the same collaborative set is narrower in scope. It does not repeat the full project description; instead it typically includes: a cover sheet, a table of contents, biographical sketches and current-and-pending-support disclosures for its own senior personnel, its own budget and budget justification, and a facilities/equipment/other-resources statement for its own portion of the work. Each organization’s Authorized Organizational Representative (AOR) certifies its own proposal independently — there is no single institution-wide certification that covers the whole collaborative set. This is the point most often missed by research offices new to the mechanism: every linked organization has full, independent submission and certification responsibility for its own proposal, even though the group is reviewed as one project.

Budget and Certification Requirements Per Organization

Because each participating organization submits and is awarded separately, each one is responsible for its own budget, its own budget justification, and its own set of NSF certifications — conflict-of-interest compliance, current-and-pending-support accuracy, and the other standard AOR certifications required at submission. There is no consolidated, cross-institutional budget document the way there would be for a subaward-based proposal; each organization’s cost share of the project stands as its own funding request, reviewed and (if successful) awarded on its own terms. Research administrators should not assume that indirect cost rates, cost-sharing commitments, or budget periods automatically align across organizations just because the proposals are linked — each institution applies its own negotiated rate and its own institutional budget policies, and those differences are expected, not a compliance problem, as long as the underlying project timeline and scope stay consistent across the set.

Subaward vs. Separately Submitted: Practical Tradeoffs

Consideration	Single proposal with subawards	Separately submitted collaborative proposal
Number of NSF awards issued	One, to the lead organization	One per participating organization
Post-award administration	Lead organization manages subaward agreements and monitoring	Each organization administers its own award directly with NSF
Best fit when	One institution is the clear intellectual/administrative lead	Co-PIs at different institutions have genuinely independent roles and each needs its own award for internal reasons
Certification burden	Lead organization’s AOR certifies the whole proposal; subrecipients typically provide only a scope/budget/commitment letter	Every organization’s own AOR certifies its own proposal independently
Linking risk	Not applicable	Requires every SRO to enter matching link information correctly before submission

Common Mistakes That Cause Compliance Problems

Titles that don’t match exactly, or omit the “Collaborative Research:” prefix. Confirm the exact string with every collaborating institution before anyone finalizes their proposal in Research.gov.
Mismatched start dates or durations entered independently by different SROs without checking against the lead organization’s proposal.
Missing or incorrect linking information entered by a non-lead organization, which can leave that organization’s proposal unlinked to the rest of the set.
Treating a non-lead proposal as a lighter-weight formality and skipping full internal routing/review, when it in fact carries the same independent AOR certification obligations as any standalone NSF proposal.
Confusing this mechanism with a Letter of Collaboration, which is a much lighter commitment used when a partner is contributing expertise or facilities access but not requesting its own budget or award — see NSF Letter of Collaboration for that distinction.

Frequently Asked Questions

Does each organization in a separately submitted collaborative proposal get its own award number?

Yes. If NSF funds a separately submitted collaborative proposal, each participating organization receives its own, separate award, distinct from the awards made to the other collaborating organizations, even though the proposals were reviewed together as one project.

Can a collaborative proposal mix subawards and separately submitted organizations?

The two mechanisms address different collaboration structures, and PAPPG’s guidance is written around choosing one or the other for a given set of collaborating organizations on a project. Where a project has a mix — a lead institution issuing subawards to some partners while another partner submits its own linked proposal — the sponsored programs offices involved should confirm the specific structure directly with the cognizant NSF program officer before submission, since Research.gov’s linking mechanism assumes a consistent structure across the collaborative set.

What happens if a non-lead organization’s proposal isn’t linked correctly?

An unlinked proposal risks being processed and reviewed independently of the rest of the collaborative set rather than as part of the coordinated project, which undermines the point of submitting collaboratively in the first place. Sponsored programs offices should verify link status with every participating institution well before the submission deadline, not assume it was entered correctly elsewhere.

Is a separately submitted collaborative proposal the same as a subaward?

No. A subaward is a single NSF award to a lead organization that then passes funds to a collaborating institution under a subrecipient agreement. A separately submitted collaborative proposal results in a distinct, direct NSF award to each participating organization. The choice between the two affects who NSF’s award terms and post-award compliance obligations run to directly.

Related CASRAI Resources

This guide reflects NSF’s Proposal & Award Policies & Procedures Guide (PAPPG), NSF 24-1, Chapter II.E, the current base edition as of writing; NSF has issued supplemental policy notices (e.g., PAPPG 24-1 Supplements 1 and 2) addressing other topics since that base edition, and NSF has stated it is deferring a renumbered full edition pending alignment with a broader OMB Uniform Guidance update. Always confirm current requirements directly against the live PAPPG at nsf.gov/policies/pappg and your own sponsored programs office before submission, since NSF revises this guide periodically.