Capturing event learnings with participant permission

Decide what you need to keep before asking anyone to share. Tell participants whether you will take notes, record, quote them or share a summary, and seek permission for each optional use. Attending a discussion does not by itself establish agreement to publish an identifiable comment elsewhere.

Choose the least detailed record that serves the purpose

Start with the intended reader. A summary recipient may need the question, the approaches discussed and the unresolved points. They may not need a recording, transcript or list of speakers. A team reviewing an event may need a private note about what to improve, though that does not make the note suitable for wider release.

Separate four possible outputs: a private organiser note, an unnamed summary, an attributed quote and a recording. Each has a different audience and level of identifiability. An unnamed summary may still identify someone through a distinctive role or incident. Name who prepares each output, where it is kept and when it should be reviewed or removed under the organisation’s retention arrangements.

Explain the plan before discussion starts

In the invitation, state what will be captured, why, who receives it and whether someone can take part without agreeing to an optional recording or quote. Repeat the practical rule at the start. If the plan changes, pause and seek agreement before collecting or using material for the new purpose.

For an unrecorded event where a short member summary is planned, an invitation could say: “We will take notes on themes and open questions for a short member summary. We will not name speakers in it. We will ask separately before using an identifiable quote. We are not recording this session.”

For an organisation covered by the Australian Privacy Principles, collection notices and later uses of personal information need attention to the applicable rules. OAIC guidance says an APP entity may use or disclose personal information for the purpose it was collected, or for a secondary purpose if an exception applies; consent is one such exception. Other exceptions may also permit secondary use or disclosure. The organisation must assess its own coverage, collection and proposed use.

Australian Privacy Principles (APP) Guidance Highlights

Capture ideas without changing their meaning

Write the original question and the circumstances behind each useful account. Note where participants differed and which points were unresolved. Do not turn one member’s experience into a recommendation for everyone. Mark a product or policy claim for verification by the responsible owner before presenting it as official guidance.

Minimise identifying details in working notes. A job title, customer situation or unusual incident may identify someone even when their name is omitted. If an example depends on those details, ask the participant whether it may be shared in the proposed form. If permission is uncertain, generalise the point without the distinctive detail, or leave it out.

Review the draft against the stated arrangement

Before release, compare the proposed summary with what participants were told. Check names, quotes, recordings, screenshots and details that could identify a speaker. Ask the relevant person to approve an attributed quote and its context. Give participants a way to flag a mistaken paraphrase when a summary is shared with them.

If someone declines attribution, keep their contribution out of an attributed output. Control access to any recording or transcript separately from the summary.

For an organisation to which APP 11 applies, OAIC guidance requires reasonable steps to protect personal information it holds and, subject to exceptions, to destroy or de-identify it when no longer needed for a permitted purpose. Retention and access arrangements depend on the organisation’s circumstances and other applicable duties.

Share only a version that fits the stated audience and handling arrangement.