LearnGrokNothing here is legal advice. A draft is a starting point for a qualified person, not a substitute for one.
Use these prompts to turn a new regulatory text and an existing internal policy into a traceable change note. They suit legal and compliance teams preparing material for policy owners, not replacing their judgement. Nothing here is legal advice. The draft is a starting point for a qualified person, not a substitute for one.
Start with the source text, not a summary someone has forwarded. You need the relevant sections, definitions, scope, dates, exceptions and transitional wording. Then use the current approved policy, including its version and section numbers. A comparison without citations is difficult to challenge and harder to approve.
Key point
Build the evidence trail first
Each proposed change should lead back to a regulatory citation and a policy section, or be clearly marked as an unresolved question.
1. Extract duties before reading for gaps
Run Extract the requirement into testable duties against the regulatory document. This produces a requirement register with one row per duty. It prevents a broad phrase such as “improve customer information” from becoming an untestable policy change.
Keep the source intact in the prompt. Include definitions and schedules where they affect who is in scope or what evidence must be retained. If you only have an extract, say so in the placeholder. The model should then record the limitation rather than silently treating the extract as complete.
Watch out
Do not replace the source with a colleague’s summary
Summaries often omit conditions, exceptions and implementation dates. Those are usually where the policy assessment changes.
2. Compare the actual policy wording
Use Map duties against the current policy with the completed register and the full policy. Add referenced procedures or control descriptions if you need to assess how the policy operates. If they are unavailable, leave them as unavailable. Do not paste an assumption in their place.
The status labels are useful because they separate four different outcomes:
| Status | Meaning | What to do next |
|---|---|---|
| Meets | The policy text addresses the duty | Confirm the operating evidence still exists |
| Partly meets | The policy covers only part of the duty | Define the missing wording or control |
| Does not meet | No adequate policy response is evidenced | Raise a policy change action |
| Cannot assess | Documents or facts are missing | Request the missing evidence or decision |
A policy may state an intention but not assign an owner, timing or record. Treat that as a possible evidence gap, not proof that a control operates. Equally, a missing policy clause does not prove that no operational control exists. The distinction matters when writing the note.
Check
Check every comparison row
You should be able to point to both a regulatory citation and a policy citation. If either is absent, the row should say "Cannot assess" or identify the missing text.
3. Make accountability explicit
Run Assign owners and resolve open questions once the findings are stable. Give it only roles and governance forums that exist in your supplied material. A plausible-sounding owner is not an accountable owner.
Separate three things that are often merged in a meeting:
- A decision on regulatory interpretation, for qualified legal or compliance review.
- A policy wording change, for the policy owner and approval route.
- An operational action, such as updating a procedure, record or training material.
Where no owner is supported, keep the action unassigned and escalate it. This is more useful than assigning it to “Compliance” by default. It also lets the policy owner see which decisions are needed before implementation can begin.
4. Produce a reviewable change note
Use Draft the policy owner change note only after the register, comparison and action list are ready. Its fixed headings make the note easier to take through an approval forum. Paste the output into your document template if required, then retain the source tables as working papers.
Read the note as a decision document. Policy owners need to see what changed, which policy sections are affected, who owns each action, and what they must decide. They do not need unsupported conclusions about compliance.
Note
Limits and behaviour can vary
Check the current product documentation before setting up a repeatable workflow or handling large source bundles: xAI documentation overview.
Check whether the output is wrong
Do not check only grammar. Test the evidence and the omissions. The output is likely wrong, or incomplete, if it does any of the following:
- It gives a deadline that does not appear in the source.
- It changes a qualified term such as “reasonable” into an absolute requirement.
- It cites a policy heading but cannot quote the relevant wording.
- It calls a control effective when you supplied no operating evidence.
- It assigns a person or team not named in the inputs.
- It answers an unclear legal interpretation instead of recording the question.
- It treats a referenced procedure as reviewed when it was not supplied.
Check a sample of material findings line by line against the regulatory source and the policy. Check all items marked Critical or High. Ask the policy owner to confirm operational facts, and ask the qualified reviewer to decide interpretation questions. Record corrections in the requirement register, then rerun the later prompts so the change note remains consistent.
Stop
Do not send the draft as a compliance conclusion
Keep the qualified-review questions and assumptions in the note until the responsible reviewer has resolved them.
When the workflow does not work
If the comparison is vague, split the regulatory source by topic and create separate requirement registers. If policy citations are missing, obtain the approved policy or mark the assessment as incomplete. If owners cannot be assigned, escalate through the stated governance route rather than guessing. If the output conflicts with the documents, correct the source extract or the register first, then rerun the comparison and change note.
