Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Research › Research Methods

Participant Information and Consent for Research

How to prepare participant information and consent for a research study: what people are told, how consent is recorded, incentives, withdrawal and deletion.
Tutorialintermediate13 min readUpdated

The professional codes the site's research guides describe from the MRS and ESOMAR share a few principles: participation is voluntary and informed; people are told who is collecting the data and why; answers are confidential unless people agree otherwise; research is never a pretext for selling, list-building or collecting debt; and children and vulnerable adults get extra care. The methods hub sets these out, and they apply whether or not a business belongs to either body. Each one turns into something written: information that makes participation informed, a statement that makes it voluntary, a promise of confidentiality that the team must then keep.

Data protection law adds legal duties wherever a study holds Personal Data, which, as the personal data glossary entry explains, includes recordings, contact details and free-text answers that identify someone. The GDPR glossary entry lists the principles: lawfulness, fairness and transparency, purpose limitation, data minimisation, accuracy, storage limitation and security, with the controller able to show that it complies. That last point is why consent is recorded and not merely obtained: a business that cannot show what a participant was told and agreed to is in a weak position whatever actually happened.

Two things follow for the people running a study. The decisions about lawful basis, retention and the exact wording belong to whoever owns data protection in the business, not to the researcher or to this page. And the researcher's job is to make those decisions possible, by setting out clearly what the study will do with what people say. The research design guide and the research brief template give consent, incentives, data handling and retention a field of their own; this tutorial fills it in.

Before you start

Have the research brief: the decision, the method, the audience and what will be delivered. Consent depends on all of them, because a diary study, a recorded home visit and an anonymous survey ask different things of people. For a survey, the guide to anonymous, confidential or attributable surveys settles which promise about names the invitation makes before this tutorial's documents are drafted.

Find out who owns data protection, and agree who does what using a RACI matrix as its page describes: one accountable role for each decision, here the lawful basis, the retention period, the final wording and the sign-off, with the researcher responsible for drafting and the study sponsor consulted. Write the rows down before drafting anything, so nobody assumes someone else approved the wording.

Check whether the study involves anyone who needs extra care, such as children or vulnerable adults, or any sensitive topic, such as health. The survey design guide notes that sensitive topics need extra care and, often, explicit consent. This page goes no further than that; such studies need advice from whoever owns data protection before they are designed. Outside research, the same care for people in difficult situations is a service question, which the guide to supporting customers in vulnerable circumstances takes through for support teams.

Gather what already exists: the business's privacy notice, any research consent wording used before, and the recruitment tutorial's recruitment log, which is where consent records for sessions usually live.

