Research protocol
A research protocol is your project’s plan and manual. It says why you’re doing the project, who it’s for, how you’ll reach them, what you’ll collect and when, how you’ll analyse it and how you’ll use what you find. It follows the shape of research protocols and evaluation plans, written for people who aren’t researchers.
Open it from Setup > Research protocol. The overview lists every section in groups (the project, people, data, governance, and delivery and sharing), with a tick on the ones you’ve written and a progress bar. Choose a section to open it on its own page.
The first draft
The starting point you chose when creating the project writes a first draft. It picks the sections that fit, fills in starter text such as the aims and design, and adds indicator rows. A training evaluation, for example, starts with questions at each level of training evaluation and indicators for attendance, usefulness, change in confidence and use at work. Projects created before protocols existed show a draft based on their starting point, which is saved the first time someone edits it.
The starter text is a starting point. Rewrite it for your project.
Writing each section
Every section says why it matters and lists what to cover. Write your answer in the box under it and choose Save. The list on the left shows every section with a tick on the ones you’ve written, and the buttons at the bottom take you to the previous and next sections.
Some sections show tables the project fills in itself:
- Who answers what, and when and Data collection list the project’s surveys, with each survey’s description of when it goes out.
- Team and responsibilities lists the project’s team and their roles.
- Type of project and approvals has a link to the HRA decision tool and fields to record its answer, the date you checked, who approved or registered the project, the reference and the approval date. Research and service evaluation templates suggest the likely answer, but only the tool can confirm it. A research project without an approval reference shows a reminder.
- Data management and protection summarises what the project already knows: which fields identify people, which are special category data, the minimum group size for results, and where the team list and data protection impact assessment are. Write the lawful basis and how long you keep data underneath.
- What you’ll measure is an indicator table: the indicator, its definition, where the data comes from, a baseline, a target, how often it’s measured and who is responsible. Add, change or remove rows, then choose Save indicators.
Use Add a section on the overview to bring in any section the starting point left out, and Remove this section from the protocol at the bottom of a section to take it out.
Recruitment, outreach and promotion
Most projects struggle to reach enough people rather than to design the questions, so this section works as an exercise. It asks you to describe the people you need to hear from, where they already spend time, who they trust, the one-line message you’ll lead with and what’s in it for them. It then asks which channels you’ll use, when each goes out and who is responsible, how you’ll make taking part easy, and what you’ll do if numbers are low. Give each channel its own link so you can see which one works.
Approving a version
When the plan is ready, and before you start collecting data, choose Approve version at the top of the protocol. That freezes a copy of the protocol with your name and the date, numbered from 1. Older versions stay available to read from Versions and changes, next to it.
You can keep editing after approving. Once a version is approved, every change asks why it was made, and the change log records who changed which section, when and why. After responses have started coming in, changes are marked as deviations from the approved plan, so anyone reading it can tell planned choices from later ones. Versions and changes lists the latest 100 changes, and each approved version keeps its full text.
Owners and admins can edit the protocol and approve versions. The rest of the team can read it. Print gives a clean copy to share or attach to an application.
The setup checklist on the dashboard counts the protocol as done once a version is approved.