How should an HR or payroll vendor segment its newsletter list?

A PEO marketer, describing his firm’s list management on an r/HumanResources renewal thread: “We send the same newsletter to a 6-person dental practice and a 200-person manufacturer — half of it doesn’t apply to either of them.” That’s not a copywriting problem. It’s a segmentation problem. The compliance rules that govern a sub-50 employer are categorically different from those that apply above the ACA Applicable Large Employer threshold. Sending identical content across both groups is a fast path to subscriber churn.

This page is part of our newsletter strategy hub and sits alongside the newsletter content guide for HR and payroll vendors. The seven dimensions below cover every structural variable that changes what compliance content applies to a given subscriber. Work through them in order; each one narrows the universe of relevant sends.

How should an HR or payroll vendor segment its newsletter list?

Start with company size, then layer states of operation, industry vertical, plan year, benefit-cycle stage, funding model, and COBRA flag. No single dimension is sufficient on its own. Size determines which federal thresholds apply. State count determines compliance complexity. Industry vertical drives topic rotation. Plan year controls renewal timing. Benefit-cycle stage governs send frequency. Funding model changes which content angle is relevant. COBRA flag adds a DOL-deadline overlay for a specific subset.

The segmentation matrix below maps all seven dimensions with sample segment definitions, content variants, and ESP filter rules. It is not a theoretical exercise. Every row corresponds to a real compliance line that separates what content is required from what is noise.

Why is company-size band a structural segmentation key, not arbitrary?

Company-size band is the most important single variable because federal compliance obligations change at specific headcount thresholds. These are not arbitrary marketing segments; they are statutory cutoffs that determine which laws apply:

• 11+ employees: OSHA 29 CFR 1904.1 requires injury and illness recordkeeping (OSHA 300 logs, 300A annual summary). Below 10, exempt.
• 50+ full-time equivalents: ACA Applicable Large Employer threshold. Employer shared responsibility mandate (IRC § 4980H) kicks in. FMLA also applies at 50 employees within 75 miles.
• 100+ plan participants: ERISA requires an independent audit of the Form 5500 annual report. The audit adds cost and timeline to the filing process. Below 100, the small-plan exemption applies.
• 250-999 and 1,000+: EEO-1 Component 1 filing required at 100+ employees. ACA employer mandate applies with full Section 4980H(b) offer-of-coverage requirements for large employers.

A newsletter that discusses Form 5500 audit preparation sent to a 40-person employer is wasted content — that employer is not required to file an audited 5500. A newsletter that omits ACA 1094-C/1095-C filing guidance sent to a 200-person employer is a service failure. Size band is where segmentation logic begins.

PayrollOrg’s biweekly state/local payroll newsletter covers all 50 states, DC, and Puerto Rico as a standalone compliance product — a model that only works because the content is already segmented by jurisdiction. The same logic applies to size bands: segment first, then produce content that is relevant to the whole segment.

How should plan-year cohorts drive a renewal-touch sequence?

Roughly 70% of small-group health plan business renews on a 1/1 calendar year. The remaining 30% splits across 4/1, 7/1, and 10/1 fiscal-year starts. When a broker or PEO sends renewal content to the full list simultaneously, 30% of recipients receive that content at the wrong time in their benefit cycle. The fix is four distinct cohorts, each receiving a 90/60/30-day renewal-touch sequence timed to their plan anniversary:

• 1/1 cohort: 90-day send in October, 60-day in November, 30-day in December. Overlaps with open enrollment, so content must be OE-specific rather than generic renewal.
• 4/1 cohort: 90-day send in January, 60-day in February, 30-day in March. Highest-risk for being drowned out by ACA filing season noise — keep renewal content separate from 1095-C reminders.
• 7/1 cohort: 90-day send in April, 60-day in May, 30-day in June. Cleanest window in the compliance calendar; renewal content can stand on its own without competing filings.
• 10/1 cohort: 90-day send in July, 60-day in August, 30-day in September. September coincides with the Summary Annual Report (SAR) distribution window, which creates a natural pairing.

Four cohorts cover approximately 95% of small-group renewals. Jackson Lewis’ 2026 pay transparency tracker runs a similar state-segmented cadence for employment law alerts — the model scales from multi-practice law firms down to a three-person broker shop.

What’s the right open-enrollment reminder cadence?

Daily during the OE window, targeting non-actors only — never a full-list blast. This is the rule practitioners know and horizontal newsletter guides consistently miss.

The Selerix open-enrollment research is explicit: reminder emails should target employees who have not yet completed enrollment, not every subscriber on the list. Full-list blasts on day one (when the window opens) and the last day (deadline urgency) are the sends that generate the most unsubscribes. Clients who already enrolled do not need the reminder and experience it as noise. Build the “non-actor” segment by suppressing confirmed enrollees, then send daily to the remainder.

The downstream consent implication for multi-state clients is covered in the multi-state payroll spoke, which covers state-specific consent rules for electronic benefit communications. For the broker-to-HR list (external marketing), the CAN-SPAM 10-business-day opt-out rule and the HIPAA marketing authorization question below are the primary compliance considerations.

Why are internal-comms benchmarks (67% open) misleading for broker-to-HR newsletters?

