L3 operators ship 30-50 pieces of output per week across newsletter + YouTube + podcast + course + 5 social platforms (per Lesson 2.5.3 voice pass at scale). Voice pass on individual pieces (per-piece quality control) catches per-piece AI-default drift. But cross-piece consistency, cross-week brand-voice drift, and quarterly brand-evolution detection require different discipline. The Sunday edit discipline is the weekly 60-90 minute review of everything operator shipped during past week against the brand standard. By May 2026, operators producing 95%+ in-voice output sustainably across 12+ months are running this discipline religiously. Operators who skip Sunday edit experience gradual voice drift visible at quarterly review but not weekly self-assessment - drift that compounds into brand-equity erosion. This lesson covers Sunday edit workflow, integration with voice pass + trust pass + retro disciplines, and failure modes specific to weekly cross-piece review.

Why Sunday Edit vs. Per-Piece Voice Pass

Per-piece voice pass (Lesson 2.5.3) catches: AI-default constructions, em-dash overuse, hedge density, specificity gaps, emoji audit, generic engagement-tag closes. Per-piece scope.

Sunday edit catches: cross-piece voice drift, brand-voice evolution patterns, cross-platform register consistency, persona-targeting accuracy, recurring voice patterns operator may not notice piece-by-piece, voice corpus refresh signals.

Different scope. Per-piece voice pass = 90-second discipline. Sunday edit = 60-90 minute weekly discipline. Both required for 95%+ in-voice output sustained across 12+ months.

The Sunday Edit Workflow (60-90 Min Weekly)

(1) Output inventory (10-15 min): Pull everything shipped past week: newsletter issue, podcast episode + 12 derivative outputs (Lesson 3.3.1), course module if applicable, social posts queue + matrix outputs, cohort communications, paid-tier exclusives. Aggregate ~30-50 pieces.

(2) Cross-piece voice consistency review (25-40 min): Read pieces in batches by surface (all newsletter + matrix posts from week; all podcast + Castmagic derivatives; etc.). Audit for: voice consistency across surfaces (does newsletter voice match LinkedIn matrix post?); brand-voice evolution (am I drifting from operator brand?); register consistency (each platform appropriate register per Lesson 2.5.1 matrix?); persona-targeting accuracy (correct persona-fit per Lesson 3.6.2?).

(3) Brand standard verification (15-25 min): Check pieces against brand-memory document (Lesson 3.1.3 Surface 8) + audience-segment thesis + verified-claims store usage. Identify any pieces drifting from established brand voice or thesis. Flag for next-week corrective signal or operator self-correction.

(4) Voice corpus refresh signals (5-10 min): Identify pieces from past week strong enough to add to voice corpus (Lesson 2.5.3 quarterly refresh). Note which pieces represent operator's current evolving voice; queue for quarterly corpus update.

(5) Next-week corrective signal (5-10 min): Document patterns identified in Sunday edit; brief note for self about adjustments needed in next week's output. Examples: 'Newsletter voice drifted toward AI-default em-dash overuse this week; recalibrate', 'LinkedIn matrix posts not landing persona target; adjust persona-of-focus next week.'

Integration With L2-L3 Quality Disciplines

Sunday edit closes the operator-side feedback loop alongside L2 Ch7 trust pass (Lesson 2.7.3) audience-side feedback loop:

Voice pass per-piece (Lesson 2.5.3): 90 sec per output × 30-50 outputs/week = 45-75 min/week distributed across week.

Sunday edit cross-piece: 60-90 min weekly batched review.

Trust pass top-10 monthly (Lesson 2.7.3): 60-90 min/month audience-side feedback.

Quarterly voice corpus refresh (Lesson 2.5.3): 30-45 min/quarter.

Combined: 90-180 min/week voice pass + 60-90 min/week Sunday edit + monthly trust pass + quarterly refresh = full operator quality control infrastructure. Total operator time across all disciplines: 2-4 hr/week = $20K-$60K annual operator-time investment at $200-300/hr opportunity. Protects $42K-$140K annual brand-voice equity (per Lesson 2.5.3 voice pass economics + Sunday edit added value).

Failure Modes of Sunday Edit Discipline

Skip Sunday edit treating per-piece voice pass as sufficient. Per-piece catches AI-default; doesn't catch cross-piece drift. Drift compounds over 4-12 weeks; visible at quarterly review but invisible weekly. Audience pattern-matches drift before operator does. Fix: Sunday edit is required discipline; not redundant with voice pass.

