Guide
Run the First Ninety Days as a Process Your HR System Owns, With the Manager as Owner
A completed checklist does not show that a joiner can do the work. We set up the first ninety days in HRKit as dated tasks with names on them, so delays are visible and every approval leaves a record.
4-minute read5 November 2026
In Brief
- The system shows a successful joiner while the engineer in week two waits for access and a first assignment. The gap shows up later as slower ramp-up and weaker confidence in the team.
- We see four actions: make the hiring manager the owner, date every joining event, write down what good looks like at thirty, sixty and ninety days, and measure access and first real work.
- Thinqmesh fits HRKit, the system that runs our own HR, to your teams and policies within four weeks, with a record of who asked, who approved and when.
Ask an HR team how onboarding is going and the answer is usually a completion figure: documents collected, policies acknowledged, induction attended. Meanwhile an engineer in week two may still be waiting for repository access and unsure whose priorities apply. The record shows a successful joiner, and the joiner would tell a different story. We believe the first ninety days should run as an operating process inside the HR system, with the hiring manager as its named owner and a measure of whether the person can do the work.
Paperwork Completion Says Little About Readiness
HR owns the design and the data, and the manager owns the commitments. The conditions that matter most are ones only a manager and a team can create: a clear first assignment, working access, a named buddy and a conversation about what good looks like.
When those events are dated tasks with a person's name on them, delays become visible as process delays. Days from joining to full access show the handoff between HR and IT. Without that figure, a late laptop reads as a slow joiner, and the cost shows up later as a slower ramp-up.
Four Actions That Make the First Ninety Days Measurable
HR owns the design and the data. The commitments belong to the hiring manager, because the conditions that matter most are ones only a manager and a team can create.
Make the Hiring Manager the Owner of the First Ninety Days
HR designs the process and holds the data. The manager owns the first assignment, the buddy and the conversations.
Before the first day the manager confirms the team, the first assignment and a named buddy. These are tasks in the HR system with the manager's name on them, visible to the joiner. When a task is late, the system shows who owns it, so a delay is a process delay and the joiner's performance is not blamed.
Get started
- Name the owner for each joining event in your current process.
- Put the manager's confirmation of team, assignment and buddy on the offer checklist.
Date Every Event That Sets the Joiner Up
Access, equipment and introductions arrive on a schedule that starts from the HR record, so IT receives the role profile without a chain of requests.
For a technology firm the role profile drives access to source control, ticketing, build tools and, for services work, the client environment. Each pending item shows as an open task with an owner. A lateral hire with a long notice period also gets a dated call from the manager during the notice period.
Get started
- List the access a new engineer needs on day one.
- Add a dated manager call midway through each long notice period.
Write Down What Good Looks Like at Thirty, Sixty and Ninety Days
The manager records the expectations in week one and the joiner confirms they were discussed.
At thirty days the joiner has completed a small piece of real work. At sixty, they take on something with little supervision. At ninety, a review against the expectations written in week one draws its evidence from the record already built, so the manager does not have to recall three months from memory.
Get started
- Draft the thirty, sixty and ninety day expectations for one role.
- Agree who records them and where the joiner sees them.
Measure Access and First Real Work
A small set of measures shows more than a long dashboard, and each is a fact that does not depend on opinion.
Days from joining to complete role access show the handoff between HR and IT. Days to a first piece of merged or delivered work show whether the joiner has been given something real. Your HR system already holds the dates, and reporting on them is the step that is usually missing.
Get started
- Find the joining date and the date of full access for the last five joiners.
- Note the date of each joiner's first delivered piece of work.
How Thinqmesh Solves This
HRKit is the system that runs our own HR and is open source, so you can read it before committing. The design is already working, and the four weeks go into your teams, policies and data.
- Week 1
HRKit on Your Data
HRKit is configured on your data and your records are assessed, because issues found early protect the date.
- Week 2
Teams, Roles and Approval Chains
Your teams, roles and approval chains are set up, with joining tasks that have a named owner and are visible to the joiner.
- Week 3
Your Records Moved Across and Checked
Existing staff records are moved across and checked, and anomalies are flagged early.
- Week 4
Joining and Leave in Real Use
Leave rules, holidays and carry-over are set to your policy, and payroll figures are exported in your provider's format.
You finish with your joining process running in your own HR system, a record of who asked, who approved and when, and your staff records checked. Reviews and hiring are agreed separately.
