PMOpackFree check
Article

Can I put programme data into an AI tool and stay within UK GDPR?

Often, yes. But the decision belongs to your organisation, not to you or the tool. A plan or RAID log usually contains personal data, such as names and roles, so your organisation stays the controller and the tool acts as its processor. Someone with authority, usually your DPO or legal team, decides whether the use is lawful. Your job is to give them the facts.

We are programme practitioners, not lawyers. What follows comes from the project side of data protection reviews: what the DPO will ask, what they need from you, and how to get to a yes or a no in days rather than months. It is general information. The person who decides for your organisation is your data protection officer or your solicitor.

Why programme data counts

People assume a project plan is not personal data because it is about work, not people. Look at the columns. Owner. Resource. Approver. Comments. A RAID log that says “issue: lead developer underperforming, escalated to HR” is personal data of the most sensitive kind. A budget tracker with day rates beside names is personal data. The dates and the figures are not, but they rarely travel alone.

So the question is not “is this personal data”. It usually is. The question is “is this use of it lawful, fair and safe”, and that is a question your organisation has to be able to answer and show its working on. The ICO’s accountability principle says the controller “shall be responsible for, and be able to demonstrate compliance with” the data protection principles, and its guide tells organisations to “keep records of what you do and why”.

Who is who

Under UK GDPR there are two roles that matter here. The ICO says “Controllers make decisions about processing activities” and “Processors act on behalf of the relevant controller and under their authority.” When you upload a file to a reporting tool, your organisation decided to do it and why: it is the controller. The tool does what it is told with the file: it is the processor.

That matters because the ICO is clear that the controller stays on the hook. It says a controller can “only use a processor that provides sufficient guarantees”, “must enter into a binding contract or other legal act” with its processors, and is “ultimately accountable for your own compliance and the compliance of your processors.” A vendor saying “we are GDPR compliant” does not transfer anything. Your organisation still decides and still answers.

The questions your DPO will ask you

Get these answered before you book the meeting and the meeting will be short.

  1. What data, exactly? Which files, which columns, which people. Bring a sample with the real column headings and made-up rows.
  2. Why? The purpose in one sentence: “to prepare the monthly board pack from the plan and RAID log we already keep”.
  3. Who is the vendor, and who are its providers? The full list, including the AI provider. See Where does my project data go when I use an AI reporting tool? for the five questions to put to the vendor.
  4. Where does it go? The ICO calls sending personal information to an organisation outside the UK a “restricted transfer” and says it must be covered by adequacy regulations, an appropriate safeguard such as the International Data Transfer Agreement or Addendum, or an exception. Your DPO will want to know which applies for each provider.
  5. Is there a contract? The processor terms or data processing agreement. The DPO reads it; you just need to find it.
  6. Does anyone train on it? The AI provider’s terms, with a date.
  7. Is a DPIA needed? The ICO says you must do one “where a type of processing is likely to result in a high risk to the rights and freedoms of individuals”, that innovative technology combined with another risk factor requires one, and that “If in any doubt, we would always recommend that you do a DPIA”. An AI tool on a file of named people may or may not meet that bar. That is the DPO’s call, not yours.

What you can do as a PM, today

  • Send less. The ICO’s data minimisation principle says personal data should be “adequate, relevant and limited to what is necessary”. Strip performance comments, pay, personal contact details, and anything the report does not need. A name in an owner column is usually necessary. A note about someone’s sick leave is not.
  • Use the organisation’s account, never a personal one. A personal account is outside the contract your organisation signed, if it signed one at all.
  • Write down what you did. Which tool, which files, which date, who approved. The accountability principle is about being able to show your working. A one-page note does it.
  • Ask before, not after. A DPO who hears about a tool at a review meeting is annoyed. One who is asked in week one is usually helpful.

A real example

A PMO on a public-sector programme wanted to use an AI tool to draft status narrative from its weekly tracker. The tracker had a “notes” column that, over two years, had become a diary of who was off sick, who was struggling and who was leaving. The DPO said no, and was right to. The PMO deleted the notes column from the export, kept it in the master file, and asked again. The second answer was yes, with a short DPIA and a line in the record of processing. The whole thing took eleven days. The notes column was the problem, not the tool.

Where PMOpack fits

PMOpack’s privacy notice sets out the facts your DPO will want. For the programme data you upload, PMOpack acts as your processor and uses the providers listed in the notice. The database is hosted in London, UK. The text needed for drafting is sent to Anthropic, whose Commercial Terms say it may not train models on customer content; PMOpack does not use your programme data to train any model. Draft report files are removed after 7 days. Published packs and their audit record are kept permanently. The privacy notice is the current statement; read it rather than this article. What PMOpack does not do: it does not decide for your organisation whether the processing is lawful, and it does not replace a DPIA. It gives you the facts to put in one.

Questions people ask

Is a project plan personal data?
If it names people, yes, at least in part. Owner columns, resource names, and any comment about a person's performance are personal data. The dates and figures on their own are not.
Who decides whether we can use an AI tool on programme data?
Your organisation, as the controller. In practice that means your data protection officer, legal team or information security function, following your own policy. Not the project manager alone, and not the vendor.
Do we need a DPIA before using an AI reporting tool?
Possibly. The ICO says a DPIA is required where processing is likely to result in a high risk to individuals, and that innovative technology combined with another risk factor triggers one. If in doubt, the ICO recommends doing one. Ask your DPO.
What should I strip from a file before I upload it?
Anything the report does not need: performance comments, salaries and day rates, personal contact details, and client names where a code will do. Less data in means less to justify.
Does PMOpack act as a controller or a processor?
For the programme data you upload, PMOpack's privacy notice says it acts as your processor, on your instructions. For your account details it is the controller. The notice lists every provider it uses.

Sources

Last checked 29 October 2026. This article is general information, not legal advice. The ICO notes that parts of its AI guidance are under review following the Data (Use and Access) Act; read the current page. Your data protection officer or solicitor decides what applies to your organisation.

  1. Information Commissioner’s Office, “What are ‘controllers’ and ‘processors’?”ico.org.uk
  2. Information Commissioner’s Office, “What does it mean if you are a controller?”: sufficient guarantees; binding contract; “ultimately accountable for your own compliance and the compliance of your processors”.ico.org.uk
  3. Information Commissioner’s Office, “When do we need to do a DPIA?”ico.org.uk
  4. Information Commissioner’s Office, “A brief guide to international transfers”.ico.org.uk
  5. Information Commissioner’s Office, “A guide to the data protection principles” (data minimisation; accountability, Article 5(2)).ico.org.uk
  6. Information Commissioner’s Office, “Guide to accountability and governance”: “keep records of what you do and why”.ico.org.uk
  7. Information Commissioner’s Office, “Guidance on AI and data protection” (notes the guidance is under review after the Data (Use and Access) Act).ico.org.uk
  8. Anthropic, Commercial Terms of Service (effective 17 June 2025): “Anthropic may not train models on Customer Content from Services.”anthropic.com/legal/commercial-terms
  9. PMOpack data handling statements are drawn from PMOpack’s own privacy notice.

See the checks on your own pack.

We are working with a small group of delivery professionals to prove the reporting journey on real work. One active workspace per person.

Or email [email protected]

For people who run project reporting for a living. Not for students, personal projects or coursework. We read every request and reply to those who fit.

Want to know where your data goes and who can see it? Read the Trust page.