Edit-as-rewrite trap. Operator turns Sunday edit into rewriting past pieces. 60-90 min review becomes 4-6 hr rewrite session. Past pieces published; can't be rewritten. Sunday edit is signal-generation for next-week corrective; not rewrite session. Fix: review only; document signals; apply forward.

Insufficient time (15-30 min). Operator compresses Sunday edit to 15-30 min during busy weeks. Insufficient to read 30-50 pieces; surface-level scan misses drift patterns. Fix: 60-90 min budget protected; if missed, audit Monday minimum rather than skip entirely.

No corrective signal documentation. Operator notices drift during Sunday edit; doesn't write down; forgets by Wednesday. No corrective signal applied to next-week production. Fix: brief notes documented in operator's Sunday journal or Notion review template.

No voice corpus refresh signal capture. Sunday edit identifies strong pieces representing evolving voice; operator doesn't tag for quarterly corpus refresh (Lesson 2.5.3). Pieces lost to refresh cycle; voice corpus stales. Fix: flag strong pieces explicitly during stage 4 of the workflow.

Operator emotional reactivity during edit. Operator reads past pieces self-critically; emotional reactivity affects assessment quality and drives avoidance of the discipline within 6-8 weeks. Fix: Sunday edit run from observational auditor stance, not critical-author stance; cycle through pieces objectively against the brand standard document.

No brand standard document to measure against. Sunday edit lacks objective criteria; degrades to subjective "feels off" sense. Without the brand standard, two consecutive Sunday edits surface contradictory findings - operator can't apply consistent corrective signal. Fix: brand standard document is the prerequisite, not an optional supplement.

Economic Impact of Sunday Edit at L3 Scale

Per L3 operator producing 30-50 pieces/week across 12+ month operator history:

Time investment: 60-90 min/week × 52 = 52-78 hr/year. At $200-300/hr opportunity = $10K-$23K annual operator-time investment.

Without Sunday edit: per-piece voice pass catches obvious AI-default; cross-piece drift accumulates. By quarter 3-4: detectable brand-voice drift; audience pattern-matches; engagement signals decline 5-15%. Brand-trust erosion (per Lesson 2.5.3) compounds. Estimated annual revenue impact: $15K-$50K (engagement decline + paid-tier retention impact + cohort conversion drop).

With Sunday edit: cross-piece drift caught weekly; corrective signals applied forward; brand-voice equity preserved. Avoided cost: $15K-$50K annually.

Net annual benefit Sunday edit: $5K-$27K (avoided cost minus time investment). Per-hour ROI on Sunday edit: $190-$870/hr. Indirect lift from sustained voice consistency drives paid-tier conversion + retention 10-25% over operators without the discipline - at $80K-$300K creator-business revenue ranges that adds another $8K-$75K/year in brand-quality attributable revenue.

This is L3 Ch7 Lesson 1. Lesson 3.7.2 covers slop detector tools + heuristics that feed into the Sunday edit's brand standard verification step. Lessons 3.7.3 + 3.7.4 cover the SEO-resilient editorial calendar + AI overviews defense that the quarterly roll-up drives.

Two register notes operators commonly slip on. First, Sunday edit is observational, not punitive - operators who use it as a self-critique session burn the discipline within 6-8 weeks (emotional reactivity drives avoidance). The stance is auditor reviewing a system, not author judging their own writing. Second, the "flagged pieces" output is for forward correction, never archive rewriting. Published pieces are published; trying to fix the archive turns 90-min review into 4-6 hr rewriting session and breaks the discipline. Document the pattern, apply the fix to next week, move on.

The Brand Standard Document - Sunday Edit's Objective Criteria

Sunday edit measures pieces against operator's documented brand standard. Without the document the review degrades to a "feels off" subjective sense; with it, the same five-stage workflow produces consistent findings week to week. Document contents:

(1) Voice characteristics: 5-8 specific patterns operator uses (sentence rhythm, characteristic phrases, signature transitions, opening + closing patterns).

(2) Tone register: Where on the casual ↔ formal axis; warm ↔ analytical; direct ↔ exploratory.

(3) Source standards: Primary-source minimum per Lesson 3.2.2; dated timestamps; named-case bias.

(4) What we DON'T do: AI-pattern transitions ("In conclusion"); generic motivational language; unverified statistics; competitor diss.

(5) Failure-mode log: Recurring errors documented + fixes specified, updated from each Sunday edit's findings.

Brand standard built one-time (3-5 hours); refreshed quarterly (1-2 hr). Provides Sunday edit objective criteria; prevents drift over 12-18 months.

