Collect only what the purpose needs
See this course’s project requirements
Assemble the fictional equipment register and its operating README from all six lessons.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Define the record schema, sample rows and quality checks.
- Document filenames, version history and the approved release.
- Justify retained fields and create a purpose-specific export.
- Specify role-based access with review and removal triggers.
- Provide a retention review schedule, hold checks and tested handoff.
Review and revise
Use these criteria to check your work and choose what to improve.
- Meaning: fields and row definitions support consistent interpretation.
- Traceability: accepted changes and the current release are identifiable.
- Proportionality: data and access match stated purposes.
- Continuity: lifecycle decisions and handoff questions are answerable.
Want more background?
The idea in everyday life
More data can create more responsibility without improving the answer. The equipment register needs to show item return status, not build profiles of attendees. You will review a proposed field list against the purpose and design a smaller useful dataset. Fictional examples make this possible without inspecting anyone’s personal documents or changing a real organization’s records.
Data minimization means keeping only the information needed for the stated task. Ask why each field is needed.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Write the narrow purpose again: identify equipment counts and recorded return status by session. Evaluate fields against that purpose rather than against vague possible future usefulness.
- 2
Review proposed additions: item condition, participant birth date, home address and session code. Item condition may support repair planning if that purpose is explicitly added; birth date and home address are unnecessary for the current task.
- 3
Mark each field keep, remove from this design, or clarify purpose. Do not collect a sensitive field just to decide later whether it might be useful.
- 4
Check adequacy as well as excess. Removing item_id would make the return register unable to identify which equipment is out. A smaller dataset still needs enough information to fulfill its function.
- 5
Create a minimized export containing only session_code, item_id, quantity and status for an authorized equipment reviewer. Record why each field remains, and keep this hypothetical export separate from real records.
See how it works.
Fictional field review: checkout_id distinguishes events, item_id distinguishes equipment, session_code locates the activity, quantity gives the count and status supports return follow-up. A proposed home_address field has no role in the stated purpose and is omitted before collection. Item_condition is deferred until the club defines a separate maintenance use and its responsible owner. The exercise keeps enough identifiers to avoid confusing two different checkouts while avoiding personal profiles. It also distinguishes minimization from random deletion: removing status would make the register smaller but unable to answer its core question about returned equipment.
Did you cover these?
- Home address and birth date are unnecessary for the stated purpose.
- Each retained field has a purpose.
- Minimized export still answers the equipment question.
What to finish
A field-by-field purpose review and a minimized sample export.
Watch for this
Using possible future usefulness as a blanket reason to collect personal details.
How can I tell I understand it?
Justify every retained field and identify an essential field that cannot be removed.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Read purpose-based adequacy, relevance and minimization guidance. UK-specific legal context is identified; the course teaches a practical design principle, not jurisdiction-wide legal advice.
Access: Free public reading; no account or certificate is required for this Life Starter course.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.