Design a content production workflow with clear approvals
A content workflow from idea to publish with stages, owners, turnaround times, and approval rules.
The prompt
Help me design a content production workflow for my team.
Team and roles: [writers, editors, designers, SEO, SMEs, legal, approvers - in-house or freelance]
Content types and monthly volume: [e.g. "8 blog posts, 4 newsletters, 40 social posts"]
Tools we use: [e.g. project board, docs, CMS, scheduling tool]
Current pain points: [e.g. "drafts stall in review", "legal sees things too late"]
Approval requirements: [who must sign off on what]
Design:
1. Stages from idea to publish to report (e.g. idea, brief, draft, edit, SME review, design, compliance, final approval, scheduled, published, promoted).
2. For each stage: owner, input, output, definition of done, target turnaround.
3. A RACI table for the main roles.
4. Approval rules by content risk: what needs only an editor vs. SME, legal, or executive review.
5. Rules that stop bottlenecks: review deadlines, maximum revision rounds, what happens if a reviewer is silent.
6. A board or tracker setup: columns, fields, and status names.
7. A backwards timeline for a typical piece and for a rush piece.
Return the workflow as a table plus a one-page summary I can share with the team.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- e.g. "8 blog posts, 4 newsletters, 40 social posts"
- e.g. project board, docs, CMS, scheduling tool
- e.g. "drafts stall in review", "legal sees things too late"
- who must sign off on what
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Find unnecessary approvals in a workflow and simplify sign-offsReviews every approval in a workflow, flags the ones that add delay without reducing risk, and proposes a leaner sign-off design with thresholds.
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Request additional fees when an architecture or engineering client changes scopeAn additional services request that ties a client's change to the contracted scope, phase, and fee, before the extra work starts.
- Write service levels and penalties for an outsourced serviceMeasurable service levels, reporting, and remedies for an outsourced provider like logistics, cleaning, IT support, or a call center.