Electronic witnessing has been the gold standard for preventing mix-ups in the IVF lab for years, and for good reason: incorrect embryo, sperm, or oocyte transfers are rare (an estimated 0.001–0.002% of cases) but serious when they happen (Sterckx et al., 2023). What's new in 2026 is where the responsibility for preventing them sits: with the update to the ESHRE Recommendations on Good Practice in the IVF Laboratory, witnessing stops being a purely technical matter the embryology team handles on its own; it's now a clinic-wide governance topic, with concrete requirements for audits, skill retention, data entry practices, and failure resilience. A clinic that "installs a system and forgets about it" no longer meets the updated recommendations, regardless of how the lab itself is running day to day.
Here's an overview of the six most important changes and what they mean for how a fertility clinic operates, not just for the lab bench.
1. Governance, Not Just Technology
Until now, many labs focused on whether an electronic witnessing system (EWS) was in place. ESHRE 2026 now specifies how that system must be governed: formal, scheduled audits - recommended on a quarterly basis - that systematically evaluate:
- what types of mismatches and near-misses occur,
- how high the false-positive alert rate is,
- where in the workflow the system causes interruptions,
- and how consistently staff actually respond when the system flags something.
ESHRE also expects ongoing technical governance of the EWS itself: data security standards against unauthorized access or manipulation, test alerts run during implementation to confirm notifications actually work, and periodic review for design flaws, unclear alerts, or a creeping "normalization of deviation" where warnings quietly start getting ignored. An EWS is therefore no longer a piece of technology validated once and left alone, it's a process that must be continuously monitored and adjusted, much like other critical QM processes in the lab.
2. Skill Retention Despite Automation
One notable point: ESHRE explicitly states that staff must continue to be trained in critical thinking and manual verification even while an EWS is in routine use. The reasoning is straightforward: the more reliably a system performs day to day, the greater the risk of "automation complacency," where staff come to trust green checkmarks blindly instead of catching anomalies themselves. ESHRE is explicit that this needs regular reiteration within the team: an EWS complements human vigilance, it doesn't replace it.
For lab directors, this means training plans must include verification scenarios without a functioning EWS, even when the system is running reliably in daily operations.
3. Mandatory Backup for Technical Failure
Also new: a clear requirement for validated manual fallback protocols. If the electronic system fails -and this is now treated as a scenario to plan for, not a hypothetical - a tested manual procedure must be able to take over seamlessly. Improvising a backup on the spot no longer satisfies the guideline; the procedure must be documented and validated in advance.
4. Double-Witnessing More Precisely Defined
ESHRE has also tightened the requirements for classic manual witnessing: two qualified staff members must verify independently; passive confirmation ("yes, that's correct") is no longer sufficient. The recommended approach is the read-back technique: one person reads the identification data aloud, and the second confirms it actively against their own, independent check. This reduces the well-known confirmation bias, where an already-expected answer gets confirmed without genuine scrutiny.
5. Clearly Defined Escalation Pathways
For any discrepancy - whether caught electronically or manually - the updated recommendations require a predefined escalation pathway: immediate halt of the procedure, documentation, and supervisory review. Improvised, case-by-case decisions made in the moment of uncertainty are meant to become a thing of the past. ESHRE goes a step further and asks that mismatches and near misses undergo structured root cause analysis focused on system-level vulnerabilities rather than individual blame - with findings feeding into the lab's CAPA (corrective and preventive action) process, not just filed away once the immediate incident is resolved.
6. Accurate Data In, Fewer Mismatches Downstream
It's easy to focus entirely on the witnessing check itself and overlook what feeds it. ESHRE explicitly calls out the importance of proper data entry and accurate sample labelling as part of good EWS practice: a mismatch traced back far enough often starts with a transcription error, not a failure of the witnessing step itself.
One Way to Close That Gap
Patient and clinic management software for fertility clinics often connect with witnessing systems so no double entry is needed. MedITEX IVF interfaces directly with the three market-leading electronic witnessing systems RI Witness, eWitness, and IMT Matcher. Through these interfaces, the patient's (or couple's) master data, and, depending on the connected system, treatment data such as the planned procedure and treatment start date, are sent automatically into whichever of the three a clinic uses, rather than being typed in a second time by hand. MedITEX delivers the data, and the witnessing of the data (the checks, confirmations, and records) happens inside the connected system. In practice, that means the reliable patient and treatment data a clinic already keeps in MedITEX carries straight through into the witnessing system it trusts - exactly the kind of "proper data entry" ESHRE is pointing at.
What This Means for Your Clinic
In short, here's what's worth checking against your current setup:
- Is there a documented audit schedule for your EWS (mismatch/near-miss typology, false-positive rate, workflow interruptions, staff response consistency)?
- Do your training plans include manual verification exercises - independent of EWS status?
- Is there a validated, documented manual backup procedure for system failure?
- Has your manual witnessing been shifted to active, independent verification (e.g., read-back) rather than passive confirmation?
- Is there a written escalation pathway for discrepancies that feeds into root cause analysis and CAPA?
- Is patient and treatment data reaching your EWS automatically and correctly, rather than through manual re-entry?
Bottom Line
The 2026 ESHRE update makes clear that witnessing is no longer a technology purchase a lab can consider "done"; it's an ongoing governance responsibility that sits with the clinic as a whole, not just with whoever runs the EWS day to day. Much of that responsibility plays out inside the EWS itself - audits, backup protocols, escalation, CAPA. But it starts further upstream, with the data that reaches the EWS in the first place. Clinics that connect their patient management system to a leading EWS - RI Witness, eWitness, or IMT Matcher - the way MedITEX does, and let patient and treatment data flow through automatically instead of being re-typed by hand, remove a real source of error before witnessing ever begins.
