Policy hierarchy
A clear policy → standard → procedure structure with ownership, review cycles and plain-language drafting that people can follow.
POL · Policy Management
We write and rationalise data policies, standards and procedures, map them to the regulations you are subject to, and embed classification, privacy and retention rules into everyday controls.
The challenge
What we deliver
A clear policy → standard → procedure structure with ownership, review cycles and plain-language drafting that people can follow.
A traceable obligations register linking each regulatory requirement to policy statements, controls and evidence.
A classification scheme for confidentiality and criticality, with tagging rules applied in your catalogue and platforms.
Personal data inventories, records of processing and privacy controls integrated with governance workflows.
Retention schedules translated into enforceable rules, with legal-hold handling and defensible deletion.
Annual attestation workflows, control testing and reporting to risk committees and the board.
Outcomes you can measure
fewer policy documents after rationalisation, with no loss of coverage
of in-scope regulatory obligations traced to a policy statement and control
of obligations, controls and evidence replacing scattered spreadsheets
Related case study · Illustrative engagement
fewer policy documents
Twenty-seven overlapping data policies were consolidated into a clear hierarchy mapped to national data protection law, with a costed three-year roadmap.
Read the case studyFAQ
A policy states intent and principles, a standard sets measurable requirements, and a procedure describes the steps to meet them. Keeping the layers distinct makes documents shorter and easier to maintain.
We build an obligations register that breaks each regulation into discrete requirements, then link each one to the policy statement, control and evidence that addresses it.
Yes. Alongside UK and EU GDPR we regularly map to Nigeria's NDPR and Data Protection Act, South Africa's POPIA and the data protection laws of the UAE and Saudi Arabia.
Keep the scheme to four or five levels, apply it at domain or dataset level first, automate tagging where possible and link classification to concrete handling rules.
At least annually, and whenever a material regulatory, organisational or technology change occurs. We set up review cycles and attestation so this happens by default.
Related insights
DORA creates important dependencies on reliable operational information. Data governance should strengthen that evidence without becoming a parallel ICT risk or resilience function.
Policy becomes effective when a reader can identify the required action, supporting control and route for exceptions. Write for operational decisions, then test the document against real work.
A 45-minute working session, no sales deck. You will leave with at least three actionable recommendations.