UX and research · Beginner · 14 min
Get informed consent and store research data safely
By Padding · Updated 18 Nov 2026
Any document editor, a shared drive with per-folder access controls and a calendar · November 2026
You will have a plain-language consent form for one study and a data-handling checklist that says what you record, where it lives, who can see it and when it is deleted.
On this page
Consent in user research is not a signature collected before the interesting part starts. It is the participant understanding what will happen to them and to what they say, and agreeing to each part of it. A form that a lawyer would accept but a participant skims in ten seconds does not do that job.
The other half is what happens after the session. Recordings sit in downloads folders, notes get pasted into team chats, and a spreadsheet with names and phone numbers outlives the project by years. Most research data problems are not breaches. They are files nobody decided anything about.
This tutorial uses a study for Larkfield Clinic, a fictional community clinic building an appointment booking app. You will interview eight patients about how they book appointments today. Because a clinic's patients may talk about their health, the example treats everything they say as sensitive. You will end with two documents: a consent form and a data-handling checklist. Both are written for one study. Copy them for the next one rather than writing a generic version nobody reads.
This is practical guidance, not legal advice. Data protection law differs by country. Under UK and EU GDPR, health information is "special category" data; under Nigeria's Data Protection Act 2023 it is "sensitive personal data". In both, it needs more care than an email address. If your organisation has a data protection lead, show them the checklist from the last step before your first session.
Step 1 · List what you will collect and cut it down
Open a new document called "Larkfield booking study: data". Make a table with four columns: What, Why we need it, Form and Keep or cut.
List every piece of information the study will touch, from recruitment to the final report. For the Larkfield study that might be:
- name, phone number and email (to book the session)
- age range and how often they visit the clinic (to check you have a mix of people)
- an audio or video recording of the session
- your typed notes during the session
- any health conditions they mention while describing a visit
- quotes used in the findings report
For each row, write one sentence in Why we need it. If you cannot finish the sentence, cut the row. Then look at Form and choose the least revealing version that still does the job:
- An age range ("35 to 49") instead of a date of birth.
- Audio instead of video, unless you need to see the participant use a phone or a screen. For an interview about booking habits, audio is enough.
- Notes that say "mentioned a long-term condition that needs monthly visits" instead of naming the condition.
- No screen share of the participant's real health records or messages. If they want to show you something, ask them to describe it instead.
You are not trying to collect nothing. You are making sure each item has a reason a participant would find fair if they read it.
Check it worked
Your table has a reason in every Why we need it cell, at least one row marked cut or changed to a less revealing form, and a clear answer to "audio, video or notes only" for the session itself.
Step 2 · Write the consent form in plain language
Start a second document called "Larkfield booking study: consent form". Write it for someone reading on a phone in a waiting room. Short sentences, no jargon, one idea per paragraph. Aim for a single page.
Use these headings, in this order, and fill each one for your study:
- What this is. "Larkfield Clinic is designing a new way to book appointments. We would like to hear how you book appointments today."
- What you will do. "A 45-minute conversation by video call with one researcher. There are no right or wrong answers. We are testing our ideas, not you."
- What we will record. "With your permission, we will record the sound of the call. We will not record video."
- What we will not ask about. "We will not ask about your health or treatment. If you mention it, it may be on the recording until we delete it, but we will not write the details in our notes or report."
- Who will see what you say. "The research team of three people. Others at the clinic will only see a summary with no names."
- How long we keep it. "We delete the recording within 30 days of your session and your contact details when the study ends."
- Your choices. "Taking part is your choice and does not affect your care at Larkfield Clinic. You can skip any question, stop at any time, or ask us to delete what you said until [date]."
- Thank-you. State what they get and that they keep it even if they stop early.
- Contact. A named person, an email address and the date by which they will get a reply.
Item 7 matters more than usual for a clinic. A patient may worry that saying no, or saying something critical, could affect their care. Say plainly that it does not, and make sure that is true: the research team should not share who took part with clinical staff.
Fill in every bracket with a real value. "We keep data for as long as necessary" tells the participant nothing.
Check it worked
Read the form aloud. It takes under three minutes, every heading from 1 to 9 has a sentence under it, there are no unfilled brackets, and it names a real deletion period, a real withdrawal date and a real person to contact.
Step 3 · Split consent into separate choices
One "I agree" box asks the participant to accept everything or nothing. Instead, end the form with separate choices, each answered yes or no:
- I agree to take part in this conversation. (required)
- I agree to the conversation being audio recorded.
- I agree to my words being quoted in the report without my name.
- I agree to Larkfield Clinic contacting me about future research.
Only the first is required to take part. If someone says no to recording, run the session with notes only; do not quietly drop them from the study. Write that down as a rule for yourself in the data document: "No to recording means notes only. No to quotes means paraphrase only."
Below the choices, add a line for the participant's name, the date, and how consent was given (signed form, online form or spoken on the call). For remote sessions a short online form works, as long as each choice is a separate question and none is ticked in advance.
Check it worked
The form ends with four separate choices, only one is marked required, none is pre-filled, and your data document has a written rule for what you do when a participant says no to recording or quotes.
Step 4 · Decide where everything lives and who can open it
Go back to the data document and add a section called Storage. Answer four questions in it.
Where does each item live? Pick one place per item and write it down. For example: contact details in one restricted spreadsheet; recordings and notes in one restricted study folder on the work drive. Not personal laptops, not phone voice memo apps, not chat threads. If your video call tool saves recordings to its own cloud by default, write down how and when you move them to the study folder and delete the original. Completed consent records count too: a signed form or an online form response links a name to that person's choices, so it lives in the same restricted place as the code-to-name sheet. If you collect consent with an online form tool, its responses sit in that tool's own cloud, so export each response to that restricted place after the session and delete it from the tool.
How do you separate names from what people said? Give each participant a code: P01, P02 and so on. Name files and notes by code only ("P03 recording", "P03 notes"). Keep the one sheet that links codes to names and contact details in a separate file with its own, smaller access list. Anyone reading the notes then sees what was said but not who said it.
Who can open what? Write the access list as names, not teams:
- Code-to-name sheet: lead researcher only
- Completed consent records (signed forms or exported form responses): lead researcher only, stored with the code-to-name sheet
- Recordings: lead researcher and note-taker
- Notes by code: the research team of three
- Findings summary: anyone at Larkfield Clinic
Then set the folder permissions to match. Check that the folder is not shared by link with "anyone who has the link".
What leaves the folder? Quotes in a report, clips in a presentation and screenshots in a design file are copies. Write a rule for them: quotes are by code only, no clips of voices without the quote permission, and nothing from a session is pasted into chat. If you plan to run recordings through a transcription or AI summarising service, list it here and check with your data protection lead whether it is approved for health-related data before you use it.
Check it worked
Open the study folder's sharing settings and compare them with your access list: the names match, there is no public link, and the code-to-name sheet and completed consent records are in a separate place that only the lead researcher can open, with no responses left in the form tool.
Step 5 · Set deletion dates and a withdrawal process
Data you have not decided to delete stays forever. Add a section called Deletion to the data document, with a date for each item:
- Recordings: 30 days after each session, once notes are checked against them.
- Code-to-name sheet and contact details: on the day the study closes, unless the participant agreed to future contact. In that case, move only their name and contact details to your research contact list.
- Completed consent records: kept, lead researcher only, for as long as you keep any notes or quotes from that participant, so you can show what they agreed to. Delete them when those notes are deleted at the end-of-project review.
- Notes by code: kept with the project files for as long as the project runs. Review them when it ends.
- Findings summary: kept. It contains no names.
Put each deletion as an event in your calendar, with the folder path in the description, so it does not depend on anyone remembering.
Then write the withdrawal process, the steps you follow if a participant emails to say "please delete what I said":
- Find their code in the code-to-name sheet.
- Delete the recording and notes for that code.
- Remove any quote from that code in draft reports.
- Reply to confirm, within the time your form promised.
- Delete their row from the code-to-name sheet and their completed consent record last, once nothing from them is left to account for.
Say on the form that withdrawal is possible until a fixed date, for example two weeks before the report goes out. After that, their words may already be part of a combined finding that cannot be separated out.
Check it worked
Your calendar shows a deletion event for each recording and one for the end of the study, each with the folder path, and the data document has a five-step withdrawal process whose deadline matches the date on the consent form.
Step 6 · Test the form and plan the consent moment
Give the form to one person outside the project, ideally someone who matches your participants. Ask them to read it, then answer three questions without looking: "What will be recorded?", "Who will see it?" and "How do you stop?" Any question they cannot answer points to a paragraph to rewrite.
Then plan when consent happens in the study:
- Before the session. Send the form with the booking confirmation, at least a day ahead, so nobody reads it for the first time under pressure.
- At the start of the session. Note in your interview guide that consent is summarised and confirmed before any questions, and that the participant's yes to recording is captured on the recording. How to run that moment is covered in Run your first user interview.
- When it gets personal. Add a line to your interview guide: if a participant starts describing their health in detail, remind them they do not need to share that and steer back to booking.
- At the end. Add a reminder to the guide's closing section of how to withdraw and by when.
Check it worked
Your test reader answered all three questions correctly, or you changed the paragraphs they missed and tested again. Your interview guide now has a note at the top to summarise and confirm consent, a line on steering away from health details, and a withdrawal reminder at the end.
Step 7 · Assemble the checklist for this study
Turn the data document into a checklist you can tick off during the study (strike through or mark each line as you go). Put it at the top of the document, above everything else:
Before the first session
- Consent form tested on one outside reader
- Study folder created, permissions match the access list, no public link
- Code-to-name sheet and a place for completed consent records set up, lead researcher only
- Deletion dates in the calendar
- Data protection lead has seen this document (or there is no such role, noted here)
For each session
- Form sent a day ahead, choices recorded
- Completed consent record stored with the code-to-name sheet; any online form response exported and deleted from the form tool
- Consent summarised and confirmed on the recording
- Recording moved to the study folder and the call tool's copy deleted the same day
- Notes saved by code only
When the study closes
- All recordings deleted
- Code-to-name sheet deleted, future-contact details moved
- Completed consent records kept, lead researcher only, until the end-of-project review of notes
- Report checked: no names, quotes only from people who agreed
Keep the blank consent form and this checklist together in the study folder. Completed forms stay in the lead researcher's restricted place, not here. At the end of the study, the ticked checklist is your record of what happened to every participant's data.
Check it worked
You have two finished documents in the study folder: a blank one-page consent form with nine headings and four separate choices, and a data document whose checklist, access list and deletion dates all agree with each other and with the form. No completed consent form or form response is in the shared study folder.
Next steps
With consent and data handling sorted, you can recruit and run sessions knowing what happens to everything you collect.
- Find and screen the right people with Recruit participants for user research.
- Run the session itself with Run your first user interview.
- Put this study in context with Write a one-page research plan.
Part of these paths
Related tutorials
- Recruit participants for user researchYou will have a one-page recruitment plan, a private scheduling sheet and a first round of research sessions booked with the right people, including a spare for the person who does not turn up.
- Run your first user interviewYou will run a 45-minute one-to-one interview with a note-taker beside you and finish with a recording, a page of structured notes and a five-line debrief written within the hour.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials