Gene Editing

GENE EDITING 101: SCIENCE, OVERSIGHT AND OPERATIONAL READINESS (PART 2/2)

ByThe Sabai Team

In Part 1 of this series, we covered the fundamental science behind gene-editing. In Part 2, we focus on execution: clarifying how IRBs and IBCs evaluate gene-editing studies, and providing actionable steps CROs and sites can take to align operations early, reduce rework and accelerate study start-up.

IRB/IBC Oversight and Operational Readiness

Gene-editing trials are not only scientifically and logistically complex; they also introduce compliance considerations that can shape start-up timelines and site workflows. Since gene editing can be durable (effectively irreversible in most cases), gene-editing trials require rigorous oversight to protect the research participants and the clinical personnel supporting these trials. In the U.S., two primary review bodies are commonly involved in the oversight of gene-editing clinical trials: the Institutional Review Board (IRB) and the Institutional Biosafety Committee (IBC). In Table 1 below, we summarize their distinct review priorities and highlight where study teams can often run into avoidable start-up delays with these oversight bodies.

Table 1. IRB vs IBC: review focus at a glance
IRB IBC
Primary objective Primary objective
Protect human participants by ensuring risks are reasonable, the consent process is clear, and privacy/confidentiality protections are appropriate. Protect staff, the community, and the environment by confirming appropriate biosafety risk controls and containment practices are employed.
What reviewers look for (plain language) What reviewers look for (plain language)
A clear, balanced description of participant risk and uncertainty, with a realistic follow-up plan and credible privacy safeguards.

A comprehensive risk assessment and site-specific biosafety plan that clearly identifies the potential risks from exposure to clinical trial materials and a mitigation plan to negate those risks.
Primary focus areas Primary focus areas
  1. Informed consent that accurately describes anticipated durability, limited reversibility, and uncertainty of therapeutic benefit
  2. Assessments of potential unintended (off-target) edits
  3. Potential for reproductive risks or germline transmission (particularly for in vivo editing)
  4. How genetic data and specimens will be collected, used, stored and protected
  5. Eligibility criteria and safeguards that match the study’s risk profile
  6. Appropriateness of the long-term follow-up plan to capture late adverse events
  7. Safety monitoring and reporting plan (AE/SAE definitions, stopping rules)
  1. End-to-end handling workflow for investigational products (IP) (i.e., receipt, storage, preparation, administration, transport, disposal)
  2. Containment level, staff training and safety SOPs and policies
  3. Personal protective equipment (PPE) requirements
  4. Spill response procedures
  5. Decontamination of patient care areas, work surfaces and equipment
  6. Waste-stream management
  7. Patient specimen handling requirements post-administration
  8. Emergency procedures and incident reporting (exposure response, medical surveillance, and notification timelines)
Examples of potential pitfalls with IRB reviews Examples of potential pitfalls with IBC reviews
  1. Consent language that overstates likely long-term benefit
  2. Consent language that understates the uncertainty of procedure-related risks or risks from (irreversible) editing
  3. Incomplete genetic data protection plan (storage, access, retention, secondary use)
  4. Long-term follow-up plans that are vague on visit cadence, responsibilities, or late adverse event capture (especially if participants relocate)
  5. Mismatch between protocol procedures and consent/participant-facing materials (e.g., sample collection, data use, optional sub-studies)
  6. Underdeveloped plan for returning results and incidental findings (what will be returned, to whom, and when)
  1. Submissions that omit requested site-specific information and workflows
  2. Unclear or inappropriate site-specific SOPs for safely handling IP
  3. Clinical environment that doesn’t align with fundamental biosafety principles
  4. Unclear or inappropriate waste-stream management (waste segregation, labeling, storage, and disposal/vendor pickup)
  5. Absence of equipment that required by Sponsor (e.g., biosafety cabinet for preparation)
  6. Site procedures that may deviate from Sponsor requirements (e.g., use of CSTDs)
  7. Inappropriate disinfection or decontamination methods
  8. Insufficient procedures relating to incident reporting (spills, exposures, and corrective actions)

With these oversight body review priorities in mind, it is critical to operationalize them early in start-up planning. IRB and IBC reviews should be treated as coordinated, parallel workstreams from the start rather than sequential hurdles. CROs and sites should engage their IRB and IBC early, ideally through pre-submission questions or brief consults, to confirm expectations and identify likely issues while the protocol and operational plans are still easy to adjust.

Early alignment helps prevent last-minute rework of consent language, biosafety procedures, or site workflows that can otherwise cascade into approval delays.

When these workstreams are aligned early, study teams are able to prevent avoidable activation delays driven by the “back-and-forth” between operational plans and committee feedback.

