Mk 095

---
name: mk-095
description: "Annual campaign scheduling. Use when the task requires a campaign calendar that avoids resource conflicts. Apply this method to the specified inputs and verify the deliverable"
---

# MK-095 | Annual campaign scheduling

For a regular chat, upload `packs/mk-095.md`. It includes the shared rules, this method, and required references

## Purpose

This skill delivers: **A campaign calendar that avoids resource conflicts**

Historical seasonality can inform planning but does not guarantee recurrence; do not create paid schedules or publish without user approval

## Required inputs


Available raw records: fixed commitments, flexible campaign dates, product readiness, task dependencies and durations, and owner/resource capacity

## Method Steps

1. Put confirmed holidays/contract dates, product readiness, stock preparation, design, review, publishing durations, and owner capacity on one calendar. Separate fixed deadlines from flexible activities
2. Work backward from launch through required dependencies. An unfinished prerequisite prevents marking downstream work ready. If the latest start has passed, reduce scope, use an available-stock offer, or move a flexible date
3. Resolve shared-resource overload by protecting dated commitments, then applying established annual objectives to flexible work. If objectives cannot determine priority, ask only for that trade-off rather than assuming simultaneous capacity
4. Schedule acquisition and member activities around their actual products, eligibility, and supply. Seasonal attention is a candidate opportunity, not a reason to launch an unready product
5. Propagate delivery, capacity, or commitment changes through affected dependencies, retaining original and revised dates. Preserve unaffected work rather than changing one date while leaving an impossible downstream schedule

## Calculation and Interpretation

Latest start = launch date minus required work and known waiting durations on the actual working calendar. Concurrent load must fit available hours/capacity. Deliver activity, dependencies, resource conflict, retain/reduce/reschedule action, and revision trigger

Check example (hypothetical): production takes five working days followed by two review days, requiring at least seven. With four remaining and no parallelizable steps, use completed assets or move the flexible launch rather than scheduling the full new production

Decision rules authored by ThinkWithBlack, 2026-10-14; original course sources remain below

## Required output fields

| Order | Field | How to complete |
|---:|---|---|
| 1 | Date/phase | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 2 | Business task | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 3 | Product and audience | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 4 | Deliverable | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 5 | Prerequisite dependencies | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 6 | Responsible role | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 7 | Resources | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 8 | Acceptance criteria | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |

## Method sources

Source file: 行銷策略實戰學程Day4-佈局獲利 × 節奏變現 × 轉單收割

Location: Annual

Source basis: extracted from course materials

Source URL: https://docs.google.com/presentation/d/1dq3xqYVUnWvUCpzZKI91yDDOzvkyG0uHy3EOsOjtItA/edit

English translation of source excerpt:

> Why learn to plan an annual schedule