TRUST ATLAS WORKSHEET
Role and territorial scope memo
EU GDPR · Step 1 · Map data and establish scope- Who prepares it
- Privacy lead + data owners
- When to prepare it
- At initiation and on material changes
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Decision
- Cover the hosted billing service for the April to June review.
- In scope
- Production billing API, hosting, releases and production access.
- Excluded and why
- Internal HR tool. It has no access to billing systems or data.
- Dependencies
- Cloud hosting and corporate identity provider.
- Approval
- Service owner approves after checking the architecture and contract.
Gather first
- Service inventory and architecture
- Customer commitments and contracts
- Applicable criteria or legal text
How to prepare it
- Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
- List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
- Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.
Review
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Handoff
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.