Brainforge Knowledge

linkedin-pre-publish-checklist

5 min read

LinkedIn Pre-Publishing Checklist

Purpose: Prevent sensitive data leaks and ensure quality before publishing any LinkedIn post Status: Active - MUST be completed for EVERY post Created: 2026-02-12 (in response to client data leak incident)

🚨 Critical: Complete ALL Checks Before Publishing

Background: This checklist was created after a sensitive client data leak incident. Every team member MUST complete these five checks before any post goes live on LinkedIn.

Rule: No post gets published without completing this checklist. No exceptions.

Approval routing (leadership)

ScenarioApprover
Leadership / sensitive narratives (normal operations)Robert, unless another owner is explicitly named on the calendar row
Robert would approve but Robert is OOOLisa (fractional CMO)

Post a short note in #marketing when approval routing changes for the week (for example, Robert OOO).

âś… The Five Mandatory Checks

1. Client Confidentiality Check

Ask yourself:

  • Does this post mention ANY client names?
  • Does this post include ANY client-specific data (metrics, revenue, team size, etc.)?
  • Does this post include ANY screenshots or images with client information?
  • Could someone identify the client from context clues (industry + size + problem)?

Action Required:

  • If YES to any: Get explicit written client permission before publishing
  • If client asked to remain anonymous: Remove ALL identifying information
  • If unsure: Ask Lisa or Robert (see Approval routing above) before publishing

Common Mistakes:

  • ❌ “Worked with a $50M e-commerce brand using Shopify…” (too specific)
  • ❌ Screenshots with company logos, names, or URLs visible
  • ❌ Metrics that could only apply to one client (e.g., “helped reduce 94.7% of duplicate records”)
  • âś… “Worked with a mid-market retail company…” (appropriately vague)

2. Internal Information Check

Ask yourself:

  • Does this post mention internal processes, tools, or methodologies that are proprietary?
  • Does this post include pricing, rates, or financial information?
  • Does this post mention internal team discussions, Slack messages, or meeting notes?
  • Does this post include screenshots of internal tools (Linear, Notion, Slack, etc.)?

Action Required:

  • If YES to any: Remove the information OR get approval from leadership (Robert, or Lisa when Robert is OOO — see Approval routing)
  • Never share: Pricing, margins, internal processes, proprietary methodologies, internal communications

Common Mistakes:

  • ❌ “Our team spent 40 hours at $200/hour on this…” (pricing info)
  • ❌ Screenshots of Linear tickets or internal Slack messages
  • ❌ “In our internal standup, we discussed…” (internal process)
  • âś… “Our team invested significant time in…” (appropriately general)

3. Sensitive Data Scrub

Ask yourself:

  • Are there any phone numbers, email addresses, or personal contact information?
  • Are there any API keys, tokens, passwords, or credentials (even partial)?
  • Are there any personal details about team members or clients not meant to be public?
  • Are there any file paths, server names, or infrastructure details?

Action Required:

  • If YES to any: Remove immediately. No exceptions.
  • Double-check all screenshots and code snippets for accidental leaks

Common Mistakes:

  • ❌ Code snippets with API keys or tokens
  • ❌ Terminal screenshots showing file paths like /Users/clientname/project/
  • ❌ Email addresses or phone numbers in screenshots
  • âś… Sanitized code examples with placeholder values

4. Professional Tone & Accuracy Check

Ask yourself:

  • Is every factual claim in this post accurate and verifiable?
  • Is the tone professional and aligned with Brainforge brand standards?
  • Are there any typos, grammatical errors, or formatting issues?
  • Does this post represent Brainforge well to prospects and clients?

Action Required:

  • Verify all claims (especially metrics, results, and technical details)
  • Read the post out loud - does it sound professional?
  • Run through grammar/spell check
  • If unsure about tone: Ask a teammate to review

Reference: standards/01-onboarding/AI-quality-checks.md for detailed quality standards

5. Image & Media Check

Ask yourself:

  • Are all images, screenshots, or videos free of sensitive information?
  • Are there any visible watermarks, logos, or branding that shouldn’t be there?
  • Are faces blurred if people didn’t consent to appear in the post?
  • Do all media assets load properly and display correctly?

Action Required:

  • Carefully review EVERY pixel of images/screenshots
  • Use annotation tools to blur/redact sensitive information
  • Test image loading before scheduling
  • For screenshots: Zoom in to 200% and check corners, tabs, notifications

Common Mistakes:

  • ❌ Browser tabs showing client names or internal tools
  • ❌ Slack/notification popups visible in corner of screenshot
  • ❌ File names visible in screenshot that reveal client info
  • âś… Clean, cropped screenshots with no extra information

đź“‹ Quick Pre-Publish Checklist (Print & Check)

Before EVERY LinkedIn post:

[ ] 1. Client Confidentiality - No client names/data without permission
[ ] 2.Internal Information - No proprietary/internal info
[ ] 3. Sensitive Data - No credentials, personal info, or tech details
[ ] 4. Professional Quality - Accurate, on-brand, error-free
[ ] 5. Media Review - All images/videos scrubbed and safe 

Reviewed by: ________________  Date: __________

🚨 What to Do If You Published Something Sensitive

If you realize AFTER publishing that a post contains sensitive information:

  1. DELETE THE POST IMMEDIATELY - Don’t wait
  2. Notify Robert or Lisa (fractional CMO) immediately via Slack or phone — Lisa if Robert is OOO
  3. If client data was leaked: Leadership will contact the client to apologize
  4. Document the incident in knowledge/sales/content/incidents/[date]-incident-report.md
  5. Review this checklist to understand what was missed

Speed matters: The faster you delete, the less damage is done.

đź“š Related Resources

🎯 Remember

When in doubt, DON’T post.

  • If you’re unsure if something is sensitive → Ask first
  • If you’re unsure if you have permission → Get it in writing
  • If you’re unsure if the client would be OK with it → Don’t include it

It’s better to be overly cautious than to leak sensitive information.

Maintained By: Marketing ops (Lisa, fractional CMO; Jadyn, coordinator)
Last Updated: 2026-05-06
Next Review: 2026-06-06 (monthly review)

Graph View

Backlinks