Operational Readiness (CROs + Sites)

Beyond committee approvals, gene-editing studies often succeed (or stall) based on whether sites and CRO teams effectively translate oversight requirements into executable day-to-day workflows: who handles what, when, and under which controls. Table 2 below outlines some practical operational readiness items that study teams can put in place early so study start-up and first-dose activities run smoothly.

Table 2. Start-up Accelerators: readiness steps that matter
Operational readiness item Action-oriented tip Why it matters Primary owner(s)
Start-up map to include IRB/IBC milestones Confirm IRB/IBC requirements early and plan for parallel review where feasible; unplanned committee steps become critical-path delays Makes dependencies visible, enables resourcing, and protects first-patient timelines CRO Start-Up Lead; Site Start-Up/CTM; IRB/IBC Coordinator
Plan around Committee cadence & rapid issue resolution If IRB/IBC meeting cadence is fixed; optimize your primary lever, which is ensuring high-quality submissions and fast response speeds to committee questions or concerns Errors in submissions or delays in responses can stall reviews drag out approval timelines CRO Regulatory Lead; IRB/IBC Coordinator; PI Delegate
Up-front reporting responsibilities Define “who reports what and when” before first dose, not during an event Reduces confusion and compliance risk; supports consistent, timely communication to the PI, IRB/IBC, and sponsor. Site PI; Site Safety Lead; Site Regulatory; CRO Safety
Cross-functional “trial run” Run a tabletop exercise with stakeholders early to validate handoffs and identify any workflow gaps. Identifying and fixing workflow issues early while the fixes are still simple can prevent a day-of-dose logistics scramble later. Avoids last-minute changes that may trigger a deviation or need for re-review. Site Operations; Pharmacy/IDS; Nursing; EHS/Biosafety; CRO Operations
Internal feasibility sign-off Document signoffs confirming that all stakeholders agree the site can execute the protocol as written before committing to timelines. Prevents late discovery of hard constraints (capabilities, space, equipment, staffing) that can drive activation delays and budget/schedule renegotiation. Site Department Leads; PI; CRO Feasibility Lead
Training plan & backup coverage Build backup coverage and document competency for every critical task. Staffing turnover, PTO, or shortages can easily stall submissions or start-up activities. Ensuring continuity coverage protects against delays and deviations and supports audit readiness by demonstrating role-based training and competency. Site Manager; Pharmacy/IDS Lead; Nursing Lead; CRO Training Support
Single “source of truth” packet Standardize the submission packet to the IRB/IBC review committees to prevent version mismatch/drift and delays. Cuts avoidable rework; supports parallel approvals by keeping IRB and IBC aligned on the same document set. CRO Document Control; Site Regulatory; Sponsor/CRO Medical Writing
Long-term follow-up (LTFP) Pre-build a participant retention plan in advance for multi-year follow-up (contact strategy, remote visit options, alternate contacts, relocation plan) and define re-consent triggers/workflows. Prevents missing safety data and reduces audit/regulatory finding risks in multi-year follow-up. Site CRC; PI; Sponsor/CRO Clinical Operations; Patient Engagement Team
Data/privacy governance for genetic data Align early on genomic data storage, access, transfer, retention, and secondary use (and how it’s communicated) Misalignment can trigger late contract/data security/legal friction and consent revisions. Site Privacy/Security; Site Legal; Sponsor/CRO Data Management; PI

Taken together, strong trial execution isn’t about piling on process, but about getting the right people in the room early and aligning on the handful of critical decisions that reduce start-up risks, review times and day-of-dose surprises. When IRB/IBC expectations, site workflows, and escalation pathways are clear up front, study teams can expect to spend less time doing late-stage rework and more time moving cleanly toward activating their first patient. And it lowers the odds of a dose-day scramble, where teams are forced to make critical on-the-spot decisions under time pressure. The payoff to thoughtfully evaluating every readiness step is a start-up that feels more predictable for everyone involved, and a study team that can stay focused on patient care, regulatory compliance and generating high-quality data.

How Sabai Can Help You

For sponsors, CROs, and study teams planning a gene-editing study, early alignment between IRB and IBC oversight is one of the most reliable ways to reduce avoidable start-up conflicts. Sabai supports trial readiness by helping teams anticipate committee questions, tighten submission packets, and translate biosafety and participant-protection expectations into site-ready workflows. Support can include IRB/IBC strategy and submission support, and protocol and informed-consent language review. If you’d like to discuss your study’s oversight pathway or readiness plan, contact us below.

Principled. Passionate. People-first.
Contact Us Today