A readiness assessment for NGS is easy to fake and hard to pass honestly. It is easy to fake because every one of the six questions below can be answered "yes, roughly" without much scrutiny, and a purchase decision built on six rough yeses looks exactly like one built on six verified ones, right up until the program is running and the gaps start to show. It is hard to pass honestly because the dimension that most determines whether a program survives its first year, informatics capacity, is also the one bench scientists are least equipped to evaluate on their own.
This assessment scores six dimensions on a simple 0-to-3 scale, for 18 points total, and gives you a threshold to act on rather than a vague sense of confidence. It assumes you have already read through the buy-versus-outsource and demand-sizing framework in the Section 1 overview on building an NGS program, and the cost figures in how much NGS actually costs. This piece is the gate you walk through before either of those documents becomes a purchase order.
Key Takeaways
|
Demand: Do You Have Enough Samples?
Score this using committed demand only: funded, named projects, not pipeline grants or expressions of interest. If you cannot name the groups and sample count for the next twelve months without checking with anyone, that gap is itself the answer.
- 0 points: No committed demand exists yet; interest is entirely informal.
- 1 point: Committed demand exists but is well below the volume needed to justify in-house ownership over outsourcing at your likely scale.
- 2 points: Committed demand approaches the break-even volume for ownership, calculated against a real outsourced-rate quote.
- 3 points: Committed demand clears the break-even volume with a documented safety margin, and a credible plan exists for what happens if it drops.
Physical Requirements
Sequencers are less physically demanding than many lab instruments, but the requirements are unforgiving when missed. Confirm: conditioned power with an uninterruptible supply sized to protect a run through a brief outage; stable temperature and humidity within the manufacturer’s range, since drift mid-run can compromise data rather than failing cleanly; bench space with maintenance clearance, not just footprint; and physical separation between pre- and post-amplification areas, far cheaper to design in than retrofit later.
- 0 points: No site assessment has been done.
- 1 point: A site walk-through has identified likely gaps, but none have been resolved or costed.
- 2 points: Power, HVAC, and space have been confirmed adequate or a costed plan exists to make them so.
- 3 points: Site requirements are fully confirmed in writing, including workflow separation, and facilities has signed off.
Informatics and Network Capacity
This is the dimension most readiness assessments underweight, and most labs fail here rather than on the bench. A sequencer produces data continuously during a run, and that data has to move somewhere, get processed, and land somewhere retrievable for years. A widely cited set of e-infrastructure recommendations for NGS facilities found that network demand per connected instrument is often modest on average but arrives in bursts tied to run completion, so the design question is peak capacity and buffering, not average throughput. The same recommendations note that storage and compute needs scale with active project count, not just sample count, and that most informatics failures happen when an informal pilot-project arrangement is asked to hold up under routine production volume.
- 0 points: No plan exists for where run data will land, how it will be processed, or who owns that pipeline.
- 1 point: A plan exists informally, resting on one person’s laptop or an ad hoc arrangement with a colleague in another department.
- 2 points: A documented pipeline exists, with defined storage, compute, and network capacity sized to your expected volume, but it has not been tested against a real production-scale run.
- 3 points: The pipeline has been tested end to end against a run at or near production volume, with a named owner and a documented retention policy.
Score this one conservatively. It is the dimension non-specialists most reliably overrate, because a small pilot run can succeed on infrastructure that will not hold up once volume becomes routine, and the failure only shows up months later, well after the purchase decision is final.
Skills Already on Staff
Distinguish skills you have from skills you can hire quickly. Wet-lab library prep transfers well from adjacent molecular biology experience and is the fastest gap to close. Bioinformatics analysis, turning a completed run into an interpretable result, is the slowest gap to close and the one most often assumed to exist because someone on staff "knows some Python."
- 0 points: No staff member has hands-on NGS wet-lab or analysis experience.
- 1 point: At least one staff member has adjacent molecular biology skill but no direct NGS experience.
- 2 points: At least one staff member has direct NGS wet-lab or analysis experience, but not both, and not with capacity to own the function full time.
- 3 points: Both wet-lab and analysis functions have a named, capable owner with dedicated time, not a shared responsibility layered onto an existing full workload.
Quality System Maturity
You do not need a mature clinical quality system to run a good research NGS program, but you need documented procedures, defined run-acceptance criteria, and a habit of recording every run outcome, including failures. Labs that skip this and later need clinical or regulated work face a far harder retrofit than labs that built the discipline in from day one.
- 0 points: No standard procedures exist; run outcomes are not systematically recorded.
- 1 point: Informal procedures exist but are not written down or consistently followed.
- 2 points: Written procedures and defined run-acceptance criteria exist and are generally followed.
- 3 points: Written procedures, defined acceptance criteria, and a complete run-outcome record are all in place and reviewed periodically.
Scoring Your Readiness
Score each of the five preceding dimensions from 0 to 3, then add one further dimension not covered above: organizational commitment, meaning whether leadership has agreed in principle to fund a multi-year program rather than a single instrument purchase. Score that the same way, 0 for no discussion yet, 3 for a documented, leadership-approved multi-year commitment. That gives six dimensions and a maximum of 18 points.
Total Score | Reading | Recommended Action |
0-8 | Not ready | Wait. Address the lowest-scoring dimensions before spending further time on platform selection or budgeting. |
9-13 | Partially ready | Pilot. Prove the gaps out at small scale, especially informatics, before committing capital. |
14-18 | Ready | Proceed to the business case using the framework in the Section 1 overview. |
Table 1. Readiness scoring matrix. Six dimensions, 0-3 points each, 18 points total. This is an original editorial framework built for this assessment, not a published industry standard; use it as a structured starting point and adjust weighting to your own institution’s priorities.
Read the Pattern, Not Just the TotalTwo labs can both score 12 out of 18 and be in completely different situations. A lab scoring low on demand and physical space but high everywhere else has a business-case problem, solvable with a stronger commitment and a clearer sample pipeline. A lab scoring high on demand and bench skill but low on informatics has an infrastructure problem that will not resolve itself once the instrument arrives; it will simply become visible, expensively, a few months into production. Look at which dimensions are dragging the score down, not only the total, before deciding what pilot or fix comes first. |
Whatever the score, the decision it feeds is the same one covered in the main guide to next-generation sequencing in the lab: whether to build in-house at all, and if so, at what scale. A readiness score of 14 or above with a favorable outsourcing comparison is still a legitimate reason to outsource. Readiness is a precondition for owning well, not an argument for owning at all. The specific comparison between core facility use, service providers, and in-house ownership is developed further in In-House vs. Outsourced Sequencing: Core Facility or Service Provider?, and the data infrastructure side of the informatics score, storage sizing, compute provisioning, and retention policy, is covered in full in Managing NGS Data: Storage, Compute, Retention, and Staffing.
This article was produced under Lab Manager's AI Editorial Guidelines.













