MFTRP Annual Re-Certification for Key Personnel

Certifying that senior/key personnel are not participating in a malign foreign talent recruitment program (MFTRP) is not a one-time, pre-award step. At both NSF and NIH, it is now a recurring obligation that comes due again on every active award, with its own deadline, its own system, and its own consequences for missing it. This page focuses specifically on that recurring re-certification requirement — what triggers it, who has to act, and what happens if a research office lets the deadline slip. For the underlying statutory definition of an MFTRP and the consequences of participating in one, see CASRAI’s general MFTRP guide.

Why this became a recurring requirement, not a one-time check

The certification framework traces back further than the CHIPS and Science Act itself. Section 223 of the FY2021 National Defense Authorization Act (Public Law 116-283) first directed federal research agencies to require disclosure of all current and pending research support from applicants and to have institutions certify that covered individuals were made aware of their disclosure obligations — the broader policy architecture of “certify, and keep certifying” that research security compliance now runs on. The CHIPS and Science Act of 2022 then added a specific, narrower prohibition on top of that architecture: 42 U.S.C. § 19231(b)(3) bars federal research agencies from making an award where a covered individual named in the proposal is participating in an MFTRP, and 42 U.S.C. § 19232(a) operationalizes that as a certification duty for both the individual and the institution.

Because an MFTRP relationship can begin or change at any point during a multi-year award — not just at the moment of application — agencies have implemented the certification as something that has to be refreshed periodically for the life of the award, not answered once and filed away. NSF and NIH have each built their own annual mechanism to do this, on different timelines and through different systems.

NSF: annual certification through Research.gov

NSF’s recurring certification applies to Principal Investigators and co-Principal Investigators — the senior/key personnel roles NSF currently requires to certify individually — on NSF awards made on or after May 20, 2024. Starting June 7, 2025, NSF began prompting all covered PIs and co-PIs to certify annually, directly inside Research.gov, that they are not a party to an MFTRP.

Where it happens: the prompt appears after signing into Research.gov; the individual’s response is recorded in the Academic/Professional Information section of their Research.gov profile.
Who certifies: each person designated as senior/key personnel certifies individually — there is no single institutional click that covers a whole award team.
How often, per person: once per year. A PI or co-PI holding several active NSF awards does not have to repeat the certification for each one — a single annual certification satisfies the requirement across all of that person’s active awards.
What it’s tied to: NSF also requires updated Current and Pending (Other) Support documentation to accompany annual and final progress reports, so research offices are usually already touching an award’s reporting cycle around the same time the MFTRP certification comes due — the two are separate obligations, but reviewing them together is the practical approach most offices take.
Consequence of missing it: NSF has stated that any proposal missing a current, signed certification for a senior/key person will be rejected or withdrawn for non-compliance. Combined with the underlying prohibition, an individual who is a party to an MFTRP is separately ineligible to serve as senior/key personnel on an NSF proposal or award made after May 20, 2024, independent of the certification mechanics.

NSF has indicated it intends to extend the post-award certification requirement beyond PIs/co-PIs to all senior/key personnel at a future date — research offices tracking this for a broad portfolio of awards should not assume the PI/co-PI-only scope is permanent.

NIH: annual certification tied to the RPPR

NIH’s recurring mechanism runs on a different clock and through a different document than NSF’s. For NIH awards where a Research Performance Progress Report (RPPR) is due on or after January 25, 2026, each individual serving as senior/key personnel must certify annually — at the time of that RPPR — that they are not a party to an MFTRP.

Mechanism: the certification is a signed statement, submitted as a flattened PDF, uploaded into Section G.1 (“Special Notice of Award and Funding Opportunity Announcement Reporting Requirements”) of the RPPR.
Required statement language: the certifying individual states, in substance, “I [name] certify that, at the time of submission, I am not a party to a malign foreign talent recruitment program.”
File naming: NIH’s guidance specifies a naming convention for the uploaded certification — one PDF per senior/key person, named to identify that individual.
Overlap with the pre-award certification: this RPPR-tied recertification is distinct from — but works alongside — the pre-award MFTRP certification NIH now collects through its Common Forms for Biographical Sketch and Current and Pending (Other) Support (effective for due dates on or after January 25, 2026, under Guide Notice NOT-OD-26-018). A senior/key person who already submits a signed certification as part of an updated Common Form for a given reporting period generally does not also need to file a separate RPPR statement for that same period — but the two are tracked through different documents, and a research office managing a large portfolio should not assume one automatically covers the other without checking which document a given reporting cycle actually requires.

