Every document cross-references every other.
Nothing is governed.
Most organizations manage documents. Few manage relationships. LDLC provides a governance framework for understanding, managing, and maintaining those relationships across the full product lifecycle.
Medical device organizations build documentation systems with an unwritten rule: every document must reference every related document. The intent is traceability. The result is a tangled web.
"Oh what a tangled web we weave when we include every cross-reference in our documents."
BOM references Drawing. Drawing references Part Spec. Part Spec references Test Method, Material Spec, and Tool DWG. SOP references DMR, Work Instruction, Work Order, Router, and Equipment Setup. Every change propagates unpredictably through the web.
The cross-reference structure creates the illusion of coherence while destroying the possibility of it. The problem is not documents. The problem is unmanaged relationships.
Read: When Documents LieIn an ungoverned system, change impact is unknown until something breaks. In a governed system, every relationship is traceable — which means every impact is visible before it propagates.
A URS is revised to tighten biocompatibility requirements following a post-market signal. Click to propagate through the governed document architecture.
Trigger the change to see propagation
LDLC numbering: 1xxxxxx Documents · 4xxxxxx Information Units · 6xxxxxx Work Units · Relationships reflect ISO 13485 / 21 CFR Part 820 design control architecture.
A governance-oriented architecture — focused on relationships between artifacts, not merely the artifacts themselves.
Every document says only what is true, only what is necessary, and only what is actively maintained. No redundancy, no decorative compliance, no documents that lie through obsolescence or drift.
Configuration management applied beyond software: every relationship between requirements, specifications, physical artifacts, and quality records is known, controlled, and traceable.
The distinction between a cross-reference and a governed relationship is everything. Cross-references create webs. Governance creates architecture.
The framework asks one question: Do the documents, records, and systems describe the same reality? Inspection readiness is the ability to demonstrate that — on demand.
LDLC names and structures the relationships between the artifacts that define, build, and demonstrate a medical device.
Design History File. The governed record of the design process. Not a folder — an architecture. Example: 100624.
Device Master Record. The complete specification for how a finished device is produced. Example: 100518.
User Requirement Specification. The governed statement of user and regulatory needs. Example: 401042.
Technical Design Requirement. The governed translation of user needs into verifiable technical specifications. Example: 401087.
Risk Management File. ISO 14971. The governed record of hazards, causes, controls, and residual risk. Example: 100312.
Engineering Change Notice. The governed information object that initiates and documents a change event. Example: 401247.
The work unit that governs creating or processing an ECN. Distinct from the ECN information object. Example: 600247.
EU MDR Technical Documentation. The structured evidence package required for CE marking. Example: 100781.
Navigate concepts, relationships, and dependencies — not just definitions. Definitions are Wikipedia. Relationships are LDLC.
The LDLC Map makes relationships navigable. Start from URS 401042 and trace its governance implications through TDR 401087, Risk Controls, Verification Records, and into DMR 100518.
Open Interactive MapDocuments can be complete, approved, and fully compliant — and still fail to tell the truth. They lie through omission, through drift, through the gap between what was decided and what was recorded. The tangled web of cross-references is not a documentation problem. It is a governance problem.
"A document can be complete, current, approved — and still lie."WHEN DOCUMENTS LIE — Introduction
Document coherence · Relationship traceability · Inspection readiness · Governance architecture · Configuration discipline
José Ignacio Mora is a manufacturing engineering and quality systems consultant with more than three decades of experience in medical device and life sciences organizations.
His work focuses on helping organizations understand, create, and maintain coherent systems — where documents, records, configurations, and quality systems describe the same reality, consistently and demonstrably.
About LDLCBegin with a conversation about the relationships, records, and decisions creating complexity in your organization.