QC CHECKLIST — EVERGREEN ASSEMBLY
For the Evergreen Page Build + Reusable Distribution Set
HOW TO USE THIS CHECKLIST
Two parts. Part 1 (sections 1–9) covers the evergreen page — the HTML build. Part 2 (sections 10–16) covers the distribution content. Run Part 1 first. Don't start Part 2 until the page passes.
PART 1: EVERGREEN PAGE BUILD
1. PREREQUISITES
- [ ] Article: built, QC'd, live
- [ ] Tool 1: built, QC'd, math validated
- [ ] Tool 2: built, QC'd, math validated
- [ ] Briefing interactive: built, QC'd
- [ ] Briefing script: written, synced
- [ ] Briefing landing page: built, launched at least once
- [ ] ⚠️ No core assets are still changing. If any asset is mid-revision, stop.
2. RECOMPOSITION — ARTICLE → EVERGREEN NARRATIVE
- [ ] ⚠️ Article sections are condensed, not pasted. Compare each narrative section to its article counterpart. Is it shorter? Does it point forward to a tool rather than standing alone?
- [ ] Each narrative section between tools is ~2 paragraphs max. Count them. If a section runs 4+ paragraphs, it's stalling momentum.
- [ ] Article conclusion / "what to do" section is removed. The tools replace this. Search for conclusion language — it should be gone.
- [ ] Article CTA / bridge section is replaced by the conversion gap and CTA sections. Not duplicated alongside them.
- [ ] Each narrative section creates a question the next tool answers. Read a narrative section, cover the tool below it. Does the section make you want to use the tool? If not, rewrite.
- [ ] ⚠️ Article visualizations preserved if they do persuasion work. If the original article had React visualizations, interactive elements, or embedded tools that created "aha" moments — are they in the evergreen page? (The Proof Gap rebuild initially dropped them and felt flat.)
3. TOOL EMBEDDING
- [ ] ⚠️ Both tools are fully functional on the page. Click/tap through every question, every input, every result state for both tools. Complete both tools start to finish.
- [ ] Tool intro screens are present. Each tool has its own intro (not just the narrative section above it). Both the narrative setup and the tool intro co-exist.
- [ ] Standalone chrome removed. No standalone nav, footer, header, or logo bar from either tool. The evergreen page's nav/footer handles this.
- [ ] ⚠️ CSS namespaced — no collisions. Inspect both tools' class names. No shared generic classes (
.question,.result,.intro,.progress). All prefixed:calc-,diag-,sf-,prc-, etc. - [ ] ⚠️ JS namespaced — no collisions. Search for all function names. No duplicates across tools. All prefixed:
calcRun(),diagNext(), etc. No shared global variables. - [ ]
var()not used in innerHTML. Search all JS forinnerHTMLassignments. If any containvar(--, replace with hardcoded hex values. - [ ] Tool result bridges intact. After completing each tool, the result screen shows the appropriate offer bridge (diagnostic CTA, $497 offer, or whatever the tool's standalone version showed).
- [ ] Tool results don't break page layout. Complete both tools and verify the result states don't overflow, overlap nav, or push other sections off-screen.
4. SECTION SEQUENCING
- [ ] Arc follows the invariant pattern. Hero → Narrative → Tool 1 → Narrative → Tool 2 → Briefing → Conversion Gap → CTA. No tools after the briefing. No narrative after the CTA.
- [ ] ⚠️ No two adjacent sections share the same background color. Walk through every section. Cream never touches cream. Dark never touches dark. Off-white never touches off-white.
- [ ] Tool sections are dark background. Both of them.
- [ ] Hero, conversion gap, and CTA are dark background.
- [ ] Narrative sections alternate cream and off-white, with dark sections breaking the pattern for visualizations or emphasis moments.
- [ ] Every section earns its place. Read each narrative section. Does it shift understanding or emotional state? If it's filler between tools, cut it.
5. CONVERSION GAP SECTION
- [ ] Three points present. Not two, not four. Three.
- [ ] Each point follows can/can't structure. "You can [X]. You can't [Y] — because [Z]."
- [ ] "Because" clauses name specific diagnostic expertise. Not generic ("because it's hard") but specific ("because you can't see your own assumption gap from inside it").
- [ ] Section leads directly to CTA. No additional narrative between the gap and the CTA section. One bridge sentence or client quote max.
- [ ] Section title present. "The Gap You Can't Close Alone" or campaign-specific alternative.
6. CTA SECTION
- [ ] Calendly link works. Click it. Does it go to the right booking page?
- [ ] Offer framing is campaign-specific. The "what I'm looking at" items reference this campaign's topic, not generic diagnostic language.
- [ ] Three diagnostic focus areas listed. Written in campaign-specific language.
- [ ] Standard elements present: 60 minutes, free, "I run these personally," capacity framing.
- [ ] CTA button is prominent and clickable. Not buried in text.
7. SECTION NAV
- [ ] Nav exists and is fixed/sticky. Scrolls with the page, stays visible.
- [ ] Active section highlights correctly. Scroll through the entire page slowly. Does the nav highlight update at each section boundary?
- [ ] Both tools appear in nav. By name (e.g., "Calculator" not "Tool 1").
- [ ] Briefing appears in nav.
- [ ] CTA appears in nav (labeled "Diagnostic" or "Book").
- [ ] Hero does NOT appear in nav. (It's above the nav.)
- [ ] Conversion gap does NOT appear in nav. (It's a transition, not a destination.)
- [ ] Nav labels are short. Scannable single words or 2-word phrases. No full section titles.
- [ ] Every nav link scrolls to the correct section. Click each one.
8. DESIGN & BRAND
- [ ] ⚠️ No gold text (#b79d64) on cream backgrounds. Use #6b5d3e (dark olive-gold) for all text on light backgrounds.
- [ ] Fonts correct. Cormorant Garamond for headings, Inter for body.
- [ ] Standard footer matches other AOS pages.
- [ ] OG meta tags present. Title, description, image (if applicable).
- [ ] Responsive. Test at mobile, tablet, desktop widths. Tools must be usable on mobile.
- [ ] Scroll animations work. Any IntersectionObserver-based reveals trigger correctly.
9. COPY QC — PAGE
- [ ] ⚠️ No twinning. "It's not X. It's Y." — one instance max, zero preferred.
- [ ] ⚠️ No three-beat parallel structures. Three items with identical sentence structure in a row.
- [ ] No AI formulaic phrases. "Here's the thing," "let's be honest," etc.
- [ ] Numbers consistent. The same case details, dollar figures, and percentages appear in the narrative, the tools, and the conversion gap without contradiction.
- [ ] No fabricated statistics. Every number traces to source material.
PART 2: EVERGREEN DISTRIBUTION SET
10. ANGLE QUALITY
- [ ] ⚠️ Each angle targets a distinct entry emotion. Read every TL post opening line in sequence. If two posts trigger the same feeling, they're the same angle.
- [ ] Minimum 3 distinct angles. Fewer doesn't support 3 campaign cycles.
- [ ] Each angle sourced from actual asset content. Every hook traces to a moment in the article, briefing, tool, or diagnostic.
- [ ] Launch-week angle included. The original posts/emails appear in the set (they worked once).
- [ ] No angle requires knowledge of another angle. Each piece stands alone.
11. LINKEDIN POSTS
TL Posts (6–10)
- [ ] Every post follows Steve Cunningham format. Short lines, white space, no narrative paragraphs.
- [ ] No CTA in any TL post. Article link in first comment only.
- [ ] Image spec for each post. No two identical image formats.
- [ ] Consistent signature block and first comment.
- [ ] ⚠️ First comment links to evergreen page, not standalone article.
Hand-Raisers (3–5)
- [ ] ⚠️ Every keyword is unique. List all keywords — verify no collisions.
- [ ] Each post specifies the tool deliverable.
- [ ] Tool description matches actual tool functionality.
- [ ] Different hook per hand-raiser (not just different keywords).
- [ ] Image or GIF spec for each.
12. EMAILS
- [ ] 2–3 alternates per slot, all 5 slots (10–15 total).
- [ ] Each alternate from a different angle.
- [ ] ⚠️ No date-specific language. Search for: day names, specific dates, "today," "tomorrow," "this morning," "this Wednesday." All replaced with evergreen language.
- [ ] ⚠️ No time-sensitive urgency that doesn't apply. "Briefing comes down at midnight" → capacity-based urgency or removed.
- [ ] Subject lines distinct across versions of the same slot.
- [ ] Every email has a click (Steve's rule).
- [ ] Tool and asset descriptions match actual assets.
13. SUBSTACK NOTES
- [ ] 3 alternates per slot, all 3 slots (9 total).
- [ ] Adapted from LinkedIn, not copy-pasted. Different format, different audience context.
- [ ] No date-specific language.
- [ ] Each note links to something (article, tool, briefing).
14. DM SEQUENCE
- [ ] Base DM structure documented (trigger → qualify → deliver → bridge → offer).
- [ ] One DM 1 opener per keyword.
- [ ] Tool link in DM 1 or DM 2 max. Value delivered early.
- [ ] DM 4 diagnostic bridge is consistent across keywords.
15. CAMPAIGN COMBOS
- [ ] ⚠️ Minimum 3 combos. Each is a full week (2 TL + 1 hand-raiser + 5 emails + 3 notes).
- [ ] Each combo named with one-line description.
- [ ] Each combo tonally cohesive. Read all pieces in sequence — one conversation, not tonal whiplash.
- [ ] No content piece appears in more than one combo (unless explicitly noted).
- [ ] Different keywords per combo.
- [ ] Combos collectively cover at least 3 distinct entry emotions.
16. CROSS-CONTENT CONSISTENCY
- [ ] ⚠️ Tool names consistent everywhere. Search all content for each tool name. No drift.
- [ ] Campaign title/anchor phrase consistent.
- [ ] Calendly link same everywhere and verified working.
- [ ] Evergreen page URL same everywhere. Not the standalone article URL.
- [ ] Numbers consistent across all distribution content and the page.
- [ ] Core claim consistent even when entry angle varies.
17. FINAL ASSET COUNT
- [ ] TL posts: (target: 6–10)
- [ ] Hand-raisers: (target: 3–5)
- [ ] Emails: (target: 10–15)
- [ ] Substack notes: (target: 9)
- [ ] DM openers: (= number of hand-raisers)
- [ ] Campaign combos: (target: 3+)
- [ ] Image/GIF specs: (= TL posts + hand-raisers)
- [ ] Evergreen page: 1 ✓
QC checklist for: Evergreen Assembly (Page Build + Distribution) Companion to: evergreen-assembly-SKILL.md Created: February 2026