The steps

  1. List every use the study will make of what people say

    Write down every way the study will use what participants say, show or do, because each use is something people must be told about and some need their own agreement. The usual list: taking part at all; audio or video recording; transcription; notes; quotes in reports; clips shown to staff, internally or in training; sharing with a supplier who transcribes, analyses or hosts the material; sending transcripts to an AI tool, which the AI research synthesis guide treats as a use participants must have been told about; re-contact for future studies; and keeping material in a research library after the study ends. A use left off the list is a use the study cannot later make.

  2. Agree the basis and the retention with whoever owns data protection

    Take the list to whoever owns data protection. Under the GDPR, as the lawful basis glossary entry explains, each purpose needs a lawful basis chosen before the processing starts and recorded beside it; consent is one possible basis, not the only one. Leave the choice to that person and write down what they decide for each use. Agree at the same time how long each kind of material will be kept, under the storage limitation principle: recordings, transcripts, notes, the recruitment log and the consent records may each have a different period. Agree, too, whether any supplier will process the material on the business's behalf, because the GDPR glossary entry notes that such a supplier is a processor.

  3. Write the participant information in plain words

    The participant information tells people what they are agreeing to before they agree. Write it for the participant, not the lawyer: short sentences, everyday words, the most important points first. It says who is running the study and for whom, what the study is for in general terms, what taking part involves and how long it takes, what will be recorded, who will see or hear it, how it will be used, how long it will be kept, the incentive, that taking part is voluntary, how to withdraw and what withdrawal removes, and who to contact with questions. Keep the topic general enough not to prime the answers, as the recruitment tutorial advises for invitations. The table in the next section lists what it covers and why.

  4. Write one consent statement for each use

    Where consent is the basis, or where the research principle of informed, voluntary participation calls for an explicit choice, give each use its own statement that people can agree to separately: to take part; to be recorded; to be quoted anonymously in reports; to have clips shown to staff; to be contacted about future research. The GDPR, as the lawful basis entry summarises it, describes consent as freely given, specific, informed and unambiguous, and as easy to withdraw as to give, which a single bundled agreement struggles to meet. As general practice, taking part should not depend on agreeing to optional uses such as clips or re-contact. Never add marketing to the list: the survey design guide rules out marketing follow-up from research without separate agreement, and the study is not a way to build a marketing list.

  5. Decide how consent is captured and where the record lives

    Choose how each person gives consent: a signed or ticked form before the session, a step at the start of an online survey, or a confirmation read aloud and recorded at the start of an interview, as the customer interviews tutorial does before recording starts. Then decide where the record lives. The list building and consent guide describes the record that makes email consent defensible: the source, the time, the wording the person saw and the choices they made. The same idea serves research. Keep the record with the participant code in the recruitment log, not in the findings, and keep the version of the wording each person saw. Access to the recruitment log is limited to the people running recruitment, which is why consent records belong there. Where the study runs on the live site, consent to analytics tracking is a separate matter covered by the privacy and consent guide.

  6. Set the incentive terms

    Write down what the incentive is, when and how it is paid, and what happens if someone leaves part-way through or turns out not to fit the study. The customer research hub's framing applies: an incentive compensates people for their time in a form that does not bias the result, such as a voucher or a charity donation, rather than a discount on the product being researched. State the terms in the participant information so nobody takes part on a misunderstanding, and pay people who withdraw or are released at the start of a session in the same way as everyone else, as the recruitment tutorial does. This page gives no amounts or tax treatment; those are for the business to settle.

  7. Prepare for withdrawal and questions

    Decide, before fieldwork, how a withdrawal is handled: who receives it, how fast, what is removed (recordings, notes, quotes, clips, the consent record of the optional uses) and from where, including any supplier or shared drive. Decide what cannot be removed, such as findings already reported in aggregate, and say so in the participant information. Name a contact for questions who can answer them, not a general inbox nobody reads. Brief everyone who will meet participants on what to say if someone hesitates or asks to stop: thank them, stop, and record the request. Withdrawing must be as easy as agreeing.

  8. Separate identities from answers and set the deletion date

    Give every participant a code and use it in notes, transcripts, coding sheets and findings, keeping the key that links codes to names in a restricted place, as the customer interviews tutorial's checklist and the AI synthesis guide both describe. Collect only what the study needs, which is the data minimisation principle in practice. Write the deletion date agreed with the data protection owner beside each kind of material, name who deletes it, and put a reminder in a calendar that will still exist when the date arrives. If material is to be kept beyond the study in a research library, that use must have been on the list, in the information and, where needed, in the consent.

  9. Check everything before the first invitation

    Before recruitment starts, read the documents side by side and check that they agree: every use on the list appears in the information; every optional use has its own statement; the deletion dates in the information match what was agreed and what the storage can actually do; the invitation promotes nothing, because, as the marketing research hub notes, an invitation that promotes a product is marketing whatever its subject line says, and the comparison of promotional and transactional email shows purpose deciding what a message is. Get sign-off from the accountable role in the RACI rows, and store the signed-off versions with the brief. For moderated sessions, the research session readiness checklist then checks these documents again alongside the recruits, materials and recording set-up before the first participant arrives.

What participant information covers

Participant information answers the questions a careful participant would ask before agreeing. The table lists what it usually covers and the principle each item serves. The wording itself is for whoever owns data protection to approve; nothing here is presented as compliant wording.

ItemWhat it tells participantsPrinciple it serves
Who is askingThe business running the study, and any supplier involvedParticipants know who is collecting the data and why
What the study is forThe purpose in general terms, without priming the answersInformed participation; purpose limitation
What taking part involvesThe activity, its length, where it happens and who will be presentInformed participation
What is recorded and howAudio, video, screen, notes or written answersTransparency
Who sees or hears itThe research team, colleagues, suppliers, any AI toolConfidentiality unless people agree otherwise
How it is usedAnalysis, anonymous quotes, clips for staff, a research libraryPurpose limitation; specific consent for each optional use
How long it is keptThe deletion date or event for each kind of materialStorage limitation
The incentiveWhat it is, when it is paid, what happens if someone stopsFairness; no hidden conditions
That it is voluntaryTaking part is optional, and optional uses are separateVoluntary participation; consent freely given
How to withdrawWho to tell, what is removed, what cannot beWithdrawal as easy as agreement
That it is not sellingNo sales contact follows from taking partResearch is never a pretext for selling
Who to contactA named person or role who can answer questionsTransparency

Consent and data handling are only part of the design. The research design guide places them in the brief beside the method and the sample, and the methods hub collects the wider ethics and data protection direction they come from.

Illustrative example — not a real result

