FS-DOC-03Operations
Process Runbook / SOP
Content Calendar Management
[YourCompany.com] · Marketing Department · Prepared by FullSpec · [Today's Date]
This runbook is your day-to-day operating guide for the automated Content Calendar Management process. It tells you exactly what the automation handles, where your team still acts, how to respond when something goes wrong, and who to call. FullSpec has built and configured every automated step described here. Your team's only ongoing responsibility in the live process is the editorial review and approval decision inside Notion.
01Process overview
This process covers the full content production lifecycle: from the moment a new content slot is added to your Notion calendar, through brief dispatch, draft submission, editorial review, Buffer scheduling, HubSpot logging, and weekly performance sync. Three agents handle every step except the editorial review itself, which stays with a person. The process runs daily, with weekly planning cycles and a scheduled Monday morning performance pull. Under normal conditions, your team interacts with the automation only through Notion and Slack, and the only action required from you is marking a record Approved or Needs Revision in Notion.
Process name
Content Calendar Management
Trigger
A new content row is added to the Notion database, or a deadline date is reached on an existing row
Final output
A published or scheduled Buffer post, an updated Notion record status, a logged HubSpot campaign entry, and engagement metrics written back to Notion weekly
Agents running
Calendar Orchestrator Agent, Review and Publish Agent, Performance Sync Agent
Tools involved
Notion, Slack, Google Docs, Buffer, HubSpot
Weekly volume
20 to 40 content pieces per month across 3 to 5 channels
Human checkpoint
Editorial review and approval: the reviewer reads the draft and marks the Notion record Approved or Needs Revision
Process Runbook / SOPPage 1 of 4
FS-DOC-03Operations
02Step-by-step: what happens and who acts
What you actually need to do: There is one human step in this process. When you receive a Slack notification that a draft is ready for review, open the linked Google Doc, read the draft, and then return to the Notion content record to mark it either Approved or Needs Revision. That single action in Notion is what triggers the rest of the pipeline. Everything before and after it is handled automatically.
Step
What happens
Who acts
Type
1
A new content row is added to the Notion database or a scheduled deadline date is reached. The automation platform detects the change and starts the workflow for that content record.
Automation
Automated
2
The Calendar Orchestrator Agent reads the topic, format, target audience, channel, and deadline from the Notion record and sends a formatted content brief directly to the assigned writer in Slack.
Calendar Orchestrator Agent
Automated
3
If no draft link has been added to the Notion record by the deadline date, the Calendar Orchestrator Agent automatically sends a Slack reminder to the writer and copies the marketing manager, flagging the overdue item without anyone needing to check.
Calendar Orchestrator Agent
Automated
4
When the writer adds a Google Docs link to the Notion content record, the Review and Publish Agent detects it and sends a Slack notification to the assigned reviewer with a direct link to the document.
Review and Publish Agent
Automated
5
The reviewer opens the Google Doc link, reads the draft, and returns to the Notion record to mark it Approved or Needs Revision. If revision is needed, a message is automatically routed back to the writer in Slack. This is the only step that requires human judgment.
Content Reviewer
Human
6
On approval, the Review and Publish Agent reads the approved copy, the target channel, and the scheduled publish time from the Notion record and creates the post in Buffer, ready to go live at the specified slot.
Review and Publish Agent
Automated
7
The Review and Publish Agent updates the Notion record status to Scheduled and creates or updates the linked HubSpot campaign record with the publish date and channel, so CRM data stays current without anyone logging it manually.
Review and Publish Agent
Automated
8
Every Monday morning, the Performance Sync Agent pulls engagement metrics from Buffer for all published pieces in the Notion database and writes the figures back into the matching content records, making them available for weekly review without any manual export.
Performance Sync Agent
Automated
Process Runbook / SOPPage 2 of 4
FS-DOC-03Operations
03Handling exceptions
The table below covers the most realistic exception scenarios for this process. In most cases the system handles the situation automatically or alerts the right person. Your team only needs to act when a scenario is explicitly marked in the 'What you do' column.
Situation
What the system does
What you do
A Notion content record is missing a required field (for example, no assignee, no deadline, or no channel)
The Calendar Orchestrator Agent cannot generate a complete brief. It skips the record and sends a Slack alert to the marketing manager naming the record and the missing field.
Open the Notion record flagged in the Slack message, fill in the missing field, and save. The agent will detect the completed record and resume the workflow automatically.
A duplicate content record appears in Notion for the same topic and publish slot
The Review and Publish Agent detects matching topic text and scheduled date when attempting to create a Buffer post. It pauses and sends a Slack alert identifying both records.
Review the two Notion records, archive or delete the duplicate, and confirm the correct record is set to Approved. The agent will retry scheduling once only one active record exists for that slot.
A writer submits a draft link but the Google Doc cannot be found or accessed
The Review and Publish Agent attempts to access the linked document and, if the link returns an error or a permission denied response, sends a Slack notification to the reviewer and the writer flagging the broken or restricted link.
Ask the writer to re-share the Google Doc with the correct permissions and update the link in the Notion record. The agent will re-trigger the review notification once a valid link is detected.
A reviewer does not mark the Notion record Approved or Needs Revision within 48 hours of being notified
The Review and Publish Agent sends a second Slack reminder to the reviewer at the 48-hour mark. If there is still no action after a further 24 hours, it escalates a Slack message to the marketing manager.
Check with the reviewer on their availability. If the reviewer is unavailable, update the Notion record yourself or reassign the review field to an available team member so the workflow can continue.
Buffer is unavailable or returns an API error when the agent attempts to schedule a post
The Review and Publish Agent retries the Buffer scheduling request up to three times over 30 minutes using exponential backoff. If all retries fail, it sends a Slack alert to the marketing manager with the content record details.
Log into Buffer directly and schedule the post manually using the copy and timing from the Notion record. Once done, update the Notion record status to Scheduled so the HubSpot sync step can proceed correctly.
The Performance Sync Agent's Monday morning run fails to retrieve metrics from Buffer (for example, due to a token expiry or API outage)
The agent logs the failure and sends a Slack alert to the process owner noting that the weekly performance sync did not complete. Notion records are not overwritten with blank data.
Contact FullSpec support at support@gofullspec.com if the issue persists beyond the following Monday's scheduled run. For a one-off gap, you can note in Notion that metrics were unavailable for that week.
Process Runbook / SOPPage 3 of 4
FS-DOC-03Operations
04Who to contact and when
Fill in the rows marked with placeholders once your team is confirmed. The FullSpec rows are fixed and do not need to be updated. Share this completed table with everyone involved in the content workflow so the right person is contacted for the right issue without confusion.
Role
Name
How to reach them
Process owner (overall accountability)
[Your name]
[Your email or Slack handle]
Marketing Manager (day-to-day calendar management)
[Rep name]
[Rep email or Slack handle]
Content Reviewer (editorial approval in Notion)
[Rep name]
[Rep email or Slack handle]
Notion database admin (field changes, permissions)
[Rep name]
[Rep email or Slack handle]
FullSpec builder (automation configuration and changes)
FullSpec team
support@gofullspec.com
FullSpec support (errors, outages, unexpected behaviour)
FullSpec support
support@gofullspec.com
For any situation where the automation is behaving unexpectedly and the exception table above does not resolve it, contact FullSpec at support@gofullspec.com before making changes to the Notion database structure or the connected tool settings. Changes to field names, database IDs, or API credentials without notifying FullSpec will break the agent triggers.
05Ongoing maintenance
The automation runs without active monitoring under normal conditions. The tasks below are the minimum upkeep needed to keep it reliable. Most take less than 15 minutes.
Whenever Notion field names or database structure changes
Notify FullSpec before making the change. Field name changes in Notion will break agent triggers immediately. FullSpec will update the field mappings in the automation platform to match.
Process owner, with FullSpec support
Whenever a content brief template changes (new format, new required fields, new channel)
Send the updated template to FullSpec at support@gofullspec.com. The brief generation logic inside the Calendar Orchestrator Agent will be updated to reflect the new format.
Marketing Manager, with FullSpec support
Monthly spot-check (first Monday of each month)
Open five recent Notion content records and confirm that status fields, Buffer schedule dates, HubSpot campaign entries, and performance metrics all reflect the correct values. Log any discrepancies.
Process owner or Marketing Manager
Weekly error-log review
Check the Slack channel where system alerts are sent for any unresolved error messages from the previous week. If any alert was not addressed at the time, action it or escalate to FullSpec.
Marketing Manager
When a team member joins, leaves, or changes role
Update the Notion record assignee field conventions and the Slack channel or handle used for brief delivery and review notifications. Notify FullSpec if routing logic needs to change (for example, a new reviewer replaces an existing one).
Process owner, with FullSpec support
Quarterly volume review (every 3 months)
Review the number of content pieces being run through the process per month. If volume has grown significantly above 40 pieces per month or expanded to new channels, contact FullSpec to assess whether agent capacity or Buffer API rate limits need to be reviewed.
Process owner or Operations Director
The single most common maintenance issue for this process is a Notion database field being renamed or reorganised without informing FullSpec. The agents reference specific field names to trigger actions and write data back. Even a minor change such as renaming 'Draft Link' to 'Google Doc URL' will silently break the draft-detection trigger, meaning no reviewer notifications will fire until the mapping is corrected. Always check with FullSpec before editing any field name in the content database.
Process Runbook / SOPPage 4 of 4