NIH Current and Pending (Other) Support Common Form: What System Enforcement Means in 2026

What Changed on May 8, 2026 — and Why It Matters

The Current and Pending (Other) Support Common Form has been in the works since at least 2024, when NIH and the National Science Foundation began coordinating a single standardized format that both agencies would accept. NIH issued NOT-OD-26-018 in late 2025 requiring the Common Form for all application due dates on or after January 25, 2026. But they also granted a grace period: ASSIST would throw a warning if you uploaded a non-compliant document, not a blocking error. That leniency period officially ended on May 7, 2026 — the last AIDS standard receipt date for Cycle 1. From May 8 forward, the warning is an error, and the error means your package does not transmit.

This is meaningful for two reasons. First, the change affects more than just new R01 applications. The enforcement applies to Just-In-Time requests, Research Performance Progress Reports, and Prior Approval submissions — every touch point where NIH asks a PI to report support. Second, the form itself is different enough from the old "Other Support" document that teams who copy-paste from previous submissions will have the wrong structure even if they remember to upload something. Institutions like UCSF, Stanford, and UNC flagged the changeover specifically because they were seeing compliance gaps even among experienced investigators.

The policy driver is not primarily bureaucratic convenience. NIH and other federal agencies have been under sustained pressure since 2019 to improve detection of undisclosed foreign support and overlapping commitments. The Common Form was designed in part to make those disclosures machine-readable and comparable across agencies. That context explains why the certification step — discussed below — is not optional.

Current Support vs. Pending Support: What the Form Is Actually Asking

The form has two categories, and the distinction matters. Current support is any active grant, contract, or other resource that provides funding or in-kind support to the PI or key personnel — including resources with no direct costs, like institutional protected time or an endowed professorship that buys effort. Pending support is any application or proposal that has been submitted and not yet decided, or that you plan to submit before or concurrent with the NIH application under review. If you have an R01 in at another institute that you submitted last cycle and are still waiting on, it goes in pending. If you plan to submit an R21 in the next cycle as a complement to this work, that can also need to appear depending on timing.

For each entry, the form asks: the project or activity title, the supporting agency or organization, the name of the PI on that project, the award number or proposal identifier, the project period, the total direct costs, and the person months of effort committed by that individual. One update that NIH deployed to SciENcv on April 22, 2026 made zero person months a valid entry — before that update, the system was throwing errors when investigators tried to enter "0" effort for support sources where they hold a named award but contribute no measurable effort, like a shared equipment grant. If you filled out the form before April 22 and ran into that glitch, you may need to regenerate your certified PDF.

What the form does not ask for — and what trips people up — is a long narrative explanation of overlap or non-overlap with the application being submitted. That explanation belongs in your cover letter or in the application itself if the potential for scientific overlap is real. The Common Form is a disclosure document, not an argument. Keep the entries factual and complete; the reviewers and grants management staff will ask you to explain overlap if they think they see it.

The SciENcv Workflow and What Digital Certification Actually Requires

Unlike the old Other Support document, which many investigators prepared as a Word file or a formatted PDF outside any NIH system, the Common Form must be generated through SciENcv — Science Experts Network Curriculum Vitae — the federally sponsored profile system. SciENcv produces a digitally certified PDF that carries a certification tag NIH systems can verify. An Other Support document that looks correct but was not generated through SciENcv will fail the compliance check, even if the content is identical to what the form would contain.

The workflow has five steps. You log in to SciENcv (accessible through NCBI, eRA Commons, or login.gov credentials). You create or update your Current and Pending (Other) Support section, entering each project individually. Once your entries are complete, you generate the PDF within SciENcv — do not download a template and fill it in separately. You then upload that certified PDF to ASSIST or your institution's system-to-system submission interface. Finally, every senior and key personnel on the application must do this separately for themselves. One PI cannot generate a certified document on behalf of a co-investigator.

The time implication is easy to underestimate. If your R01 has four key personnel who each have seven or eight support entries to enter, you are coordinating four separate SciENcv sessions, four PDFs, and four upload confirmations — on top of everything else in the final submission sprint. Institutions with a grants management team often assign someone to coach all key personnel through this step two to three weeks before the deadline. If your institution does not do that, build the time into your own calendar.

Where the Form Shows Up Beyond Your Initial Application

Most investigators think about Other Support only during the initial application. That is a mistake in 2026. The Common Form is now required for Just-In-Time submissions — the request NIH sends after a potentially fundable score, asking for updated support information before the grant can be recommended for an award. JIT is already a stressful moment; receiving a JIT request and then discovering your team's SciENcv entries are months out of date adds an unnecessary scramble. The safe habit is to keep SciENcv current as a rolling practice, not something you reconstruct when a JIT notice arrives.

