Running the employee lifecycle as a system
At twenty people, onboarding lives in a Google Doc, offboarding lives in someone's memory, and HR lives in a separate vendor. The work is real and the residue is everywhere.
A partner services firm at twenty people has an HR problem it does not call an HR problem.
There is an HRIS for headcount and payroll. There is a Google Doc titled “New Hire Onboarding” that the last admin updated nine months ago. There is a spreadsheet, somewhere, that lists who has which tool. When someone leaves, three of those four sources of truth get touched, and one of them does not, and the firm finds out six months later when a Slack seat is still billing for a person who has been gone since spring.
The work is real. The system is not.
How the lifecycle actually runs
A new hire starts on a Monday. The hiring manager remembers most of the setup steps. The admin remembers the rest. A Google Doc with twenty-three checkboxes is the source of truth for the first week. By Friday, the new person has access to most of what they need, is missing one tool nobody thought of, and has been added to the spreadsheet that nobody opens unless something is wrong.
A senior consultant leaves three months later. Their manager runs through the offboarding from memory. Email is revoked. The CRM seat is deactivated. Slack is offboarded that afternoon. The expense tool, the analytics tool, the partner portal that the consultant logged into twice, the design tool the firm signed up for last year, all keep billing. The vendor sends a renewal in eight months and a finance person notices.
That is the lifecycle most firms run. Not because anyone designed it. Because nobody decided not to.
The shape of a lifecycle that runs itself
The fix is not heroic. It is treating the same work the firm already does as a system the firm can see.
A real lifecycle has four moving parts.
First, every employee has a status, and the status changes are stamped automatically. Active, onboarding, offboarding, on leave, departed. The status is on the same record that holds the deal owner, the time entries, the role. Not a separate vendor that nobody looks at.
Second, onboarding is a template, not a memory. Role-based, because a sales hire’s first month is not a delivery hire’s first month. Structured across Day 1, Week 1, Month 1, Month 3. The same checklist every time, the same accountability every time, the same visible progress every time.
Third, offboarding is a template too. Standard, senior, contractor. Each carries the right tool-revoke steps so that the seats the firm pays for line up with the people who are still there. The default outcome is pending revoke. The exception is “keep the access” with a documented reason.
Fourth, there is a dashboard. Headcount by status. Lifecycle metrics that the founder can read without asking. Onboardings in the last thirty days. Offboardings in the last thirty days. Average tenure at departure. The offboarding queue as a list, not a memory. CSV when finance asks.
That is the system. Not new work. The same work the firm already does, made visible.
Why this matters before it hurts
Most firms get to this only after the hurt. A vendor renewal lands and the answer to “do we still need this” is “we are not sure who is on it.” A new hire’s first week sets the wrong expectation about how the firm runs. A departure leaves residue for two quarters because nobody owned the closing list.
The cost is not one thing. It is small failures across a lifecycle the firm thinks it is running.
A real lifecycle compresses that. Every status change is a visible event. Every tool grant is on the person, not on a vendor portal. Every offboarding closes the loop the same way. The founder reads the dashboard and the work is done, or the work is not done, and either answer is on one screen.
What PartnerView ships
PartnerView treats HR as part of operations, not as a separate system you bolt on.
Every employee carries a live status. Six role-based onboarding templates, one for each persona the firm hires for, structured across Day 1, Week 1, Month 1, Month 3, so the first ninety days follow a known shape. Three offboarding templates, standard, senior, and contractor, that bulk-transition tool access to pending revoke instead of relying on someone to remember every login. An HR dashboard at the admin level that reads as one screen: headcount by status, lifecycle metrics, the offboarding queue, monthly tool cost, granted seats. CSV export when finance needs the file.
The lifecycle is not a Google Doc. It is the system. And the system is the same one the firm uses for deals, projects, time, and revenue, so the person on a deal record is the same person on the onboarding checklist is the same person on the offboarding queue. One record, one truth, one place to look.