Content Production Workflow Map

Northlight Media — Editorial Pipeline from Brief to Published to Distributed

Date: 2026-05-30 · Prepared by: Resolvix · Status: Sample Deliverable
Deliverable type: Operations & Process Design — Workflow Map (~$650)
Industry: Digital Media / Publishing

About this sample. This is one example of what a successful Resolvix deliverable looks like at this scope and type — not a template that every engagement follows. Your expert brings their own expertise and judgment to the work: the structure, the emphasis, which angles they dig into, and how they organize their findings will all vary based on your industry, your specific question, and where the research leads. What stays consistent across every engagement is the standard: analysis grounded in evidence, prioritized recommendations, concrete action steps, and a phased implementation plan. All company names, figures, and scenarios in this sample are illustrative.

Context

Northlight Media is a digital media company with a 45-person in-house editorial team publishing across three verticals (technology policy, climate & energy, and urban development) plus a network of approximately 65 remote contributing writers. Combined output: 280–320 articles per month, with approximately 30% going into paid distribution channels (sponsored amplification, newsletter placements, content partnerships).

This workflow map documents the full content production pipeline from editorial brief creation to post-publication paid distribution — across six stages with 14 discrete handoff points. It identifies current cycle times per stage, cumulative lead time, handoff failure modes, and their downstream consequences.

The workflow was mapped through structured interviews with 18 staff members (editors, writers, fact-checkers, SEO specialists, audience development staff), a 90-day review of production tickets in Asana, and audit of Northlight's CMS (WordPress VIP) publishing logs.

Pipeline Overview

STAGE 1          STAGE 2          STAGE 3          STAGE 4          STAGE 5          STAGE 6
Editorial  ────► Assignment  ────► Writing &  ────► Editorial  ────► CMS &       ────► Distribution
Brief              & Kickoff        Draft            Review           Publishing       & Analytics

2–3 days           1–2 days         4–12 days        3–6 days         1–2 days         Ongoing
                                    (variable)

Total pipeline cycle time (brief to published):
- Target: 10–14 days (standard article)
- Actual average: 17.4 days (based on 90-day Asana audit)
- Range: 7 days (fast-track, staff writer) to 38 days (complex investigation, remote contributor)
- Time lost in handoffs vs. active work: estimated 4.2 days per article on average

Stage 1: Editorial Brief Creation

Duration: 2–3 days
Primary owner: Section Editor
Supporting roles: Managing Editor, SEO Specialist

Process steps

1.1 Story identification. Section Editor identifies story through one of four channels: (a) pitch from staff writer, (b) pitch from remote contributor, (c) editor-originated idea from news monitoring, or (d) scheduled evergreen slot in editorial calendar.

1.2 Viability screen. Section Editor applies informal 3-question screen: Is this differentiated from what competitors have already published? Do we have or can we access the primary sources needed? Does it fit our editorial calendar for the next 3–4 weeks?

1.3 SEO brief. If story passes viability screen, Section Editor requests SEO brief from SEO Specialist. SEO Specialist uses Semrush to identify target keyword cluster, search volume, and competitive landscape. Deliverable: 1-page SEO brief with primary keyword, secondary keywords, estimated traffic potential, and suggested headline angle.

1.4 Brief drafting. Section Editor drafts editorial brief using the Northlight Brief Template (in Asana). Brief includes: story angle, target audience, primary sources to contact, key questions to answer, suggested word count, target keyword cluster, deadline, and compensation (for remote contributors).

1.5 Managing Editor approval. Brief submitted to Managing Editor for approval. Managing Editor checks: editorial calendar fit, resource availability (is assigned writer available?), and no duplicate coverage in-progress. Approval or revision requested within 1 business day.

1.6 Brief publish. Approved brief assigned to writer in Asana. Brief status changes to "Assigned." [HANDOFF 1: Editor → Writer]

Stage 1 failure modes

Stage 2: Assignment & Kickoff

Duration: 1–2 days
Primary owner: Writer (staff or remote contributor)
Supporting roles: Section Editor

Process steps

2.1 Writer brief review. Writer reviews brief in Asana and raises questions or flags within 1 business day of assignment. Staff writers are expected to respond same day; remote contributors are given 24 hours.

