OPS-SOP-017 — Content Publishing & Compliance Sign-Off
1. Purpose
This SOP governs the review, approval, and publishing workflow for all Unity Care Solutions content. It ensures that all external-facing content — regardless of channel — is compliance-reviewed before publication, legal claims are verified, benefit language is accurate, and the DPC/self-funded framing is consistent and defensible. This SOP works in conjunction with OPS-SOP-016 (Ad Creative Review) and covers the broader content publishing ecosystem including AMOS pipeline, social cadence, and broker materials.
2. Scope
Applies to all Unity Care Solutions external-facing content including:
- Blog posts and articles (website)
- LinkedIn organic content (Unity brand and/or sales team posts)
- Website copy updates (any page with benefit language, pricing, or plan information)
- Email campaigns (employer prospects, employee audiences, broker audiences)
- Broker-facing materials (sell sheets, pitch decks, one-pagers, comparison guides)
- AMOS pipeline content (Jay's team — automated scrape → filter → publish workflow)
- Dash Activate ad creatives (see also OPS-SOP-016)
- Press releases or media statements
3. Content Types & Review Matrix
| Content Type |
Operations Reviews |
Tessa Sign-Off Required |
Notes |
| Blog posts |
Yes — accuracy, brand voice |
Yes — if any benefit claims, coverage language, or DPC framing present |
Educational posts with no benefit claims: Operations only |
| LinkedIn content (organic) |
Yes |
Yes — if post references plan benefits, costs, or coverage |
General thought leadership without claims: Operations only |
| Website copy updates |
Yes |
Yes — required for all benefit/plan language |
Coordinate with dev/CMS owner before deploying |
| Email campaigns |
Yes |
Yes — all campaigns referencing plan benefits |
See OPS-SOP-016 for ad-linked email flows |
| Broker materials |
Yes |
Yes — all materials that describe plan design or claims |
Spartan Wealth (Kaylin Konja) may review for accuracy |
| AMOS pipeline content |
Yes — approval gate required |
Yes — any content with regulated claims must clear Tessa before publish |
See Section 7 for AMOS workflow detail |
| Dash Activate ads |
Yes |
Yes — all creatives per OPS-SOP-016 |
Batch submissions encouraged to manage volume |
| Press releases |
Yes |
Yes |
Legal (Dickinson Wright) review also recommended for significant announcements |
4. Pre-Publishing Compliance Checklist
Before any content is published, the submitting team member must confirm all applicable items below:
✓ Compliance Reviewed: Content submitted to Tessa and approval received (or Operations-only review completed for non-regulated content per matrix above)
✓ Legal Claims Verified: All statements about plan benefits, cost savings, or coverage are accurate per the current plan document. No claims are exaggerated, speculative, or not supported by plan terms.
✓ No Unapproved Benefit Promises: Content does not promise benefits, coverage levels, or premium structures that are not currently authorized by the plan. No forward-looking benefit promises without legal sign-off.
✓ DPC / Self-Funded Framing Accurate: DPC services are described accurately and not framed as insurance. Self-funded plan is distinguished from fully-insured products. ERISA plan disclosures are present where required.
✓ Brand Voice Consistent: Content reflects Unity Care Solutions brand standards; no off-brand messaging or unauthorized co-branding.
✓ Approval Logged: Tessa's approval is recorded in the Creative Compliance Log (OPS-SOP-016) or the Content Approval Log as applicable.
✓ Publish Authorized: Operations has given final go-ahead to publish/schedule.
5. Social Media Cadence — Unity Brand
Target cadence: 1 post per day on Unity brand social accounts. A content calendar is maintained by Marketing and reviewed weekly by Operations to ensure the pipeline stays full and approved.
- Marketing prepares content calendar for the coming week (submitted to Operations by Friday for the following week)
- Operations reviews calendar for accuracy, brand alignment, and flags any posts requiring Tessa review
- Posts requiring Tessa review are submitted to Tessa no later than 2 business days before intended publish date
- Approved posts are scheduled in the social scheduling tool
- No post is published without Operations sign-off and, where required, Tessa approval
TBD: Social scheduling tool to be confirmed and documented here. Content calendar template to be created and linked.
6. Dash Activate Workflow Integration
Dash Activate generates approximately 50 creatives per month. All Dash Activate creatives follow the same review process as other ad creatives (OPS-SOP-016), with the following volume management guidance:
- Batch submissions to Tessa weekly (e.g., every Monday) rather than submitting one-at-a-time
- Each creative in the batch must receive individual review — batch submission does not mean batch approval
- Dash Activate team must not launch any creative until individual approval is confirmed in the Creative Compliance Log
- Operations coordinates with Dash Activate to align creative submission cadence with Tessa's 24-hour turnaround window
7. AMOS Pipeline Integration (Jay's Team)
The AMOS content pipeline (managed by Jay's team) automates content scraping, brand filtering, and publishing. The following approval gate is mandatory in the AMOS workflow:
Stage 1 — Scrape Jay's team sources or generates content candidates via AMOS pipeline.
Stage 2 — Brand Filter AMOS applies automated brand filter to remove off-brand, inaccurate, or potentially non-compliant content. Filtered content enters the approval queue.
Stage 3 — Operations Review Operations reviews the approval queue. Approves content that is compliant, accurate, and on-brand. Flags any content with regulated claims for Tessa review before it advances.
Stage 4 — Tessa Sign-Off (when required) Any content with benefit claims, DPC framing, self-funded plan language, or regulatory language is submitted to Tessa via the standard compliance thread before the Publish stage.
Stage 5 — Publish Content cleared at all applicable stages is released to publishing by Operations. Jay's team executes the publish. No content advances to Publish without Operations confirmation.
TBD: AMOS queue access and handoff protocol between Jay's team and Operations to be documented and linked here. Confirm whether Operations has direct queue access or reviews via shared report.
8. Escalation & Non-Compliance
Content published without completing this checklist is a compliance violation. Any team member who publishes unapproved content must immediately notify Operations. The content must be taken down pending proper review. The incident is logged and reported to leadership.
- If a compliance issue is identified post-publication, Operations escalates to Tessa and legal (Dickinson Wright) within 24 hours
- Operations makes the go/no-go call on immediate takedown vs. revision-in-place based on Tessa's guidance
- Repeat violations escalate to leadership for corrective action
9. Related Documents
- OPS-SOP-016 — Ad Creative Review & Legal Approval (Tessa Workflow)
- Creative Compliance Log [link TBD]
- Content Calendar Template [link TBD]
- AMOS Pipeline Documentation [link TBD]