Direct answer: make a PPV send card for one campaign. Record the audience decision already made elsewhere, the exact asset version, one Hook, one Promise, the Selected price supplied by the creator, one CTA, and one Follow-up rule. Read the card from top to bottom and remove any claim the asset cannot fulfil before writing final message copy.
This planner builds one send. It does not provide scripts, decide a price, select a segment, approve a preview, run a launch checklist, or design a resend experiment. Those are separate decisions with separate evidence. The card exists to keep one message internally consistent before it moves into production.
Start only when the asset and intended audience are known. If the audience has not been selected, complete the mass-message segmentation plan first. Do not use this card to reverse-engineer an audience from whatever copy sounds exciting.
Freeze the one-send input block
Give the campaign a unique ID, working name, owner, planned window, audience label, asset ID, asset version, runtime or item count, creator-entered price, and current status. “One send” means one defined message event with one asset promise. A later send should receive a new card or version so the history remains auditable.
Copy the audience label from the approved segmentation record. Do not add sensitive assumptions or invent motives. A useful label describes an observable eligibility rule, such as people who opted into a named content interest, while the underlying process controls who can receive the message.
Lock the asset version before final copy review. If editing changes the media, update the version and repeat the alignment check. A beautifully worded message can still disappoint when it describes a different cut, length, theme, or format from the attached asset.
Write a Hook that earns attention honestly
The Hook is the opening idea, not a complete script. Write it as a short planning statement: the moment, question, contrast, or recognisable interest that gives the recipient a reason to read. It should connect to the known audience context without pretending to know a private feeling or action.
Test the hook with three questions. Would the intended audience recognise why this is relevant? Does the wording remain accurate if read literally? Can the asset deliver on the curiosity created? Remove artificial urgency, invented scarcity, and claims about what “everyone” is doing unless the campaign owner has direct, appropriate evidence.
Keep only one main opening idea. When a hook combines a confession, countdown, challenge, discount, and personal promise, the message becomes hard to scan and harder to evaluate. Extra ideas belong in a parking-lot field, not in the approved card.
Define the Promise from the asset
The Promise states what the buyer should reasonably expect to receive after unlocking. Build it from observable asset facts: theme, format, perspective, number of items, approximate duration when verified, and distinctive moment. Do not fill gaps with implication. If a fact is uncertain, confirm it from the final asset or omit it.
Use a two-column check: “message says” and “asset shows.” Every material claim should have a matching asset fact. If the message says the set contains a sequence, verify that the attached files are complete and ordered. If it describes an extended scene, verify the actual duration against the approved file.
The promise should be specific enough to set expectations and restrained enough to stay true. It is not a list of every visual detail. Choose the one or two aspects most relevant to the audience decision already made.
Attach the exact asset and preview handoff
Record storage reference, filename, version, content type, approved thumbnail or teaser reference, and the reviewer who confirmed the asset. This page does not perform preview quality review. Hand the selected material to the PPV preview checklist for that separate task.
Use status labels such as draft, asset locked, copy ready, preview approved, scheduled, sent, or stopped. A send cannot be “ready” while the asset is still changing. If a replacement file is uploaded, return the card to asset locked and recheck the promise.
Keep the card free of unnecessary media duplicates. A durable reference and version are more useful than downloading copies into several sheets. The operational owner should be able to locate the approved asset without guessing between similarly named files.
Record the creator's Selected price
The price field is an input, not an output of this planner. Record currency, amount, decision owner, selected date, and any approved internal reference. Do not label the amount optimal, normal, premium, or discounted unless another documented process supplies that classification.
Check that the amount in final copy and scheduling tools matches the card. A mismatch is a production defect, not a copy preference. If the amount changes, increment the card version and have the creator or authorised owner reconfirm it.
This planner does not compare prices or estimate demand. Keep those conversations outside the send review so a copy editor does not accidentally become the pricing decision-maker.
Choose one clear CTA
The CTA tells the eligible recipient what action the message invites. It should match the actual platform interaction and the promise on the card. Use one action rather than competing instructions. Supporting text can clarify what unlock contains, but it should not introduce a second campaign.
Read the CTA next to the hook and promise. The opening should lead naturally to the offer, and the CTA should not make a broader claim than the asset description. Avoid pressure based on invented personal knowledge. Clear choice and accurate expectation are enough.
Add a no-send condition: missing asset, inconsistent price, unapproved preview, unresolved audience rule, or policy concern. A card that names stop conditions helps an operator pause cleanly instead of improvising around a defect.
Predeclare one Follow-up rule
A Follow-up rule specifies whether one follow-up is planned, who is eligible, the earliest timing, what event suppresses it, and when the campaign stops. It does not write the follow-up copy or test resend variants. Example structure: “At most one follow-up after the approved interval; exclude unlockers, opted-out recipients, and anyone no longer eligible; stop after the campaign close.”
The suppression rule matters as much as timing. The operator should not ask an unlocker to buy the same item again or continue after a stop state. Pull eligibility from the current approved record at execution time rather than assuming the original list is still correct.
If no follow-up is needed, state “none” and name the reason. Leaving the field blank invites later improvisation. A planned absence is operationally clearer than an ambiguous blank cell.
Run the card review in order
Read aloud: audience, hook, promise, asset facts, price, CTA, follow-up eligibility, stop state. Then ask whether a reviewer unfamiliar with the campaign can explain what is sent, to whom, what is offered, and what happens next. Any unclear answer sends the card back to its owner.
Complete final scheduling and launch controls in the PPV launch checklist. That handoff covers execution readiness; this page ends when the message plan is internally aligned and versioned.
After the send, record factual execution details on the card: actual send time, version used, whether the planned follow-up ran, and any defect. Do not write a success conclusion from one result. The record exists to support later analysis by the appropriate owner.
Copy the PPV send card
Use these fields in order: campaign ID; owner; audience reference; asset ID and version; verified asset facts; Hook; Promise; Selected price and currency; CTA; Follow-up rule; suppression events; stop conditions; preview status; card version; approvals; planned time; actual time; and execution note.
Quality checks: one audience, one attached version, one opening idea, one truthful promise, one selected amount, one action, and at most one declared follow-up path. Reject vague asset references, missing decision owners, unsupported superlatives, and copy that adds facts not present on the card.
Limitations and sources
Use a final handoff note when more than one person touches the campaign. Name the current owner, the next required check, the file version, the unresolved question, and the point after which edits must stop. A copy change after asset approval can alter the promise just as easily as an asset change can invalidate the copy. Reopening the card is preferable to letting two versions circulate.
Archive stopped cards as well as sent cards. The reason may be a missing asset, changed audience decision, inconsistent amount, or campaign cancellation. Keeping that record prevents an abandoned draft from resurfacing later without its context and gives the team examples of useful stop decisions.
Limitations: a complete card cannot predict purchases or make a weak asset relevant. It does not replace policy review, audience selection, price decisions, media QA, scheduling controls, or post-send analysis. It only improves traceability and alignment for one send.
The stage-and-handoff approach adapts the GOV.UK Service Manual guidance to map a user's whole problem and use clear language grounded in needs. Current platform rules should be checked directly in the OnlyFans Terms and Acceptable Use Policy. The card and review sequence are original SirenCY editorial tools.