2.2 Kickoff conversation. For complex or investigative pieces (>1,500 words, multiple sources required): Section Editor and Writer hold a 20–30 minute kickoff call or async Loom exchange to align on angle and source strategy. For standard assignments: kickoff is async via Asana comments.

2.3 Source outreach initiated. Writer begins source identification and outreach. For articles requiring expert interviews: writer sends outreach emails, typically requesting 30-minute interview.

2.4 Deadline confirmation. Writer confirms draft deadline in Asana. If writer has a conflict with the assigned deadline, this must be raised at Stage 2 — not at Stage 3 when the draft is due. [HANDOFF 2: Editor → Writer confirmed]

Stage 2 failure modes

Stage 3: Writing & Draft Submission

Duration: 4–12 days (high variance; primary driver of total pipeline variability)
Primary owner: Writer (staff or remote contributor)
Supporting roles: Section Editor (check-ins); Fact-Checker (flagged during writing, not after)

Process steps

3.1 Research and interviews. Writer conducts research, secures and conducts source interviews, reviews primary documents. For remote contributors: no oversight during this phase beyond scheduled check-in at the midpoint of the drafting window.

3.2 Mid-assignment check-in. Section Editor sends a brief async check-in at the midpoint of the drafting window (e.g., day 3 of a 6-day window) to assess progress, flag any sourcing blocks, and confirm angle has not drifted from the brief. This step is currently optional and performed inconsistently.

