Template: List of Hazard-Related Use Scenarios

Template Download

This is a free template, provided by OpenRegulatory.

If you are a user of Formwork, our eQMS software, choose “QMS” on the top menu and “OpenRegulatory Templates” on the left menu, and then open the relevant folder to find this template ready to load into Formwork.

If, for some mysterious reason, you’re using a different QMS Software, you can also simply download this template – specifically, as Word (.docx), PDF, Google Docs or Markdown file. Scroll down for a preview!

The template license applies (don’t remove the copyright at the bottom).

Tired of copy-pasting? If you want to save time and edit these templates directly, you can use Formwork, our eQMS software. And if you’re looking for step-by-step instructions for filling them out, check out our Wizard 🙂

Don't Miss Updates to This Template
Subscribe to our newsletter and we'll keep you posted on which templates we've changed.

Questions? Still Lost in Regulation?

Good news! Our goal is to provide lots of stuff for free, but we also offer consulting if you need a more hands-on approach. We get stuff done really fast. Have a look!

Template preview

Mapping of Standard Requirements to Document Sections

IEC 62366-1:2015 SectionTitleDocument Section
5.4Identify and describe Hazard-Related Use Scenarios1
5.5Select the Hazard-Related Use Scenarios for Summative Evaluation1


The goal of the list of Hazard-Related Use Scenarios is to gather all Use Scenarios which could be associated with a Hazard, e.g., if a user doesn’t understand a certain feature of the app (bad design leading to poor usability), then a Hazard could be encountered which could subsequently lead to a Hazardous Situation.

1. Hazard-Related Use Scenarios

Fill out this list with Use Scenarios which could be Hazard-related. A good rule of thumb is to have 3-10 scenarios, based on the risk profile of your software.

Also, note that you should prefer to create a spreadsheet for this table (e.g., in Google Sheets) as putting a table in a document will surely lead to chaos. But then again, there’s always a certain level of chaos in regulatory documentation.

IDUser GroupDescriptionApp State / EnvironmentTasksAcceptance Criteria
1PhysicianAssess COVID score1) App is installed
2) App displays patient result
Understand COVID score and initiate further medical treatmentCOVID score is understood correctly

Template Copyright openregulatory.com. See template license.

Please don’t remove this notice even if you’ve modified contents of this template.

Template preview


Leave the first comment