What FDA's April 2026 Draft Guidance Means for Off-Target Confirmation

On April 14, 2026, FDA issued draft guidance — "Safety Assessment of Genome Editing in Human Gene Therapy Products Using Next-Generation Sequencing" (docket FDA-2026-D-1255, CBER/Office of Therapeutic Products). It builds on the agency's January 2024 gene editing framework, and it's the first time confirmation gets treated as its own technical problem rather than a footnote to nomination.

That split matters. Off-target risk assessment has always had two jobs: nomination (finding where an editor might have cut — GUIDE-seq, CHANGE-seq, CIRCLE-seq, INDUCE-seq) and confirmation (checking, at each candidate site, whether an edit actually happened, and how often). The 2024 guidance called these "identification" and "verification". The 2026 draft renames them "Nomination" and "Confirmation", and gives confirmation its own dedicated section — with its own recommendations on methods, controls, depth, and reporting.

Why orthogonal confirmation, specifically

The guidance wants confirmation done by a method independent of the nomination assay — an orthogonal check, not a second pass with the same tool. It also asks for confirmatory testing at all nominated sites, and says plainly that "stringent filtering criteria should be avoided to enable evaluation of editing rate at the nominated off-target edit sites". A site that comes back "no signal" because the assay couldn't amplify it isn't a clean result. It's a gap that got filtered out by failure, not by design.

What multiplex PCR misses

This is where confirmation workflows can run into trouble. Multiplex PCR-based methods are well-established, but every additional primer pair in a multiplex reaction is a chance for cross-interaction — and cross-interaction shows up downstream as amplification bias and eventually target dropout. In our own benchmarking, PCR-based panels at the 100+ site scale have shown dropout rates up to 40%, depending on sequence context, panel design, and how much optimization time went into it.

That's not a rounding error. It's dozens of nominated sites sitting in a safety dossier as "no signal" — exactly the kind of data blind spot the guidance is now primed to ask about, since it explicitly names "minimize PCR amplification bias and/or primer bias" as an expectation.

How LockSeq fits

LockSeq confirms candidate sites with gap-fill padlock probes — one probe per target, reduced cross-interaction, so the failure mode behind PCR dropout is greatly reduced and remains only sequence context dependent. UMI (unique molecular identifier) tagging before amplification means consensus calling suppresses stochastic errors like DNA polymerase errors and the sequencing noise that otherwise masquerades as low-frequency variants, which is what gets sensitivity down to 0.1% VAF (variant allele frequency) with high-confidence edit detection.

Across the panels run to date, that's below 10% dropout — not zero, and still dependent on sequence context and panel difficulty, but well below what multiplex PCR shows at the same scale. And it sits inside the guidance's own "probe-based sequence enrichment" category, listed as one of the acceptable confirmatory approaches. The framing is method-neutral, not an endorsement — but it's a category the guidance recognizes by name.

Human genetic variation

The guidance also flags a source of off-target risk that a reference genome can't see: any individual's genome carries several million variants, and a single one can create or erase an off-target site relative to a given gRNA. FDA's response on the nomination side is to ask sponsors for an in silico analysis against population variation databases, stratified by genetic ancestry where prevalence data supports it. On the confirmation side, LockSeq's reporting handles the same problem a different way — every report classifies variants against each sample's own donor-matched, untreated control, not only against the reference genome. That separates "common" variants (present in both control and edited sample — germline or population background, not editing-related) from "edited-only" signal, so a donor's own genetic background doesn't get mistaken for an editing outcome, and a real edit at a variant-created site isn't masked because the reference genome never flagged it.

The timing is the part programs underestimate

The draft expects off-target and translocation studies completed before the original IND is filed, with full study reports submitted alongside it. That's not a "characterize it during Phase I" expectation — safety assessment is now front-loaded into early R&D. A confirmation method that needs multiple optimization cycles per panel, redone every time the panel changes, is the wrong tool for that timeline.

Comments on the draft closed July 14, 2026, so some of the detail is still open. The direction isn't: FDA wants confirmation that can show its work, site by site, at the data level — and wants that evidence in hand before the IND goes in, not scrambled together after a reviewer asks.

If you're scoping an off-target safety package and want to talk through where confirmation fits into your IND timeline, get in touch.

Sources

• FDA, "Safety Assessment of Genome Editing in Human Gene Therapy Products Using Next-Generation Sequencing," draft guidance for industry, CBER/Office of Therapeutic Products, April 2026 (docket FDA-2026-D-1255) — fda.gov
• FDA, "Human Gene Therapy Products Incorporating Human Genome Editing," guidance for industry, January 2024 — fda.gov
• Federal Register notice, April 15, 2026 (comment deadline July 14, 2026) — federalregister.gov