The OEM Buyer’s Guide to LED Therapy Device Compliance Documentation

A customer in the EU requested our “technical file” for CE marking. We didn’t have one. We had to assemble it in 2 weeks — a scramble that cost $5,000 in consultant fees and delayed the order by 3 weeks. After that, we created a compliance documentation system. Now when a customer or regulator requests documentation, we can provide it in 2 hours instead of 2 weeks.

Compliance documentation is not just a regulatory requirement. It’s a sales tool (customers ask for it), a liability protection (if there’s a product issue), and a quality management tool. Here’s what you need and how to organize it.

---

The Compliance Documentation Types

Document Type	Purpose	Required For
Technical file (for CE)	Evidence of conformity with applicable directives	CE marking (EU)
Design controls (for FDA)	Evidence of design process, verification, validation	FDA 510(k) (USA)
Risk management file	Evidence of risk analysis and mitigation	CE, FDA, ISO 13485
Declaration of Conformity (DoC)	Manufacturer’s declaration that product meets requirements	CE marking
Test reports	Evidence of testing (safety, EMC, performance)	CE, FCC, FDA, other markets
User manual and labeling	Instructions for use, safety warnings	All markets
Quality management system (QMS) documentation	Evidence of quality processes	ISO 13485, CE, FDA
Post-market surveillance documentation	Evidence of ongoing monitoring and reporting	CE MDR, FDA

The technical file is the most comprehensive. It includes design documentation, test reports, risk analysis, labeling, and the Declaration of Conformity. EU regulators can request it at any time. If you don’t have it, you can’t sell in the EU.

The risk management file is required for medical devices and recommended for wellness devices. It documents the risks associated with the device and how you’ve mitigated them. It’s essential for liability protection.

The Technical File Contents (CE Marking)

The technical file is a folder (physical or electronic) that contains all evidence of conformity.

Section	Contents
1. General information	Product name, model, intended use, manufacturer details
2. Applicable directives and standards	List of directives (LVD, EMC, etc.) and standards (IEC 60601, etc.)
3. Design documentation	Specifications, drawings, circuit diagrams, software documentation
4. Risk analysis	ISO 14971 risk management report
5. Test reports	Safety (IEC 60601-1), EMC (IEC 60601-1-2), photobiological safety (IEC 62471)
6. Labeling and user manual	Product label, packaging label, user manual in required languages
7. Declaration of Conformity	Signed DoC
8. Post-market surveillance	Complaint handling, incident reporting, market surveillance

The technical file must be kept for 10 years after the last product is placed on the market (for medical devices under MDR). This is a regulatory requirement. If a regulator requests it, you must provide it within a reasonable timeframe (usually 7-30 days).

The Documentation Organization System

Organize documentation so it’s easy to find and update.

Organization Method	Pros	Cons	Recommendation
Physical folder (paper)	Easy to understand, accepted by regulators	Bulky, hard to search, hard to update	Not recommended
Electronic folder (PDFs on server)	Easy to access, searchable	Can be disorganized if not structured	Acceptable for small companies
Document management system (DMS)	Structured, version-controlled, audit trail	Cost, complexity	Recommended for scaling companies
Cloud-based QMS software (Greenlight Guru, MasterControl)	Purpose-built for medical devices, integrated	Expensive ($5,000-20,000+/year)	For medical device companies

The electronic folder method is sufficient for small-medium companies. Create a folder structure: “Compliance > [Product Name] > Technical File > [Sections 1-8].” Store PDFs with clear naming: “Risk Analysis v2.3 2025-01-15.pdf.”

The version control is essential. Every document should have a version number and date. When you update the document, archive the old version and create a new version. This is required for regulatory compliance.

The Documentation Maintenance

Compliance documentation is not a one-time task. It must be maintained.

Maintenance Activity	Frequency	Trigger
Update technical file	Annually or when product changes	Product change, new standard, regulatory update
Review risk analysis	Annually	Part of post-market surveillance
Update test reports	When product changes or standard changes	Product design change, new standard version
Review labeling and manual	When product changes	Product change, user feedback
Post-market surveillance	Ongoing	Complaints, incidents, market feedback

The product change trigger: If you change the product (new LED supplier, new controller board, new enclosure material), you must evaluate if the technical file needs updating. If the change affects safety or performance, you may need new testing.

The regulatory update trigger: If a new version of a standard is published (e.g., IEC 60601-1:2012 → IEC 60601-1:2025), you must evaluate if your product still complies. If the new standard has new requirements, you may need new testing.

What We’ve Learned

1. The $5,000 consultant fee to assemble a technical file in 2 weeks was avoidable. If we had maintained the technical file from the start, we could have provided it in 2 hours instead of scrambling. Now we have a documentation system. When customers or regulators request documentation, we provide it immediately.

2. The version control saved us during an audit. A regulator asked for our technical file. We provided it. They noticed a discrepancy between the risk analysis (v2.1) and the test report (v2.0). We explained the version difference and provided the updated test report (v2.1). Without version control, we wouldn’t have caught the discrepancy.

3. The cloud-based QMS software is worth the cost for medical device companies. We switched from electronic folders to Greenlight Guru. The software manages document versions, audit trails, and CAPA (corrective and preventive actions). It costs $10,000/year but saves 50-100 hours/year in documentation management. For a medical device company, it’s justified.

4. The post-market surveillance documentation is often overlooked. We didn’t have it initially. Then we had a customer complaint about a skin reaction. We didn’t have a process for documenting and investigating. Now we do. The post-market surveillance documentation is required by CE MDR and FDA, and it’s essential for continuous improvement.

5. The technical file must be updated when the product changes. We changed our LED supplier. The new LEDs had the same wavelength but different irradiance. We didn’t update the technical file initially. Then we realized the test report (which measured irradiance) was outdated. We updated the test report and technical file. Lesson: every product change requires a documentation review.

The OEM buyer’s guide to LED therapy device compliance documentation requires understanding the documentation types (technical file, risk management file, test reports, DoC, labeling, QMS), organizing documentation in a structured system (electronic folders or DMS), maintaining documentation (update on product changes, regulatory updates, annual review), and keeping documentation for 10+ years. The $5,000 consultant fee and 3-week delay we experienced from not having a technical file taught us that compliance documentation is not optional — it’s a regulatory requirement, a sales tool, and a liability protection. Create the documentation system from Day 1, not when a customer or regulator asks for it.