Product & Project Delivery
Plan Research Consent and Recording Before a Customer Session
Prepare a complete customer research information sheet and a linked permissions and storage record. Distinguish notes, optional audio, observers and later reuse, with a worked changed-consent case that keeps deletion confirmation separate from a stopped recording.
Before a customer research session, explain what participation involves and record the person's specific choices about notes, recording, observers, use, and retention. Verify that the session's tools and attendees match those choices before collecting research data. If the arrangement changes, pause and clarify it. Accepting a calendar invitation does not establish agreement to recording or later reuse. A recording indicator alone does not supply that agreement either.
This LandOffer.ai guide uses official research guidance checked October 27, 2026 and two completed fictional handling cases. It is an operational planning example, not a legally approved consent form. Your research and privacy owners must confirm the applicable organizational and regional requirements. No participant was contacted, session conducted, recording made, or account setting changed for this article.

Resolve the operating arrangement before writing the invitation
Start with the research question and the smallest information needed to answer it. Then decide who must attend, which materials will be used, where records will go, and who can retrieve or delete them. Writing “we respect your privacy” cannot resolve an unspecified recording destination or an observer list that changes without notice.
GOV.UK's informed-consent guidance describes explaining the researcher, purpose, activities, data, recipients, voluntariness, retention, and observation or recording arrangements. It recommends an understandable information sheet before the session and organizational privacy or legal review. This is guidance for its government-service context; its legal framing does not establish the rules for every private employer or participant location.
Separate participation from individual collection methods. A person may be comfortable describing a task while declining audio, screen capture, or a particular observer. Offer a genuinely workable alternative where the study permits it. If the research cannot proceed within their choices, explain that and end or reschedule rather than quietly changing the method.
Assign an owner to the tools as well as the paperwork. Meeting recording, local recording, transcription, an AI assistant, and screen capture may create different records or involve different processors. An approved meeting platform does not by itself approve each optional feature. Confirm the actual configuration through your organization's process before inviting participants.
Worked asset: a complete invitation and information sheet
The following example belongs to fictional Reedline Services. Researcher Daphne is studying how customers identify the responsible team for an equipment-service request. Malik will take notes. Designer Noor is a proposed additional observer, and privacy owner Etta reviews the information and handling plan. All people, approvals, choices, dates, and storage arrangements here are invented.
Daphne prepares this invitation for participant P-04:
We would like to understand how you decide who should handle an equipment-service request. The proposed session is November 13, 2026, at 14:00 UTC for 30 minutes: five minutes to review participation choices, twenty minutes discussing a fictional request example, and five minutes to close. We are evaluating the workflow, not your performance. Please do not open customer records, account details, or confidential documents. Participation is optional, and you may skip a question or stop.
I will facilitate, and Malik will take limited task notes. Noor would like to observe only if you agree. Audio recording is optional; no video, screen recording, transcription service, or AI note-taking assistant is planned. We can run this study with notes alone. Please read information sheet RS-12 version 1.2 and tell us which arrangements you accept before we begin.
The accompanying completed information sheet makes the invitation's boundaries usable:
| Information field | Filled fictional arrangement |
|---|---|
| Responsible organization and contact | Reedline Services; Daphne at research@example.com for participation questions, routed to Etta for data requests. This is an example address, not a live contact |
| Purpose and activities | Understand responsibility-finding in a service request, using researcher-created mock material; no real account access |
| Collection choices | Limited notes required for this particular study; audio optional. No camera, screen capture, AI assistant, or external transcription |
| People and access | Daphne and Malik handle raw records. Noor may observe only with separate agreement. Project colleagues receive reviewed task findings, not raw recordings |
| Use | Internal design research for this request workflow; no marketing, sales demonstration, employee assessment, or public clips |
| Storage and routine retention | Approved restricted research workspace. Notes and any permitted audio deleted by December 13, 2026; ordinary consent evidence retained until February 11, 2027 |
| Choices and contact afterward | Skip questions, pause, stop, or revise participation choices. Contact Daphne with study RS-12 and participant code; Etta handles linked-record requests under the approved process |
These dates are stipulated example policy: 30 days for raw records and 90 days for ordinary consent evidence after November 13. They are not universal legal retention periods. Before using a real version, confirm backups, processors, deletion procedures, complaint routes, and any permitted retention exceptions, then describe them accurately. Do not promise a deadline your systems cannot meet.
In the fictional response, P-04 agrees to participate with Daphne and Malik, accepts notes, and declines audio and Noor's observation. Daphne records the date, sheet version, method of confirmation, and separate choices. In the written plan, Noor is excluded from the session and no recording or assistant feature is authorized. The real meeting setup would still need to be checked. An empty checkbox is not converted into agreement.
The completed disposition is notes-only session with the two named researchers, subject to the opening check. P-04 has not agreed to every future study, a sales testimonial, or use of identifiable quotes in a public presentation. The example stops short of inventing findings from the session.
Confirm the plan without recording first to obtain permission
At the opening, Daphne states who is present and reads back P-04's choices. She asks whether the person has questions and whether the notes-only arrangement still works. If an unexpected attendee appears, she pauses rather than taking notes while negotiating their presence.
The consent guidance describes several ways to retain confirmation, including remote correspondence and verbal evidence. Choose an approved method that matches the person's accessibility needs and recording choices. In this case, written confirmation is already planned; starting an unwanted audio recording merely to capture consent would contradict P-04's choice.
GOV.UK's notes-and-recording guide says notes and recordings can contain personal data, calls for consent before collection, and limits use to the agreed purpose. It also discusses observers' records. A notetaker's private scratch file can create another copy to manage even when the official recording is off. Without a record of that copy, the team could miss it when responding to a later withdrawal.
Daphne's opening checklist names the meeting service's recording state, local capture, transcription, assistants, and attendees. These are checks to perform in the actual approved environment, not controls we tested. If the host cannot establish what an automatic recorder or processor is doing, the safe operating decision is to pause collection until the responsible owner resolves it.
Worked asset: a filled permissions and storage record
The second asset turns the information sheet into a handling record. Its filenames and permissions are fictional design records; no restricted folder or actual participant file was created. P-04's code links the records, but does not make them anonymous.
| Record and purpose | Access and destination | Retention, owner, and present decision |
|---|---|---|
| RS-12/P-04 confirmation, linked to sheet v1.2 | Daphne and Etta in the restricted consent area; Malik receives only the choices needed for the session | Daphne records notes yes, audio no, Noor no. Routine evidence deadline February 11, 2027 |
| RS-12/P-04 task notes | Daphne and Malik in the restricted research area; no open project channel | Malik labels observations separately from interpretation. Delete by December 13, 2026 unless withdrawn earlier under the approved process |
| P-04 audio, screen, transcript, or AI summary | No destination authorized because these records are not authorized | Do not create. A convenient export location does not supply permission |
| Internal findings draft | Daphne and Malik review before the named project group receives it | Remove identifying details and keep each included point within the agreed purpose; public reuse remains outside scope |
| Link between participant contact and code | Daphne and Etta only, separate from the general analysis view | Etta can locate linked records for requests; protect the linkage rather than calling a code anonymous |
This record resolves who can handle which material. It does not establish that a chosen storage product enforces those permissions. The real setup still needs its approved access check, export restrictions where applicable, and a way to find copies on researchers' devices or in processor systems.
GOV.UK's research-data management guide recommends collecting only necessary information, approved storage and devices, restricted access, an agreed retention period, and naming that allows participant records to be located. Its suggested retention examples are not copied into Reedline's fictional schedule. Choosing a shorter number alone also would not prove compliance.
Malik's handling decision is to write directly into the approved notes record, not a personal notebook app that synchronizes elsewhere. If an approved temporary local copy is necessary, its transfer and removal need an owner and evidence. “Uploaded” and “local copy removed” are separate states; neither should be checked complete because the other happened.

