QuQi

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.

Obter o ficheiro da competência Deixe os agentes tratar disso
CATEGORIA
Produção de conteúdo
FORMATO
compliance-review-without-gutting-the-draft.md
PASSOS
7
PREÇO
Grátis — sem conta
QUANDO USAR ISTO

Use when publishing in a regulated sector and legal or compliance review keeps returning drafts unrecognisable or too late.

O ficheiro da competência

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.

## O que precisa primeiro

- 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

## Método

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.

## O que isto produz

A reviewed draft plus a maintained list of pre-approved wordings and a written no-review scope.

## Onde isto corre mal

- 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

---

Da biblioteca de competências da QuQi - https://www.quqi.io/pt/skills/compliance-review-without-gutting-the-draft
Transferência gratuita · sem conta, sem e-mail

O que precisa primeiro

  • 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

Método

  1. 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.
  2. 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.
  3. 03 Put a compliant alternative next to every risky claim. Reviewers approve a choice quickly and rewrite prose slowly.
  4. 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.
  5. 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.
  6. 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.
  7. 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.

O que isto produz

A reviewed draft plus a maintained list of pre-approved wordings and a written no-review scope.

Onde isto corre mal

  • 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 esta skill na sua própria IA

O ficheiro é markdown simples, com o nome e o gatilho no frontmatter. Quando um assistente consegue carregar skills sozinho, é esse frontmatter que lê para decidir que esta se aplica.

Claude Code Guarde-a como ~/.claude/skills/compliance-review-without-gutting-the-draft/SKILL.md e o Claude carrega-a sozinho quando o que está a fazer corresponde ao gatilho. Coloque-a em .claude/skills dentro de um projeto se toda a equipa a deve ter.
Claude Carregue o ficheiro na secção de skills das suas definições. A partir daí aplica-se sozinho em qualquer conversa onde o gatilho encaixe, sem ter de se lembrar dele.
ChatGPT Não existe um formato de skills onde a instalar, por isso cole o conteúdo do ficheiro nas instruções de um Projeto ou de um GPT personalizado. Passa então a aplicar-se a todas as conversas desse projeto e não só àquela onde o colou.
Qualquer outro Cole o markdown na conversa antes da sua pergunta. Funciona em qualquer assistente, só tem de ser colado de novo de cada vez.

Mais em Produção de conteúdo