How to Write a Personal Data-Handling Note for an Automation

How should a small business document personal-data processing for the people who handle an automation?

Create a short data-handling note for the automation. State its purpose, the minimum personal data it uses, where that information enters the process, which types of handler need instructions, and what each handler should do when the input falls outside the approved boundary. Keep the language clear and adapt the instructions to the people who will use them.

Describe the processing activity in plain language

The European Data Protection Board says personal-data processing activities should be explained in clear language and adapted to each category of handler in documents they can refer to. Open the note with the business task, what information moves through the activity and its intended outcome, then place it within broader controls for automation. Avoid technical shorthand that a person using the workflow would not understand.

Sources: Secure personal data | Data protection guide for small business | European Data Protection Board.

  • Name the business task.
  • Describe the processing activity.
  • State the intended outcome in ordinary language.

State the minimum information the task uses

Experian UK says data minimisation requires organisations to collect, process and store only the minimum personal data required for the specific intended purpose. State the approved minimum information and its task-specific purpose, and revisit the process when the minimum required information cannot yet be defined clearly. Keep the note concise by referring to the approved boundary rather than recreating a detailed field-review worksheet.

Sources: Data Minimisation: Guide to Collect Less, Protect More - Experian UK.

  • List only the approved minimum inputs.
  • Link each input to the task.
  • Do not turn the note into a field-by-field worksheet.

Adapt instructions to each type of handler

Identify the handler types involved in the workflow, such as the people who configure it, submit records or review its output. Give each handler type a practical instruction, including who reviews exceptions and escalates unresolved cases. For each type, state the approved use, the boundary not to exceed and the action to take when an input falls outside it.

  • Identify handler types relevant to the workflow.
  • Give each type a practical instruction.
  • Pause and escalate inputs outside the boundary.

Review the note when the workflow changes

The European Data Protection Board says secure personal data is in the interests of both individuals and the organisations processing it. Review the note whenever the task, approved inputs or handler arrangements change so that the written boundary continues to match the workflow. This note is an operating document, not a privacy notice, legal opinion or guarantee that the processing meets every applicable requirement.

Sources: Secure personal data | Data protection guide for small business | European Data Protection Board.

  • Review when purpose changes.
  • Review when inputs change.
  • Review when handler arrangements change.

Plain-language, handler-specific processing note template

Use these headings to create a short operating note for one approved automation. Replace bracketed wording with the facts of the workflow and keep the instructions understandable for the people who use it.

Note headingWhat to write
Purpose and activity[Describe the business task, processing activity and intended outcome in plain language.]
Approved minimum information[State the minimum personal information used and how it supports the task.]
Where information enters[Describe the point at which the approved information enters the workflow.]
Handler instructions[For each relevant handler type, state approved use, boundary and the action for out-of-boundary inputs.]
Review trigger[Update this note when the task, inputs or handler arrangements change.]

This template documents an approved workflow boundary. It is not a privacy notice, legal opinion or statement about a platform’s security, storage or access-control behaviour.

When this is not the right approach: Do not use this note as a substitute for an assessment required for potentially high-risk processing or for advice on obligations that apply to your business. Do not use it to describe a workflow whose approved purpose and minimum inputs have not yet been decided.

What follow-up questions matter most?

How should the note begin?
State the business task, the processing activity and the intended outcome in ordinary language. The reader should be able to understand the activity without interpreting a technical configuration.
What should the note say about inputs?
State the approved minimum information and connect it to the task. Do not expand the note into a general catalogue of fields or claim that categories are always safe or prohibited.
How should instructions differ by handler?
Give instructions that match the handler's involvement, such as configuring, submitting to or reviewing the workflow. Tell handlers to pause and escalate when an input falls outside the approved boundary.

What steps does this workflow follow?

Write an automation data-handling note

  1. Describe the task: State what the automation does, the processing activity and the intended outcome in plain language.
  2. State the approved inputs: List the minimum information the approved task uses and connect each item to that purpose.
  3. Name handler types: Identify the types of people who configure, submit to, review or otherwise handle the activity.
  4. Give boundary instructions: Tell each handler what to do within the approved boundary and to pause and escalate records outside it.
  5. Review on change: Update the note when the task, approved inputs or handler arrangements change.