Use one row per recipient, campaign, and product decision
A stable send ID keeps later notes and coverage references attached when a status changes. Recipient ID and type distinguish a journalist, creator, or dual-role contact. Campaign and product or pair explain the purpose of the parcel. Dates show actual milestones instead of asking one overloaded status column to tell the whole story.
The current cutePR ledger supports contact, campaign, product or pair, status, planned, address-needed, ready, sent, delivered, and posted dates, expected content, notes, shipping notes, and delivery notes. The downloadable workbook adds a manual shipping reference, follow-up due date, evidence URL, and evidence state. Those added columns are template-only today and must not be described as native integrations.
| Field group | Columns | Current cutePR support |
|---|---|---|
| Identity | Send ID, recipient ID, recipient type | Contact is linked; template keeps a portable send ID |
| Purpose | Campaign, product or pair, selection reason | Campaign and product or pair are linked; reason can live in notes |
| Workflow | Status and milestone dates | Supported |
| Context | Expected content, notes, shipping notes, delivery notes | Supported as manual text |
| External operation | Shipping reference and follow-up due | Template-only; no carrier or task integration |
| Evidence | Observed coverage URL and evidence state | Create a linked coverage record in cutePR; template columns do not import automatically |
Name the outcome you actually know
Use pending while the send is planned, waiting for an address, or ready. Use sent and delivered for manually confirmed logistical facts. Use posted only when content has been observed, then capture the link and evidence in a coverage record. Use no post after a deliberate review, not immediately after delivery. Use cancelled when the parcel will not proceed.
The template's evidence state adds four reporting distinctions: unknown, not yet published, observed and needs proof, and proven. Unknown means the operator has not finished the check. Not yet published is time-bound, not a final failure. Observed and needs proof means a claim exists but its durable URL, screenshot, PDF, clipping, or note still needs to be attached.
| Evidence state | Meaning | Next action |
|---|---|---|
| Unknown | No completed review | Check the relationship and agreed review window |
| Not yet published | Nothing observed and follow-up is not due | Leave pending; do not classify as failure |
| Observed, needs proof | Content was seen but evidence is incomplete | Add URL, screenshot, PDF, clipping, file, or note |
| Proven | Coverage and supporting evidence are recorded | Link to campaign reporting |
| No publication confirmed | Review completed without observed content | Record no post with date and context |
| Cancelled | Send did not proceed | Keep the reason; exclude it from sent totals |
Read the fictional fifteen-send example
The Solstice workbook contains fifteen decisions across the Mistral jacket, Dune tote, and a paired look. Two are cancelled before dispatch, one needs an address, two are ready, six are sent or delivered without observed content, three have linked evidence, and one is marked no post after a documented review. These figures illustrate states; they are not benchmarks or promised conversion rates.
J-014's article is proven with a fictional URL and a note describing the product presence. C-008 remains not yet published because the agreed observation window is still open. Another creator is no post only after the review date passes. Repeated products remain separate rows because recipient, campaign context, and evidence differ.
| Review queue | Synthetic count | Question |
|---|---|---|
| Pre-dispatch | 5 | Is the selection still appropriate and are the practical details ready? |
| Sent or delivered, no observed content | 6 | Is follow-up due, or is the outcome still unknown? |
| Observed with evidence | 3 | Is the coverage linked to the correct contact, campaign, and product? |
| No post after review | 1 | Is the date and context clear enough for reporting? |
Run one calm weekly review
Filter first for address needed and ready records so parcels do not stall. Then inspect sent and delivered rows whose next review date has arrived. Capture observed coverage with durable evidence, update only supported facts, and leave genuinely unknown outcomes unknown. Finally, reconcile cancellations and no-post decisions before preparing a report.
cutePR can keep this workflow connected in a private per-user workspace, but it does not ship products, collect addresses, read carrier events, monitor social platforms, or send follow-up emails. The paid founding beta includes an agreed migration of an existing ledger and close founder support. Its preferential price lasts during beta; the later standard price is announced in advance, and no public amount is set yet.
- Review address-needed and ready rows.
- Check due sent and delivered rows without assuming a post.
- Move observed content into the coverage evidence record.
- Explain no-post and cancelled decisions before reporting totals.