Sunday Edit Tooling - Five-Tool Stack

The 60-90 min review runs against a fixed tool stack so the operator doesn't lose minutes hunting for surfaces:

(1) Notion template for weekly Sunday edit (Lesson 3.1.3 SSoT): recurring page with sections for Voice / Fact-check / Engagement / Brand-standard / Planning. Operator fills in real-time during the block.

(2) Beehiiv / Kit analytics dashboard: open / click / reply / unsubscribe per piece. 5-min scan surfaces top + bottom quartile.

(3) Originality.ai (Lesson 3.7.2): slop-detection scan on flagged pieces.

(4) Verified Claims store (Lesson 1.2.4): cross-reference past week's claims; new claims registered; dated claims re-verified.

(5) Voice corpus (Lesson 2.5.3): top-performing pieces from past week added to corpus; expired anchors removed.

Three Quality Gates - Fact-Check vs. Voice Pass vs. Sunday Edit

Sunday edit is non-redundant with the per-piece gates; each catches different failure modes:

Fact-check pass (Lesson 2.7.1): per-piece, pre-send. Verifies numerical claims, dates, named cases against the Verified Claims store. 10-15 min/piece. Catches: hallucinated statistics, outdated company data, drift between Cat 4 verifiable claims and what got drafted.

Voice pass (Lesson 2.5.3): per-piece, pre-send. Verifies operator voice - AI-default constructions, em-dash overuse, hedge density, specificity gaps, emoji audit, generic engagement-tag closes. 90 sec - 2 min/piece. Catches: per-piece AI register slips.

Sunday edit (this lesson): weekly, post-send. Audits all pieces shipped past week against brand standard. 60-90 min/week. Catches: cross-piece voice drift, brand-voice evolution patterns, cross-platform register inconsistency, persona-targeting accuracy across surfaces.

Three gates layered: fact-check + voice pass at draft stage prevent shipping bad content; Sunday edit catches what slipped through and identifies process improvements (failure-mode log updates, brand-standard refinements, voice corpus refresh candidates). Each gate non-redundant; all three required for paid-tier operator quality across 12+ month spans.

Three Nested Review Cadences

Sunday edit is the weekly layer of a three-cadence stack:

Weekly Sunday edit (60-90 min, this lesson): content quality vs. brand standard. Tactical.

Monthly review (60 min): engagement metrics aggregation + idea pipeline health + voice corpus updates. Operational.

Quarterly strategic review (3-4 hr): editorial calendar (Lesson 3.7.3) + persona refresh (Lesson 3.6.2) + RAG ingest (Lesson 3.6.1) + ladder positioning (Lesson 3.4.3). Strategic.

Weekly feeds monthly feeds quarterly. The L4 weekly review with AI co-thinker (Lesson 4.5.3) is a separate Sunday block - strategic business decisions vs. Sunday edit's content-quality scope. Operators running both Sunday blocks (~2.5 hr combined) outperform single-discipline peers by 25-40% on annual revenue.

Quarterly roll-up specifics: weekly Sunday edits aggregate into a ~3 hr quarterly pass covering (1) voice consistency trends - has brand voice held across 13 weeks or drifted? (2) Fact-check failure patterns - is there a recurring claim-source operator should improve? (3) Engagement signal trends - which topic categories trending up/down? (4) Brand standard document updates - what needs refinement based on the quarter's failure-mode log? (5) Process map updates (Lesson 3.1.1) - is the weekly workflow still producing target output? This quarterly pass drives next-quarter editorial calendar (Lesson 3.7.3), persona refresh (Lesson 3.6.2), and RAG ingest (Lesson 3.6.1). Sunday edit is the foundation discipline; the quarterly pass is the strategic adjustment layer that compounds 12-18 month brand-equity gains.

Composite Case: Podcast Operator Catches Quarterly Drift

Composite Case: 80-episode podcast operator + weekly newsletter + matrix posts, 14 months in, no Sunday edit discipline. Starting state: per-piece voice pass running fine; quarterly self-review surprised operator with measurable voice flattening across podcast intros and LinkedIn carousels. Reader feedback ("you sound different on LinkedIn than in the newsletter") had been ignored for 6 weeks. Action: installed 75-min Sunday edit block. Pulled all 12-18 pieces shipped during week into a single Notion review doc; ran voice corpus comparison (12 anchor pieces in Claude Project); flagged 4-6 voice-drift instances per week. Updated voice corpus monthly with 3-4 new in-voice anchor pieces. Week 12 result: cross-platform voice cohesion lifted measurably (reader feedback shifted from "you sound different on X" to "your voice is unmistakable"), one viral LinkedIn carousel attributable to a phrasing the Sunday edit promoted from intuition into corpus. Operator now treats Sunday edit as the brand's quality gate.

