Agree when automated meeting notes may be used

What this means for your practice

Set the permitted use and information-handling arrangements before enabling capture. Explain the workflow to participants through the organisation's approved process and keep sensitive content appropriately controlled.

A practical conversation with your supplier

Rehearse a meeting outside the agreed scope and confirm capture is not assumed. For an allowed meeting, inspect access and the participant explanation used through your approved process. The supplier should demonstrate the settings, while the organisation decides the authorised purpose and information handling.

Plan the first improvement

List the kinds of meetings the organisation wants help documenting and identify who decides whether each is suitable. A routine project meeting and a discussion involving more sensitive information may need different arrangements. The responsible team should determine authorised use, participant communication, access and handling before the tool is enabled. Ask the supplier to demonstrate how those decisions appear in the actual workflow rather than rely on assumptions about default settings. Name the owner of the resulting record and clarify whether generated notes are a draft awaiting review.

Decide how participants can raise a correction through the agreed process. Include a meeting that falls outside the approved scope in the rehearsal, because staff need a clear way to stop or decline capture as well as start it. Review exceptions with the responsible owner. The objective is useful administration with understood boundaries, not collecting a record of every conversation simply because the software makes it possible.

How to check the result

Track notes created without a clear authorised purpose.