NIST Measurement Science and Engineering Research Grants 2026: $10,000–$500,000 a Year for Up to Five Years

NIST Measurement Science and Engineering Research Grants 2026: $10,000–$500,000 a Year for Up to Five Years

The National Institute of Standards and Technology (NIST) Measurement Science and Engineering (MSE) Research Grant Programs are an open federal funding route for organizations whose research, partnerships, or technical outreach advances NIST’s mission. The 2025-NIST-MSE-01 notice covers work across measurement science, standards, artificial intelligence, advanced communications, advanced manufacturing, nanotechnology, neutron research, information technology, and related fields. It can support a recipient’s own research or the recipient’s portion of collaborative research.

The current Grants.gov record lists September 15, 2026 as the closing date. A June 2026 amendment changed the earlier rolling-submission language: applications must be received in Grants.gov no later than 11:59 p.m. Eastern Time on that date. That change matters. An applicant who saw an older version of the notice or a historic NIST page should plan around the fixed deadline in the current federal record.

This is not a personal fellowship and it is not a general-purpose innovation award. Individuals and unincorporated sole proprietors are not eligible to apply. The applicant must be a qualifying non-Federal entity with a defined project, an appropriate research or partnership purpose, and the organizational capacity to perform the work. NIST encourages a broad range of organizations, including minority-serving institutions and community colleges, but encouragement does not replace the eligibility and technical requirements in the notice.

Key details

The range in the table should be used as a planning reference, not as a guaranteed award amount for every MSE application. The NIST page gives that annual range for the Information Technology Laboratory’s grant program and describes performance periods of up to five years. The umbrella notice covers multiple NIST programs, so applicants should use the full announcement and the relevant technical contact to confirm the appropriate scope and budget.

What this opportunity can support

The notice is intentionally broad, but it is not vague. NIST describes support for activities that develop, expand, strengthen, or sustain NIST partnership programs, as well as research or a recipient’s portion of collaborative research. The federal record identifies areas such as metrology, standards, nanotechnology, artificial intelligence, advanced communications, advanced manufacturing, promotion of U.S. innovation and industrial competitiveness, measurements in science, neutron research, and coordination of the U.S. standards system with government and private-sector organizations.

For an information-technology project, the NIST ITL guidance lists applied and computational mathematics, artificial intelligence, big-data analytics, biometrics, cloud computing, cyber-physical systems, cybersecurity, forensic science, health information technology, high-performance computing, human factors and usability, information access, information processing and understanding, Internet of Things, privacy engineering, and statistical design and analysis. It also says financial support may be provided for relevant education and outreach programs, conferences, workshops, or other technical research meetings, although NIST cannot be an official sponsor or co-sponsor of an event funded through that program.

The practical test is whether the proposed work advances a NIST-relevant measurement, testing, standards, or technology objective. A project should identify the technical problem, explain why measurement quality or standards matter, and show how the expected results can be used by researchers, industry, public agencies, or other users. A generic product-development pitch with no measurement or standards connection is a weak fit, even if the product uses advanced technology.

Who is eligible

The current Grants.gov record says the notice is open to all non-Federal entities, subject to the full NOFO. The listed eligible types include institutions of higher education, nonprofit organizations, for-profit organizations, state and local governments, Indian tribes, hospitals, foreign public entities, and foreign governments. NIST also specifically encourages applications from minority-serving institutions and community colleges.

The exclusion for individuals and unincorporated sole proprietors is important. A researcher may have the right expertise and still need an eligible university, company, nonprofit, hospital, government, or other organization to serve as the applicant. That organization must be able to accept and administer a federal award. A consultant or independent researcher can potentially participate through an eligible entity, but that does not make the individual an eligible direct applicant.

Eligibility should be checked at the organizational level and at the project level. Confirm that the proposed applicant is non-Federal, has the registrations and internal authorization required for Grants.gov, and can manage the financial and technical obligations of the award. If partners are involved, define whether they are subrecipients, contractors, unfunded collaborators, or another type of participant. Do not assume that a letter from a federal laboratory or a commercial partner changes the lead organization’s eligibility.

How to judge fit before drafting

