For either ISO 9001 or ISO 13485
<!–
================================================================================
MSI PRODUCT PAGE BLOCKS — SOP-004 Sales Management
Three self-contained blocks. Paste ONE per product page, below the buy button.
HOW TO USE
1. Edit the product page in Elementor.
2. Drag an HTML widget to the position below the Add to Cart button.
3. Copy ONE block below — from its "BLOCK n BEGINS" comment to "BLOCK n ENDS" —
and paste the whole thing, including the and
What is actually in the ISO 13485 document
Twenty-five pages covering the whole of ISO 13485:2016 Clause 7.2 —
determination of requirements, review prior to commitment, and communication arrangements.
Written for device organisations as a filled-in worked example, not adapted from a quality
base.
25pages, editable Word
21obligations cross-referenced
10MSI notes in the margin
139marked decisions that are yours
Since 2 February 2026, this is a regulatory document. The
FDA Quality Management System Regulation incorporates ISO 13485:2016 by reference into 21 CFR
Part 820. For US-marketed devices, your customer-related processes procedure is the operative
form of a federal requirement, and the records it generates are inspectable.
Three things device sales procedures routinely omit
01
User training determination
Clause 7.2.1(d) requires you to determine any training needed to ensure specified performance
and safe use, and 7.2.2(d) requires confirming at review that it is available or planned.
There is no ISO 9001 equivalent, so it is absent from most procedures adapted from a quality
base. It matters beyond compliance: where a risk control is implemented through the user
rather than through the design, the training is the risk control. Supply without it
and the control is not in place.
02
Supply interruption reporting
ISO 13485 has no equivalent to ISO 9001’s contingency clause. For device manufacturers the
obligation arises from law instead — which is precisely why it is missing from so many quality
systems. No clause checklist points at it. This procedure covers both regimes: FD&C Act
Section 506J in the United States, and EU MDR and IVDR Article 10a.
03
Advisory notices, arranged in advance
The arrangement for issuing an advisory notice is a communication requirement of the clause,
not something to work out during the event. Appendix B logs it alongside customer
communication and complaints, so the route exists before you need it.
What’s included
- The complete Clause 7.2 procedure — sixteen numbered sections, editable Microsoft Word
- A channel-enumerated trigger covering every route an inquiry can arrive by
- One accountable owner, with a named alternate for every gating role
- Review routing decided on criteria rather than on order value
- User training determination at both determination and review
- Regulatory authority communication and advisory notice arrangements
- Supply interruption reporting under both the US and EU regimes
- A records table with no blanks — location, owning role and retention period for each
- A maturity ladder — eight elements, four levels each, described as observable behaviour
- A full clause cross-reference mapping twenty-one obligations to where each is addressed
- A process interaction map including the regulatory reporting and vigilance interface
- Appendix A — Requirements Review Record, built to function as the release gate
- Appendix B — Communication, Complaint and Advisory Notice Log
- Appendix C — Contract Review Work Instruction, with a worked example
Every appendix, form and worked example is part of the document. Nothing is
sold separately.
Who it’s for
Quality and regulatory managers at device manufacturers, contract manufacturers and
specification developers certified or certifying to ISO 13485. Particularly useful for
organisations whose customer-related processes procedure was adapted from an ISO 9001 base, which
is where the training and reporting obligations usually go missing.
Not sure yet? The
free Sales Management
Maturity Check has a device path that adds the requirements with no ISO 9001 equivalent.
Under five minutes, and your score appears without entering anything.
Questions
Is this a template or a finished procedure?
Both, deliberately. It is written as a filled-in worked example so you can see what each
element looks like when done properly, with bracketed placeholders wherever a value is
genuinely yours to set. You are editing a working document rather than filling in a hollow
outline.
Does it address the QMSR?
Yes. Since 2 February 2026 the FDA Quality Management System Regulation incorporates ISO
13485:2016 by reference into 21 CFR Part 820. The procedure is written on that basis, and the
cross-reference maps obligations across both the standard and the regulation.
Why not just adapt an ISO 9001 procedure?
Because the clause numbers do not map and the obligations differ. ISO 13485 predates the
harmonised ten-clause structure, and it carries requirements with no ISO 9001 counterpart —
user training determination and advisory notices among them. Adapting a quality procedure is
how those requirements go missing in the first place.
What format is it?
Editable Microsoft Word (.docx). Adapt it, rebrand it, and adopt it into your own document
control system. The licence permits the buying organisation to use it across its own sites
and issue it to employees, contractors and auditors, and permits consultants to adapt it for
engagements they deliver.
Will this pass an inspection?
A procedure does not pass an inspection; an organisation does. What this gives you is a
procedure that addresses every requirement of the clause with a named owner and a named
record. Conformity is demonstrated by implementation and evidence. Unfilled placeholders are
unmet requirements, so fill them.
We run both a device line and a general line.
Take the integrated ISO 9001 and ISO 13485 version instead. It covers both standards in one
document with device-scope content marked throughout, and includes a decision record naming
every point where the two standards diverge.
.msi-pp-root, .msi-pp-root *, .msi-pp-root *::before, .msi-pp-root *::after { box-sizing:border-box; }
.msi-pp-root {
–pp-green:#217A4E; –pp-green-d:#18613D; –pp-navy:#0D1F3C; –pp-ink:#16211D;
–pp-body:#3F4B47; –pp-rule:#D3E0D8; –pp-tint:#F1F6F3; –pp-paper:#FFFFFF; –pp-mute:#71807B;
–pp-sans:-apple-system,BlinkMacSystemFont,”Segoe UI”,Roboto,Helvetica,Arial,sans-serif;
–pp-mono:ui-monospace,”SF Mono”,”IBM Plex Mono”,Menlo,Consolas,monospace;
max-width:860px !important; width:100% !important; margin:0 auto !important;
padding:8px 0 20px !important; font-family:var(–pp-sans) !important;
color:var(–pp-body) !important; line-height:1.62 !important; text-align:left !important;
background:transparent !important;
}
.msi-pp-root p, .msi-pp-root h2, .msi-pp-root h3, .msi-pp-root ul {
margin:0 0 15px !important; padding:0 !important; text-transform:none !important;
letter-spacing:normal !important; font-family:inherit !important; }
.msi-pp-root p:last-child { margin-bottom:0 !important; }
.msi-pp-root strong { color:var(–pp-ink); font-weight:600; }
.msi-pp-root em { font-style:italic; }
.msi-pp-root a { color:var(–pp-green) !important; text-decoration:underline !important; }
.msi-pp-root a:hover { color:var(–pp-green-d) !important; }
.msi-pp-sec { padding:34px 0; border-top:1px solid var(–pp-rule); }
.msi-pp-sec:first-child { border-top:none; padding-top:14px; }
.msi-pp-h2 { font-size:clamp(21px,2.6vw,27px) !important; line-height:1.2 !important;
font-weight:700 !important; letter-spacing:-.018em !important; color:var(–pp-ink) !important;
margin-bottom:14px !important; }
.msi-pp-root h3 { font-size:17px !important; font-weight:700 !important; color:var(–pp-ink) !important;
line-height:1.3 !important; margin-bottom:8px !important; }
.msi-pp-sec p { font-size:16px !important; }
.msi-pp-lede { font-size:17px !important; color:var(–pp-body) !important; }
.msi-pp-micro { font-size:13.5px !important; color:var(–pp-mute) !important; margin-top:14px !important; }
.msi-pp-stats { display:grid; grid-template-columns:repeat(auto-fit,minmax(140px,1fr)); gap:1px;
background:var(–pp-rule); border:1px solid var(–pp-rule); margin:22px 0 0; }
.msi-pp-stat { background:var(–pp-paper); padding:18px 16px; }
.msi-pp-n { display:block; font-family:var(–pp-mono); font-size:27px; font-weight:700;
color:var(–pp-green); line-height:1.05; letter-spacing:-.02em; }
.msi-pp-l { display:block; font-size:12.5px; color:var(–pp-mute); margin-top:6px; line-height:1.35; }
.msi-pp-note { background:var(–pp-tint); border-left:3px solid var(–pp-green);
padding:18px 20px !important; margin-top:22px !important; font-size:15px !important; }
.msi-pp-list { list-style:disc !important; padding-left:20px !important; }
.msi-pp-list li { font-size:15.5px !important; line-height:1.55 !important; margin-bottom:9px !important;
color:var(–pp-body) !important; }
.msi-pp-list li:last-child { margin-bottom:0 !important; }
.msi-pp-arg { border-top:1px solid var(–pp-rule); padding:20px 0 4px; }
.msi-pp-arg:first-of-type { border-top:none; padding-top:6px; }
.msi-pp-tag { font-family:var(–pp-mono) !important; font-size:11px !important;
letter-spacing:.09em !important; color:var(–pp-green) !important; margin-bottom:8px !important; }
.msi-pp-arg p:last-child { font-size:15.5px !important; }
.msi-pp-cta-line { background:var(–pp-tint); padding:16px 18px !important; margin-top:18px !important;
font-size:15px !important; }
.msi-pp-faq { border-top:1px solid var(–pp-rule); padding:20px 0 4px; }
.msi-pp-faq:first-of-type { border-top:none; padding-top:4px; }
.msi-pp-faq p { font-size:15.5px !important; }
@media (max-width:640px) {
.msi-pp-root { padding:6px 0 14px !important; }
.msi-pp-sec { padding:26px 0; }
.msi-pp-stat { padding:14px 12px; }
.msi-pp-n { font-size:23px; }
}