See CASRAI’s NIH Other Support Template guide for how the pre-award certification interacts with NIH’s broader Other Support and Current and Pending Support disclosure rules, and CASRAI’s NIH Senior/Key Personnel Training Requirements guide for the related (but separate) research-security training obligation that runs on its own schedule.

Other agencies

DOE, NASA, DOD, and other CHIPS-Act-covered agencies are implementing the same underlying statutory prohibition and certification duty, but as of this writing NSF and NIH have published the most fully documented, agency-wide mechanics for the recurring annual piece specifically. A research office supporting investigators across multiple funders should confirm each agency’s current notice directly rather than assuming NSF’s Research.gov cadence or NIH’s RPPR-tied cadence applies elsewhere.

Why the recurring nature matters more than it looks

Treating the annual re-certification as a formality repeats the same exposure every year rather than closing it out once. A few consequences follow directly from that:

Fresh false-statement exposure each cycle. Certifications made to a federal agency are subject to the general federal prohibition on false statements (18 U.S.C. § 1001). Because the MFTRP certification recurs annually, a knowingly false certification in year two of an award creates its own, independent exposure — it isn’t covered or excused by an accurate certification made at the original proposal stage.
Status can change mid-award. The point of an annual (rather than one-time) certification is that a senior/key person’s circumstances can change after an award starts. A relationship that didn’t exist — or wasn’t yet disclosable — at proposal submission can exist by the next certification cycle, and the recurring requirement is built specifically to catch that.
Missed deadlines have submission-level teeth. Both agencies now enforce this through hard blocks rather than soft reminders: NSF rejects or withdraws a proposal missing a current certification for a senior/key person, and NIH’s related pre-award certification became a hard eRA system error (not just a warning) as of May 8, 2026, under NOT-OD-26-079.

Building a re-certification tracking process

Because the obligation resets annually and is tied to different trigger events per agency (an anniversary-style prompt at NSF, an RPPR due date at NIH), the practical failure mode isn’t researchers refusing to certify — it’s a research office not knowing a certification is due until a proposal or report is already blocked. A workable process generally needs to:

Maintain a per-award, per-person calendar of certification trigger dates (NSF: track when each PI/co-PI last certified, so a coming due date is flagged well before a new proposal or renewal needs to go in; NIH: track each award’s RPPR due date, since that’s what triggers the requirement, not a fixed calendar anniversary).
Confirm which document actually satisfies the certification for a given reporting cycle before assuming it’s covered — a Common Form submission and an RPPR Section G.1 upload are not automatically interchangeable at NIH.
Route the reminder to the individual, not just the department — certification at both agencies is made by the named senior/key person, not by an administrator on their behalf.
Keep a record of what was certified and when, separate from the proposal or RPPR system itself, so the office can answer “when did this person last certify” without re-pulling the underlying federal submission.

Frequently asked questions

Is the annual re-certification the same thing as the certification made at proposal submission?

No. The pre-award certification (made when a proposal is submitted) and the annual/recurring certification (made during the life of an active award) are two applications of the same underlying statutory duty, but they are tracked separately and, at NIH, are literally different documents submitted through different systems.

What happens if a PI misses NSF’s annual certification deadline?

NSF has stated that a proposal missing a current, signed certification for a senior/key person will be rejected or withdrawn for non-compliance. There is no indication NSF treats this as a curable formality after the fact within a pending proposal review — the certification needs to be current before submission.

Does NIH require the MFTRP certification with every single RPPR?

For awards where an RPPR is due on or after January 25, 2026, yes — each senior/key person certifies at that reporting point, unless an equivalent certification has already been captured through an updated Common Form submission for that same reporting period.

If a senior/key person holds multiple NSF awards, do they certify separately for each one?

No. NSF’s annual certification is per person, not per award — one certification in Research.gov in a given year satisfies the requirement across all of that person’s active, covered NSF awards.

Does a false annual certification carry the same legal exposure as a false initial certification?

Both are certifications made to a federal agency and both fall under the general federal false-statements prohibition (18 U.S.C. § 1001). The recurring nature of the requirement means that exposure is created fresh at each certification cycle, not just once at the original proposal stage.

Related CASRAI resources

Malign Foreign Talent Recruitment Program (MFTRP): Definition, Disclosure, and Consequences — the statutory definition and base certification requirement this page builds on
NIH Other Support Template — how MFTRP certification interacts with NIH’s foreign-disclosure rules
NIH Senior/Key Personnel Training Requirements — the related research-security training obligation
Current and Pending Support
Other Support (NIH format)
ORCID iD for NIH Senior/Key Personnel
Research Security Officer (RSO)
Undue foreign influence
Foreign talent recruitment programme — the broader, multi-jurisdiction concept
Export Control Reform and Research Security