Training module
PII Processing: Context, Roles & Scope
Define PII processing context, determine controller and processor roles, and set practical PIMS scope boundaries under ISO/IEC 27701
Who decides what in your PII processing — and where does your PIMS actually begin and end?
Define processing context, determine controller and processor roles, and establish defensible PIMS scope boundaries that reflect real operations.
Overview
What this module is about
A Privacy Information Management System only works if its foundations are defined with precision. Organisations must be clear about what constitutes PII processing in their environment, which roles apply, and where system boundaries sit across internal units and external parties.
This module focuses on the architectural front end of a PIMS: defining processing context in a maintainable way, determining controller and processor roles including joint arrangements, establishing internal accountability models, and formalising scope statements and boundary artefacts that reflect real operations and sourcing structures. The emphasis is on governance clarity that enables consistent decision-making, auditability, and long-term maintainability.
Audience
Who it is for
Management system implementers and coordinators
Executives and department heads accountable for management system performance
Those responsible for processes, policies, assets, risks and controls
Auditors seeking insight into management-side practice, not audit technique
Consultants working on management system design, governance or improvement
Decision supportIs this module for you?
It is a good fit if you…
need clarity on what counts as PII processing in practice.
want clean controller and processor role separation.
need defensible scope boundaries for a PIMS.
work across internal units or external parties.
support ISO/IEC 27701 implementation or oversight.
It may not be the best fit if you…
are looking for legal interpretation of privacy laws.
want execution guidance for DPIAs or data subject rights.
need detailed operational privacy controls.
already operate a stable, well-defined PIMS scope and role model.
What to bring
This module assumes participants can already work with basic privacy and data protection concepts, including:
What counts as PII/personal data in their operating context
Common processing lifecycle language (collect, use, share, retain, delete)
Basic awareness of regulatory drivers and contractual obligations
Agenda
What is taught
7 parts01Defining PII processing context in a way the organisation can maintain
How to describe real PII processing in terms of services, products, channels, locations, and data flows at a level that stays accurate as the organisation changes
02Determining the organization's role: controller, processor, joint roles
How to apply practical tests to determine who decides purposes and means versus who acts on instructions, including mixed-role scenarios with platforms, partners, and internal functions
03Internal accountability model for privacy roles
How to translate external role concepts into internal ownership, decision rights, escalation paths, and evidence expectations that actually work day to day
04External parties and boundary-setting
How to decide what sits inside the PIMS scope versus what is managed through interfaces with suppliers, sub-processors, partners, affiliates, customers, and how to document those choices
05PIMS scope statement and boundary artefacts
How to produce a scope statement that is operationally useful and support it with concrete boundary artefacts such as context maps, role registers, interface registers, and exclusion logs
06Keeping scope and roles up to date
How to define change triggers and lightweight review routines so scope, roles, and responsibilities remain credible without creating a parallel governance machine
07Technology as an enabler
How to use inventories, ticketing links, contract repositories, and AI-assisted summaries to keep processing context current while keeping human judgement in control
Outcomes
Learning outcomes
01
Describe ISO/IEC 27701 expectations for processing context, roles and scope in a PIMS
02
Define a high‑level PII processing context that is usable for governance and maintenance
03
Determine and justify controller and processor roles for real‑world scenarios
Translate external role concepts into an internal accountability model that supports decisions and escalation
Produce a clear PIMS scope statement with boundaries, interfaces and exclusions
Identify typical scoping and role pitfalls and set up practical review triggers to keep roles and scope current
Materials
The content and the assessment
Written module
The full content in writing, complete in itself. Videos are recorded for parts of it as an alternative way through, and the written module always carries everything.
Exercises
Graded work on the case organisation's own registers: structured answers checked against the encoded case, written answers scored against a rubric traced to it, with a trainer holding the final word on every assessed item.
On completion
The assessed exercises must be passed before the certificate is issued.
Scheduling
No public run of PII Processing: Context, Roles & Scope is scheduled at the moment. Tell us you are interested and we will let you know when the next one opens, or discuss running it in-house.
Module facts
- Module ID
- HAM-DP-S-01
- Discipline
- Data Protection
- Domains
- Governance
- Part of tracks
- Management System Manager
Case organisation
All modules share one company
Each module enters the company at a particular point in its history and finds it as that history has left it.
Northstar Integrated Services AG is a group headquartered in Zurich, operating in six European countries, with about 1,350 employees at the end of 2025. It provides digital operations platforms and managed operational services to regulated organisations in healthcare, the public sector and industrial services. Founded in 2008 as a field-operations firm serving business customers, it had about twenty-five employees when its first regulated customer, a hospital group, required documented decisions, named accountability and evidence on request. It moved into the platform business in 2016 and in 2024 acquired an operating business in Poland and the Czech Republic, whose legal entity continues inside the group.
Linked registers
Organisation and people, roles, risks, objectives, policies, documents and records, communications, findings, audits and reviews, interested parties, processes
Records, not summaries
The evidence sits in the registers and documents where a real organisation would keep it.
A history
The company has a timeline from 2008, so a structure can be examined before and after it changed.
More than one legal entity
A Swiss parent company and an acquired subsidiary in Poland and the Czech Republic, with customers in several jurisdictions
Why it matters
Judgement develops on material that is incomplete and partly contradictory, as it is in practice. Northstar is built that way on purpose. Because modules enter its history at different points, a governance structure can be seen while it is built, when it is outgrown and when it is rebuilt.
Delivery & dates
How this module reaches you
Delivered live online, combining conceptual framing, discussion, case work and direct interaction with the trainer. In-house and contextualised delivery is available on request.
No public run is scheduled at the moment. Most modules run on request as well as on the public calendar, so tell us the timing you need.
Want this module scheduled?
We will tell you when the next run is scheduled, or run this module in-house with your own case material.
Not sure it is the right module?
Describe your context in a short message and we will tell you honestly.