Sunday Edit Tool Stack (2026)

Tool	2026 Price	Role in Sunday edit	Notes
Claude Project (Opus 4.6)	$20/mo Pro	Voice corpus comparison + drift detection	Load 12 anchor pieces + week's shipped output
Notion Plus	$10/mo	Weekly review doc + drift log	Template per week
Hemingway Editor	$19.99 one-time	Sentence-rhythm baseline check	Useful but not load-bearing
Originality.ai	$15/mo	AI-default-prose detection signal	Operator judgment overrides tool
ProWritingAid	$10-20/mo	Stylistic consistency across pieces	Tune to operator voice or it nags

The Most Common Failure Mode

The mistake that turns more Sunday edits into productivity theater than any other: treating Sunday edit as a proofreading session instead of a voice-drift detection session. Operator opens the week's shipped pieces and fixes typos, polishes sentences, tweaks one or two lines. Skips the comparison against voice corpus entirely. Result: per-piece quality stays flat, cross-piece drift goes uncaught, voice corpus never refreshes. Six months later the operator's voice has measurably flattened and the Sunday edits log doesn't show why. The fix: Sunday edit is a comparison ritual, not a polish ritual. The operator's job is to scan for drift patterns across the week's pieces, log them, and update the voice corpus monthly. Typos are a per-piece concern that should already be caught during voice pass.

The Sunday edit is the only discipline that catches drift the operator cannot feel piece-by-piece. Skip it for a quarter and the brand voice flattens without warning.

Week 1, Week 4, Week 12: Sunday Edit Compounding

Week 1. First Sunday edit runs 100-120 min (template + workflow setup). 3-5 drift instances flagged.

Week 4. Sunday edit at 70-85 min. Drift log has 12-15 entries; first patterns visible (e.g., LinkedIn carousels drifting more than newsletter).

Week 12. Sunday edit at 60-75 min. Monthly voice corpus refresh has happened twice. Voice consistency measurable across surfaces - reader feedback signals the lift.

Key Takeaways

• Sunday edit discipline is weekly 60-90 min review of past week's 30-50 output pieces; catches cross-piece voice drift + brand-voice evolution + cross-platform consistency that per-piece voice pass (Lesson 2.5.3) doesn't.
• 5-stage workflow: output inventory (10-15 min) + cross-piece voice consistency review (25-40 min) + brand standard verification (15-25 min) + voice corpus refresh signals (5-10 min) + next-week corrective signal (5-10 min).
• Integration with L2-L3 quality disciplines: per-piece voice pass + Sunday edit + monthly trust pass + quarterly corpus refresh = full operator quality control infrastructure.
• Total operator quality control time: 2-4 hr/week at L3 scale = $20K-$60K annual operator-time investment.
• Seven failure modes: skip Sunday edit (per-piece insufficient for cross-piece drift), edit-as-rewrite trap, insufficient time (15-30 min vs. 60-90 min), no corrective signal documentation, no voice corpus refresh signal capture, operator emotional reactivity during edit, no brand standard document to measure against.
• Brand standard document (3-5 hr one-time, 1-2 hr quarterly refresh) is the prerequisite - provides objective criteria across five sections (voice characteristics, tone register, source standards, what we don't do, failure-mode log).
• Five-tool stack supports the workflow: Notion template, Beehiiv/Kit analytics, Originality.ai, Verified Claims store, voice corpus.
• Three quality gates distinguished: fact-check pass (per-piece, claims), voice pass (per-piece, register), Sunday edit (weekly, cross-piece). All three required for paid-tier operator quality across 12+ months.
• Economic impact: without Sunday edit drift compounds to $15K-$50K annual revenue impact (engagement decline + retention + conversion drops); Sunday edit avoided cost = revenue preserved.
• Time investment: 52-78 hr/year × $200-300/hr = $10K-$23K. Net annual benefit: $5K-$27K.
• Per-hour ROI on Sunday edit: $190-$870/hr.
• Three nested cadences: weekly Sunday edit feeds monthly review feeds quarterly strategic roll-up (3 hr) covering voice trends, fact-check patterns, engagement signals, brand-standard refinement, process-map updates.
• L3 Ch7 sequence: Sunday edit (this lesson) → slop detector tools (3.7.2) → SEO-resilient calendar (3.7.3) → AI overviews defense (3.7.4).