The 67% open rate figure comes from ContactMonkey’s 2025 Internal Email Benchmark Report, which analyzes newsletters sent by HR departments to their own employees — internal communications. The 195,000+ campaigns in that dataset are company-to-staff sends, not business-to-business marketing. Employees open HR emails because their employer requires or expects it. That dynamic does not apply to broker-to-HR-contact emails, which land in a professional’s already-crowded inbox alongside vendor pitches from every benefits, payroll, and HR tech company in the market.

The correct external benchmark is Mailchimp’s industry-average open rate of 21.33% with a 2.62% CTR. The Business and Finance category runs at 31.35%, which is the upper bound to target. Segmentation lifts performance: Mailchimp’s own segmentation research shows segmented campaigns achieve 14.31% higher open rates than non-segmented sends. Applied to the 21.33% baseline, that puts a well-segmented broker newsletter in the 24-28% range without any other changes. Combine segmentation with a strong content-to-compliance-calendar match and the 28-32% band is achievable.

As Netchex puts it plainly: “Brokers who are only visible once a year lose ground to those who position themselves as strategic partners across all twelve months.” A segmented newsletter is the mechanism that makes year-round visibility operationally feasible for a small broker shop.

When does HIPAA require written authorization for an HR newsletter?

The HHS HIPAA marketing rule (45 CFR § 164.508(a)(3)) requires written authorization before a covered entity or business associate uses PHI for marketing. For HR and payroll vendors, the trigger is not the newsletter itself — it is the targeting logic used to build the send list.

A benefits broker who handles PHI as a business associate crosses the HIPAA marketing line when it sends communications that target individuals based on their health plan election, claim history, or other PHI. A generic compliance-topic newsletter sent to an HR contact list does not, on its own, require written authorization. But the moment the list is filtered by “employees enrolled in Plan A” or “members with active claims above $X,” the communication becomes marketing under HIPAA and written authorization is required for each recipient.

The practical implication: keep newsletter subscriber lists at the employer-contact level, not the plan-member level, unless written authorization is in place. Broker-to-HR-director newsletters are generally fine. Broker-to-employee newsletters that use PHI-based segmentation are not. For a deeper treatment of the consent layer, see the multi-state payroll spoke.

How does the ERISA electronic-disclosure safe harbor apply to SBC distribution?

ERISA’s electronic disclosure rules create two pathways for distributing plan documents — Summary Benefit Coverage (SBC), Summary Plan Description (SPD), Summary Annual Report (SAR) — by email:

The 2002 safe harbor (29 CFR § 2520.104b-1(c), DOL EBSA Reporting and Disclosure Guide) covers two participant categories: (1) employees who have work email addresses as an integral part of their duties (“wired at work”), and (2) participants who affirmatively consent to electronic delivery. Wired-at-work employees can receive SBC/SPD documents by email or URL link with a notification. Participants not wired at work must affirmatively consent, and that consent must be documented.

The 2020 retirement-plan rule (Federal Register, May 27, 2020) expanded the safe harbor to a notice-and-access model: post the document on a secure website and send a notice to the participant’s email address or mobile number. This pathway does not require affirmative consent for participants who have provided an email address to the plan.

For newsletter purposes, the practical implication is that SBC distribution embedded in a newsletter email satisfies the 2002 safe harbor for wired-at-work employees and consenting participants. A broker who uses a newsletter to distribute the SBC during open enrollment needs to confirm that its subscriber list maps to one of those two ERISA categories, or falls under the 2020 notice-and-access rule.

Which state pay-transparency rules drive segmented content rotations in 2026?

Pay-transparency laws require salary range disclosure in job postings and, in some states, upon employee request. As tracked by Jackson Lewis’ 2026 pay transparency guide, the states currently requiring salary ranges in job postings are: California, Colorado, Hawaii, Illinois (effective January 1, 2025 for employers with 15+ employees), Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, and Washington.

For HR and payroll newsletter segmentation, this list drives a specific content rotation for clients operating in those states. A PEO or HR consulting firm whose clients include multi-state employers in any of these 11 states should maintain a “pay transparency states” tag in its ESP and send pay-transparency content updates to that segment when the law changes — which it does frequently, as Illinois’ January 2025 expansion illustrates. Sending pay-transparency compliance content to a single-state employer in a non-covered state wastes the send and can create confusion about what applies to them.

The same segmentation logic that governs pay-transparency content applies to minimum-wage state alerts, paid-leave mandates, and state-specific wage notice requirements at hire. California, New York, Illinois, Washington, and Oregon generate the most state-alert sends annually. Maintaining a state-operation tag for each of those five, combined with the states-of-operation count (single / 2-4 / 5+), covers the bulk of state-segmented content routing without over-complicating the ESP filter logic.

One dimension that does not appear in the seven-dimension matrix but belongs in every segmentation build is the states-of-operation count as a proxy for content complexity. Single-state clients get state-specific compliance alerts for one state. Clients operating in five or more states are in a different category entirely — they face a rolling calendar of state UI tax rate updates, paid-leave accrual tracking, wage notice requirements at hire (California, New York), and pay-transparency postings across multiple jurisdictions simultaneously. That audience is the one that converts to higher-tier services. Flag them in the ESP and treat them as a premium segment.

For a full treatment of the multi-state compliance communication question, including state-specific consent rules for electronic benefit notices, see the companion spoke on multi-state payroll newsletters.