LinkedIn Hand Raiser Post — Quality Control
Pre-Build: Status Viability Gate
- [ ] Can complete: "The reader who comments [TRIGGER WORD] is telling their network: ___"
- [ ] That signal is something the reader WANTS their network to see
- [ ] The trigger word is a status badge (signals capability, not need)
- [ ] The body's topic is something the reader can engage with publicly without admitting weakness
If the trigger word or body topic is status-negative, redesign before proceeding.
Pre-Build: Intake Validation
- [ ] CTA type locked (Lead Shark comment trigger / Workshop registration)
- [ ] Asset or event described — what it is, who it's for, what it does
- [ ] Angle locked (from the angle library)
- [ ] Status angle articulated — what does taking the action signal about the reader?
- [ ] Hook locked — above the fold, gap-creating
- [ ] Arc defined including CTA transition point
- [ ] Trigger word designed (Lead Shark) — status-positive, topic-connected, memorable
- [ ] Signature block locked — positioning, not bio, connects to the post's topic
- [ ] Format locked — text post or carousel
Status Design (Check First — This Shapes Everything)
- [ ] Can articulate in one sentence: "The reader who comments/registers is telling their network: ___"
- [ ] The trigger word itself is a status badge — commenting it signals sophistication, not neediness
- [ ] The body gives the reader new vocabulary or a framework they'll use in their own conversations
- [ ] Engaging with this post (like, comment, share) is something the reader wants their network to see
- [ ] The audience segments (if used) are identities the reader wants to claim publicly
- [ ] The signature block reinforces the status transfer for everyone who views the thread
- [ ] The CTA doesn't require the reader to admit weakness, ignorance, or desperation publicly
- [ ] The overall status arc: reader starts curious → learns something → gains capability → takes action that signals that capability to their network
Hook Quality
- [ ] Visible before "See more" fold (~210 characters)
- [ ] Creates a gap the reader must close
- [ ] Uses one of the five types: Scene, Claim, Number, Quote, Pattern
- [ ] Does not start with "I"
- [ ] Specific, not vague
- [ ] No question hooks
- [ ] Clicking "See more" is itself a self-selection act that signals something about the reader
Value Body Quality
- [ ] Value body is 70–80% of the post's word count
- [ ] Delivers genuine insight — works as standalone thought leadership without the CTA
- [ ] Each block does one thing
- [ ] Evidence is specific: numbers, dialogue, concrete details
- [ ] Single through-line
- [ ] No filler blocks
- [ ] At least one section has details that increase dwell time (escalating specifics, dialogue, math)
- [ ] The body is provocative enough to generate substantive comments alongside trigger comments
CTA Quality
CTA Transition
- [ ] 1–2 lines maximum
- [ ] Connects the insight to the asset — not a topic pivot
- [ ] Feels like a natural next step
- [ ] No performative phrases ("Speaking of which," "If this resonated," "Want to go deeper?")
- [ ] Status-positive: "there's a tool for this" not "I have something to sell you"
Lead Shark Comment Trigger
- [ ] Trigger word is ALL CAPS, 1–2 words
- [ ] Trigger word connects to the post's topic
- [ ] Trigger word is status-positive to comment publicly
- [ ] Asset description is one sentence before the trigger line
- [ ] Format: "Comment [KEYWORD] and I'll send it."
- [ ] No additional instructions cluttering the CTA
Workshop / Webinar Registration
- [ ] Specific date and time
- [ ] Format described (live, virtual, etc.)
- [ ] Who it's for — 1–3 segments, each specific
- [ ] If using hybrid approach: "Comment [KEYWORD] and I'll send the registration link" instead of direct link
- [ ] If direct link: accept the 60% penalty, body must be strong enough to compensate
- [ ] If limited seats, actual number stated — no false scarcity
Signature Block
- [ ] Format: "I'm Kathryn Brown. I [positioning] for [audience] so [stakes]."
- [ ] Positioning connects to this specific post's topic
- [ ] Stakes are specific ("$44K decisions" not "better results")
- [ ] Signature is the final line
- [ ] Signature works as passive lead gen — everyone who views the thread sees it
Distribution Architecture
Dwell Time
- [ ] Total length is 1,500–2,600 characters (300–550 words including CTA)
- [ ] Not under 1,300 characters
- [ ] At least one section has escalating specifics or concrete details
- [ ] The body rewards full reading — each block reveals something new
Comment Generation
- [ ] Trigger word will generate volume (it's easy to type, clear what the reader gets)
- [ ] Body is provocative enough to also generate substantive discussion comments
- [ ] Dual-comment potential: some readers will comment on the content AND type the trigger word
- [ ] Social proof snowball: early comments make later commenting feel safe and desirable
Algorithmic Hygiene
- [ ] No external links in post body (60% penalty) — use comment trigger hybrid if link needed
- [ ] No hashtags
- [ ] No emojis
- [ ] No engagement bait phrasing beyond the trigger
- [ ] Post stays in Advisory OS topic lane
- [ ] Content includes genuine human insight
Value-to-CTA Ratio
- [ ] Value body: 70–80% of word count
- [ ] CTA section (transition + trigger + signature): 20–30%
- [ ] If CTA section exceeds 30%, value body needs more substance
- [ ] Post does not read as "ad with a long intro"
Prose Quality
Voice Compliance (voice.md)
- [ ] Advisory OS vocabulary (deploy, build, constraint, capability, system)
- [ ] Avoid list honored (no leverage, synergy, coaching, game-changer, journey)
- [ ] Confident and direct tone
- [ ] Short paragraphs (1–3 sentences)
- [ ] Specific numbers over vague claims
- [ ] No hedge language, no academic phrasing, no marketing hype
Sentence-Level (linkedin-sentence-editor.md)
- [ ] Rule 1: End strong
- [ ] Rule 2: Acronyms defined
- [ ] Rule 3: Economy
- [ ] Rule 4: No repetition
- [ ] Rule 5: Varied word choice
- [ ] Rule 6: 3–5 precision vocabulary upgrades
- [ ] Rule 7: Two-comma max
- [ ] Rule 8: Adverbs killed
AI Pattern Detection (copy-qc.md)
QC posture: fail-first. When a pattern is detected, the default is FAIL. To keep a flagged line, cite a specific golden example (03-golden-examples.md) that uses the same structure and was annotated as acceptable in its Copy QC Notes. No rationalizing — show the precedent or rewrite.
P1 — Must Fix
- [ ] No twinning
- [ ] No mirror reversals
- [ ] No question → silence → revelation arcs
- [ ] No correction-revelation family compounds
P2 — Rewrite Unless Exception
- [ ] No three-beat parallel lists (unless data pattern)
- [ ] No "Not because X. Because Y."
- [ ] No formulaic setups — max 1 per post with evidence
- [ ] No trying-to-be-quotable lines
P3 — Fix If Multiple
- [ ] Max one dramatic single-word beat
- [ ] No rhetorical hand-holding
- [ ] No three+ consecutive same-opener sentences
Compound Check
- [ ] No pattern accumulation
- [ ] Sentence lengths vary
- [ ] Passes read-aloud test
Structural Gate
- [ ] Value body is scene-led, not thesis-led — the insight emerges through narrative, not announced in the opening
- [ ] Structural pattern matches the closest golden example (03-golden-examples.md)
- [ ] If thesis-led: rewrite scene-first before running any other checks
Final Gate
- [ ] Would the writer say every line in a real conversation?
- [ ] Does the body deliver genuine value, or is it a setup for the pitch?
- [ ] Is the CTA transition tight enough that the reader doesn't feel the shift?
- [ ] Would the reader want their network to see them commenting on this post?
- [ ] Does the trigger word work as an identity badge?
- [ ] Does the signature block position effectively for everyone viewing the thread?
- [ ] Will this post generate both trigger comments (volume) and substantive comments (quality)?