The compliance training gap
Regulated industries run on documented proof. A training record is not a courtesy — it is a regulatory requirement with audit consequences if it is incomplete or inaccurate. The problem is what most training records actually prove.
A classroom sign-in sheet proves a person was in the room. It does not prove they understood the procedure. It does not prove they made the correct decision when presented with a simulated scenario. It does not prove they can perform the task correctly under pressure. An inspector who asks "how do you know the training worked?" gets an answer that amounts to: attendance was recorded.
That gap costs regulated manufacturers during audits, during incident investigations, and during corrective action reviews. The documentation does not match the actual risk because the training was never designed to capture performance — only presence.
XR training is designed differently. Every session generates a performance record automatically. No additional documentation effort. No manual data entry. The record exists because the system ran.
What XR training captures
An XR training session records more than completion. It captures the session timestamp, the module version that ran, the scenario path the learner took, the decisions made at each branch point, time-to-completion by section, and error count by step.
That data is generated at the system level. The learner does not fill out a form. The facilitator does not create a record. The data is produced as a byproduct of the training itself.
For regulated environments, this matters for two reasons. First, the record is accurate. It reflects what actually happened in the session — not what an instructor remembered or recorded after the fact. Second, the record is specific. An auditor asking about a technician's qualification for a particular procedure gets a timestamped record of which scenario version they completed, how many attempts it took, what errors they made, and what score they achieved.
NDA designs XR training systems for regulated manufacturing environments.
Regulated industry use cases
Three sectors in the Borderplex carry the highest XR compliance training demand.
Medical device manufacturing in Juárez is significant. Foxconn Health Solutions, Flex Medical, and others operate under FDA 21 CFR Part 820 — Quality System Regulation for medical devices. Part 820 requires documented, repeatable training for personnel performing critical operations. XR session logs satisfy this requirement. They are audit-ready without additional assembly.
FDA 21 CFR Part 211 governs pharmaceutical manufacturing. Personnel qualification requirements under Part 211 require that training is documented, that it covers the specific procedure the person performs, and that retraining is triggered and documented when procedures change. XR platforms with version-controlled content and automated retraining triggers are built for this requirement.
Aerospace manufacturing under FAA oversight operates in Juárez through facilities including Honeywell and PESI. AS9100 quality management standards require training records that demonstrate competency, not just completion. XR scenario scoring and branching decision logs provide that evidence directly.
COFEPRIS — Mexico's equivalent of the FDA — governs pharmaceutical and medical device production under NOM-241. Good manufacturing practice requirements under NOM-241 include training documentation standards that align closely with FDA expectations. XR training records satisfy both in facilities operating under dual regulatory oversight.
Scenario design for compliance
Compliance XR training is not generic content adapted for a regulated context. It is built from the regulatory requirement outward.
The scenario must reflect the actual procedure performed by the actual role. A simulation of a general pharmaceutical cleanroom environment does not satisfy a training requirement for a specific gowning procedure at a specific facility. The content must be specific, current, and version-controlled.
Every scenario must document: the correct procedure path, branch points where incorrect decisions are possible, acceptable deviations versus critical failures, and the competency threshold required for a passing record. These decisions are made during content design. They cannot be retrofitted after the module is built.
Branch-point logic is where compliance training differs from general simulation. In a regulated scenario, a wrong decision at a critical step — administering a component in the wrong sequence, skipping a documentation step, bypassing a verification — is not just scored. It is flagged as a critical error in the session record. That record is distinguishable from a passing record that included non-critical errors.
Competency thresholds must align with the facility's quality management documentation. If the SOP defines a critical step, the training scenario must define a corresponding critical error. The two documents need to match before the module is deployed.
AI-generated reporting and LMS integration
XR platforms with AI-assisted reporting generate compliance summaries without manual aggregation. A quality manager requesting training status for a team before an audit gets a report that reflects the actual session data — by person, by procedure, by date, by version, by score. The report is generated from the platform. It does not require someone to compile it from individual records.
LMS integration exports session data in SCORM or xAPI format to existing learning management systems. The XR training record becomes part of the learner's LMS profile alongside other training completions. For regulatory purposes, the LMS record and the XR platform record are both available. Redundancy in compliance documentation is a feature.
Retraining triggers can be configured at the platform level. When a procedure version changes, the system identifies which learners completed the previous version and flags them for retraining. The trigger is automatic. The retraining record is generated when the learner completes the updated module. Nothing falls through a manual process gap.
Validation and qualification of XR training
Regulated environments require that training systems themselves be validated before use. A VR training module used to qualify personnel for a regulated procedure must be validated as fit for purpose — that it accurately represents the procedure, that its scoring logic is correct, and that its records are reliable.
IQ/OQ/PQ validation protocols — Installation Qualification, Operational Qualification, Performance Qualification — apply to XR training systems in pharmaceutical and medical device environments. This is not optional. Using an unvalidated system to generate qualification records creates a compliance liability, not a solution.
Plan the validation protocol before content development begins. The validation scope affects content design decisions. Changes to a validated module require documented change control and revalidation. Build this into the content maintenance process from the start.