SOP-MKT-calendar-freeze-coordination-v0¶
Status: v0 Draft. This SOP was committed in Michelle's council review implementation guide (2026-04-19) as a P3 authoring requirement. The offer revision cycle pattern it governs has not yet been executed — this is a forward-looking governance document. CMO (Michelle) should review for accuracy against actual workflow intent and promote to v1.0 after council review.
1. Purpose¶
Define how eco|monetize™ coordinates a calendar freeze when offer, messaging, or category positioning is under active revision — preventing conflicting content, outreach, or sales activity from going live during a revision cycle.
Why this exists: When the offer is being revised (pricing, framing, Assessment scope, category positioning), agents across CMO, CRO, and CDO may produce content or initiate outreach that reflects the old offer. A calendar freeze pause window stops new outbound until the revision is ratified and propagated.
2. Trigger Conditions¶
A calendar freeze is initiated when any of the following occur:
| Trigger | Who calls it | Scope |
|---|---|---|
| Offer revision cycle begins (pricing, scope, or framing change) | CMO or CRO → CoS | All outbound content and outreach |
| Category or positioning change going to council review | CMO → CoS | Content production and category.positioning assets |
| CEO-directed messaging hold | CEO → CoS | All external-facing content |
A freeze is not needed for: - Iterative copy improvements on stable offer framing - Internal documentation updates - Campaign execution within the ratified offer framework
3. Freeze Scope¶
During a calendar freeze, the following activities pause:
| Activity | Paused during freeze |
|---|---|
| New content drafts that reference the offer (CMO, category.positioning) | Yes |
| Outreach sequence enrollment (sales.ops, CRO) | Yes |
| Website copy updates touching offer positioning | Yes |
| Investor or partner materials that reference offer | Yes |
| Social/LinkedIn scheduling | Yes |
The following continue during a freeze:
| Activity | Continues during freeze |
|---|---|
| In-flight outreach already in sequence | Yes — do not pull mid-sequence |
| Content drafts that do not reference the offer | Yes |
| Internal ops, SOPs, agent contracts | Yes |
| CEO-initiated communications | Yes (CEO is not frozen) |
4. Freeze Lifecycle¶
Declaration¶
- CMO or CRO identifies offer revision is imminent → notifies CoS via Slack DM
- CoS (Eva) posts freeze declaration to
#exec-checkins:🟡 CALENDAR FREEZE DECLARED | {date} | Reason: {offer revision / positioning change / CEO directive} | Expected lift: {date or TBD} | Owner: CMO - CoS notifies all affected agents via session-dir drops per Section 9 handoff protocol
During freeze¶
- CMO owns the revision process and tracks progress
- category.positioning pauses new asset production, documents in-progress work
- sales.ops pauses new sequence enrollment; flags any time-sensitive outreach to CRO for exception judgment
- CoS includes freeze status in daily CEO Summary until lifted
Lift¶
- CMO declares offer/positioning ratified → notifies CoS
- If council review was the trigger: council review must return Ship consensus before lift is authorized
- CoS posts lift notification to
#exec-checkins:🟢 CALENDAR FREEZE LIFTED | {date} | Ratified offer: {brief description} - CMO dispatches updated offer framing to all affected agents
- All paused activities resume with the ratified framing
5. Exception Handling¶
Time-sensitive outreach during freeze: CRO or CMO may authorize a specific outreach exception with a written rationale. Exception noted in #exec-checkins. This is not a full freeze lift — only the named exception proceeds.
Freeze running >2 weeks: CoS escalates to CEO with a recommendation: extend freeze with justification, or lift with partial ratification. Stale freezes block pipeline.
6. Coordination Points¶
| Handoff | Direction | Mechanism |
|---|---|---|
| Freeze declared | CoS → all agents | Session-dir drop + #exec-checkins post |
| Revision complete | CMO → CoS | Slack DM |
| Freeze lifted + new framing | CMO → all agents | Session-dir handoff report + #exec-checkins |
| Exception authorization | CRO/CMO → CoS | #exec-checkins note |
Open Items for CMO Review (v0 → v1.0 Promotion)¶
- Confirm the trigger list — are there other revision scenarios that should trigger a freeze?
- Define the standard freeze duration expectation (currently "TBD")
- Confirm whether LinkedIn scheduling is paused or just held for review
- Confirm if category.positioning has additional coordination needs not captured here
Council review recommended before v1.0 promotion (affects CMO, CRO, CDO workflows simultaneously).
Change Log¶
| Version | Date | Change |
|---|---|---|
| v0 | 2026-04-21 | Initial draft — sop.manager. Per Michelle's council review implementation guide Section 4. Forward-looking governance; workflow not yet executed in v1.2. Needs CMO review for accuracy. |
Owner: cmo (Michelle) Co-owner: category.positioning Drafted by: sop.manager Status: v0 Draft — needs CMO review, council review, CMO approval Version: v0