Start with the relationship, not the parcel
For Solstice, Journalist J-014 receives the Mistral jacket because it fits a planned rainwear feature. Creator C-008 receives a Dune tote after sizing and gifting preferences have been checked. The selection reason and relationship notes matter before either send becomes ready. A product gift does not create an obligation to publish, and expected content is context rather than a guaranteed deliverable.
Each send links one contact, one campaign, and one product or pair. Planning, shipping, delivery, and publication notes remain attached to that record. The operator can create a send from the campaign workspace or from the contact drawer, then see the history again from the relationship. That continuity is more useful than an isolated tracking number.
| Send context | Synthetic J-014 example | Synthetic C-008 example |
|---|---|---|
| Reason | Relevant rainwear feature | Product fit and existing creator relationship |
| Product | Mistral jacket | Dune tote |
| Expected content | No promised publication | Optional styling post, never guaranteed |
| Current evidence | Article URL entered manually | No publication observed yet |
| Report treatment | Coverage linked to send | Send remains visible with an unknown outcome |
Use statuses that describe the operational fact
The ledger supports planned, address needed, ready, sent, delivered, posted, no post, and cancelled. When a send moves to sent, delivered, or posted without its matching milestone date, cutePR adds the missing date so report counts remain coherent. Notes are still manual, and a status should be changed only when the operator has evidence for it.
No post is stronger than not yet observed. Use it when the review window has passed and the operator is deliberately recording the absence of a publication. A planned or ready send is still pending. A delivered parcel does not prove that the product was used, and a social or editorial link should become a coverage record rather than living only in delivery notes.
| Status | Meaning |
|---|---|
| Planned | Recipient and product selected; work has not reached address or dispatch readiness |
| Address needed | The next manual task is to obtain or confirm an approved address |
| Ready | Selection and practical details have been reviewed |
| Sent | Dispatch is recorded manually |
| Delivered | Delivery is recorded; publication remains a separate fact |
| Posted | Observed content exists and should be captured as coverage evidence |
| No post | The operator has deliberately recorded no observed publication after review |
| Cancelled | The send will not proceed |
Carry the send into coverage and reporting
When J-014's fictional article appears, the operator creates coverage with its date, media, contact, campaign, product, type, link, quality context, and available evidence. Linking it to the product send is valid only when the same contact, campaign, and products match. This prevents a convenient but false connection between a parcel and unrelated coverage.
The report snapshot can count product sends, sent, delivered, posted, and no-post records; show seeded products and creators; and list linked social coverage where it exists. Unknowns remain part of the report. The operator can distinguish a sent product with no evidence from an observed publication rather than converting every parcel into performance.
- Attach a primary link, screenshot, PDF, clipping, stored file, or manual proof note when available.
- Keep product presence and visual evidence separate from delivery status.
- Record quality and EMV context manually; do not infer value from a shipment alone.
- Freeze a dated report snapshot so later edits do not rewrite what was shared.
A manual PR ledger, not a fulfillment platform
cutePR has no Shopify or ecommerce catalog sync, address collection automation, carrier integration, warehouse workflow, creator portal, automatic social capture, affiliate attribution, payments, or bulk email. Shipping and delivery notes are entered by the operator. Journalist and creator discovery is not supplied as a licensed database.
The private paid beta suits one operator who already has the relationships and wants the sends to stay connected to campaigns, contacts, coverage, and reports. The founder can help migrate an agreed existing ledger. There are no shared seats or client partitions today, and no public price has been chosen; founding customers receive a preferential beta price before a standard price announced in advance.