Get a Draft Through Compliance Review
Drafts sent whole to legal come back either hedged into uselessness or three weeks late, and writers respond by pre-hedging everything, which is worse than either. Reviewers are not trying to ruin the page; they receive a document with no indication of which sentences carry risk, so they treat all of it as risky. The fix sits on the content side: isolate the claims that genuinely need review, propose compliant alternatives yourself, and hand the reviewer a decision rather than a manuscript.
CATEGORY
Content production
FORMAT
compliance-review-without-gutting-the-draft.md
WHEN TO REACH FOR THIS
Use when publishing in a regulated sector and legal or compliance review keeps returning drafts unrecognisable or too late.
The skill file
compliance-review-without-gutting-the-draft.md
---
name: compliance-review-without-gutting-the-draft
description: Use when publishing in a regulated sector and legal or compliance review keeps returning drafts unrecognisable or too late.
---
# Get a Draft Through Compliance Review
Drafts sent whole to legal come back either hedged into uselessness or three weeks late, and writers respond by pre-hedging everything, which is worse than either. Reviewers are not trying to ruin the page; they receive a document with no indication of which sentences carry risk, so they treat all of it as risky. The fix sits on the content side: isolate the claims that genuinely need review, propose compliant alternatives yourself, and hand the reviewer a decision rather than a manuscript.
## What you need first
- the applicable rules for your sector in writing, not a colleague's recollection of them
- the last ten review rounds and what each changed, which reveals the reviewer's real pattern
- a named reviewer and an agreed turnaround, not a shared inbox
- the draft with its factual and performance claims already marked
## Method
1. Build a list of previously approved wordings from past review rounds. Most of what a reviewer changes they have changed before, and reusing an approved phrasing requires no new decision from anyone.
2. Mark the draft into three classes before sending: claims needing review, claims already approved verbatim elsewhere, and everything else. This step alone removes most of the turnaround.
3. Put a compliant alternative next to every risky claim. Reviewers approve a choice quickly and rewrite prose slowly.
4. State what each claim rests on beside it. A performance figure carrying its source and period usually survives, while the same figure bare gets cut.
5. Ask for the rule behind any change you do not understand instead of just accepting it. Some changes are the regulation and some are the reviewer being careful, and only the first kind has to bind every future draft.
6. Add each decision to the approved-wordings list as it is made, so the next draft starts with more pre-approved material than this one did.
7. Agree what needs no review at all and get that scope in writing. Without a stated exemption everything drifts back into the queue within a quarter.
## What this produces
A reviewed draft plus a maintained list of pre-approved wordings and a written no-review scope.
## Where this goes wrong
- Pre-hedging the whole draft to avoid comments, which produces a page that says nothing and still comes back edited
- Treating each review as a one-off, so the same twenty corrections are made every month and turnaround never improves
- Editing the page after approval, which puts unreviewed wording live under a sign-off that no longer covers it
---
From the QuQi skill library - https://www.quqi.io/skills/compliance-review-without-gutting-the-draft
Free to download · no account, no email
What you need first
-
the applicable rules for your sector in writing, not a colleague's recollection of them
-
the last ten review rounds and what each changed, which reveals the reviewer's real pattern
-
a named reviewer and an agreed turnaround, not a shared inbox
-
the draft with its factual and performance claims already marked
Method
-
01
Build a list of previously approved wordings from past review rounds. Most of what a reviewer changes they have changed before, and reusing an approved phrasing requires no new decision from anyone.
-
02
Mark the draft into three classes before sending: claims needing review, claims already approved verbatim elsewhere, and everything else. This step alone removes most of the turnaround.
-
03
Put a compliant alternative next to every risky claim. Reviewers approve a choice quickly and rewrite prose slowly.
-
04
State what each claim rests on beside it. A performance figure carrying its source and period usually survives, while the same figure bare gets cut.
-
05
Ask for the rule behind any change you do not understand instead of just accepting it. Some changes are the regulation and some are the reviewer being careful, and only the first kind has to bind every future draft.
-
06
Add each decision to the approved-wordings list as it is made, so the next draft starts with more pre-approved material than this one did.
-
07
Agree what needs no review at all and get that scope in writing. Without a stated exemption everything drifts back into the queue within a quarter.
What this produces
A reviewed draft plus a maintained list of pre-approved wordings and a written no-review scope.
Where this goes wrong
-
Pre-hedging the whole draft to avoid comments, which produces a page that says nothing and still comes back edited
-
Treating each review as a one-off, so the same twenty corrections are made every month and turnaround never improves
-
Editing the page after approval, which puts unreviewed wording live under a sign-off that no longer covers it
Use this skill in your own AI
The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.
Claude Code
Save it as ~/.claude/skills/compliance-review-without-gutting-the-draft/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude
Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT
There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else
Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.
Questions about this skill
When do I change the review process rather than keep sending drafts to legal as they are?
When drafts come back unrecognisable or three weeks late, and writers have started pre-hedging everything, which is worse than either outcome. Sending the draft whole is the cause: the reviewer receives a document with no indication of which sentences carry risk, so all of it is treated as risky. The fix sits on the content side, not the reviewer's.
What do I need before the next review round?
The applicable rules in writing rather than a colleague's recollection, the last ten review rounds and what each one changed, a named reviewer with an agreed turnaround, and the draft with its factual and performance claims already marked. Without the review history you cannot build the approved-wordings list, and most of what a reviewer changes they have changed before.
What comes out of this, and which part compounds?
A reviewed draft, a maintained list of pre-approved wordings, and a written no-review scope. The wordings list is the asset, because each draft starts with more pre-approved material than the last and reusing an approved phrasing needs no new decision from anyone. The marking pass alone removes most of the turnaround, before the reviewer reads a word.
What is the mistake that costs the most?
Editing the page after approval, which puts unreviewed wording live under a sign-off that no longer covers it, and that is the version quoted back at you in a complaint. Treating each review as a one-off costs less dramatically but constantly: the same twenty corrections are made every month and the turnaround never improves.
More in Content production