> ## Documentation Index
> Fetch the complete documentation index at: https://docs.harpgtm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Copy review

> Hold every rendered email until your agent has reviewed it, approve or lightly edit drafts in send order, and save copy notes that apply to every draft after.

Copy review puts a check between a rendered email and the send. It is on per playbook, with **Require copy review**.

## How it works

1. Harp renders each email from the template and your agent's research answers.
2. The draft waits in the review queue instead of sending.
3. Your agent calls `copy_review_queue` to read the drafts due soon, in send order.
4. It approves drafts, or saves light edits, with `save_copy_reviews`.
5. Approved drafts send on schedule, from your mailbox, at the normal pace.

If the answers or the template change after the queue was read, the draft no longer matches and saving returns **draft changed, re-read the queue**. Your agent reads the queue again and reviews the new version.

## Copy notes

A copy note is a lasting rule, such as "never open with a compliment" or "mention the role by name". Save one for the whole workspace or for one playbook with `add_copy_note`, or in the playbook settings under **Copy notes**. Your agent applies them when it reviews.

## Held emails

Separately from review, an email in a playbook campaign is held when one of its variables has no answer yet. Open the enrollment to see why its next email is held. It is retried later and sends once the answer exists.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.