Prepare the evidence before generating the report
For the fictional Aster & Rue Solstice campaign, the operator records each article or social post manually. A coverage item can include the media or creator, contact, date, market, campaign, product, type, tier or creator band, quality, product presence, link, EMV context, notes, and supporting evidence. Screenshots, PDFs, clippings, stored files, archive links, secondary URLs, and manual proof notes can strengthen the record.
Report readiness makes gaps visible. A record is ready when it has EMV, a quality score, and either a primary link or at least one evidence item. That definition is an internal completeness check, not a claim that the coverage caused an outcome. Missing proof, missing quality, and missing EMV remain queues the operator can review before freezing a stakeholder version.
| Readiness question | What to inspect |
|---|---|
| Can the item be identified? | Publication or platform, contact, date, market, and type |
| Does it belong in this report? | Campaign, period, product or pair, and audience scope |
| Can somebody verify it? | Primary URL or stored evidence with provenance |
| How was it assessed? | Quality, product presence, sentiment, and transparent notes |
| Is a value estimate present? | EMV amount, justification, source, and rule version where used |
Freeze the question and the numbers together
A report snapshot stores the period and filters with the resulting metrics and rows. It can include coverage count, manually recorded EMV, tier 1 and 2 count, campaign funnel states, evidence gaps, product sends, sent or delivered records, posts, no-post gaps, seeded products, creators, platforms, and social coverage. The available sections depend on the selected scope and the data that exists.
In the Solstice example, one report is for a campaign review, not a general monthly dashboard. Journalist J-014's fictional article is included because its campaign and evidence match. Creator C-008's delivered product send remains a seeding record but does not become coverage while no post is observed. That distinction keeps activity, outputs, and later outcomes from collapsing into one total.
| Report layer | Synthetic example | Limit |
|---|---|---|
| Activity | Contacts selected and product sends recorded | Does not prove attention or publication |
| Output | Observed article or creator post | Requires a coverage record and evidence |
| Quality | Message, prominence, product presence, and relevance | Operator assessment must be explained |
| Estimate | Manually entered EMV | Formula and assumptions must be disclosed |
| Outcome | A measured audience or business change | Include only when a separate source supports it |
Report measures without manufacturing certainty
AMEC's Barcelona Principles 4.0 reject advertising value equivalency and call for qualitative and quantitative analysis across outputs, outcomes, and impact. Its Integrated Evaluation Framework begins with objectives and moves through outputs, out-takes, outcomes, and organizational impact. A coverage total or product-send count therefore answers an operational question; it does not by itself demonstrate reputation, preference, sales, or causal ROI.
cutePR can preserve a manual EMV estimate because some operators need to report it. The amount should sit beside its formula, source, rule version, justification, and limits. EMV is not a replacement for AVE and is not automatically revenue. The current product does not infer reach, scrape engagement, or claim attribution. Where outcomes were not measured, the report should say so plainly.
- Define the stakeholder question and objective before selecting metrics.
- Separate work completed, coverage observed, audience response, and business outcome.
- Use both qualitative and quantitative evidence.
- Label estimates and unknowns; never present them as causal ROI.
Current product and beta boundaries
Coverage collection is manual. cutePR does not provide media monitoring, automatic social capture, scheduled report emails, a public client portal, branded sharing, shared seats, or multi-client partitions. Current operator-facing and generated output is English by default; localized acquisition copy must disclose any English-only export labels rather than relabeling a sample as a shipped French export.
The paid founding-customer beta provides one private workspace per user, personal onboarding, and help migrating an agreed source. Feedback from real use can influence priorities. The beta price is lower than the later standard price, which will be announced in advance; the amount and cadence are decided with the customer before enrollment and are not published here.