How to manage compliant product documentation across the product lifecycle
|
An auditor asks a simple question: which revision of the assembly drawing was released for the batch you shipped in March, and who signed it off? The drawing is in your CAD vault, the change order is in PLM, the approval sits in someone's inbox, and the operating manual that went out with the machine lives on a shared drive.
Answering takes three people and most of the week.
That hunt for information adds up long before any auditor arrives. According to a work-sampling study of 78 design engineers published in the Journal of the American Society for Information Science and Technology (2010), information behaviors such as searching documents and asking colleagues took up 55.75% of their working time.
Every hour spent hunting for the right version of a spec is an hour your engineering team does not spend on the product.
This guide shows you how to manage product documentation so it stays complete, current, and provable across the whole product lifecycle. You'll see which documents belong in it, what US and export regulations now expect, and a six-step method your engineering and technical documentation teams can put into practice.
Key takeaways
- Product documentation covers every record a product generates, from the first requirements document to the disposal instructions
- The FDA's Quality Management System Regulation took effect on February 2, 2026, and US manufacturers exporting machinery to the EU face new documentation rules from January 20, 2027
- Complete product documentation depends on three controls: versioning, approval workflows, and audit trails
- Retention periods vary by product, market, and regulation, so set retention rules per document class
- A document management system works alongside your PLM, CAD, and ERP systems as the controlled record of what was released, when, and by whom
What is product documentation?
Product documentation is the complete set of records created over a product's lifecycle, from development and production through use, maintenance, and disposal. It includes design files, technical specifications, test reports, certificates, and user manuals. It proves to regulators, auditors, and customers that the product was designed, built, and supported as required.
Types of product documentation, from design to disposal
Most manufacturers produce five families of documentation over a product's life. Each has a different owner, a different audience, and a different reason to be kept.
Development and design documentation
This is where the product begins, with requirements, CAD drawings, test reports, and engineering change orders (ECOs). Its main audience is internal. When a field failure happens years later, this is the record that explains why the part was designed the way it was.
Technical documentation
Technical documentation captures what anyone needs to install, operate, and assess the risks of a technical product. Internal technical files hold the risk assessment and the evidence of conformity. External technical documentation reaches the customer as assembly instructions, operating manuals, and safety information.
Process and production documentation
Bills of materials, work instructions, and inspection plans describe how the product is built. Strong process documentation also records every change to that process, which matters as soon as a quality issue has to be traced back to a specific production run.
Regulatory and quality documentation
Declarations of conformity, certificates, and quality control records prove that you met your legal and customer obligations. For many manufacturers this family is governed by a quality management system built on ISO 9001 or an industry-specific standard.
User and service documentation
Manuals, maintenance schedules, and disposal instructions support the product once it leaves your site. These documents change the most after launch, and they are the ones your customers actually read.
What compliant product documentation requires in 2026
Two major rule changes land within a year of each other: one already in force for US medical device makers, one coming for anyone exporting machinery to Europe. Both raise the bar for how long and how well you control your records.
US product liability and recall exposure
In the US, product liability is shaped largely by state law, and the window in which a claim can be brought varies from state to state. Your documentation is your defense.
When a claim or recall arrives, you need to show which design and which instructions applied to the affected units, and that each change was reviewed and approved. Complete records also let you trace a defect to specific components and batches, so a recall stays as narrow as the problem.
FDA QMSR for medical device manufacturers
The FDA's Quality Management System Regulation took effect on February 2, 2026, and amends 21 CFR Part 820 by incorporating ISO 13485:2016 by reference.
The familiar Design History File and Device Master Record terms give way to ISO 13485 concepts such as the design and development file and the medical device file. The requirement underneath stays the same: controlled, traceable records that are updated whenever the design changes, for the life of the device.
ISO 9001, ANSI Z535.6, and IEC/IEEE 82079-1
Across industries, ISO 9001 document control requires documented information to be reviewed, approved, versioned, and protected. ANSI Z535.6 sets the format for safety messages in manuals and instructions, which matters for any product sold in the US.
IEC/IEEE 82079-1 is the international standard for preparing instructions for use, and Europe adopts it as EN IEC/IEEE 82079-1.
The EU Machinery Regulation, if you export
If you ship machinery to Europe, Regulation (EU) 2023/1230 replaces the Machinery Directive and applies from January 20, 2027. It allows instructions to be supplied digitally for the first time, provided they stay accessible and downloadable, and a paper copy is available on request.
Digital instructions must remain available for the expected lifetime of the machine and for at least ten years after it is placed on the market. That turns your manual into a controlled record you maintain for over a decade.
Our guide to compliance in manufacturing covers the wider US obligations, including ITAR and EAR for export documentation.
Automate Work. Accelerate Business.
Bring together AI, ECM, and workflow automation in one powerful enterprise platform.
How to manage compliant document documentation
Hey Doxi, how do you manage compliant document documentation
The method below works whether you run one plant or forty. It assumes your engineers keep working in the systems they know, and it adds the control layer that most documentation setups are missing.
1. Map every document to a lifecycle phase and an owner
Start with an inventory. List the documents each lifecycle phase produces, who creates them, who approves them, and who needs to retrieve them later. Most teams discover that nobody owns the handover points, such as the moment a released drawing becomes an input to a work instruction.
Group the documents into product-centric digital files, one per product, product family, or machine. When an auditor asks about a serial number, you open one file.
2. Decide which system is the master for what
Your PLM system is the right place to manage the engineering bill of materials and design changes while a product is in development. Your CAD system owns the models. Your ERP owns the production and order data. Problems start when released documents stay scattered across all of them, with no single place that records what was actually shipped.
Make a clear decision: authoring happens in the engineering systems, and released documents go into one controlled repository. That repository becomes the record auditors, service teams, and customers rely on, and it stays readable long after the PLM system has been upgraded or replaced.
3. Control versions: working, released, frozen
Every document needs a visible status. Engineers save working versions while they edit, and only a reviewed version gets published as the current one. A document management system handles this with major and minor version numbers, so a draft never gets mistaken for the approved release.
Once a document is final, freeze it. Doxis can mark a version as final, and from then on the system rejects any new version of that document. Superseded versions stay in the history, restricted, so you can always show what applied on a given date.
4. Route every change through review and approval
An ECO that waits in an inbox is invisible. Process automation routes each new document or change to the right reviewers, holds the document while it is under review, and records the decision. If a reviewer asks for changes, the document goes back to its author with the comments attached.
For quality-critical documents, add four-eyes or six-eyes approval, so the person who wrote a work instruction cannot also release it. Doxis Quality Management adds mandatory read confirmation, which lets you prove that the shop floor has seen the new version.
5. Set retention rules by document class, not by folder
There is no single retention period for product documentation. The EU Machinery Regulation sets a minimum of ten years after the product is placed on the market. ISO 13485 requires medical device records to be kept for at least the lifetime of the device as the manufacturer defines it, and no less than two years from release. Your own product liability exposure may argue for longer.
Define the retention rule once per document class, such as declarations of conformity or test reports, and let the system apply it.
Doxis retention management blocks deletion before the retention period expires, and audit-proof archiving keeps the content unaltered for as long as the rule requires. Retention applies to a document and all of its versions, so the full revision history stays intact.
6. Make the audit trail automatic
Who changed what, and when? An audit trail answers that without anyone having to reconstruct it. Doxis records every operation on a document, including the user and a time stamp, and can log changes to the metadata as well.
Build your processes so the audit trail is created as the work happens. When the evidence writes itself, audit preparation shrinks to a search.
Your product documentation readiness checklist
Use this list to test your current setup. If you can't tick an item within a few minutes, that's where to start.
- Every product or machine has one file that holds all its released documentation
- Each document shows a clear status: working, in review, released, or final
- You can identify the version of every drawing and manual that applied on any past date
- Every released document has a recorded reviewer and approver
- Retention rules are defined per document class and applied automatically
- Released documents can't be deleted or overwritten before their retention period ends
- Digital instructions for EU customers stay downloadable for at least ten years
- Your team can find a document by its content, even without knowing its number
- An auditor's request can be answered in hours
That last item is the real test. If your answer still depends on one experienced colleague who knows where everything is, your documentation is at risk the day that person moves on. AI document search helps here, because it finds documents by what they contain.
How to choose product documentation software
Product documentation software should make the six steps above routine. When you compare options, test them against the documents and processes you actually have.
- Versioning and release control: working and released versions, final-version freezing, and a complete history
- Configurable workflows: review and approval routes you can adapt per document class, with escalation when a step stalls
- Retention and audit-proof storage: rules per document class, deletion locks, and tamper-proof archiving
- Audit trails: automatic logging of every operation, readable by an auditor without IT support
- Integration: open interfaces to your ERP and other business systems through standard business system integrations, plus REST and CMIS APIs for project-specific connections
- Deployment and certification: a choice of cloud, on-premises, or hybrid operation, backed by independent compliance certifications
Ask every vendor to show you how their software connects to your specific PLM and CAD systems, and whether that connection is a shipped product or a project. The honest answer tells you how much of your budget goes to integration work.
Where product documentation fits into your wider content lifecycle
Product documentation doesn't stop at the edge of engineering. The same machine also generates supplier certificates, service contracts, and warranty claims, and each of them points back to the product.
When these records live in separate systems, the fragmentation you fixed for engineering comes back one department later. A service technician needs the current manual and the customer's contract. A recall team needs the design history and the list of delivered units. Quality needs the supplier's test certificate next to your own inspection record.
A complete document lifecycle covers:
- Capture: incoming supplier documents and certificates classified and filed with intelligent document processing
- Management: versioned, searchable documents organized by product
- Process: approvals and changes routed through workflows with a full audit trail
- Retention: archiving and deletion rules that follow the regulation for each document class
- Integration: documents linked to the orders and assets in your ERP and other business systems
That's why so many manufacturing CIOs now treat modern document management as one platform for all product-related content.
Manage product documentation with Doxis
Your engineers already know how to write good documentation. What slows them down is finding the right version, getting it approved, and proving later that it was released correctly.
Doxis gives your product documentation one controlled home, with versioning, approval workflows, retention rules, and audit trails built in.
Your teams keep working in their PLM and CAD systems, and every released document lands in one place.
Document management is one part of the Doxis Intelligent Content Automation platform. The same platform covers AI-powered processing of incoming documents and audit-proof archiving, so supplier certificates, contracts, and service records for each product sit alongside the engineering files. See how Doxis supports document management in manufacturing.
- One product-centric file for every released drawing, manual, certificate, and report
- Working, released, and final versions, with the full history restricted and available for audit
- Review and approval workflows with four-eyes or six-eyes release for quality-critical documents
- Retention rules per document class, deletion locks, and audit-proof archiving
- Audit trails that record every change without manual entry
- One platform for engineering, quality, procurement, and service documents across all your locations
Drive technology manufacturer SEW-EURODRIVE started from a familiar place. Its documents were spread across several legacy ECM systems, teams kept documents current by hand, and work was duplicated because nobody could see which documents already existed or whether they were still accurate. Over more than ten years, the company moved to Doxis across more than 20 countries and now manages around 313 million documents on the platform.
Automate Work. Accelerate Business.
Bring together AI, ECM, and workflow automation in one powerful enterprise platform.
FAQs on compliant product documentation
What does product documentation include?
Product documentation includes every record created over a product's life: design files, technical specifications, test reports, bills of materials, certificates, declarations of conformity, user manuals, and service documentation.
What is the difference between product documentation and technical documentation?
Technical documentation is one part of product documentation. It covers what's needed to install, operate, and assess the risks of a product, while product documentation also includes design, process, quality, and service records.
How long do you have to keep product documentation?
It depends on the product and the market. The EU Machinery Regulation requires at least ten years after a machine is placed on the market, and ISO 13485 ties medical device records to the lifetime of the device.
Is there a standard for product documentation?
No single standard covers all product documentation. IEC/IEEE 82079-1 governs instructions for use, ANSI Z535.6 covers safety messages, and ISO 9001 and ISO 13485 set document control requirements.
What changed with the FDA QMSR in 2026?
On February 2, 2026, the FDA's QMSR began incorporating ISO 13485:2016 into 21 CFR Part 820. Records such as the Design History File are now organized under ISO 13485 concepts, and they still need to be controlled and kept current.
What is product lifecycle documentation?
Product lifecycle documentation is the record of a product from its first requirements through production, use, maintenance, and disposal. It lets you prove what was designed, built, and shipped at any point in time.
Can a DMS replace a PLM system?
No. A PLM system manages product structures and design changes during development, while a DMS manages released documents, approvals, retention, and audit trails. The two work best side by side.
What should product documentation software include?
Look for version control, configurable approval workflows, retention rules per document class, audit-proof archiving, automatic audit trails, and open interfaces to your ERP and engineering systems.
How can we help you?
+49 (0) 30 498582-0Your message has reached us!
We appreciate your interest and will get back to you shortly.