One door for every client.
Automated compliance for Kickstart.
On January 1 PDC opens a client portal that collects the PRQ and census from every client, runs the ~150 Kickstart plans (safe-harbor match, per-payroll-period) through automated compliance, and sends everything else for human review. This page is the record of what the team decided on October 28, what is still open, and who owns what. The full detail is here too — expand any workstream.
JD's direction, repeated throughout the meeting. Everything below sits inside it.
- Scope. The automated compliance lane covers safe-harbor match, per-payroll-period plans only — roughly 150 pre-named Kickstart plans. Everything else goes through the same portal for PRQ and census, then to people.
- Everyone uses the portal. Census collection through the portal is for all clients in January. It would be a failure if January only covered the 150.
- Build for the masses. Do not build for the 1-in-100 scenario. Edge cases take the old-school manual path until an enhancement covers them.
- Ship, don't cook. Something releases January 1 that works in some manner. Fires get put out afterward. JD takes responsibility for mistakes.
- Enhancements layer in later. Clients see the same front door every year while the system improves underneath. Nothing built now has to last five years.
- Structure first. A live master checklist with timeline, owners and deliverables, so nothing gets revisited a hundred times. JD builds it; Brandon makes it shared.
What a client experiences from the email to the result. The client never learns which lane they were in.
The 90/10 picture. If 90% of plans process automatically and the system escalates the other 10% to a person, that is a home run. Clean plans get results; the rest see a professional review message — Brandon's TSA-line analogy: a secondary screening, not a rejection.
Pick your name. Only the items you own show, each marked with the spin-off meeting it belongs to.
Each card is one of JD's spin-off meetings. The headline decisions are on the card; Expand shows every item from the meeting, tagged.
Build work on the related piece waits on the decision. Each is assigned to a spin-off meeting.
| Decision | Who decides | Meeting |
|---|
JD's rule: everything here is possible down the line and nothing here is required for January 1.
This briefing was assembled from the recording of the October 28 meeting (JD, Tony, Brandon, Isela, Sonia). The recording was captured in segments with gaps between them and cuts at the edges, so a few decisions may have been made in moments that were not captured. Where a statement describes how the current system behaves, that is what was said in the room, not something checked against the live build — those items are marked to confirm.
Cut mid-sentence and never resumed in what was captured:
- JD's answer to an advisor asking why a complex plan took 20 days when a Kickstart plan took two minutes
- A thought about ad hoc billing and ad hoc reports from the vendor download
- Brandon's point on the back-end data pipeline and 5500 data
- Whether the demoed PRQ and dashboard were running locally
JD referenced a Word document with his pathway notes and the mockup he demoed; neither is part of this record. If a decision was made in a gap, it is not here — tell Tony or JD and it gets added.
The editable, comment-able version of this record is in the shared doc — ask Tony for the link if you don't have it.