Keep systems actionable
The inventory should help responders know where to look and who owns each source. Avoid broad lists that do not tell the team how to fulfill a request.
- Name the system, owner, data category, and fulfillment notes.
- Keep inactive or out-of-scope systems clearly marked.
- Review ownership after reorganizations or vendor changes.
Connect systems to tasks
System inventory becomes useful when it drives repeatable tasks. Use owners and templates to create targeted work for access, deletion, correction, export, and review workflows.
- Assign tasks to the people who can actually retrieve or act on data.
- Keep task instructions specific to the system.
- Attach evidence back to the case instead of unmanaged channels.
Example: turn a system name into useful instructions
“Customer support” is a starting point, but it does not tell a colleague how to complete a search. Useful fulfillment notes might say which team can search tickets, what account identifier to use, and how to document a search with no matching records.
- Include the normal search contact or responsible team.
- Describe the kinds of records the system may contain without storing customer records in the inventory itself.
- Tell the task owner how to document the search and return relevant evidence to the case.
- Adding a system to the inventory does not automatically search it or delete information from it.
Need more help?
Product support is available at support@privacyrequests.co. Requesters should contact the company handling the request first because that company controls the case record and response decisions.