Operations · Custom Build

New-hire onboarding tracker for small teams

Replaced the email-spreadsheet-Slack scramble with one place to see where each hire actually is.

Example build — representative of the kind of engagement we take on, not a named client project.

Screenshot of the hire status board — columns for paperwork, equipment, payroll, first week.

The problem

After the offer, nobody could say where a hire stood without pinging three people.

Onboarding lived in a spreadsheet, an IT thread, a payroll checklist, and Slack messages asking whether the laptop had arrived.

The build

One row per hire, updated by the form and the email.

Paperwork, equipment, payroll, and the first-week plan sit on one page. The hiring manager opens it instead of hunting threads.

The result

Status questions left Slack.

IT, payroll, and the hiring manager see the same board. A new hire isn’t stuck because someone missed a thread.

Who it's for

For the ops lead who cannot say where a hire stands.

People and operations teams at small companies. After the offer, onboarding is a spreadsheet, an IT thread, a payroll checklist, and a Slack ping about the laptop. This example shows those on one board.

What it replaces

  • An onboarding spreadsheet only one person updates
  • An IT thread for the laptop and accounts
  • A payroll checklist that lives in email
  • Slack messages asking whether equipment has arrived

How it works

  1. 1. One row per hire

    Paperwork, equipment, payroll, and the first-week plan are columns on the same board. Status is a row, not a search across tools.

  2. 2. The form and the email update the row

    Changes come from the form and from email. Nobody retypes a Slack thread into the tracker at the end of the day.

  3. 3. The hiring manager opens the board

    IT, payroll, and the hiring manager see the same row, so a status question has one place to land.

  4. 4. The follow-up leaves Slack

    A new hire is not stuck because someone missed a message about a laptop, a payroll form, or day-one access.

Stack

  • TypeScript/Node.js
  • Postgres
  • Resend

Questions teams ask

Is this a live client onboarding system?

This is an example build. It shows the kind of new-hire onboarding tracker we scope for operations teams. It is not a named client project.

What does an onboarding tracker replace?

The scramble after the offer: a spreadsheet, an IT thread, a payroll checklist, and Slack messages about equipment. One row per hire shows paperwork, the laptop, payroll, and the first week.

Who needs to see a new hire’s status?

IT, payroll, and the hiring manager. They share one board, so “where do they stand?” is not a ping to three people.

Want something like this for your team?

Every build starts from a written scope and a fixed quote. Not sure this is the right shape? A consultation is how we decide, and services lists how custom builds and workflow projects are priced.

Start a custom build