What is inside the workbook
The first worksheet is Contacts because that is the sheet cutePR can read during contact import. It contains one row per person or clearly labeled generic editorial contact. The Outlets worksheet keeps publication-level details out of the personal record, while Campaign references records where a contact was considered or used without becoming a second contact database.
The separation remains valuable even if the workbook never enters cutePR. It prevents a journalist's new job from erasing the media organization, and it lets several people point to the same outlet. The sheets use stable IDs in the example so that names can change without breaking every reference.
| Worksheet | Purpose | Import support |
|---|---|---|
| Contacts | One person or generic editorial contact per row | Supported when placed first; recognized fields are mapped during review |
| Outlets | Publication identity, URL, country, language, category, tier, and notes | Reference only; the current parser reads the first worksheet |
| Campaign references | Contact, campaign, selection, last action, and outcome note | Template only; campaign history is not imported by the contact importer |
| Field dictionary | Definitions, allowed values, examples, and ownership | Documentation only |
A field set that survives the next campaign
The template keeps fields narrow enough to review. Contact name, outlet, role, primary email, markets, languages, topics, tier, source, and notes match the fields the current importer reads. Markets, languages, and topics may contain several values in the source file, but cutePR normalizes recognized values into relational links after acceptance.
The workbook also includes a review date and a no-go summary for operator use. Those two columns are valuable working fields but are not imported by the current contact parser. Keep them in the source and move their meaning deliberately during an accompanied migration instead of assuming every template column becomes an app field.
| Field | Example from the fictional file | Decision it supports |
|---|---|---|
| Contact ID | J-014 | Keeps references stable when a name or role changes |
| Name | Riley Martin | Identifies the person; a media-only row becomes a generic editorial contact |
| Outlet | Northline Journal | Links the relationship to a publication |
| Role and topics | Features editor; fashion; business | Explains editorial fit |
| Markets and languages | UK; FR and en; fr | Supports geographic and language selection |
| Source and reviewed on | Prior campaign; 2026-09-10 | Makes provenance and freshness visible |
| Relationship notes | Prefers concise product context | Preserves operator knowledge |
| No-go summary | No unsolicited gifting | Prevents an inappropriate next action |
How to read the filled example
The example has twelve contact rows. J-014 appears once even though the relationship spans two campaigns. Creator C-008 has platform and sizing context in notes rather than a promised-post field. One shared editorial address is labeled as an outlet-level contact. Two repeated emails demonstrate an exact duplicate. Two similar names at different outlets remain separate. One invalid source email is retained as a warning, not treated as a sendable address.
The Campaign references sheet shows selection and activity without presenting outreach as automated. A contact can be shortlisted, exported for Outlook, manually marked as sent, or excluded. Product-send and coverage details belong in their own ledgers; this media-list workbook records only enough context to find the related campaign.
- Filter by topic, market, language, and no-go status before building a campaign list.
- Review stale roles and outlet changes instead of copying every row forward.
- Resolve exact identifiers before judging similar names.
- Keep fictional or redacted data when demonstrating the workbook outside your private workspace.
Use the template safely with cutePR
The current importer accepts CSV, XLS, and XLSX files. For Excel files it reads the first worksheet, so keep Contacts first. The parser recognizes common English, French, and Spanish header aliases, but the import preview remains the source of truth for what was mapped. Unsupported worksheets and working-only columns do not become campaign or outlet records automatically.
Joining the paid founding-customer beta is optional after downloading the template. If you do join, the founder first agrees the migration scope, reviews formats and volume, and uses the validated import flow. You see the preview and reconciled counts before acceptance. This process does not promise a universal rollback or a lossless import of every custom field.