China Marketing SOP Template
Use a China marketing SOP template to convert an operating process into a clear main path, decision gates, exceptions, owner handoffs, records, and review cadence.
- VERSION
- 2.0.0
- UPDATED
- 2026-08-01
- LICENSE
- MIT
- FILES
- 04
npx skills add fffffrost/market-skills --skill sop-flowchartDocument decisions and exceptions, not just the happy path.
A useful SOP makes coordination observable. It tells a new operator when the process starts, who owns each action, what evidence moves work forward, which exceptions interrupt the path, and what record proves completion.
Set the process boundary
Define the trigger, start state, completion state, included teams, exclusions, frequency, and policy constraints.
Where does this SOP start and stop?Name roles before steps
Identify the accountable owner, operators, approvers, consulted experts, and recipients of each handoff.
Who decides, who acts, and who only advises?Write the main path
Describe actions with inputs, systems, outputs, acceptance checks, and expected timing.
Can a new operator complete the normal case?Expose decision gates
Turn approvals and conditions into explicit yes/no questions with evidence and authority.
What exact condition allows work to proceed?Route failure and edge cases
Add missing-input, rejected-claim, delayed-owner, platform-change, and escalation branches.
What happens when the normal path cannot continue?Preserve the operating record
Specify logs, version ownership, retention, audit trail, review date, and improvement signals.
What proves the SOP ran and shows where it failed?CHINA MARKETING SOP TEMPLATE
PROCESS BOUNDARY
SOP name and version:
Trigger / start state:
Completion state:
In scope:
Out of scope:
Policy or platform constraints:
ROLE MAP
Accountable owner:
Operators:
Approvers:
Consulted experts:
Handoff recipients:
MAIN PATH
Step | Owner | Input | Action / system | Output | Acceptance check | SLA
DECISION GATES
Gate | Yes/no question | Required evidence | Decision owner | Yes route | No route
EXCEPTION ROUTES
Missing input:
Rejected claim or asset:
Owner unavailable:
Platform / policy change:
Emergency escalation:
RECORDS
Execution log:
Approval record:
Source / asset version:
Storage and retention:
GOVERNANCE
SOP owner:
Review cadence:
Change trigger:
Current known gaps:Four details that turn a flowchart into an operating system.
This example explains process design only. Actual approval authority, systems, and retention rules must come from the organization.
Use an approved brief or submitted request, not a vague instruction to start marketing.
Replace 'review content' with the evidence, owner, and yes/no condition required to proceed.
Route missing evidence or rejected claims back to a named owner without silently improvising.
Store the version, approval, output, and exception so the process can be improved rather than remembered.
- Current process
- Rules and exceptions
- Owners and systems
- Required records
- Mermaid source
- Main flowchart
- Rule table
- Handoff notes
Know where the workflow must stop.
- Unconfirmed business or platform rules remain marked as unresolved
- Does not configure automation systems permissions or external workflows
- Regulated or high-risk processes still require domain review
These conditions distort the result.
- Platform approvals and agency handoffs are hidden inside generic steps
- Dense scoring and exceptions are forced into the main graph
- Chinese labels are vague or too long for frontline execution
How the skill works
- 01Separate the main path rules and handoffs
- 02Normalize steps by owner and output
- 03Draw only operational branches
- 04Externalize dense rules and exceptions
- 05Validate every local handoff
- 06Deliver maintainable source
Inspect the source before installing.
Instructions, templates, compatibility, and dependencies remain in one open directory.
- ├─SKILL.md
- ├─agents/openai.yaml
- ├─listing.yaml
- ├─references/sop-template.md