NIH Biographical Sketch Common Form 2026: SciENcv, ORCID, and Avoiding ASSIST Errors

What Flipped on May 8, 2026

Something changed quietly in early May that affects every NIH applicant going forward. From May 8, 2026 onward, the warnings that ASSIST threw when you submitted a legacy biographical sketch format converted to hard errors — meaning the application simply won't go through. The leniency period that started when NIH first required Common Forms on January 25, 2026, under NOT-OD-26-018, ended with the final AIDS standard receipt date for Cycle 1 on May 7. After that date, system warnings became system stops.

If you submitted an application before May 8 using the old FORMS-H biosketch PDF, you probably saw a warning but got through anyway. That window is now closed. Any new application, JIT submission, RPPR, or prior approval request with a due date on or after May 8 must use Common Forms prepared through SciENcv. There's no workaround and no template you can fill out offline.

This isn't NIH being difficult. The shift is part of a cross-agency standardization effort — NIH, NSF, and other federal funders are converging on a shared researcher profile infrastructure. It comes with real benefits once you're past the initial setup friction. But the transition has been bumpy, particularly for labs with investigators who've never used SciENcv and for multi-PI teams where one person can hold up an entire submission because their ORCID isn't linked.

What the Two Common Forms Actually Are

Two forms are affected by this mandate. The first is the Biographical Sketch Common Form, which replaces the old NIH-specific biosketch PDF. NIH's version includes both the federal-wide Biographical Sketch Common Form and an NIH Biographical Sketch Supplement that covers NIH-specific fields the common form doesn't include. In practice the content looks familiar: personal statement, positions and honors, contributions to science, and additional information. The structural change is that SciENcv is the only authorized tool to generate it.

The second is the Current and Pending (Other) Support Common Form. It replaces the old NIH-specific current-and-pending document and, like the biosketch, must now come from SciENcv. The content requirements are similar to before — list all active and pending research support, in-kind contributions, and resource commitments — but the new form adds more structured fields for effort reporting, project period, and overlap disclosures. If you have foreign financial interests or institutional conflicts requiring special disclosure, there are designated fields for those. Grants management officers are checking them closely, so fill them accurately.

Neither form has a blank PDF template you can download and complete manually. You build both in SciENcv, export the PDFs, and attach them to your submission. SciENcv can pull data from your NCBI My Bibliography, your eRA Commons profile, and linked sources, but the quality of what it pre-populates depends entirely on how current those upstream records are. If your My Bibliography is outdated, budget time to clean it up before your first SciENcv run.

ORCID Is Now Required for Every Senior and Key Person

This is the requirement that's caught the most teams off guard. For applications with due dates on or after January 25, 2026, every senior or key person listed on the application must have an ORCID ID, and that ID must be linked to their eRA Commons Personal Profile.

ORCID (Open Researcher and Contributor ID) is a free, persistent identifier for researchers — a permanent author tag that follows your work across institutions, name changes, and career transitions. If you don't have one, registration takes about five minutes at orcid.org. Registration isn't the hard part. The linking step is.

To link your ORCID to eRA Commons, you log in to your personal eRA Commons profile and connect the account through the profile settings. ORCID must authorize the connection, and if your ORCID email differs from your eRA Commons email, verification can take several business days. Don't wait until the week before submission to do this for anyone on the team.

Walking Through the SciENcv Workflow

You access SciENcv through NCBI — the same system as PubMed and My Bibliography. Log in with your eRA Commons credentials or NCBI account; both work. Once you're in, create a new document, select the Biographical Sketch Common Form, and choose NIH as your agency. That step matters: selecting NIH ensures the NIH Biographical Sketch Supplement is included alongside the federal common form. Skipping the agency selection is a common first-time mistake that produces a technically valid but NIH-incomplete document.

SciENcv will offer to import data from linked accounts — NCBI My Bibliography for publications, ORCID for professional history if you've loaded it there, and sometimes institutional directory data. Review everything it imports. Autofill isn't reliable: pulled-in entries sometimes carry incorrect dates, missing journal information, or duplicate records from preprint servers. A publication list that looks right at a glance can contain real errors that a careful reviewer will notice.

For the personal statement, SciENcv gives you a text field you fill directly in the tool. The character limit hasn't changed dramatically from prior biosketches, but the interface is less forgiving than writing in Word — no track changes, limited formatting options. Many researchers draft the personal statement in Word and paste it in, then do a final proof in SciENcv before exporting. That workflow is fine; just confirm nothing gets stripped in the paste step.

When you export to PDF, check the formatting carefully. SciENcv handles font and margin compliance, but confirm the page count is what you expect before attaching to your submission. Keep the filename simple — ASSIST sometimes flags PDFs with spaces or special characters in the name. Something like LastName_Biosketch.pdf works without issue.

Plan at least two hours for your first SciENcv biosketch if your publication list needs cleanup, longer if key people need to link their ORCID accounts first. Subsequent submissions go much faster. SciENcv saves document versions, so once the initial setup is done, future updates are targeted edits rather than rebuilds.

Catching ASSIST Errors Before They Block Submission

Since May 8, the most common ASSIST submission errors fall into three categories. All three are fixable with lead time. None are fixable the hour before a deadline.

The fix for all three is the same: build a pre-submission checklist that includes SciENcv verification and ORCID confirmation for every key person, starting at least two weeks before any deadline. These are not edge-case problems — they're appearing in labs that have submitted NIH grants for years. The mandate is new enough that habits haven't caught up yet.

Which Submissions Are Affected

To be concrete about scope: as of May 8, 2026, the Common Forms requirement applies to new applications, resubmissions, revisions, renewals, JIT submissions, RPPRs, and prior approval requests — essentially any submission to NIH with a due date on or after that date. It covers all NIH institutes and centers, and includes K, F, R, T, and U mechanisms. If you're preparing a K99/R00 or an F31 right now, your biosketch must come from SciENcv.

For training program coordinators managing T32 or T35 programs, every trainee biosketch needs to be a compliant Common Form. That can mean setting up SciENcv access for a rotating cohort of students who have little experience with eRA Commons. If your program hasn't already built a one-page SciENcv setup guide for incoming trainees, this summer is a reasonable time to do it — before the next recruitment cycle.

Institutions with strong sponsored programs offices should already have updated their internal workflows. But the ORCID-linking step is personal — no research administrator can complete it on someone else's behalf — so even well-managed programs are seeing delays on that point. There's no administrative shortcut. Build it into your timeline explicitly, the same way you schedule the internal deadline for routing and sign-off.

Frequently Asked Questions