Current & Pending Support Form by Agency

A researcher who has just generated a Current and Pending Support Common Form in SciENcv for one federal proposal often assumes the same document, or at least the same profile, carries straight over to the next agency’s application. It mostly does — that is the entire point of the National Security Presidential Memorandum 33 (NSPM-33) harmonization effort — but not completely. NSPM-33 standardizes what a Common Form asks a senior/key person to disclose. It does not force every federal research agency onto the identical tool, the identical effective date, or the identical field-by-field requirement. This guide compares the Current and Pending Support Common Form as it actually exists across agencies today: which agencies generate it in SciENcv, where the fields genuinely diverge, and how to build one profile that produces correct, agency-specific documents without re-keying the same data four separate times.

Last verified September 2026 against SciENcv’s own help documentation (NCBI Bookshelf), NSF’s NSPM-33 policy pages, and NSF’s Current and Pending Support FAQ. This is a fast-moving, multi-agency rollout — re-check the specific funding agency’s current instructions before relying on an effective date here for a live submission.

What NSPM-33 actually standardizes — and what it leaves to each agency

NSPM-33 sets a government-wide baseline: senior/key personnel on federally funded research must disclose current and pending support, and that disclosure must use a common, harmonized data structure so it can be compared consistently across agencies and used for research-security screening. What NSPM-33 does not do is hand every agency an identical, ready-to-use online form on the same day. Each agency must separately work with its own Paperwork Reduction Act officer to get its specific implementation of the Common Form approved by the Office of Management and Budget, and each then sets its own effective date, its own enforcement mechanism, and, within the bounds of the shared structure, some of its own additional required fields.

The practical result is a form that looks and behaves almost identically wherever you encounter it — because the underlying schema is shared — but that is not interchangeable in every particular. Two agencies using the Common Form is not the same as two agencies accepting one document unmodified.

The fields on the Current and Pending Support Common Form

Across agencies, a Current and Pending Support Common Form is built from repeated entries, one per active or pending project, position, or in-kind resource. The core fields that appear in every agency’s version are:

Field	What it captures
Project/Proposal Title	The name of the specific award, application, or in-kind arrangement.
Source of Support	The funding organization — federal agency, foreign government, foreign or domestic institution, industry sponsor.
Identifying Number	The award or proposal number, where one has been assigned.
Status	Active or pending.
Total Award Amount and Period	Cumulative funding and the start/end dates it covers.
Location of Project	The institution where the work is actually performed, which is not always the applicant institution.
Person-Months Per Year Committed	Effort the individual is actually devoting, which agencies note may differ from formally budgeted effort.
Overlap	A statement of overlap, or lack of it, with the project being proposed.

That shared core is where the similarity ends for some agencies. NSF’s own Current and Pending Support guidance separately requires a brief statement of Overall Objectives for every listed project, proposal, or in-kind contribution — a field NIH’s worked-through Common Form example does not carry as its own line item. Small differences like this are exactly why copying a completed form from one agency’s document into another’s is not a safe shortcut; see NIH’s Other Support Common Form guide for the fully worked NIH example and its complete disclosure/exclusion rules.

Which agencies generate the form in SciENcv — and which don’t yet

SciENcv (Science Experts Network Curriculum Vitae), the shared NIH/NSF-hosted tool behind My NCBI, is where most researchers actually build these documents. SciENcv’s own help documentation is explicit that it does not yet cover every federal research funder:

Agency	SciENcv document generation	Notes
NSF	Mandatory	SciENcv became mandatory (fillable PDF option retired) for Biographical Sketch and Current & Pending Support for proposals due on or after October 23, 2023.
NIH	Mandatory	Mandatory for due dates on or after January 25, 2026 (NOT-OD-26-018); system-level validation became a hard error on May 8, 2026 (NOT-OD-26-079). Requires an ORCID iD linked to eRA Commons.
DOE	Supported	Listed among SciENcv’s supported agencies per its own help documentation.
USDA	Supported	Listed among SciENcv’s supported agencies per its own help documentation.
Other agencies (e.g. NASA, DOD components)	Not confirmed in SciENcv as of this writing	SciENcv’s own documentation describes “other agencies forthcoming” without naming which or when. Confirm the specific solicitation’s current instructions rather than assuming SciENcv generation is accepted or required.

That last row matters more than it might look. It is tempting to assume that because NSPM-33 is a government-wide policy, every federal funder now accepts a SciENcv-generated Common Form. What is actually confirmed, directly from SciENcv’s own help material, is a shorter list: NIH, NSF, DOE, and USDA. A solicitation from an agency not on that list may still require the NSPM-33-aligned data content, delivered through that agency’s own portal, PDF template, or submission system rather than through SciENcv — that is a real, meaningful difference in mechanism even where the underlying disclosure obligation is functionally the same.

Generating one SciENcv profile, multiple agency documents

SciENcv is built around a single ongoing profile per researcher, not a fresh document per proposal. The practical workflow:

Build the profile once. Enter appointments, positions, and active/pending support as structured data in the SciENcv profile, not as a one-off document.
Generate a document per target agency and document type. From that same profile, use SciENcv’s “Generate Document” step and select both the document type (Biographical Sketch, or Current & Pending Support) and the specific target agency. SciENcv formats the output to that agency’s current Common Form layout from the shared underlying data.
Re-verify before each submission. Because Current and Pending Support must reflect the individual’s status as of the certification date, a document generated for one proposal is not automatically valid for a later one if anything — a new award, a changed appointment — has changed in between.
Know the one hard constraint on reuse. SciENcv’s own documentation is explicit that when copying an existing document as the starting point for a new one, “document types must match” — a Current and Pending Support document can only seed a new Current and Pending Support document, never a Biographical Sketch, regardless of agency. The underlying profile data is shared; the generated documents are not freely interchangeable across document types.

