Workflow templates

A workflow template is a saved checklist of collection tasks that is applied automatically the moment a matching request is verified. It's the difference between "a request arrived, someone should figure out what to do" and "a request arrived and the work is already assigned".

Matching

Each template can be scoped by:

• Request type (access, erasure, and so on), or left blank to match any.
• Jurisdiction, or left blank to match any.

When a request is verified, the most specific matching template wins: a template scoped to both type and jurisdiction beats one scoped to just type, which beats a catch-all.

What a template contains

• Tasks: each names a data source. On application, the task routes to that source's current owner, whether that's a team member or a contact.
• An optional SLA in days: if it's shorter than the request's legal deadline, the request's due date is tightened to your internal target, and the tightening is recorded. A template can never loosen the legal deadline.

A sensible starting set

1. Access, any jurisdiction: one task per major data source.
2. Erasure, any jurisdiction: the same sources, with deletion confirmation expected (see Erasure requests and attestations).

Add more specific templates as patterns emerge, for example a US-scoped opt-out template touching only your marketing systems.

Manual application

If a request arrives that no template matched (or you disabled auto-application), you can apply a template by hand from the request detail page, and add ad-hoc tasks on top.