◆ Acrobat · edit

Mark Proof As Draft

Add a visible footer stamp '[stamp=DRAFT — NOT FOR PRINT — v1.2 7/15/2026]' on every page of the proof so the creative…

2heights
2tasks
1roles do it
See the prompt↓More edit workflows

The same job, four heights

do it · improve it · decide · become
AExecute — “help me do it”Add a visible footer stamp '[stamp=DRAFT — NOT FOR PRINT — v1.2 7/15/2026]' on every page of…+
Add a visible footer stamp '[stamp=DRAFT — NOT FOR PRINT — v1.2 7/15/2026]' on every page of the proof so the creative team knows it’s a work in progress.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.
BImprove — “do it better”Mark the proof clearly: add a faint, full-width header 'DRAFT — NOT FOR PRINT — v1.2…+
Mark the proof clearly: add a faint, full-width header 'DRAFT — NOT FOR PRINT — v1.2 7/15/2026', apply a semi-opaque diagonal page stamp on every page, and insert a one-line version note on the cover sheet explaining what changed since v1.1 so the team sees the purpose immediately.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.

The real tasks

1 of them
Add a visible version note on a proof so the creative team knows it’s a work in progress.

Who does this

1 roles
Music Publisher

Questions people ask

honest answers

Because you rarely think 'I want the redaction tool'. You think 'I have to share this without leaking the client's details'. Start from the need, and the feature finds you.

Real. Every job here was drawn from what people in real roles were actually seen doing in Acrobat — not a feature checklist.

No. Each page gives you a ready prompt you can paste into an AI assistant, plus the plain steps to do it yourself. Start with either — the goal is the finished job, not the tool.