3.3 Draft writing. Writer produces first draft in Google Docs (shared with Section Editor at creation, not just at submission — Northlight's stated policy, inconsistently followed).

3.4 Draft self-review. Writer reviews draft against brief checklist before submission: angle match, word count within 10% of target, all required sources included, SEO keyword naturally included, no factual claims without citation.

3.5 Draft submission. Writer submits draft by updating Asana ticket status to "Draft Submitted" and sharing Google Doc link (or confirming it's already shared). [HANDOFF 3: Writer → Editor]

3.6 Fact-check flagging. For articles with claims requiring verification (data, statistics, quotes from sources not on record): writer flags specific claims in the Google Doc using the Northlight fact-check comment convention ([FC: claim to verify]). Fact-checker is looped in at this stage, not after editorial review.

Observed timing data (90-day Asana audit):

Remote contributor on-time submission rate of 39–51% is the single largest contributor to pipeline variance and overall cycle time inflation.

Stage 3 failure modes

Stage 4: Editorial Review

Duration: 3–6 days (target: 2–3 days)
Primary owner: Section Editor
Supporting roles: Managing Editor (escalation), Fact-Checker, Copy Editor

Process steps

4.1 First read. Section Editor reads draft within 1 business day of submission (current SLA; met ~68% of the time per Asana audit). Editor assesses: angle adherence, source quality, argument structure, length, tone.

4.2 Decision: accept, revise, or kill. Editor makes one of three calls:
- Accept (minor edits): Proceeds to copy edit. Minor line edits made directly in Google Doc.
- Revise (substantive): Section Editor writes revision notes in Google Doc comments and Asana ticket. Returns to writer with specific revision requests. Revision turnaround expected: 2 business days for staff writers; 3 for remote contributors. [HANDOFF 4: Editor → Writer for revision]
- Kill: Managing Editor must approve any kill decision. Section Editor documents rationale in Asana. If remote contributor article: kill triggers kill fee process (Ops team handles payment).

4.3 Revision review. If revision requested: Editor reviews revised draft. Second revision may be requested, but Section Editor must escalate to Managing Editor if more than 2 revision cycles occur on the same piece.

4.4 Fact-check. Fact-Checker works through all [FC:] flags in Google Doc. For each flagged claim: verifies against cited source, marks verified with [FC-OK] or raises a dispute. Disputed claims returned to writer for clarification or source. Fact-check SLA: 48 hours from assignment for standard articles; 72 hours for long-form. [HANDOFF 5: Editor → Fact-Checker; HANDOFF 6: Fact-Checker → Editor]

4.5 Copy edit. Copy Editor performs grammar, style (AP Style + Northlight house style), and headline review. Checks: headline word count (6–12 words), deck/subhead present, all proper names and titles verified, no AP style violations. [HANDOFF 7: Editor → Copy Editor; HANDOFF 8: Copy Editor → Editor]

4.6 Final editor sign-off. Section Editor gives final approval. Asana status updated to "Ready for CMS." [HANDOFF 9: Editor → CMS/Publishing team]

Stage 4 failure modes

Stage 5: CMS & Publishing

Duration: 1–2 days
Primary owner: CMS Producer
Supporting roles: SEO Specialist, Section Editor, Photo/Art team

Process steps

5.1 Content ingestion. CMS Producer copies finalized Google Doc content into WordPress VIP. Applies standard formatting: H2/H3 heading structure, paragraph breaks, pull quotes, internal links (minimum 3 per article per SEO policy).

5.2 SEO optimization. CMS Producer applies SEO metadata in Yoast: meta title, meta description, focus keyword, slug. Cross-references the Stage 1 SEO brief. If SEO brief was not completed at Stage 1 (~22% of articles — see Stage 1 failure modes), SEO Specialist must be looped in at this stage, adding 4–8 hours.

5.3 Image sourcing and tagging. CMS Producer sources or receives hero image (from Photo/Art team for original shoots; from licensed image library for standard articles). Images are resized, alt-tagged, and credit-captioned per policy.

5.4 Internal link audit. CMS Producer uses the Northlight internal link checklist to verify: at least 3 links to related Northlight content, no broken internal links, no links to articles scheduled for deletion.

5.5 Preview and final check. Section Editor reviews article in WordPress preview mode. Checks: formatting, images, all edits from Stage 4 are present, links work. [HANDOFF 10: CMS Producer → Section Editor for preview approval; HANDOFF 11: Editor → CMS Producer for publish]

5.6 Scheduling and publish. Article scheduled for publish at target time slot (current calendar: 7:00 AM, 11:00 AM, or 3:00 PM ET, based on vertical and day of week). CMS Producer sets scheduling and confirms in Asana.

Stage 5 failure modes

Stage 6: Distribution & Analytics

Duration: Ongoing post-publish (structured activities in first 30 days)
Primary owner: Audience Development team (2 FTEs)
Supporting roles: Section Editor, Paid Distribution Manager (for sponsored amplification)

Process steps

6.1 Organic distribution (Day 0 — publish day).
- Article added to vertical newsletter queue (newsletters send Tuesday and Thursday)
- Social posts drafted and scheduled (Twitter/X, LinkedIn; Threads for select verticals) — 3 posts per article, staggered over 7 days
- Article pinned in relevant Slack communities where Northlight has approved presence

6.2 Newsletter inclusion. Audience Development reviews upcoming newsletter and confirms article is queued. Editor writes or reviews newsletter teaser copy (2–3 sentences). Newsletter send triggers within 48–72 hours of publish for most articles.

6.3 Paid distribution decision (Days 1–3). Paid Distribution Manager reviews first-48-hours performance data (pageviews, time on page, scroll depth, social shares). Decision threshold: articles with ≥800 pageviews in first 48 hours AND time-on-page >2:30 are eligible for paid amplification. [HANDOFF 12: Analytics → Paid Distribution Manager]

6.4 Paid amplification (if approved). Paid Distribution Manager activates paid channels:
- LinkedIn Sponsored Content (B2B verticals)
- Newsletter co-sponsorship placements with partner publications (technology policy vertical has 3 active content partners)
- Taboola/Outbrain for broad reach articles (urban development vertical primarily)
Budget per article: $800–$4,500 depending on content type and target audience.

6.5 Content partnership distribution (select articles). Articles flagged for content partnership syndication are submitted to partner publications per partnership agreements. Partnership submissions require Section Editor approval and Managing Editor sign-off for exclusivity windows. [HANDOFF 13: Section Editor → Managing Editor → Partnership contact]

6.6 30-day performance review. Audience Development produces a 30-day performance brief for each article in the paid distribution cohort. Metrics: total pageviews, unique visitors, avg. time on page, social reach, referral sources, estimated email-attributed pageviews, paid amplification ROI (cost per 1,000 qualified readers). Brief shared with Section Editor and Managing Editor. [HANDOFF 14: Analytics → Editorial team]

6.7 Evergreen update flag. At 90 days post-publish, Audience Development flags articles in the top 20% of organic search traffic for consideration as evergreen candidates. Evergreen candidates are added to the editorial calendar for a refresh cycle within 6 months.

Stage 6 failure modes

Aggregate Cycle Time Summary

Handoff delays (time between completion of one stage and the next stage owner picking up the work) account for an estimated 4.2 of the 6.4 excess days. This is not a skills or capacity problem — it is a handoff visibility and accountability problem.

Recommendations

Priority 1 — Implement a mandatory mid-assignment check-in for all remote contributor assignments
The 39–51% on-time submission rate for remote contributors is the single largest pipeline failure. A mandatory async check-in at the midpoint of every remote contributor drafting window (Loom video or structured Asana comment), with a 24-hour response SLA, would surface blocks early enough to either resolve them or reassign. Estimated impact: reduce remote contributor late submission rate from ~55% to ~30%; recover approximately 1.8 days of average pipeline time.

Priority 2 — Require Google Docs to be shared with the Section Editor at draft creation, not submission
This is already Northlight's stated policy. Enforce it technically: the brief template in Asana should include an instruction to create and share the Doc immediately, and editors should reject any draft that arrives as a new share (rather than an already-visible document). This alone catches angle drift before it becomes a full revision cycle.

Priority 3 — Move fact-checking parallel to (not sequential to) editorial review for flagged articles
Currently, fact-checking begins after the editor's first review. For articles with FC flags, loop in the fact-checker as soon as the draft is submitted. Editor and fact-checker work simultaneously. This eliminates the sequential wait (1–2 days) between editorial acceptance and fact-check completion.

Priority 4 — Build a hard Stage 1 gate: no brief advances without SEO brief attached
22% of articles arrive at the CMS stage without a completed SEO brief, forcing the SEO Specialist into a reactive role at the worst possible time. Make the SEO brief a required attachment before a brief can be assigned in Asana. This is a workflow configuration change, not a cultural one.

Priority 5 — Establish a formal 48-hour paid amplification decision window with a standing owner
38% of eligible articles miss the paid amplification window because no one is explicitly accountable for reviewing performance data and making the decision. Assign the Paid Distribution Manager a standing Monday/Wednesday/Friday review of articles published in the prior 48 hours. Create a simple scorecard (pageviews, time-on-page) that triggers automatic consideration — no editorial judgment call needed.

Priority 6 — Begin producing 30-day performance briefs for all paid-amplified articles
61% non-completion on the 30-day brief is a systemic gap. This is the primary mechanism for editorial learning from distribution performance. Assign it explicitly to one Audience Development FTE; build it into their standing weekly workflow, not as an ad-hoc task.

Priority 7 — Track handoff SLAs in Asana, not just stage completion
Current Asana tracking captures when stages are completed, not when handoffs are picked up. Add a "handoff received" timestamp field to each stage transition. This surfaces the 4.2 days of invisible handoff delay and creates accountability for pickup speed.

Action Steps

Implementation Plan

Phase 1: Handoff Accountability (Weeks 1–4)

Objective: Close the visibility gaps that allow 4.2 days of handoff delay to accumulate invisibly.

Milestones:
- Week 1: Asana template updated (SEO brief gate, Doc-at-creation requirement); fact-check parallel loop policy issued; Paid Distribution standing cadence established; 30-day brief assigned
- Week 2: Mid-assignment check-in policy drafted and issued to all remote contributors; handoff timestamp fields added to Asana
- Week 4: First full month of new handoff tracking data collected; baseline comparison to prior 90-day audit

Success criteria — Phase 1:
- SEO brief completion rate at time of assignment: from 78% to 100%
- Paid amplification decision made within 48 hours of publish: from 62% to 90%+
- 30-day performance brief completion rate: from 39% to 90%+

Phase 2: Cycle Time Reduction (Months 2–4)

Objective: Reduce average pipeline cycle time from 18.4 days to 14 days or below.

Milestones:
- Month 2: Mid-assignment check-in data available for first full cohort of remote contributor assignments; measure impact on on-time submission rate
- Month 3: Fact-check parallel loop in place for at least 30 days; measure Stage 4 cycle time change
- Month 4: Full 90-day cycle time audit; compare to baseline

Success criteria — Phase 2:
- Average pipeline cycle time: ≤14 days (from 18.4 days)
- Remote contributor on-time submission rate: ≥65% (from ~45%)
- Stage 4 cycle time: ≤3.5 days average (from 4.8 days)
- Articles requiring >2 revision cycles: ≤10% (from 18%)

Prepared by Resolvix. This sample represents the depth and specificity of analysis delivered at this scope. Actual engagement outputs reflect your specific data, systems, and context.