Choose a limited question
Use an invented question such as how many agreed delivery activities were completed during a training week. Do not start with a real location-history export. Make a fictional table containing vehicle codes, activity categories and completion markers, with no names, addresses or actual journeys. The exercise asks which information is necessary to answer the stated question. It does not claim that every form of aggregation is anonymous or legally sufficient. Actual processing decisions need the appropriate local assessment and the openly agreed purpose before information is collected or shared.
Build two versions
Create a detailed fictional table and a second version containing only the combined result needed for the question. For example, count the marked completed activities without retaining invented street-by-street descriptions in the summary. Keep the arithmetic simple enough that another participant can check it. If the summary leaves out information, identify the omission rather than presenting it as a complete account. A smaller report can answer a narrow question well while being unsuitable for another purpose. That is a useful distinction, not a defect to hide by collecting everything.
Look for remaining identification
Ask whether a small group, unusual activity or retained code could still make a person recognisable. Removing a name does not automatically remove privacy concerns. Avoid adding real examples to make the lesson seem more convincing. POTRAZ’s primary legislation and regulations are relevant sources for local questions, but this website does not prescribe a legal anonymisation threshold or determine an exemption. UK ICO guidance provides a foreign comparison concerning monitoring, not Zimbabwean law. Use the references to identify questions for qualified advice rather than to certify the exercise’s output.
Try a Gweru training example
Imagine a Gweru organisation comparing two fictional weekly reports. One exposes every invented stop; the other answers the agreed activity-count question with a combined total and an explanation of scope. Participants discuss whether the extra detail contributes to that question and what privacy concerns it could introduce in a real service. No live data is exported. This hypothetical example recommends no software and promises no efficiency saving. It trains people to connect information detail to a purpose instead of assuming the longest report is the most useful.
Explain the chosen level of detail
Write the question, the information used, the limitations of the combined result and who would appropriately receive it. Ask another participant to check both the calculation and the scope statement. If a later task needs more detail, treat it as a new assessment rather than quietly reusing information for a different purpose. A useful summary exercise demonstrates that clarity and restraint can work together. It supports thoughtful report design while leaving actual access, retention, legal basis and service configuration with the properly authorised people and their appropriate advisers.
Sources & further reading
Use these references to check the underlying guidance and any current local requirements. Practical worksheets and illustrative examples in this guide are original educational material.
- POTRAZ: Data Protection Act No.5of2021, original publication
- POTRAZ: SI155of2024, Data Controllers and Data Protection Officers
- UK ICO: Specific considerations for monitoring workers, including work vehicles
This guide is general information. Source notes are not a claim of independent professional review.