People & HR

How to manage benefits enrollment as Small Law and Accounting Practices

People & HRFor Small Law and Accounting Practices3 apps11 steps~22 min to set up

Benefits enrollment at a six-attorney or four-CPA practice is a once-a-year scramble that falls on whoever has the most patience. You're collecting election forms over email, chasing the two people who haven't responded, manually cross-checking against your Paylocity or ADP payroll records to make sure deductions match what employees actually chose, and updating the carrier portal by hand. The broker sends a spreadsheet. Someone opens it on their personal laptop and emails you a different version. Three weeks later, payroll runs with the wrong premium split for one associate and nobody notices until February. There's no system — just a folder in someone's Outlook and institutional memory.

Build this on Starch → See the apps used

People & HRFor Small Law and Accounting Practices3 apps11 steps~22 min to set up

Outcome

What you'll set up

A benefits enrollment tracker that pulls current employee records from Paylocity or ADP and shows you exactly who has responded, who hasn't, and what each person elected — all in one view instead of a shared spreadsheet

Automated email follow-ups through Outlook that go out on a schedule to employees who haven't submitted their elections, with reminders that escalate as the deadline approaches

A post-enrollment audit dashboard that flags any mismatch between what was elected and what's loaded in payroll, so you catch errors before the first deduction runs

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Task Manager Scheduling Knowledge Management

Data sources & config

Starch syncs your Paylocity employee and payroll data on a schedule (employees, payroll runs, benefits, time-off records). Starch connects directly to Outlook on a schedule for drafting and sending enrollment reminder emails. Your benefits carrier portal is automated through your browser — no API needed — for uploading final election files. ADP users can substitute Starch's scheduled sync of ADP workers and org units in place of Paylocity.

Prompts to copy

Build me a benefits enrollment tracker that pulls all active employees from Paylocity, shows each person's enrollment status (not started / in progress / submitted), their elected plan tier, and their dependent count. Flag anyone who hasn't responded 5 days before the deadline.

Create an automated email sequence through Outlook that sends a reminder to any employee who hasn't submitted their benefits election by Day 7 of open enrollment, a second reminder on Day 12, and a final urgent notice on Day 14 with the deadline in the subject line.

Build a post-enrollment audit view that compares submitted elections against what's currently in Paylocity payroll records and highlights any discrepancies in plan type, premium tier, or dependent count.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Paylocity (or ADP) to Starch — Starch syncs your employee roster, benefits data, and payroll run history on a schedule so the enrollment tracker always reflects your current headcount, including any mid-year hires or terminations.

2 Connect Outlook to Starch — Starch syncs your Outlook messages and calendar on a schedule, which lets the enrollment automation send follow-up emails from your actual firm address and track who has replied.

3 Tell Starch to build the enrollment status dashboard: describe in plain language that you want a table of all active employees, their current benefits election status, plan tier chosen, dependent count, and a red flag for anyone past the response deadline.

4 Load your carrier's plan options and premium rates into Starch as reference data — paste the broker's spreadsheet into a Starch knowledge base so the agent can validate elections against eligible plans and correct premium amounts.

5 Set up the automated reminder sequence: tell Starch which Outlook email address to send from, what the open-enrollment window is, and what the escalation schedule looks like. Starch drafts the emails and sends them on your trigger dates.

6 As employees submit elections (via email, a form, or directly into the tracker), Starch updates their status in the dashboard in real time — anyone who replies to the Outlook reminder thread gets their status flipped automatically.

7 One week before the deadline, run the mid-enrollment audit: ask Starch to show you everyone still marked 'not started' and generate a list with their direct manager and personal email so you can make calls if needed.

8 After the election window closes, Starch compares the final elected benefits against what's currently recorded in Paylocity and surfaces a discrepancy report — wrong plan tier, missing dependent, incorrect premium split.

9 Use the discrepancy report to correct records in Paylocity before payroll runs. For carrier portal uploads, Starch automates the file submission through your browser — navigating to the portal, logging in, and uploading the election file — no API required.

10 After the first payroll cycle post-enrollment, Starch pulls the payroll run data from Paylocity and checks that actual deductions match elected premiums for every employee. Any mismatch triggers an alert to whoever manages payroll at the firm.

11 Archive the enrollment records in Starch's knowledge base — elected plans, effective dates, dependent information — so when an employee asks in March what they elected in November, you can answer in thirty seconds instead of digging through email.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

November 2025 Open Enrollment — Six-Attorney Firm

Sample numbers from a real run

Employees eligible for enrollment	11
Responses received by Day 7	7
Automated reminders sent by Starch (Days 7–14)	4
Responses after automated reminders	3
Manual follow-up calls needed	1
Paylocity mismatches caught in post-enrollment audit	2
Estimated hours saved vs. prior year manual process	9

