# ISO 13485 Document Templates (Quality Manual, Software Validation, Supplier Quality Agreement)

> Source: https://netray.co/tools/iso-13485-document-templates
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable ISO 13485 template set covering a quality manual outline, a software validation plan for ERP and quality software, and a supplier quality agreement.

## Category

compliance-legal

## Industry

Medical Devices

## Audience

- Quality manager
- Regulatory affairs
- Medical device manufacturer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Medical Devices Ltd

#### Site address

**Key:** site

**Type:** text

**Default:** 12 Industrial Park, Springfield

#### Device scope

**Key:** device

**Type:** text

**Default:** Class II single-use surgical instruments

#### Regulatory role

**Key:** role

**Type:** select

**Options:**

- Manufacturer
- Contract manufacturer
- Importer
- Distributor

**Default:** Manufacturer

#### Management representative

**Key:** qm

**Type:** text

**Default:** Director of Quality

#### Software to validate

**Key:** system

**Type:** text

**Default:** ERP system (inventory, lot traceability, nonconformance module)

#### Software version

**Key:** version

**Type:** text

**Default:** Release 2026.1

#### Supplier name

**Key:** supplier

**Type:** text

**Default:** Precision Plastics GmbH

#### Supplied product or service

**Key:** part

**Type:** text

**Default:** Injection moulded housings, part PN-7741

#### Date

**Key:** date

**Type:** date

**Default:** 2026-10-20

**Blocks:**

#### Part A. Quality Manual (outline)

**Body:** Document: Quality Manual
Organization: {{company}}, {{site}}
Issue date: {{date}}
Quality manual owner: {{qm}}

#### A1. Scope and exclusions

**Body:** This quality management system applies to the design, manufacture, and distribution of: {{device}}. The organization acts as: {{role}}.

List any requirement of ISO 13485:2016 clause 6, 7 or 8 that is not applicable and the justification (for example, design and development excluded for a contract manufacturer that does not design). Regulatory requirements cannot be excluded.

#### A2. Process interactions and procedures

**Table:**

**Columns:**

- Clause
- Topic
- Documented procedure required
- Our document ID

**Rows:**

**0:** 4.2.4

**1:** Control of documents

**2:** Yes

**3:** QP-001

**0:** 4.2.5

**1:** Control of records

**2:** Yes

**3:** QP-002

**0:** 5.6 / 8.2.4

**1:** Management review and internal audit

**2:** Yes (audit)

**3:** QP-003

**0:** 7.4

**1:** Purchasing and supplier evaluation

**2:** Yes

**3:** QP-004

**0:** 7.5.6

**1:** Process validation

**2:** Yes

**3:** QP-005

**0:** 8.3

**1:** Control of nonconforming product

**2:** Yes

**3:** QP-006

**0:** 8.5.2

**1:** Corrective action

**2:** Yes

**3:** QP-007

**0:** 8.5.3

**1:** Preventive action

**2:** Yes

**3:** QP-008

#### Part B. Software Validation Plan

**Body:** Software: {{system}}
Version: {{version}}
Organization: {{company}}

Clause 4.1.6 requires validation of software used in the quality management system before initial use and after changes, in proportion to risk. Clause 7.5.6 and 7.6 apply to software used in production and monitoring.

#### B1. Intended use and risk

**Body:** Intended use: record lot and serial traceability, control inventory status (quarantine, released, rejected), and route nonconformances for {{device}}.

Risk assessment: describe how a software failure could affect product quality or compliance, rate the risk (high, medium, low), and set the validation depth to match. A lot status error that allows shipment of rejected product is high risk.

#### B2. Validation activities

**Table:**

**Columns:**

- Step
- Activity
- Evidence
- Owner

**Rows:**

**0:** 1

**1:** User requirements specification approved

**2:** Signed URS

**0:** 2

**1:** Supplier assessment (vendor documentation, release notes)

**2:** Supplier record

**0:** 3

**1:** Installation verification (environment, version, configuration)

**2:** IQ record

**0:** 4

**1:** Test cases for lot status, traceability, access roles, audit trail

**2:** OQ results with screenshots

**0:** 5

**1:** Test with real workflows and data

**2:** PQ results

**0:** 6

**1:** Release and training

**2:** Validation summary report, training records

**0:** 7

**1:** Change control and revalidation criteria

**2:** Change records

#### Part C. Supplier Quality Agreement

**Body:** Between {{company}} (Buyer) and {{supplier}} (Supplier).
Product or service covered: {{part}}.
Effective date: {{date}}.

