What a fractional DPO does in the first 90 days
An organization that hires a privacy lead for a few days a month needs to know what those days buy. The honest answer is a sequence of small, checkable outputs, not a policy binder.
Key points
- A fractional data protection officer is an outside specialist who carries the privacy lead role for a set number of days a month, instead of a full-time hire, and reports to the same senior people a staff officer would.
- The first 90 days are mostly about finding out what the organization holds and who decides things: a short list of processing activities, a register of the privacy risks, the open requests and vendors, and a plan the board has seen.
- Every output below is something you can ask to see: a register, a log, a calendar, a decision list.
- Whether you must designate a data protection officer at all is a legal question, answered by the law that applies to you and your counsel. A fractional officer is one way to fill the role where it is required, and a useful lead where it is not.
Three phases, in order
The work runs in this order because each phase depends on the one before: first understand what exists, then rank what matters, then put the recurring work on a calendar.
Days 1 to 30: discover
The first month is mostly conversations. We meet whoever runs marketing, HR, product, support, finance and IT, and ask the same questions of each: what personal data do you collect, where does it go, who else can see it, and what have you promised people about it?
Out of that come four working documents.
- A first list of processing activities. Not complete, but enough to start. The regulator’s own guidance on the record the GDPR requires (the ICO’s documentation guidance) lists what a record covers: the purposes, the categories of people and data, the recipients, transfers to other countries, retention schedules and security measures. The method is covered in records of processing built from systems.
- A list of vendors that touch personal data, from contracts and the accounts-payable ledger, not from memory.
- The open and recent requests from individuals, and how each was handled. A process nobody has written down is still a process, and this is where it shows.
- What the public notices say. The privacy notice, the cookie banner and the forms, read against what the systems do.
We also ask what has gone wrong before: complaints, a lost laptop, an email sent to the wrong list. Those answers tell us where the weak points are faster than a questionnaire does.
Days 31 to 60: rank and fix
With the picture drawn, the second month ranks it. Not every gap deserves attention in the same quarter, and a risk register is how that choice is made visible and signed for. Each entry names a risk, an owner, what reduces it today, and what you decided to do about it. The structure is described in privacy risk register and vendor management.
Three kinds of work usually surface as urgent in this month.
- A request process that works when it is not expected. One intake route, one owner, and a clock. See data subject requests across jurisdictions.
- The processor contracts with the biggest exposure: the vendors holding the most sensitive data or the most of it.
- Any new project already in flight that processes personal data in a new way, which needs an impact assessment before it launches, not after. See privacy impact assessments.
What we do not do is decide on your behalf. The register records the decision and who made it. Choices about risk acceptance belong to the people who answer for the business.
Days 61 to 90: set the rhythm and hand over decisions
A privacy lead who works a few days a month is only useful if the recurring work happens in the days between. The third month turns the discovery and the register into a calendar: vendor reviews due, records to refresh, training to run, requests to report, the board paper to write.
We also produce a short list of decisions that are yours, each with the options and our recommendation. Typical items are whether to adopt a consent platform, whether to localize a data store, and which jurisdictions need local counsel. A first report goes to the board or the executive sponsor in plain language: what was found, what was fixed, what remains and what it depends on.
By day 90 the privacy work has an owner, a calendar and a list of decisions that are yours to make, so the engagement can continue at a lower rate of days or end without leaving a gap.
The legal questions that stay with counsel
Whether you must designate a data protection officer at all is a legal question, answered by the law that applies to you and your counsel. A fractional officer is one way to fill the role where it is required, and a useful lead where it is not.
Article 37(6) of the GDPR says the officer may be a member of staff or may fulfil the tasks under a service contract, so an outside appointment is permitted in principle; counsel confirms the arrangement for your situation. The text is on EUR-Lex. The laws differ: the GDPR and UK GDPR have designation rules, while other regimes use different titles and duties for the person who runs the privacy function. Specialists in the relevant regime, such as the GDPR, join where the work needs them, and the legal conclusions are reached with your counsel.
What to ask any provider before you sign
- Who does the work on a given day, and does that person hold the relevant regime’s expertise?
- What are the written outputs at day 30, 60 and 90?
- Who is told when the engagement finds something serious, and how quickly?
- How are conflicts of interest handled if the provider also sells software or legal services?
- What happens to the working papers when the engagement ends?
The service itself is described on fractional DPO and privacy programme. Our security work is led by professionals who hold the CISSP, which matters here because most privacy gaps are access and retention gaps.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What is a fractional DPO?
A fractional data protection officer is an outside specialist who carries the privacy lead role for a set number of days a month, instead of a full-time hire, and reports to the same senior people a staff officer would.
What happens in the first 90 days?
The first 90 days are mostly about finding out what the organization holds and who decides things: a short list of processing activities, a register of the privacy risks, the open requests and vendors, and a plan the board has seen.
Do we have to appoint a DPO at all?
Whether you must designate a data protection officer at all is a legal question, answered by the law that applies to you and your counsel. A fractional officer is one way to fill the role where it is required, and a useful lead where it is not.
Can a DPO be an outside provider?
Article 37(6) of the GDPR says the officer may be a member of staff or may fulfil the tasks under a service contract, so an outside appointment is permitted in principle; counsel confirms the arrangement for your situation.
What do we have at the end?
By day 90 the privacy work has an owner, a calendar and a list of decisions that are yours to make, so the engagement can continue at a lower rate of days or end without leaving a gap.
Start the first 30 days
Tell us what you collect, in which countries and who currently owns privacy. The reply says what the first month would cover. The service is fractional DPO and privacy programme; related reading is the Canadian privacy law map.