# Design History File (DHF) Index Template

> Source: https://netray.co/tools/design-history-file-index-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable index of the records that make up a medical device design history file, with status, owner and review date for each document.

## Category

engineering-plm

## Industry

Medical Devices

## Audience

- R&D engineer
- Quality engineer
- Regulatory affairs

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### DHF section

**Key:** section

**Type:** select

**Options:**

- Design plan
- Design input
- Design output
- Design review
- Verification
- Validation
- Transfer
- Changes
- Risk management

#### Document number

**Key:** doc_no

**Type:** text

#### Document title

**Key:** title

**Type:** text

#### Revision

**Key:** rev

**Type:** text

#### Owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Draft
- In review
- Approved
- Superseded

#### Approval date

**Key:** date

**Type:** date

#### Pages

**Key:** pages

**Type:** number

**Rows:**

#### Design and development plan, infusion pump v2

**Section:** Design plan

**Doc no:** DP-0412

**Rev:** C

**Owner:** R&D lead

**Status:** Approved

**Date:** 2026-02-14

**Pages:** 18

#### User needs and design input requirements

**Section:** Design input

**Doc no:** DI-0412

**Rev:** D

**Owner:** Systems engineer

**Status:** Approved

**Date:** 2026-03-09

**Pages:** 42

#### Risk management file and hazard analysis

**Section:** Risk management

**Doc no:** RM-0412

**Rev:** E

**Owner:** Quality engineer

**Status:** Approved

**Date:** 2026-05-21

**Pages:** 76

#### Drawings, BOM and software specification

**Section:** Design output

**Doc no:** DO-0412

**Rev:** F

**Owner:** Mechanical engineer

**Status:** In review

**Date:** 2026-08-03

**Pages:** 120

#### Design verification protocol and report, flow accuracy

**Section:** Verification

**Doc no:** VER-0412

**Rev:** B

**Owner:** Test engineer

**Status:** Approved

**Date:** 2026-07-11

**Pages:** 55

#### Usability validation (summative) report

**Section:** Validation

**Doc no:** VAL-0412

**Rev:** A

**Owner:** Human factors lead

**Status:** Draft

**Date:** 2026-09-30

**Pages:** 38

**Totals:**

#### Total pages

**Key:** pages

**Agg:** sum

**Format:** number

#### Documents indexed

**Key:** doc_no

**Agg:** count

**Format:** integer

**Notes:** Extend the rows for every record in your design project. Under ISO 13485 the equivalent term is the design and development file. Keep the index current as records are revised, and confirm what your quality system procedures require in the file.

## Content

**Intro:** A design history file collects the evidence that a device was designed under control. This worksheet gives you an index to build and maintain, so any reviewer can see which records exist, who owns them and whether they are approved.

**Sections:**

#### How to use this worksheet

**Body:** Add one row per record in the design project. Pick the DHF section, enter the document number, title, revision, owner and status, and add the approval date. The total pages and document count at the bottom help you spot gaps. Export to Excel and keep the index as the first page of the file or in your document management system. Update it each time a record is revised or superseded.

**Bullets:**

- Index by section so gaps in a design stage are visible
- Reference the current approved revision of each record
- Mark old versions as superseded instead of deleting rows
- Link each requirement to its verification and validation record

#### What belongs in the file

**Body:** The old FDA design control requirement in 21 CFR 820.30 expected a file that demonstrates the design was developed according to the approved plan. ISO 13485 clause 7.3 asks for a design and development file covering the plan, inputs, outputs, review, verification, validation, transfer and changes. Together they point to the same content: the plan, input requirements, outputs such as drawings and specifications, design reviews, verification and validation results, transfer to production, and a history of changes and the risk management file.

#### DHF, DMR and DHR

**Body:** People often mix these up. The DHF shows how the design was developed. The device master record, or medical device file, holds the instructions and specifications needed to manufacture and release the device. The device history record shows how one lot or serial number was actually built. The DHF feeds the DMR at design transfer, and the DMR is what each DHR proves was followed.

#### Common mistakes

**Body:** Frequent problems are inputs with no matching verification, a design review held without independent attendees, outputs that do not state acceptance criteria, and a file assembled at the end of the project from memory. Build the index from day one and review it at each design gate, so missing records are noticed when they can still be produced properly.

**Cta:** If your drawings, BOMs and change orders live in PLM or ERP, Netray can help reconcile them with the DHF index on your own infrastructure.

**Faq:**

#### What is a design history file?

**Answer:** It is the compiled record showing a medical device was designed according to an approved plan and the design control process. It holds plans, requirements, outputs, reviews, verification, validation, transfer and change records.

#### Do I need a separate DHF for each device?

**Answer:** Generally yes, one per device type or family, as defined in your procedure. Variants that share design records can reference the same documents, as long as the file clearly shows what applies to which model.

#### Does the DHF have to be one physical binder?

**Answer:** No. It can be an index that points to records in different systems, provided each record is controlled, retrievable and the index is current. Many teams keep the index in a spreadsheet or document control tool.

#### When should the DHF be closed?

**Answer:** The file stays open for the life of the product because design changes keep adding records. Many firms baseline it at design transfer and release, and then add later changes through change control.

## Search terms

design history file index template, DHF index, design history file template excel, DHF checklist medical device, design and development file ISO 13485, design control documentation list, DHF vs DMR vs DHR, design history file example

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