1. Quality system: Supplier maintains a quality management system appropriate to the product (ISO 13485 or ISO 9001 certification, or equivalent, as agreed).
2. Specifications: Supplier manufactures to the Buyer's current drawing, specification and approved revision. Supplier does not change materials, process, site or sub-supplier without prior written notice and Buyer approval.
3. Inspection and records: Supplier provides a certificate of conformance and the agreed inspection data with each lot and keeps records for the period stated in the agreement.
4. Traceability: Supplier maintains lot traceability to raw material.
5. Nonconformance and corrective action: Supplier notifies Buyer within an agreed time of any suspected nonconformance and responds to corrective action requests within the agreed time.
6. Audit and access: Buyer, its customers and regulators may audit the Supplier's processes related to this product on reasonable notice.
7. Complaints and recalls: Supplier cooperates in investigations and field actions.

#### Approvals

**Signatures:**

- Buyer quality representative
- Supplier quality representative
- Management representative

**Notes:** This is a starting point, not legal advice or a certified quality system. ISO 13485 requires documents appropriate to your products and regulatory role, so adapt every section. Do not reproduce text of the standard. Software validation depth must be justified by risk for your ERP and QMS tools.

## Content

**Intro:** This is an editable ISO 13485 document template set in one place: a quality manual outline, a software validation plan that suits ERP and QMS software, and a supplier quality agreement. Fill the fields once and export a Word or PDF draft you can adapt.

**Sections:**

#### What ISO 13485 requires you to document

**Body:** ISO 13485:2016 requires a quality manual (clause 4.2.2), a set of documented procedures for specific processes, and records that show the system runs. Many people over-document. The standard explicitly requires procedures for control of documents, control of records, internal audit, nonconforming product, corrective action, and preventive action, among others, and you decide the depth for the rest. It also requires a medical device file (4.2.3) for each device type or family. Use this set as the skeleton and add what your regulatory role needs, such as FDA 21 CFR 820 or EU MDR requirements.

#### Software validation for ISO 13485

**Body:** Clause 4.1.6 requires validation of software applications used in the quality management system, with the approach proportional to risk and its intended use. ERP systems that hold lot traceability, inventory status, nonconformance records and document approvals fall inside this. A sensible plan states the intended use, assesses the risk, defines test cases for the functions that affect product quality, and sets criteria for revalidation after upgrades or configuration changes. Keep the evidence: test scripts, results, screenshots and an approval signature. Cloud ERP updates arrive often, so agree how releases are assessed.

**Bullets:**

- Write a user requirements specification before testing
- Test access roles and audit trail, not only happy paths
- Risk based: test hardest where failure can reach the patient
- Revalidate on major upgrades and relevant configuration changes

#### Supplier quality agreements

**Body:** Clause 7.4 requires you to evaluate and monitor suppliers based on their effect on product quality, and the controls scale with risk. A supplier quality agreement is the contract-level way to make them accept change notification, record keeping, traceability, audit access and corrective action timing. Keep it clear and balanced rather than clever; suppliers will sign a short document faster. Link the agreement to your approved supplier list, so the status of each supplier is visible to purchasing.

#### Common mistakes

**Body:** Copying another company's manual verbatim is the most common error: auditors will ask staff about it and the answers will not match. Other mistakes include a software validation done once at go-live and never revisited, a quality manual that excludes design when the company does design, and supplier agreements that nobody monitors. Review these documents at management review and after any process change.

**Cta:** If your ERP holds lot traceability and nonconformance records, Netray can build a read-only AI layer on your own servers that helps you gather validation evidence and answer auditor questions.

**Faq:**

#### Is a quality manual mandatory in ISO 13485?

**Answer:** Yes. Clause 4.2.2 requires a quality manual that includes the scope, exclusions with justification, the documented procedures or references to them, and a description of how the processes interact. Its length and format are up to you.

#### Do I have to validate my ERP under ISO 13485?

**Answer:** If it is used in the quality management system or affects product quality, such as lot traceability, inventory status or nonconformance records, clause 4.1.6 requires validation proportional to risk. The depth depends on the intended use.

#### Can a supplier quality agreement replace supplier audits?

**Answer:** No. The agreement sets expectations and legal rights, while evaluation and monitoring under clause 7.4 uses audits, performance data or certificates depending on risk. Use both for critical suppliers.

#### How many procedures does ISO 13485 need?

**Answer:** There is no fixed number. The standard names the processes that need documented procedures, and you add others needed for effective operation. A small manufacturer can often cover the required set in fewer than twenty documents.

## Search terms

iso 13485 document templates, iso 13485 template, iso 13485 sample document, example of iso 13485, software validation template iso 13485, supplier quality agreement template iso 13485, iso 13485 quality manual template, iso 13485 procedures list

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json