MSI's ISO Q/EMS Design and Development

Q/EMS Design and Development Procedure

$249
One integrated procedure satisfying ISO 9001:2015 Clause 8.3 and ISO 14001:2026 Clause 8.1 a) together. Environmental requirements become design inputs, determined before the input set is approved and considered across every life cycle stage, rather than reviewed against a design already fixed. Environmental content is marked inline throughout, with a Q/EMS process interaction map.
ISO 9001:2026 publishes around September 2026. Buy now, get the rebuild free.
This template is built to ISO 9001:2015 — the edition currently in force and the one your certificate is issued against. When the new edition publishes, MSI rebuilds this template against it and sends it to you at no charge. Nothing for you to do: the version stamp in your file is how we know which edition you hold.

What is actually in the document

The full ISO 9001 Clause 8.3 procedure with the ISO 14001 environmental requirement folded into the six places it genuinely touches — the trigger, the inputs, the input question set, the outputs, the change significance test and the records. Sixteen numbered sections, three appendices, and a Q/EMS process interaction map. Environmental content is marked inline rather than pulled into a separate section.

  • 49pages, editable Word
  • 44obligations cross-referenced
  • 34MSI notes and callouts
  • 72marked decisions that are yours
ISO 14001 has no design and development clause. What it has is one lettered requirement inside Clause 8.1, and it presumes a design process already exists: consistent with a life cycle perspective, the organization shall establish controls, as appropriate, to ensure that its environmental requirements are addressed in the design and development process for the product or service, considering each life cycle stage. That sentence is the whole integration — and it is the requirement most often unmet in organizations that hold both certificates.

Three things Q/EMS organizations get wrong

01 · The aspects register and the design procedure never meet

Organizations do life cycle perspective properly. Design is listed as a life cycle stage in the aspects register, the impacts are assessed, the register is current and defensible. And nothing connects it to the design process — the register says design matters, the design procedure has no environmental input, and no document links the two. Clause 8.1 a) is that link, and it is the one thing an auditor can check in five minutes.

02 · Environmental review happens after the design is fixed

Where environmental requirements are checked at the end, the answer is always the same: the design complies, or it does not and it is too late to do much about it. A life cycle perspective applied at input capture changes what gets designed; applied at release it only records what was. This procedure asks seven life cycle questions during input capture, before the material is chosen.

03 · Nobody owns the question

The commonest structural reason Clause 8.1 a) goes unmet is that no role is responsible for determining which environmental requirements apply to a given design project. The answer then arrives from whoever happens to know, late. This procedure gives the Environmental Manager three named trigger routes, a determination to make before the input set is fixed, and a confirmation at the release gate — including a recorded nil return where nothing applies.

What’s included

  • The complete Clause 8.3 procedure with ISO 14001 Clause 8.1 a) integrated, editable Microsoft Word
  • A Q/EMS process interaction map, embedded and supplied as an editable SVG, with environmental interfaces marked
  • Environmental content marked inline rather than separated, so it reaches the people doing the design
  • Three environmental trigger routes — a changed compliance obligation, a significant aspect needing design control, an environmental objective only a product change can meet
  • The seven life cycle questions — raw materials, design, production, transport, use, end of life, final disposal — asked at input capture
  • A named Environmental Manager role with a determination before the input set is approved, including recorded nil returns
  • Complexity tiering that includes environmental criteria, so a material or end-of-life change cannot fall to the lightest tier
  • An environmental conflict route for where a functional requirement can only be met by worsening an environmental one
  • An environmental confirmation at the release gate, and aspects register updates before release rather than after
  • Change significance tested against environmental effect, satisfying Clause 6.3 planning of changes
  • A records table with no blanks, and a cross-reference covering ISO 9001 8.3 and ISO 14001 8.1 a), 6.1.2, 6.1.3, 6.2, 6.3 and 8.1
  • Appendix A — Design and Development Plan, built to function as the release gate
  • Appendix B — Design Review and Decision Log
  • Appendix C — work instruction with a worked example

Every appendix, form, map and worked example is part of the document. Nothing is sold separately.

Who it’s for

Quality and environmental managers at organizations certified to both ISO 9001 and ISO 14001 that design products or services. Particularly useful where the two systems are managed by different people, where the aspects register is strong and the design procedure is silent on environment, or where a 14001 auditor has asked how environmental requirements reach the design and the answer took some assembling.

Not sure yet? The free Design and Development Maturity Check scores eight elements in under five minutes, and your score appears without entering anything.

Questions

Is this the same as the IMS version?

No. This one covers ISO 9001 and ISO 14001. If you also hold ISO 45001, the IMS variant covers all three and is the one to buy — buying this one as well would duplicate most of it.

ISO 14001 barely mentions design. Is there enough here to justify a separate document?

The clause text is one sentence, and that sentence is exactly the point. It requires environmental requirements to be addressed in the design process considering each life cycle stage, which touches inputs, outputs, change control and records. What this document does is put that requirement where a designer will actually encounter it, rather than leaving it in the environmental manual where designers do not look.

Do we need a life cycle assessment?

No, and the standard says so in its guidance: thinking carefully about the environmental aspects the organization can control or influence at each life cycle stage is sufficient. Seven questions answered honestly at input capture meets Clause 8.1 a). A consultant-led assessment does not, if the answers never reach the designer.

Which one do I need?

This one if you hold ISO 9001 and ISO 14001. ISO 9001 alone, take the single-standard version. Medical devices, take the ISO 13485 or the integrated 9001/13485 version. All three of 9001, 14001 and 45001, take the IMS version.

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 — thresholds, roles, stage names, systems, retention periods. You are editing a working document rather than filling in a hollow outline.

What format is it?

Editable Microsoft Word (.docx), with the process interaction map embedded in the document and supplied separately as an editable SVG. Adapt it, rebrand it, and adopt it into your own document control system.

Will this pass an audit?

A procedure does not pass an audit; an organization does. What this gives you is a procedure that addresses every requirement of the clauses it covers, with a named owner and a named record, describing a process people can actually follow. Conformity is demonstrated by implementation and evidence. Unfilled placeholders are unmet requirements, so fill them.

We use different clause numbering.

Every cross-reference sits in a table at the back rather than baked into the body text, precisely so you can renumber without unpicking the procedure.

I already own MSI’s Design and Development course. Do I need this too?

The course teaches the method — how to get the process out of the heads of the people who do the work. This is the document. Where a form appears in both, this template carries the current revision; the version stamp in the footer tells you which you are holding. The template contains no video.

Can you help us implement it?

Yes. Call MSI at 760-434-9141 to schedule a planning session.