How to Draft a GDPR RoPA from a Process Inventory
RoPA tables invent processors in Ireland. Purposes and recipients only from the inventory.
The matching generator is the GDPR Record of Processing (RoPA) from a Process Inventory (Not Legal Advice) (Gdpr Ropa From A Process Inventory Not Legal Advice) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Print the not-legal-advice banner
Draft a RoPA table from a process inventory. Categories of data, purposes, and recipients only if listed. Not legal advice, not a DPA/SCC questionnaire, not a privacy-policy FAQ. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Process inventory (process name, data categories, purposes, recipients): [Inventory]
Controller identity I may print (or UNKNOWN): [Controller]
Legal bases I may state (or NONE): [Bases]
Retention notes I may state (or NONE): [Retention]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Banner I require: [Banner]
Transfer tools I may name (or NONE): [Transfers]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
One row per named process
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Inventory nouns, Controller, Bases, Retention, Transfers, Lang. Forbidden: inventing legal bases, inventing SCCs.
- Banner: print Banner (not legal advice).
- RoPA table: one row per Inventory process. Columns: process, data categories, purpose, recipients. Missing cells: NOT IN INPUTS.
- Legal bases column: only Bases; if NONE, write LEGAL BASIS NOT IN INPUTS.
- Retention: only Retention; if NONE, write RETENTION NOT IN INPUTS.
- Transfers: only Transfers; if NONE, write TRANSFER TOOL NOT IN INPUTS.
- Refuse: DPA questionnaire answers invent, SCC module invent, privacy-policy FAQ invent, certification claims.
- Compliance pass: quote Banned and Never. Gaps list of five. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Leave recipients NO_DATA if blank
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- RoPA from Inventory only. Not legal advice and not DPA/SCC questionnaire.
- Never invent legal bases or transfer tools when NONE/UNKNOWN.
- Keep Banner visible.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse DPA and SCC padding
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (gdpr ropa from inventory, record of processing activities, not legal advice ropa) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.