Start with the NIST program or laboratory that best matches the project. The MSE notice spans many technical areas, so “NIST” by itself is not a research rationale. A project about trustworthy artificial intelligence may fit the NIST Artificial Intelligence Innovation Lab’s measurement and evaluation interests. A cybersecurity proposal may need to connect its work to security metrics, conformance testing, privacy risk, cryptography, or another stated objective. A statistical project may be strongest when it addresses uncertainty, experiment design, calibration, interlaboratory comparisons, or statistical methods for machine learning.

Write a one-page fit memo before opening the application forms. Name the relevant NIST unit or objective, quote or paraphrase the matching topic from the NOFO, state the technical question, and list the deliverables. Then identify the user who would rely on the result. The user might be a standards developer, a testing laboratory, an industry sector, a public agency, or a research community. This exercise exposes proposals that are interesting but not sufficiently connected to the notice.

The strongest projects also make the measurement problem visible. Explain what is currently difficult to measure, compare, validate, reproduce, secure, or standardize. Describe the consequence of that gap and the improvement the project will deliver. If the work develops a tool or dataset, specify the validation method, documented limitations, intended users, and path to adoption. If it is collaborative research, identify the division of work and why each partner’s contribution is necessary.

Funding and budget design

NIST’s ITL application page lists an anticipated amount of $10,000 to $500,000 per year and project performance periods of up to five years. That does not mean every proposal should request the maximum or assume five years of support. A defensible budget follows the work plan, technical risk, staffing, equipment, data, travel, subcontracting, and evaluation needs.

Build the request from milestones. For each major cost, state the activity it enables, the person or organization responsible, the timing, and the measurable result. Personnel effort should match the actual tasks. Equipment should be justified by a capability that is necessary to produce or validate the result. Travel should be connected to a technical meeting, collaboration, field activity, or other allowable purpose rather than included as a broad professional-development line.

The Grants.gov record lists no cost-sharing or matching requirement. That simplifies the financial structure, but it does not remove the need to explain institutional resources. Reviewers still need to know whether the team has access to facilities, instruments, data, secure computing, test environments, participants, or partner expertise. Describe existing resources accurately and distinguish committed support from resources that are merely hoped for.

If the proposed work includes a conference, workshop, or outreach activity, connect it to the relevant NIST mission and explain what technical result the activity produces. The ITL page allows support for relevant education and outreach programs and technical meetings, but it says NIST cannot be an official sponsor or co-sponsor for an event funded through the program. That distinction should appear in the project design and budget narrative.

Application process and required preparation

The official NIST application page directs applicants to Grants.gov for instructions and submission. Begin with the full 2025-NIST-MSE-01 package on the federal record, including the current version history and amendment. Treat the amended September 15 date as controlling. A Grants.gov search by the funding opportunity number is useful if the page URL changes.

Before drafting, confirm the applicant’s SAM.gov and Grants.gov registrations, Unique Entity Identifier, organization profile, and Authorized Organization Representative access. Registration problems are administrative issues, but they can prevent a technically excellent application from being submitted. Assign one person to own the submission workspace and another to review the final package for completeness.

The application should present a coherent technical narrative, work plan, budget, timeline, organizational capability statement, and any required federal forms or attachments in the current package. The full NOFO controls the exact page limits, forms, certifications, and formatting rules. Do not rely on an old application template, a prior year’s checklist, or a partner’s memory of the process.

Use a compliance matrix with one row for every required form, narrative element, attachment, and eligibility condition. Add an owner, internal due date, source of evidence, and final file name. The matrix should include the fixed deadline, the 11:59 p.m. Eastern Time cutoff, the relevant NIST program contact, and a final test submission well before the closing hour.

What reviewers are looking for

The NIST ITL evaluation criteria assign a maximum of 30 points across four areas. Technical quality and intellectual merit receive 0–10 points. Potential impact of the results receives 0–10 points. Capability to perform the work receives 0–5 points. Match of the budget to the proposed work receives 0–5 points.

Those weights suggest how to organize the proposal. The research plan should be reasoned, organized, innovative or potentially transformative, and include a reasonable mechanism for assessing success. The impact section should show a plausible path to technical application and a sustained influence on the relevant field, while also explaining alignment with the NIST mission. The capability section should provide evidence about training, accomplishments, facilities, equipment, data access, partner roles, and management. The budget section should make each requested dollar easy to trace to the work.

Avoid treating “innovation” as a substitute for evidence. A reviewer should be able to tell what is new, what has already been demonstrated, what remains uncertain, and what the proposed experiments or development steps will establish. Use baseline measurements, validation datasets, prior publications, pilot results, standards gaps, or partner commitments where available. If evidence is preliminary, label it as preliminary and explain how the project will test it.

