NIH S10 Shared Instrumentation Grant: How to Build a Winning Equipment Application

What the S10 Actually Funds (and What It Doesn't)

The S10 Shared Instrumentation Grant covers the purchase of a single piece of biomedical research equipment. There are two main variants under the S10 umbrella. The Shared Instrumentation Grant (SIG) targets instruments in roughly the $100,000 to $600,000 range. The High-End Instrumentation Grant (HEI) targets instruments above that threshold, with awards reaching up to around $2 million. Both awards are one-time and non-renewable for the same instrument — once you win an S10, you cannot re-apply for the same piece of equipment when it ages out.

What the S10 does not cover is equally important to understand. It funds the acquisition price of the instrument, not installation costs beyond what's included in the vendor quote, not personnel to operate it, and not ongoing service contracts. Your institution is expected to absorb those costs, and reviewers look for evidence that it plans to. A budget that folds in personnel or maintenance often raises flags in review. Keep the budget clean and tied directly to the purchase price.

The mechanism is explicitly for shared use across multiple investigators. If the proposed instrument will primarily serve one lab, reviewers will notice. The program was designed to support core-facility-level resources that genuinely expand capability across an institution, not to acquire equipment that one PI controls and others use occasionally. That distinction is the conceptual foundation of the entire application.

The Major User Requirement: Where Most Applications Fall Short

NIH requires that S10 applications include at least three major users, each with active NIH research support. "Active NIH support" typically means a current R-mechanism, U-mechanism, or similar active award — not a pending application, and not a subcontract where someone else holds the prime. Each major user needs to show a credible, specific scientific need for the instrument, and together the user group should represent enough demand to justify meaningful instrument time.

The distinction between a genuine major user and a nominal one is something reviewers are trained to assess. A genuine major user can name two or three specific experiments within their currently funded aims that require this instrument, explain why existing institutional access is inadequate, and quantify roughly how many hours per year they expect to use it. A nominal major user says they "plan to use the instrument for future work" and attaches a letter that reads like a courtesy signature. Reviewers count how many users fall into each category. An application built around nominal users scores poorly regardless of how strong the lead applicant's own scientific case is.

The lead user plays a distinct role from the major users. This is the PI who submits the application, coordinates the others, and takes institutional responsibility for the instrument after the award. The lead PI's own scientific case for the instrument anchors the justification section. Their NIH funding record and publication history matter more here than in a typical R-mechanism application, because reviewers are also assessing whether this person can manage a shared resource and maintain it as a productive institutional asset.

Writing the Scientific Justification: Science First, Equipment Second

The most common failure in S10 applications is treating the scientific justification as a product description. Reviewers want to understand why the absence of this instrument is blocking or limiting specific NIH-funded science, what experiments each major user cannot do without it, and why the proposed instrument is the right solution rather than an alternative the institution might already have access to.

A well-structured justification opens with the scientific problem the instrument addresses, not the instrument itself. If you're proposing a cryo-electron microscope, the first paragraph should explain what biological questions across your institution require near-atomic-resolution structural analysis, and which of those questions cannot be adequately addressed with available alternatives such as X-ray crystallography or lower-resolution electron microscopy. Then you connect the instrument's specific capabilities to those questions. Each major user gets their own subsection, tied to their active NIH-funded aims by name and grant number.

Reviewers also want some evidence that the proposed experiments are feasible with this instrument. If your institution has had temporary access to a similar instrument at a core facility elsewhere, preliminary data from those experiments is valuable. If you haven't had any hands-on access, a vendor quote along with a letter from a collaborating institution that hosts a comparable instrument can help bridge the credibility gap. You don't need a complete set of preliminary data, but you do need to show that the scientific plan isn't purely theoretical. The "criticality argument" — a clear statement of why this instrument is necessary rather than merely convenient — should appear explicitly, not be left implicit.

Building a Credible User Group

Organizing the user group is the work that happens before you write a single word of the application. You need investigators who have active NIH funding, a genuine experimental need for the instrument, and enough institutional tenure that they're unlikely to leave before the instrument pays off. A group of three strong users is more convincing than a group of six weak ones, and reviewers will read past the count to assess depth.

Letters from major users are not boilerplate. Each letter should reference specific aims from the user's active grants, name the specific experiments that require the proposed instrument, and quantify projected instrument time. A letter that says "I support this application and look forward to using the facility" tells reviewers the user wasn't seriously engaged in the planning process. Give each user a structured prompt that asks for their grant number, the relevant aim, the specific measurement the instrument enables, and a realistic hours-per-year estimate — then follow up to ensure the letters actually include this content before you finalize the application package.

Career stage mix matters. One or two senior investigators with strong publication records in the instrument's application area anchor the user group's credibility. Early-stage investigators can be strong major users if their science is genuinely instrument-dependent, and including them signals that the equipment will support the institution's next generation — reviewers view that positively. Avoid stacking the user group with investigators from a single department. Cross-departmental use suggests the instrument serves a real institutional need rather than a cluster's convenience.

Institutional Support: Why the Administrative Letter Matters

The institutional support letter from your grants office or administration is not a formality. Reviewers use it to assess whether the instrument will still be operational in five years. An institution that provides no specifics — just a statement that it "supports this application" — is implicitly telling reviewers they haven't thought about maintenance, staffing, or how the instrument transitions to a sustainable user-fee model once the award money is spent.

A strong institutional support letter addresses four concrete things: dedicated space for the instrument, a plan for ongoing maintenance including service contracts and equipment reserves, how the instrument will be staffed, and how the institution plans to sustain usage fees after acquisition. "We will charge users a market-rate service fee and cover shortfalls from the departmental facilities budget" is substantially stronger than "we plan to recover costs." If your institution is genuinely committing to a full-time instrumentation specialist, name the position and the department responsible for the salary. Reviewers who see a funded technical staff line in the institutional commitment understand that the instrument is being taken seriously at the administrative level, not just by the applicant PIs.

The Review Process and Timing Strategy

S10 applications are reviewed by Special Emphasis Panels assembled specifically for instrumentation grants, not by standing study sections. This matters for how you write. The reviewers are typically a mix of instrumentation specialists, engineers, and investigators with core facility management experience. Writing for a panel that also includes instrument engineers is different from writing for a basic science study section — your instrument specifications need to be precise and your scientific case needs to be accessible to someone who may not work in your exact subfield.

The review timeline for S10 applications typically runs with a due date in February or March for the SIG cycle, followed by a spring study section and awards later in the fiscal year. Because the lead PI and all major users need to coordinate letters, any preliminary usage data, and institutional commitments, you should start organizing the group at least 10 to 12 months before your target due date. The institutional commitment section in particular requires conversations between your grants office, facilities management, and sometimes your department chair. Those conversations don't happen quickly, and trying to compress them into four to six weeks before submission usually produces a thin or inconsistent institutional support letter.

One strategic reality: research offices at many institutions coordinate S10 submissions internally and may limit how many applications go forward in a given cycle. Talk to your sponsored programs office early. If another group is organizing a competing S10 application for a different instrument, the timing and priority of submissions becomes a negotiation worth having months before the deadline.

Common Mistakes That Sink S10 Applications

Treating the application as a purchase request

If your scientific justification reads like a product brochure, reviewers will score it like one. Start with the biological questions the instrument enables, not with the instrument's features. The instrument is the means; the blocked science is the argument.

User letters that don't reference specific aims

A letter that mentions "ongoing NIH-funded research" without naming specific experiments is a yellow flag. Reviewers expect each major user letter to cite a grant number, name a relevant aim, and describe the specific measurement the instrument enables that the user cannot do today.

Proposing an instrument your institution already has nearby

If a similar instrument exists at a nearby institution or within a shared core at your own university, reviewers will expect you to explain why that access is inadequate — capacity limits, scheduling conflicts, travel barriers, proprietary protocols. "It would be more convenient" is not a sufficient reason to justify an award.

A vague or absent maintenance plan

Reviewers think about whether this instrument will still be running when the user group's current grants end. An application that doesn't address service contracts, technical staffing, and replacement-parts reserves is implicitly asking NIH to fund an instrument that may sit idle within three years.

Lowballing the equipment cost to appear conservative

Get an accurate vendor quote that includes installation and any required infrastructure upgrades, then budget for the actual number. A cost that looks artificially low raises questions about whether you have done your vendor due diligence. Reviewers know what instruments cost, and a budget that requires a later supplement is not a selling point.

Frequently Asked Questions

Can I apply for an S10 as a new investigator?

Yes, but it's harder without a track record. A new PI leading an S10 application needs either an exceptionally strong set of co-users or a clearly documented institutional need that a senior PI hasn't yet organized around. More commonly, new investigators serve as major users rather than as the lead PI — they demonstrate genuine need through their active NIH funding and build their profile for a future lead role once they have more institutional standing.

Can the S10 fund computing infrastructure or software?

Generally no. The S10 program is designed for physical research instruments that generate data. Computing clusters, software licenses, and data storage are typically outside the scope and are better addressed through institutional investment or other mechanisms. Some highly specialized scientific computing hardware exists in a gray area, but those cases are uncommon and require a compelling argument that the hardware qualifies as research instrumentation rather than IT infrastructure.

What if one of our major users loses their NIH funding between submission and review?

Notify your program officer immediately. If the departure leaves you with fewer than three well-supported major users, reviewers will flag it. You may need to identify a replacement user or strengthen the remaining users' cases substantially. This situation is more common than applicants expect, which is one reason to start with four or five serious candidate users when organizing — it gives you a buffer if someone's funding status changes before the study section.

Should I call a program officer before submitting an S10?

Yes, strongly. NIH program officers who manage the S10 program can tell you whether your proposed instrument is a competitive fit for the current cycle, whether they're aware of other applications targeting similar instruments, and whether your user group looks credible at a high level. That call costs you 20 minutes and can save you months of wasted effort on an application that was unlikely to succeed. The relevant program contact is listed on the SIG and HEI parent announcements on Grants.gov.