Work through changed consent before the first real session
A second fictional participant, P-05, initially accepts notes and audio under the same information-sheet version, with Daphne and Malik present. At minute eight, P-05 says they want the recording stopped. Daphne pauses collection and asks whether the person wants to stop the study entirely or continue with notes only, without pressing for a reason.
P-05 chooses notes only and asks for the earlier audio to be removed. The filled change record reads: audio permission withdrawn at minute eight; notes permission reconfirmed before continuing; no screen, transcript, assistant, or additional observer authorized. Malik marks the change in the session record, and Etta owns removal of the linked audio and any permitted temporary copies. A stopped recorder is not proof that earlier audio was deleted.
On November 14, P-05 withdraws the remaining research participation. In this fictional process, Daphne halts further use and identifies P-05's notes, audio-removal record, and any traceable findings draft. Etta coordinates removal of the linked research material and P-05's original consent record, checks with Malik for additional copies, and retains only the minimum withdrawal correspondence permitted by the example's reviewed policy until February 11. No actual deletion or participant confirmation occurred here.
The Department for Education's withdrawal guidance provides a concrete department-specific example: involve research operations, locate linked material and other copies, and distinguish identifiable data from genuinely anonymized information. Its own correspondence-retention arrangement is not a rule for Reedline or your organization. Do not anonymize newly withdrawn raw data merely as a workaround for keeping it.
Reedline's review outcome remains pending confirmation of removal, not “all deleted.” Etta must check the applicable system and processor procedures before reporting completion. If a real request meets an unclear retention obligation or material that can no longer be linked to a person, the privacy owner must determine and explain the appropriate response. Avoid promising unlimited recall of every derivative.
Leave a usable plan, not a reassuring sentence
Before a real session, compare the information-sheet version, confirmed choices, attendee list, collection settings, destinations, access owners, and retention dates. Provide an accessible way to ask questions, and offer a pause or a new appointment if the person needs time to consider the arrangement. If any collection method or recipient lacks agreement, resolve that gap before using it. A clear record lets the participant and team refer to the same arrangement afterward.
Keep the participant's choices attached to the materials throughout analysis and sharing. A later request for a clip, transcript, or wider audience is a new scope question, not automatic permission from the original meeting. Revisit the approved arrangement with the responsible owners rather than silently expanding it.
Save the filled invitation, confirmation record, handling map, and changed-consent route before collecting customer data. More workplace guidance is available through LandOffer.ai. The next action is to have your research and privacy owners review those concrete arrangements, then make the actual session match what the participant agreed to.
Sources and Further Reading
- GOV.UK: Getting informed consent for user research — updated November 5, 2018; current body checked October 27, 2026.
- GOV.UK: Taking notes and recording research sessions — updated September 19, 2017; current body checked October 27, 2026.
- GOV.UK: Managing research data and participant privacy — current primary guidance checked October 27, 2026.
- Department for Education: Handling withdrawal of consent — department-specific procedure checked October 27, 2026.