Plimsavo Footwear prepares consent for recorded home visits

Plimsavo Footwear, an invented walking-shoe retailer, plans 10 recorded home visits with customers who returned a pair within the last 2 months, to see how people break in and judge walking shoes. The research lead lists the uses: taking part, video recording, transcripts, anonymous quotes in the report, short clips in a staff training session on fitting advice, and re-contact for a follow-up study.

The first draft has one consent box covering everything. The data protection owner asks for separate statements, and the final form has 5: taking part, recording, quotes, clips in staff training and re-contact. Taking part does not depend on any of the others. The draft information also promised that "all recordings are deleted 3 months after the study"; checking the storage shows the video files are copied automatically to a shared drive with no deletion process. The team moves the files to a restricted folder, names the research lead as responsible for deletion with a calendar reminder, and changes the information to match what the process can actually do.

Of the 10 participants, 8 agree to clips in training and 6 to re-contact. The incentive is a £40 voucher, paid whether or not the visit finishes. A week after her visit, one participant emails to withdraw. The research lead removes her video, transcript, notes and any clips from the analysis folder and the training draft before analysis starts, marks her code as withdrawn in the recruitment log, keeps the record of the withdrawal, and confirms by email that it is done. The report states that 9 visits were analysed.

Verify it worked

  • Compare the use list from the first step with the participant information. Every use appears in both, and nothing appears in only one.
  • Read the consent form. Each optional use has its own statement, and taking part does not depend on any of them.
  • Open the recruitment log. A test entry shows the participant code, the wording version seen and each choice. Notes and transcripts show codes, not names.
  • Read the deletion date beside each kind of material. A named person owns it, a reminder exists and the storage can delete the files.

If it goes wrong

  • The information and the consent form disagree. The form was probably drafted without the use list beside it. Read them side by side again and get sign-off again from the accountable role.
  • Recordings sit somewhere with no deletion process. The promise was written before anyone checked the storage. Move the files to a restricted folder, name who deletes them and change the information to match.
  • A participant asks to withdraw and nobody knows who handles it. The withdrawal plan was never written. Thank them, stop, record the request, then agree what is removed and from where.
  • The lawful basis or retention is still undecided. These choices belong to whoever owns data protection. Take the use list back to them and hold the first invitation until they decide.

Next steps

Common mistakes

  • One box for everything. A single agreement to taking part, recording, clips and re-contact is neither specific nor freely given for the optional uses.
  • The researcher choosing the lawful basis. The basis, the retention and the final wording belong to whoever owns data protection.
  • Uses nobody listed. Sending transcripts to an AI tool or showing clips to staff when participants were told the material stayed with the research team.
  • Deletion promises with no process. A date in the information that nothing and nobody will act on.
  • Consent kept with the findings. Names and signed forms belong in the restricted recruitment log, linked by participant code.
  • Withdrawal that is hard. No named contact, no plan for what is removed, and no honesty about what cannot be.
  • Incentives that bias or bind. A product discount as the incentive, or payment withheld from people who stop part-way through.
  • An invitation that sells. A research invitation carrying an offer is marketing, whatever its subject line says.
  • Checking after fieldwork starts. Documents that disagree with each other, found once participants have already signed them.

Frequently asked questions

Is consent always the lawful basis for research?

Not necessarily, and the choice is not the researcher's to make. Under the GDPR every purpose needs a lawful basis chosen before processing starts, and consent is only one of the bases the regulation lists. Whoever owns data protection in the business decides which applies to each use the study makes of personal data. What does not change is the research principle the site's guides describe from the MRS and ESOMAR codes: participation is voluntary and informed, whatever the legal basis for handling the data.

How long can we keep research recordings?

No longer than the purpose needs, which is the GDPR's storage limitation principle; the actual period is a decision for whoever owns data protection, and this page gives none. What the study team can do is make the period real: write the deletion date into the participant information, the recruitment log and the place the recordings are stored, decide who deletes them, and check that it happened. A promise of deletion with no process behind it is worse than no promise.

What happens if someone withdraws after their interview has been analysed?

Decide that before fieldwork and say it in the participant information. As general practice, a withdrawal removes the person's recordings, notes and quotes from everything still being worked on and from any future use, and stops any further contact. Findings already reported in aggregate, where the person cannot be identified, usually cannot be unpicked, and the information should say so honestly rather than promise what the team cannot do. Agree the wording with whoever owns data protection.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Market Research Society — MRS
  2. ESOMAR — ESOMAR
  3. Regulation (EU) 2016/679 (GDPR) — EUR-Lex
  4. Direct marketing guidance — Information Commissioner's Office (UK)

Related