Timeline for the 2026 submission

The current deadline is September 15, 2026, at 11:59 p.m. Eastern Time. Work backward from that cutoff rather than treating it as the day to upload files. A practical schedule is:

1. Immediately: confirm applicant eligibility, registrations, the relevant NIST program, and the current Grants.gov package.
2. Before the narrative is final: secure partner roles, facility access, data permissions, letters or institutional approvals, and a realistic technical timeline.
3. At least one week before the deadline: complete the narrative, budget, forms, and attachment checks; ask a technically qualified reader to score the proposal against the four criteria.
4. Before the final day: upload the complete package, resolve validation errors, and submit through the Authorized Organization Representative. Save the Grants.gov tracking information and the submitted files.
5. After submission: retain the final application, monitor the federal record for updates, and respond only through the official channels if NIST requests clarification or additional information.

NIST’s public page lists Patricia Wilburg in the Information Technology Laboratory as a contact for ITL questions, with the email and phone number shown on the page. The umbrella notice covers more than ITL, so a project outside information technology should use the relevant program or agency contact in the current NOFO rather than assume that the ITL contact is the right technical reviewer.

Common mistakes to avoid

The first mistake is submitting as an individual or unincorporated sole proprietor. The second is treating the broad MSE title as permission to propose any attractive science project. A good idea needs a specific NIST connection and a user-facing result.

Another common problem is describing partners without assigning responsibilities. Name the lead, technical leads, facilities, data owners, decision rights, deliverables, and reporting path. A collaboration is persuasive when the relationship solves a defined capability gap; a long partner list without work allocation adds little.

Budget inflation is also risky. A five-year maximum performance period is not a reason to stretch a one-year proof of concept into five years. Conversely, a large equipment request needs a clear utilization plan, procurement timing, maintenance approach, and explanation of why existing resources are insufficient. Keep the requested amount aligned with the maturity of the evidence and the scale of the work.

Finally, do not submit against the old rolling deadline. The 2026 amendment replaced that language with a fixed September 15, 2026 closing date. Check the current Grants.gov record and allow time for organization review and electronic submission problems.

Frequently asked questions

Can an independent researcher apply directly?

No. The federal record says individuals and unincorporated sole proprietors are not eligible. An independent researcher may need to work through an eligible organization that can submit and administer the award.

Can a for-profit company apply?

Yes. For-profit organizations are included among the non-Federal entity types listed in the eligibility information, provided the company and proposed work meet the full NOFO requirements.

Can an organization outside the United States apply?

The current eligibility language includes foreign public entities and foreign governments. An international applicant should read the complete notice and confirm any registration, project, and award-administration requirements before investing in a submission.

Is matching funding required?

Grants.gov lists no cost-sharing or matching requirement for this opportunity. Applicants should still document the facilities, staff time, partnerships, and other resources that make the work feasible.

Is this a grant or a cooperative agreement?

The federal record lists both grant and cooperative agreement as funding instruments. The final instrument depends on the approved project and federal involvement. The applicant should not assume that the award will operate like an unrestricted grant.

What is the maximum award?

The NIST ITL page gives an annual planning range of $10,000 to $500,000 and says performance periods may run up to five years. The umbrella notice covers multiple programs, so the relevant program guidance and approved budget control the actual award.

Where should questions go?

Start with the current Grants.gov package and the appropriate NIST program contact. For ITL questions, NIST lists Patricia Wilburg and provides contact details on its ITL MSE Grant Application Process page. Keep a written record of any clarification that changes the application’s interpretation.

Official links and next steps

The controlling application record is 2025-NIST-MSE-01 on Grants.gov. Read the synopsis, version history, current amendment, and full announcement before preparing the submission. The NIST overview and ITL guidance are available at NIST’s ITL MSE Grant Application Process page.

The best next step is an eligibility-and-fit review led by the proposed applicant organization. Confirm the entity type, registrations, NIST program match, technical question, collaborators, facilities, measures of success, budget logic, and deadline. If those pieces line up, draft the proposal around one measurable contribution to NIST’s measurement science, standards, testing, or technology mission. Submit the complete package through Grants.gov before September 15, 2026 at 11:59 p.m. Eastern Time, and retain proof of submission.