Home » Records of Processing Activities (RoPA) Services
Pembroke Privacy helps organisations create, review and maintain their RoPA under Article 30 of the GDPR.
The RoPA is a fundamental element of your data protection framework. A well-maintained register demonstrates compliance to supervisory authorities and indicates that an organisation has a clear view of its processing activities and has considered the purpose of each activity.
We work with privacy teams and business functions to document processing activities, identify gaps and establish a practical approach to keeping records up to date.
Whether you need to build a RoPA from the beginning or improve an existing register, we can help you meet your Article 30 GDPR obligations.
The RoPA is a fundamental element of your data protection framework.
A Record of Processing Activities, commonly called a RoPA, is a documented record of an organisation’s personal data processing activities. Article 30 GDPR specifies the information controllers and processors must record, with different requirements for each role. The record must be available to the relevant supervisory authority on request.
For a controller, a RoPA explains why personal data is processed, whose data is involved, the types of information used, who receives it and any relevant international transfers. It also records, where possible, erasure time limits and a general description of security measures.
A well-maintained RoPA supports the GDPR’s accountability principle and helps your organisation understand its processing. It is not, on its own, proof of full GDPR compliance.
An existing register may no longer give an accurate picture of your organisation. You may need support if:
We tailor our support to your organisation’s requirements and internal resources. We take a project management approach when delivering RoPA projects. Projects can focus on creating a new register, reviewing an existing RoPA or improving the way it is maintained through staff training.
1. Agree the scope and responsibilities
We begin by understanding your organisation, the legal entities and business functions involved, and whether you act as a controller, a processor or both. We review the records you already hold and agree the scope of the work with your team.
2. Identify processing across the business
We identify key stakeholders and work with relevant teams, such as HR, finance, IT, marketing and operations, we gather information about how personal data is collected, used, shared and retained. Data mapping helps identify processing that may be missing from the register, including activities involving external providers and new technologies.
3. Develop or improve the records
We help structure and document the information required by Article 30, using an appropriate format templated RoPA for your organisation. We ensure all necessary information is included, such as lawful bases, process owners and links to related privacy assessments, while keeping the prescribed information clear and accessible.
4. Validate information and identify gaps
We work with the relevant business owners to check that entries reflect actual practice. Where information is incomplete or inconsistent, we identify what needs clarification and help prioritise the next steps. Wider compliance issues can be considered separately where further advice or remediation is required.
5. Establish a maintenance approach
We help define who is responsible in each business function for supplying updates, who coordinates the register and what changes should trigger a review. This keeps RoPA maintenance connected to business activity, rather than relying on a one-off exercise that quickly becomes outdated.
Your organisation remains accountable for its processing. Our role is to provide specialist support and a structured approach, with input from the people who understand how the business operates.
Depending on the agreed scope, our support can include:
We agree the deliverables at the outset, taking account of your organisation’s size, complexity and existing resources.
Whether you need a new register, a review of existing records or support with ongoing maintenance, speak to Pembroke Privacy about the right approach for your organisation.
Tell us whether you already have a RoPA, which areas need support and whether there is an audit or regulatory request we should take into account.
Pembroke Privacy combines data protection expertise with practical experience supporting organisations’ privacy programmes. Our team includes qualified lawyers and data protection professionals, with experience advising Irish and international organisations.
Our existing External DPO service includes review, monitoring and support for keeping Records of Processing Activities up to date. RoPA work sits within our wider understanding of data protection governance, rather than being treated as an isolated document exercise.
Working with our team can help you:
They may do. Article 30(5) provides a limited exemption, not a blanket exemption for smaller organisations. Processing must still be recorded where it is not occasional, is likely to result in a risk to individuals’ rights and freedoms, or involves special-category or criminal-conviction and offence data. Routine HR and payroll processing is not occasional. The scope depends on the activities involved.
A RoPA should remain current as processing changes. Article 30 does not prescribe one universal review interval. Regular reviews should be supported by updates when relevant changes occur, such as a new system, supplier, processing purpose, data category or international transfer.
Not necessarily. A spreadsheet may be suitable for a smaller organisation, while a more complex business may benefit from dedicated software. The important requirements are accurate written records, practical maintenance and the ability to provide the information in a readable format on request.
No. Data mapping is the discovery work used to understand what personal data an organisation holds and how it moves through processes and systems. A RoPA is the structured record of processing activities containing the information required by Article 30. Data mapping helps make that record complete and accurate.
No. A RoPA records processing activities. A Data Protection Impact Assessment evaluates the impact of processing likely to result in a high risk to individuals’ rights and freedoms. A DPIA does not replace a RoPA, and not every processing activity requires a DPIA. Pembroke also provides DPIA support.
Article 30 requires the record to be maintained and made available to the supervisory authority on request. It does not create a routine filing obligation. If your organisation receives a request from a supervisory authority, you should respond in accordance with that request and provide the actual maintained record.
No. Accountability rests with the organisation, and accurate records require input from the relevant business functions. The DPO can advise and help coordinate the approach, but process owners need to supply and validate information about the activities they manage.
The scope depends on the number and complexity of processing activities, the condition of existing records and the availability of internal stakeholders. We discuss those factors with you before agreeing the work, deliverables and fees.