For the parallel Biographical Sketch side of the same workflow, see SciENcv: How to Create Your NIH and NSF Biosketch and the worked NSF Biographical Sketch example.

Where agencies genuinely diverge on the same form

Effective and enforcement dates are not synchronized. NSF’s SciENcv mandate predates NIH’s by more than two years (October 2023 vs. January 2026), and each agency has run its own separate leniency-period-to-hard-error timeline.
Extra required fields differ. NSF’s Overall Objectives statement is a documented example of a requirement layered onto the shared Common Form structure rather than a universal field every agency enforces identically.
Persistent identifier requirements. NIH requires an ORCID iD linked to the individual’s eRA Commons account and displayed in the Common Form’s Persistent Identifier field before the form validates; confirm the equivalent linkage requirement, if any, for each other agency separately rather than assuming it is identical.
Certification workflow. Under the SciENcv-generated Common Form, the individual senior/key person certifies the document themselves, a shift from older institution-assembled practice — but the specific certification language and where it is captured is agency-defined, not shared verbatim.
Adjacent documents are not always in SciENcv at all. NSF’s Collaborators & Other Affiliations (COA) disclosure, a related but distinct requirement, uses NSF’s own required spreadsheet template uploaded directly to Research.gov — it is not generated inside SciENcv, even though it sits alongside the Biosketch and Current and Pending Support in the same proposal package. See NSF Collaborators & Other Affiliations (COA) Template.

A practical workflow for researchers applying to more than one agency

For a PI or co-investigator with proposals pending at more than one federal agency in the same cycle:

Keep the SciENcv profile itself current continuously — add a new award or appointment as soon as it becomes active or pending, rather than reconstructing history at each proposal deadline.
Generate a fresh document per submission, selecting the correct target agency each time, rather than reusing a PDF exported for a different agency’s proposal.
Confirm the receiving agency’s current mandate status before assuming SciENcv output will be accepted — check the specific funding opportunity announcement or program officer guidance, especially for agencies not yet confirmed as SciENcv-supported.
Route foreign appointments, in-kind resources, and any research-security-relevant disclosures through the institution’s sponsored-programs or research-security office regardless of which agency’s form is being generated — the underlying compliance obligation under NSPM-33 does not vary by agency even where the form mechanics do.

Common mistakes

Assuming “Common Form” means one universal document. It means a shared data structure, not a single interchangeable file accepted unmodified everywhere.
Assuming every federal agency is on SciENcv. Only NIH, NSF, DOE, and USDA are confirmed in SciENcv’s own documentation as of this writing; others require checking the current solicitation.
Copying a Current and Pending Support document as the seed for a Biographical Sketch, or vice versa. SciENcv’s document-copy feature only works within the same document type.
Treating an NSF-generated document as automatically satisfying NIH’s requirement, or the reverse. Confirm the specific agency’s current instructions rather than assuming a document generated for one funder transfers unmodified to another.
Letting a generated document go stale. A Current and Pending Support disclosure certifies accuracy as of a specific date; a new award, ended appointment, or changed in-kind resource means the document needs regenerating and recertifying, not silent reuse.

Frequently asked questions

Is the Current and Pending Support Common Form identical across every federal agency?

The underlying data structure is shared under NSPM-33, but effective dates, some additional required fields, certification workflow, and whether the document is generated in SciENcv at all currently differ by agency. Treat “Common Form” as a shared schema, not a single interchangeable document.

Can I generate one document in SciENcv and submit it to both NIH and NSF?

No. SciENcv generates a separate, agency-formatted document for each target agency from the same underlying profile data. Select the correct target agency each time you generate a document, and regenerate rather than reuse a PDF built for a different agency’s proposal.

Does every federal research agency require SciENcv?

No. SciENcv’s own help documentation confirms NIH, NSF, DOE, and USDA, with other agencies described as forthcoming rather than named. Agencies outside that list may still require NSPM-33-aligned Current and Pending Support content, just delivered through their own submission process rather than SciENcv.

What if my target agency isn’t listed as supporting SciENcv generation?

Check that agency’s current funding opportunity announcement or program officer guidance directly, and route the question through your institution’s sponsored-programs office — do not assume a SciENcv-generated document will be accepted, or that no equivalent disclosure is required, without confirming.

How often does the form need to be regenerated?

Whenever the underlying facts change — a new active or pending award, a new or ended appointment, a changed in-kind resource — and at each agency-specific checkpoint (for example, NIH’s Just-in-Time and RPPR checkpoints), even if nothing has changed, since certification itself confirms currency as of that date.

Related CASRAI resources

References

NSF, “NSPM-33 Common Form: Biographical Sketch,” nsf.gov/policies/nspm-33/common-form-biosketch
NSF, “Current and Pending (Other) Support FAQs,” nsf.gov/funding/senior-personnel-documents/faq/current-pending
NSF, “Senior Personnel Documents,” nsf.gov/funding/senior-personnel-documents
NCBI, SciENcv Help documentation, NCBI Bookshelf (NBK154494), ncbi.nlm.nih.gov/books/NBK154494
NIH Guide Notice NOT-OD-26-018, “NIH’s Implementation of Common Forms for Biographical Sketch and Current and Pending (Other) Support for Due Dates on or after January 25, 2026”
NIH Guide Notice NOT-OD-26-079, “Announcement of Upcoming System Enforcement of Common Forms and End of NIH’s Leniency Period” (issued April 21, 2026)

The Current and Pending Support Common Form, Agency by Agency