Saving a package warns that every assigned client gets the update.
Tracker I-9 · Mitratech · 2026
Tracker I-9 helps US employers verify that new hires can legally work. Partners called distributors resell it and set it up for each of their clients, one long form at a time. I designed Distributor Packages: build a complete setup once, then hand it to any client.
Three months after release
~40%less time to onboard a client
~70%fewer setup tickets from partners
1package IDreplaces about 50 configuration arguments

Before: every client set up by hand, about 50 settings at a time. After: assign a package and the client takes on all of it. Drag to compare.
Role
Product Designer
Timeline
Shipped February 2026
Team
PM, Engineering, QA, Services
Status
Shipped. Public documentation ↗
Problem
The problem
Distributors set up every client by hand. Each one needed about 50 settings, spread across several tabs or sent as about 50 API arguments, and nothing could be saved or reused. So similar clients were rebuilt from scratch, mistakes surfaced late in QA, go-lives slipped, and partners kept raising setup tickets.
The solution
Distributor Packages. A distributor builds a complete setup once, saves it as a package, and assigns it to any client in one step. Change the package and every client on it follows.
Before: about 50 settings, set one by one, for every client. After: pick a package and the client takes on all of it.
People
The partner admin who sets up their own clients.
Needs
to get a new client live quickly, without a mistake.
Pain
about 50 settings per client, with nothing to reuse.
And behind every one of them, an employer waiting for their go-live date.
Research
This was an internal admin feature on a legacy product, so there was no lab and no survey. The evidence was already sitting in the brief, the product and the support queue. I pieced it together from four places.
01The brief and API specAbout 50 configuration arguments per client, and a request to simplify the Create and Update Client API.
02The existing screensI rebuilt the current admin and client screens in Figma, which meant going through every tab a setup touched.
03Working sessions with the PMWhere it became clear that a setup changed on one client couldn't be reused anywhere else. Anything reusable had to live at the distributor level.
04Partner ticketsA steady stream of "how do I set this up?" questions landing with support.
A client’s life, before packages
The same work, at every stage. The pain wasn’t any one form. It was doing it again and again.
“The API wasn’t really the problem. The problem was memory. Once a setup was right, there was nowhere to keep it.”
Key insight
Approach
CreateClient()
About 50 arguments, per client
Simplify the Create and Update Client API. A shorter call still means building every setup from scratch.
It changed names three times
One of my Figma frames still says “Create New Configuration Template”.
The questions the brief didn’t answer
The brief said what a package was. It didn’t say what happens around it. These were the questions I had to design answers for.
Constraints
None of this could look new or break anything. The interesting part was designing inside the lines.
Legacy UIReuse the existing Distributor Roles pattern. No new components.
One phaseEverything ships together, in a single release.
No feature flagLive for every new and existing distributor on day one.
Nothing breaksExisting APIs and manual setup keep working exactly as before.
Two permission levelsEvery screen works for Full access and Read only admins.
High stakesThese settings shape how a client’s I-9 process runs, so nothing can change silently.
Design
A package can touch many clients at once, so every screen follows one rule: show the consequence before the click. It works at two levels, and admins can move in and out at every step.
Try it yourself
- 1Assign a packagePress the teal button in Package Details.
- 2Edit the packageUse the dark admin card below. This client should update.
- 3Change one setting by handClick any tick box on the screen. The client leaves the package.
Admin level · System SettingsTracker Pro Package2 clients on it. This client is not one of them.
One package, two places to manage it, and a way in and out at every step.
At the admin level
Build it once
A package uses the same sections, in the same order, as the client page admins already knew: product configurations, passwords, email, site settings, logo and system messages. Each one gets a name and an External Package ID, both unique within the distributor, and shows how many clients use it.
A
Package details: name, status, number of clients and External Package ID.
B
Product configurations: the feature switches every client gets.
C
User password settings: minimum length and character rules.
D
Email settings: from addresses, subject line and company signature.
E
General site settings: data masking, landing pages and Section 1 and 2 options.
F
Client logo: upload or delete it.
G
System messages and instructions, one row per message.
H
Save and Cancel, at the top and the bottom of the form.
Edit it, and say so
Changing a package changes every client on it, so saving one tells the admin exactly that before anything happens.
Retire it carefully
Switching a package off depends on who’s still using it.
01No clients on itOne confirmation.
02Clients on it, another package existsKeep them or move them. Nothing pre-selected.
03Clients on it, nowhere to move themA warning, then a second confirmation.
Tracker says what Inactive means: the package can no longer be assigned through the UI or the API.
The riskier the change, the more the screen asks.
At the client level
Assign or change in one step
On the client page, an admin picks a package and the client takes on all of it. The option only shows when it can work, and Change Package moves a client from one package to another the same way.
Assign Package opens one dropdown listing the distributor’s active packages.
Leave it, cleanly
Not every client fits a package exactly. Edit a setting on a client that has a package, and Tracker says what will happen: the settings update and the link to the package is removed. The assign option comes back, so the client can rejoin later.
Point people to the right place
On the client page, package details are read-only. Hover over them and Tracker tells you where to edit them, instead of just saying no.
87 screens for a “small” feature
Every path above has its own states, and I designed all of them: 87 screens across the admin and client flows.
Errors
A missing name or ID, the wrong length, or a duplicate External Package ID.
Confirmations
After every create, edit, status change and assignment.
Read-only
A view-only version of every package screen.
Keeping the build honest
Owning the client flows
I designed the client-side flows end to end: first assignment, moving between packages, and leaving a package.
Holding the pattern
When a two-over-two panel layout came up, I flagged that it broke consistency with the rest of the page, made the case, and left the final call with the PM.
Design QA
I caught build issues, like elements not aligned with their tab, and pointed to a similar fix we’d already made on System Email Customization.
Impact
The goal was to stop partners rebuilding the same setup and asking us how. Three months after release, both showed up in the numbers.
Measured three months after release.
Learnings
On a legacy product with a fixed UI pattern, the design lived in the rules: what a package controls, what happens when a client needs to differ, and how clearly a change that reaches other clients gets announced. Next time I’d agree how we’ll measure setup time before launch, so the impact shows up in numbers, not just in shipped scope.





