Responsible systems

Collect the fields the purpose actually needs

Editorial edition · 16 November 2026

The idea

An analysis often begins with a convenient export containing more fields than the task requires. Reducing that input simplifies handling and limits exposure. The question is not only whether a field can be collected, but whether it changes the intended result.

Design choice

List required fields before requesting a source extract. Replace direct identifiers with suitable task-specific references when possible. Remember that aggregation or pseudonyms do not automatically eliminate every identification risk.

Worked example

A workload analysis needs time, category and duration, but not message bodies. The extraction process omits content rather than asking every downstream analyst to ignore it.

Before you ship

  • Justify every collected field
  • Minimise at the extraction boundary
  • Review residual identification risks

Examples are illustrative. Adapt the checks to your own environment.

Further reading

W3C provenance overview

Search the library