The form also applies to Research Performance Progress Reports, which are due annually on active grants. Each RPPR requires updated Current and Pending (Other) Support Common Forms for the PI and key personnel. If a co-investigator joined a new collaborative agreement since your last RPPR, that has to appear. If a grant ended mid-year and you did not remove it from a previous document, the current year's RPPR needs a corrected version. Prior Approval requests — for changes in scope, significant budget reductions, or no-cost extensions with activity changes — also require the Common Form as of May 8, 2026. Check the specific Prior Approval request instructions, because not all prior approval types require it, but budget-affecting requests generally do.

Five Errors That Will Stop Your Submission Cold

Uploading a non-SciENcv PDF

A PDF that looks like the Common Form but was not generated through SciENcv lacks the digital certification tag. ASSIST now checks for that tag. The document looks fine to the human eye and fails system validation. There is no workaround — regenerate through SciENcv.

Missing key personnel

Every individual designated as senior or key personnel needs their own certified Common Form. A common shortcut — uploading only the PI's document and relying on old Other Support documents for co-investigators — now triggers a hard error. Confirm your key personnel list early and coordinate their SciENcv sessions before the final week.

Leaving out in-kind and no-cost support

Institutional protected time, endowed chair resources, donated equipment or space from an industry partner, and even significant access to shared core facilities can qualify as reportable support. Reviewers and grants management staff are trained to notice when a PI's effort allocation leaves little room for the proposed work but the form only lists federal grants.

Stale SciENcv data from a prior submission

SciENcv saves your entries across sessions, which is convenient — until you generate a PDF without reviewing and updating entries first. Grants that ended, pending applications that were declined, new collaborations that started: all of these need to reflect the situation at submission, not six months ago. Build in a review step before every certified PDF generation.

Regenerating the PDF after the certified version was uploaded

If a key personnel member updates their SciENcv entries after the certified PDF has already been uploaded to ASSIST, the uploaded version no longer matches the current SciENcv state. That is generally not an error in itself, but it creates confusion if grants management later requests a verification. Set a cutoff date after which no SciENcv entries are changed without uploading a replacement PDF.

Building a System So This Doesn't Sink You at JIT

The investigators I've seen handle this cleanly treat SciENcv as a living document rather than a submission artifact. They update their Current and Pending entries within a week of any change in their support portfolio — a new award letter, a declined application, a subaward that started or ended — rather than reconstructing the history at submission time. It takes less than ten minutes per update when done immediately. It takes two to four hours of scrambling when done from memory under deadline pressure, and the error rate in the scramble version is higher.

For labs with multiple co-investigators, consider designating a single point of contact — a lab manager, a senior postdoc who handles administrative tasks, or the grants coordinator at your department — who tracks which key personnel have current SciENcv entries and chases the ones who need updating four weeks before any deadline. That person does not need to do the SciENcv work themselves; they just need to know who is behind. You also want a shared calendar event, set well in advance, for every RPPR due date on active grants. The RPPR deadline is not negotiable, and discovering at the last minute that three co-investigators haven't touched their SciENcv since the original application is a bad place to be. Keep the system current and the JIT request becomes a thirty-minute task rather than a two-day emergency.

Frequently Asked Questions

Is the Current and Pending (Other) Support Common Form the same as the old "Other Support" document?

No. The old Other Support document was a formatted PDF applicants typically prepared in Word and converted. The Common Form is generated exclusively through SciENcv and carries a digital certification tag. The content categories overlap substantially, but the format, the required fields, and the production workflow are different. You cannot submit the old format for applications due on or after May 8, 2026.

Do I need a separate SciENcv account from my eRA Commons account?

SciENcv can be accessed directly through your eRA Commons credentials — no separate registration is needed if you already have an eRA Commons account. You can also access it through NCBI or login.gov. Some investigators find the NCBI route more intuitive for editing entries; others prefer eRA Commons because the ORCID linkage is handled there. Either path produces the same certified PDF.

What if a co-investigator holds a foreign appointment — does that change what goes in the form?

Yes. Foreign appointments, affiliations with foreign institutions, and any funding from foreign government entities must be disclosed regardless of whether they are formally listed as support in the domestic sense. The research security context behind the Common Form means that omissions here carry more institutional risk than they did under the old Other Support format. If there is any uncertainty about whether a foreign affiliation qualifies, disclose it and let NIH grants management make the determination. The downside of over-disclosure is minimal; the downside of under-disclosure is not.

If my application is submitted before May 8 but my JIT comes after, which format applies?

The format that applies is determined by the date of the subsequent action, not the original application. A JIT request received after May 8, 2026 requires the Common Form even if the underlying application was submitted under the old format. The same logic applies to RPPRs and prior approval requests. When in doubt, contact your NIH Grants Management Specialist — they can tell you exactly which format they expect for your specific situation.

NIH Current and Pending (Other) Support Common Form: What System Enforcement Means for Your 2026 Submissions

Table of Contents