Nigeria Data Protection Act
Decide which Nigerian registration and audit duties apply, then track how sensitive data is handled and reported.
Protection of Personal Information Act · South Africa
Operationalize conditions for lawful processing and security compromise reporting.
Responsible parties and operators processing personal information within POPIA’s scope.
A documented program covering lawful processing, accountability, security and data-subject rights.
Evaluate prior authorization triggers, special personal information, children’s data and local direct-marketing rules.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
POPIA kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Confirm scope and appoint owners · Information officer + legal [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Confirm scope and appoint owners | Information officer + legal | Before implementation | Set a start date | Scope memo; Officer registration; Processing register | Open |
| Implement lawful processing and rights | Privacy operations + product | Before processing and on requests | Set a start date | Notices; Processing rationale; Rights procedure | Open |
| Contract with operators and assess safeguards | Legal + security | Before outsourcing or transfers | Set a start date | Operator agreements; Safeguard evidence; Transfer review | Open |
| Report qualifying security compromises | Responsible party + information officer | As soon as reasonably possible after discovery | Set a start date | Incident log; Regulator notice; Affected-person communication | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify responsible parties and operators. Confirm officer registration, role responsibilities and processing conditions.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Confirm processing grounds, notices and purpose limits. Implement access, correction, objection and retention workflows.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Document security obligations and operator escalation duties. Evaluate cross-border transfers and prior authorization triggers.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Fictional details. Use the same fields with evidence from your work.
The register shows actual access paths, the basis for each transfer and a clear release decision.
Share the decision with supplier and access owners so they can implement the conditions before data is available.
Document facts and mitigation, notify the Information Regulator and affected data subjects where required, and account for permitted delays.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.