Template: Usability Evaluation Protocol

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
4.2Usability Engineering File(all)
4.3Tailoring of the Usability Engineering effort(all)

1. User Group and Environment

Describe the user group here, e.g., physicians with experience in a certain field.

Also, describe the environment in which the user test is being conducted. Obviously, both the user group and environment should match whatever you described in your Intended Use. So, if your app is intended to be used by emergency physicians in a brightly-lit hospital environment, you should also have these people do the usability test in a similar environment.

2. Preparation

Describe whether you prepare users in any way. Again, this should be based on the use context in which your users will be using your device in real life. So, if people typically carefully read the user manual before (not sure in which parallel universe that happens), you can give them the manual and some time to study it. More realistically, you’ll probably test how users handle your device when they haven’t read the manual.

If there are official training which are required before users can use your device, you should do this training first, of course.

3. List of Tasks

This table lists the tasks you want your users to perform. It’s kind of the master table which will be copy-pasted for each user below – you’ll be filling out the observations and hazards encountered by each user.

As always, using a spreadsheet (e.g., Google Sheets) instead of a document is a very good idea here.

IDDescriptionApp State / EnvironmentInstructionsAcceptance CriteriaObservationsHazards encountered

4. Protocols

Copy-paste the table above for each user and fill it out during the test. Note down the names and ages (or any other important characteristics) per user.

User 1 (Name, Age)

IDDescriptionApp State / EnvironmentInstructionsAcceptance CriteriaObservationsHazards encountered

User 2 (Name, Age)

IDDescriptionApp State / EnvironmentInstructionsAcceptance CriteriaObservationsHazards encountered

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