Using UCDmanager to track user research consent forms
User research produces valuable evidence, but it also creates a responsibility to record how participants agreed to take part. Consent forms, information sheets, withdrawal requests and permission for recordings should be easy for the research team to find without exposing unnecessary personal information.
UCDmanager can provide a shared structure for this work. By organising consent status alongside personas, use cases, research notes and usability findings, teams can connect ethical checks with the activities they govern rather than leaving them in disconnected spreadsheets or email threads.
For Australian teams, the process should reflect the Privacy Act and Australian Privacy Principles, as well as any organisational, health-sector or university requirements. A project involving participants in Sydney, Melbourne, Brisbane or regional communities may also need clear arrangements for remote sessions, local time zones and data access across multiple offices.
Define what consent needs to cover
Before creating records in UCDmanager, identify the activities that require permission. A moderated interview may need consent for participation, note-taking, audio recording and the use of anonymised quotations. A usability test may require separate approval for screen recording, photographs or the reuse of findings in presentations.
Consent should be specific, informed and voluntary. It should explain the project purpose, what participants will do, how long a session will take, who will see the data and how they can withdraw. For work with Aboriginal and Torres Strait Islander participants, teams should also follow appropriate community engagement and data governance protocols rather than relying on a generic form.
Create a consent register within the project
A dedicated consent record or research activity can act as the central reference point for each participant or session. Useful fields include participant code, recruitment source, study activity, consent date, consent version, approved uses, recording permission, withdrawal status and review date.
Avoid placing full names, contact details or signed forms into general project notes unless the organisation has approved that practice. A coded identifier can connect the consent record with research findings while reducing exposure of personal information. The signed document can remain in an approved document management system, with UCDmanager storing its controlled reference and current status.
Connect consent to research activities
Consent tracking becomes stronger when each interview, observation or usability test is linked to the relevant participant code and study record. This helps researchers verify that permission existed before using a quote, image, recording or behavioural observation in an analysis.
A shared workspace also reduces duplicate checks. For example, a researcher preparing a Melbourne prototype test can review whether each participant agreed to video recording, while a colleague analysing notes can see whether quotations may be used outside the internal team. The project record should make the permitted uses clear without revealing sensitive personal information.
Record decisions during sessions
Research notes often contain the practical evidence that consent conditions were followed. Note whether the participant confirmed permission at the start, declined a particular recording method or asked for a comment to be removed. These details are especially important when a session changes from the original plan.
Teams can use collaborative note-taking to capture consent-related observations while the session is underway. Use participant codes instead of names, and separate direct identifiers from the working notes. If a participant withdraws permission after the session, update the consent status and flag all affected outputs for review.
Manage access and document storage carefully
Consent information should be available to the people who need it, not automatically to everyone on a project. Establish roles for researchers, moderators, analysts, project owners and administrators. Access should reflect the sensitivity of the information and the stage of the study.
UCDmanager can serve as the coordination layer, while the original forms are held in an approved repository with suitable authentication, backups and retention controls. Organisations comparing secure hosting options should assess location, contractual protections, access logging and Australian privacy obligations rather than selecting a service based on price alone.
Monitor expiry, withdrawal and retention
Consent is not always permanent. A participant may agree to one study but not future research, or may permit internal analysis while refusing publication of quotations. Add review dates and expiry conditions to the project record so the team can identify permissions that need renewal.
Withdrawal requests should trigger a documented process. Mark the relevant consent record, identify linked notes and recordings, and record which materials were deleted, anonymised or retained for a lawful reason. Australian organisations should align this process with their privacy policy, research governance requirements and any applicable records-management schedule.
Use consent status in research reporting
Before distributing findings, filter the evidence according to each participant’s approved permissions. A quote that was acceptable for internal synthesis may not be suitable for a public case study. Likewise, a screen recording may support analysis but be excluded from a stakeholder presentation.
When results come from usability testing, connect the consent review with the reporting workflow described in usability test reports. Record the participant sample, collection dates, exclusions and permission limits alongside findings. This creates a clearer audit trail for Australian clients, regulators, ethics reviewers and internal decision-makers.
A consistent consent register makes research safer and easier to manage. UCDmanager helps teams bring participant permissions into the same collaborative environment as research planning, analysis and usability documentation, while controlled storage and careful access rules protect the underlying personal information.