How should contract manufacturers handle DHR review across multiple device customers?
By Savi C., Co-Founder · Published Nov 16, 2026
Two sets of obligations on one record
Under the QMSR, 21 CFR 820.3 defines a manufacturer as anyone who designs, manufactures, fabricates, assembles or processes a finished device, and the definition expressly includes contract sterilizers. A contract manufacturer building finished devices therefore runs its own quality system, keeps its own production records and answers to FDA directly.
Its customers carry their own obligation. ISO 13485 clause 4.1.5 requires an organization that outsources a process affecting product conformity to monitor and ensure control over it, proportionate to the risk, and those controls must include written quality agreements. The record for each device or batch is one document, but two quality systems rely on it.
The practical problem is that every customer brings different specifications, release arrangements and paperwork expectations to the same production floor. A single internal DHR review procedure works only if it is driven by a clear, per-customer definition of what the review must cover.
What each quality agreement should settle about DHR review
Question
Whose specifications govern
What to define
The customer drawing, bill of material and acceptance criteria, at which revision, and how revisions reach the floor
Question
Who reviews the DHR
What to define
Whether the contract manufacturer reviews only, or the customer also reviews before acceptance, and what each review covers
Question
Who authorizes release
What to define
Who releases product from the contract manufacturer, who releases to distribution, and how each authorization is recorded under clause 8.2.6
Question
Nonconformances
What to define
Which nonconformances the customer must be told about, and who can approve use or release under concession under clause 8.3.2
Question
Changes
What to define
Which process, material or supplier changes need customer approval before use
Question
Customer property
What to define
How customer-supplied components, tooling or labels are controlled, and how loss or damage is reported under clause 7.5.10
Question
Records
What to define
What the DHR packet contains, the format and timing of handover, who retains originals, and for how long
Why review gets harder with each new customer
Each customer adds its own drawing revisions, inspection points, labeling content and release steps. Reviewers who move between customer lines in a day have to switch rulebooks with every packet, and a typical failure in that setting is applying the right check to the wrong customer, or a superseded revision to the right one. The quality agreement is where those differences are written down, so the DHR review procedure should point back to it rather than restate it.
Running DHR review across many customers
Set up per customer
- A review profile for each customer and product: specifications, inspection points, labeling requirements and release route
- Customer-specific requirements traceable to the clause of the quality agreement they come from
- A controlled list of who may authorize release for each customer
During review
- The traveler was issued at the customer revision in effect on the build date
- Customer-supplied materials identified and traced to the build
- Every nonconformance dispositioned, and customer notification made where the agreement requires it
- Release authorized by the person the agreement and your procedure name
Across customers
- Exceptions trended by customer, product and line, so a shared process problem shows up even when no single customer sees it
- Retention set to the longest of the customer requirement, the device lifetime and the two-year minimum from release in ISO 13485 clause 4.2.5
- Customer audit and FDA inspection requests answered from one controlled record, not separate copies
How Litewave fits
A contract manufacturer reviews the same kind of record against many different rulebooks. Litewave reads paper or electronic records, checks every entry against the master record and specifications that apply to that customer, and shows QA only the exceptions, each linked to the page it came from. Litewave proposes, qualified people approve. Our published results come from pharmaceutical manufacturing, and device figures will be published only when a device customer has agreed to them.
Questions we get asked
Does the brand owner have to review every DHR from its contract manufacturer?
Not necessarily. The QMSR and ISO 13485 require the brand owner to control the outsourced process in proportion to risk, including through a written quality agreement. That agreement can assign DHR review to the contract manufacturer, but the brand owner keeps responsibility for the product and must be able to show the controls work.
Who signs release when a contract manufacturer builds the device?
Whoever the quality agreement and procedures name. Often the contract manufacturer releases product to the customer and the customer authorizes distribution, and ISO 13485 clause 8.2.6 requires the identity of each person authorizing release to be recorded.
Can one DHR review procedure serve every customer?
One procedure can, if it calls up a customer-specific set of requirements for each review. A generic checklist applied to every customer is where missed customer requirements tend to come from.