Your open enrollment window opens November 1 for a January 1 effective date. Starch pulls 11 active employees from Paylocity — six attorneys, two paralegals, an office manager, a bookkeeper, and a part-time legal assistant. By Day 7, seven have submitted elections. Starch sends automated Outlook reminders to the four who haven't, and three respond within 48 hours. One associate — a second-year who is traveling for a deposition — needs a direct call; you see her flagged in the dashboard and call her the same day. After the window closes, the audit view surfaces two issues: one paralegal elected the PPO family tier but Paylocity still shows employee-only from last year's enrollment, and one attorney's HSA contribution amount doesn't match what he submitted. Both are corrected in Paylocity before the December 15 payroll run. Starch automates the carrier portal upload through the browser, navigating to the benefits portal, logging in, and uploading the finalized election file — saving the office manager about two hours of manual data entry. The whole cycle took roughly three hours of human attention instead of the twelve it took the prior November.

Measurement

How you'll know it's working

Enrollment completion rate by deadline (target: 100% submitted before carrier cutoff date)

Time from enrollment window open to full response — days to get every employee on record

Payroll deduction accuracy rate after first post-enrollment payroll run (errors per employee)

Hours of administrative staff time spent on benefits enrollment vs. prior year

Number of mid-year benefits corrections submitted to carrier (proxy for enrollment quality)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Paylocity native benefits module

Paylocity has a built-in enrollment workflow, but it requires employees to log into the portal themselves, doesn't draft follow-up emails from your firm's Outlook address, and can't cross-check elected benefits against payroll deductions after the fact without manual report exports.

ADP Workforce Now benefits administration

ADP's benefits tools are comprehensive for large employers but configured by your ADP rep, not by you — building a custom enrollment tracker or audit view requires a support ticket, not a plain-language description.

Shared spreadsheet + email (current state)

Free and familiar, but version-controlled by whoever saved it last — no automated reminders, no audit trail, and no way to catch a mismatch between what was elected and what payroll actually runs.

Gusto (live-query via Starch's integration catalog)

Gusto is a cleaner HR platform for small firms, but its benefits enrollment is a self-contained flow — you can connect Gusto from Starch's integration catalog and query it live, though Gusto doesn't offer the same scheduled-sync depth as Paylocity or ADP for post-enrollment audit work.

BambooHR benefits tracking

BambooHR has a benefits tracking module and is reachable from Starch's integration catalog, but it's a separate HR system you'd have to maintain in parallel with QuickBooks and your practice management tools — more accounts, more reconciliation.

On Starch RECOMMENDED

One platform — task manager, scheduling, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

We use ADP, not Paylocity. Does this work?

Yes. Starch syncs your ADP workers, org units, and pay statements on a schedule — the same way it handles Paylocity. The enrollment tracker and post-enrollment audit view work identically; you just connect ADP instead when you set up the integration.

Our benefits carrier doesn't have an API. Can Starch still upload the election file?

Yes. If your carrier portal is web-based — and almost all of them are — Starch automates the upload through your browser. No API needed. Starch logs in, navigates to the file upload screen, and submits the election file. If the portal requires a specific file format, describe that to Starch and it formats the export accordingly.

Does Starch store our employees' health plan election data? Is that a problem for a law firm?

Starch is not SOC 2 Type II certified today. If your firm has strict data handling requirements around employee health information, that's worth knowing upfront. For many small practices the risk profile is similar to what you're already accepting with a shared spreadsheet in Outlook — but it's an honest question to raise with your malpractice carrier or office counsel before storing PHI-adjacent data in any cloud tool.

Can we use this if our employees are on a spouse's plan or waiving coverage?

Yes — you tell Starch what the possible election statuses are (enrolled in plan A, enrolled in plan B, waiving, covered elsewhere) and the tracker captures whatever each employee submits. Waivers and opt-outs are just another status in the dashboard, and Starch can flag them in the post-enrollment audit the same way it flags plan-tier mismatches.

We also use QuickBooks to track benefit-related payroll expenses. Can Starch connect those two?

Yes. Starch syncs your QuickBooks data on a schedule — invoices, payments, journal entries, and vendor data. You can build a view that shows benefit deductions as they appear in QuickBooks payroll journal entries alongside what was elected in the enrollment tracker, so your bookkeeper isn't reconciling those two sources manually at year end.

What if someone's life event (new dependent, marriage) happens mid-year and they need to update elections?

You'd handle that by running a shorter, targeted version of the same workflow — tell Starch to open an enrollment record for one employee, send them a reminder with a specific deadline, and run a mini-audit once they submit. The same tracker works for qualifying life event changes; it's just a filtered view instead of the full firm.