Practical guide / Content Calendar & Performance Workbook 1.0

From the idea to the publication and its latest result.

Connect content, channels, campaigns, approvals and publication records. Review the latest cumulative metrics rather than adding every snapshot, and keep calendar counts visible when several items share a day.

Illustration of a content camera, a wall calendar and a conversation bubble

Your first useful result: Plan the content and approval Follow the first task

Plan the content and approval

Create channels, optional dated campaigns and a Content ID. Keep the stage, owner and deadline explicit.

The linked records and input checks use the same stable IDs and your chosen dates.

Review: Review the labelled results and correct source warnings before acting.

Schedule each publication

Link the content to its channel and planned date. Add the actual date only after publication; update approval and asset references yourself.

The linked records and input checks use the same stable IDs and your chosen dates.

Review: Review the labelled results and correct source warnings before acting.

Review the latest metrics

Enter cumulative views and interactions with an observation date. Calendar shows daily counts and a complete publication list below.

The linked records and input checks use the same stable IDs and your chosen dates.

Review: Review the labelled results and correct source warnings before acting.

Check the assumptions.

  • Save a working copy. Manual entry, with no automatic sync or external connections.
  • Supplied tables have fixed capacities. Extend formulas, tables and validation together before using extra rows.
  • Keep source units and metric definitions consistent. Blank means unknown; enter 0 only for a confirmed zero.
  • Resolve the highlighted input rows before relying on the summary.
  • Uses exact-mode XMATCH. Requires Excel 2021, Excel 2024 or Microsoft 365; older Excel editions are not supported. Native Excel, Google Sheets and Numbers have not been verified.
  • Manual planning and actual cumulative metrics, with no platform API, auto-publishing, forecasts or rights verification.
  • Each publication is one content item on one channel. Reuse the Content ID across separate publications.
  • Supplied rows: 20 channels, 60 campaigns, 300 content items, 400 publications, 400 assets and 600 performance snapshots.
  • Performance uses the latest dated cumulative snapshot per publication. It never adds snapshots as independent activity. Zero views leaves the rate unavailable.

Keep a copy you can return to.

Keep the supplied clean and example files unchanged. Save your own working file with a useful name, such as content-planning-2027-home.xlsx, and keep a dated backup before a large edit. A purchased ZIP is the blank source, not a backup of your entries.

If an input or formula is replaced

Undo the edit while it is still available, or return to a known good backup. If you need a fresh clean file, transfer only your records into its marked input cells and follow the setup guide again. Do not paste whole sheets over the supplied formulas, validations or reference lists. Check IDs, units, dates and linked results against the example before relying on the copy.

When the supplied rows are full

20 channels · 60 campaigns · 300 content · 400 publications · 400 assets · 600 performance. Calculation ranges and validations have fixed capacities. A new row below a table does not prove that every linked result includes it.

For a separate period, project or volume, preserve the old workbook and start a named clean copy. If records must carry forward, record exactly which inputs you transfer, preserve their references and compare the opening and closing figures. Avoid copying historical activity as both an opening amount and a new movement. There is no automatic migration between files.

Inspect the workbook before you choose.

View its real sheets and a fictional calculation example.

Explore Content Calendar & Performance Workbook

Written for version 1.0. Examples describe the supplied workflow; they are not customer results.