The 30-60-90 Day Onboarding Tracker That Knows Who's Falling Behind

Lead: Most 30-60-90 day plan templates give you a document. Ours gives you an alarm. We analyzed the official onboarding and 30-60-90 resources from monday.com, Airtable, and Notion, kept the one strong idea each had, fixed what none of them solved, and rebuilt the result as a free, open source Baserow template you can download and own outright.

Why most 30-60-90 day plan templates fail the same way

Every manager who hires someone eventually reaches for a 30-60-90 day plan. The pitch is simple: define what "good" looks like at day 30, day 60, and day 90, and use it to keep a new hire's ramp on track.

The plan works for exactly as long as someone remembers to check it. Then the real failure mode shows up.

It isn't a missing template. It's that nothing in the plan knows when a milestone has slipped. A new hire's Day 30 goal — "shadow three calls," "ship a first PR," "resolve 20 tickets solo" — quietly passes its deadline. Nobody notices, because the plan is a document, not a system. By the time someone checks in at day 90, three separate ramp milestones are late, and the new hire has spent two months without the structure the plan was supposed to provide.

A 30-60-90 day plan earns its place when it tells you who is behind without anyone opening the document to check. That's the bar we used rebuilding this category, and it's the test worth applying to any template you evaluate — including ours.

What the big three actually give you

We ran the official 30-60-90 and onboarding resources from monday.com, Airtable, and Notion through our extraction pipeline — same rubric, same eight-person review panel, all three scored on demand, reusability, and enterprise readiness. Each one gets exactly one part of this pattern right. None gets all three.

monday.com: the right phase structure

monday.com's two official posts — the "First 90 Days" template and the "30-60-90 Day Plan" template — correctly frame onboarding as three named phases with a theme each: learn, contribute, own. That's the right mental model, and it's one of the two structural ideas we kept. The first-90-days post even ties each phase to a manager check-in cadence: week one, day 30, day 60, day 90.

What it's missing: everything after the framing. Both are blog posts with an embedded static board mockup, not a real product. There's no underlying record of a new hire linked to their milestones — so a manager running eight onboarding plans at once has no single view of who's behind across all of them. The 90-day check-in structure is calendar discipline a human has to maintain, not software that enforces it.

Airtable: the right relational shape

Airtable's official Employee Onboarding template is a genuine two-table, linked-record base — new hires and their onboarding tasks, related rather than duplicated. That's the correct minimum shape for this category, and it's the second idea we kept: two linked tables, not one flat checklist.

What it's missing: the phase structure itself. Airtable has no dedicated 30-60-90 template in its official library — teams have to invent the day-30/60/90 framing themselves on top of a generic checklist. And nothing in the base flags an overdue task automatically; status is a field a manager has to remember to look at.

Notion: proof the market wants more, fragmented across four templates

Notion's marketplace actually has the deepest bench here — a general 30/60/90 plan, a sales-specific onboarding variant, a career-plan variant, and a fuller "Employee Onboarding OS / New Hires Portal" template. That range confirms real demand across personas: new leaders, new individual contributors, sales reps all search for the same underlying phase structure.

What it's missing: a queryable database underneath any of them. The core 30/60/90 templates are page-based documents — goals written as text under Day 30/60/90 headers. There is no way to filter "show me every new hire with an overdue Day-30 milestone," because milestones aren't rows with a due date and a status property. And with four competing official templates for one job, there's no single canonical version to point a new hire at.

The three, side by side

Each commercial source wins exactly one column. Ours is the only one with a check in every row.

<!-- COMPARISON GRID: embed content/comparison-grid-30-60-90-onboarding.html here -->

| Capability | monday.com | Airtable | Notion | OpenSource AI Pro | |---|---|---|---|---| | Named 30/60/90 phase structure | ✓ Yes | ✗ No | ◐ Partial (fragmented across 4 templates) | ✓ Yes | | Linked new-hire ↔ milestone data model | ✗ No | ✓ Yes | ✗ No | ✓ Yes | | Formula-driven overdue milestone flag | ✗ No | ✗ No | ✗ No | ✓ Yes | | Single canonical version (not fragmented) | ✓ Yes | ✓ Yes | ✗ No | ✓ Yes | | Cross-new-hire "who's behind" view | ✗ No | ✗ No | ✗ No | ✓ Yes | | Self-host & own your data | ✗ No | ✗ No | ✗ No | ✓ Yes |

Competitor details reflect each platform's public template pages as of July 2026.

The rebuild: both ideas, one open source template

Our 30-60-90 Day Onboarding Tracker combines monday.com's named phase structure with Airtable's linked-record model — built on Baserow, the open source Airtable alternative you can self-host. Then we added the feature none of the three ship: an enforced overdue-milestone flag.

The Starter edition ships with:

Two linked tables. New_Hires and Milestones — each a real entity. A milestone links to the new hire it belongs to, carries a Phase (Day_30 / Day_60 / Day_90), an Owner, a Due_Date, and a Status. Nothing is buried in a free-text paragraph the way Notion's page-based templates handle it.

An Overdue_Milestone flag nobody has to maintain. A formula field compares each milestone's due date against today and its status. If the date has passed and the milestone isn't marked Complete, the flag fires — automatically, on every view load, with zero automations or background jobs required.

An Overdue Milestones view that leads the template. Open the base, click once, see every new hire with a slipped Day-30, Day-60, or Day-90 milestone — across the whole team, not one plan at a time. This is the view that replaces the "let me check in on everyone" meeting.

Working sample data with a deliberate negative-proof row. Six new hires, fourteen milestones across all three phases. Two milestones are deliberately overdue so the flag demonstrates itself the moment you open the template — and one milestone is deliberately marked Complete despite a past due date, to prove the formula checks status, not just the calendar. A naive version of this flag would wrongly light up a milestone someone already finished on time; ours doesn't.

[VIDEO EMBED: Pattern of the Week — The 30-60-90 Day Onboarding Workflow]

What "open source" buys you here

The fair question: BambooHR, Rippling, and a dozen HRIS tools already do onboarding. Why does open source matter for a 30-60-90 plan specifically?

No per-employee HRIS pricing just to track a ramp plan. Full HRIS platforms bundle onboarding into a per-seat, per-module price built for payroll and benefits administration — overkill if all you need is to know whether new hires are on pace. Self-hosted Baserow has no per-seat fee at any scale, for a job that's genuinely lightweight.

Your new-hire data stays yours. A ramp plan can carry candid manager notes about how someone is performing in their first 90 days — exactly the kind of record that shouldn't live in a vendor's cloud by default. Self-hosting keeps it inside your own infrastructure.

The overdue formula is inspectable. Open the field editor and you'll see the actual logic that decides a milestone is late — not a black box behind an HRIS dashboard you can't audit.

[VIDEO EMBED: Teardown — What monday.com's 30-60-90 Day Plan Template Gets Right (and Doesn't)]

How the lifecycle works

The workflow underneath the template is the same one we found, in pieces, across all three commercial sources:

New Hire Starts → Day 30 Milestones → Day 60 Milestones → Day 90 Milestones → Ramp Complete

The Starter edition implements the spine: New_Hires and Milestones as linked tables, an Overdue_Milestone formula, and the exception view that surfaces everyone who's behind. The Operational edition (coming next) adds manager-scoped views, reminder notifications ahead of each due date, and a Milestones_Complete rollup per new hire. The Enterprise edition adds an audit trail on status changes, a manager sign-off checkpoint before a ramp is marked complete, and an admin-configurable milestone-template table so HR can standardize default Day 30/60/90 goals per role.

That tiering is deliberate. A plan a manager understands in five minutes gets used. A plan with an approval workflow attached on day one gets ignored.

Get the Starter template

The Starter edition is free, with working sample data, deployable to any Baserow instance — cloud or self-hosted.

[DOWNLOAD CTA: Get the free 30-60-90 Day Onboarding Tracker →] (Email-gated download. You'll also get our weekly pattern breakdown — one reusable workflow pattern, every week, no filler.)

Evaluation checklist for any 30-60-90 day plan template

Building your own, or evaluating another one? Hold any candidate against these five questions:

1. Are new hires and their milestones separate linked records — or is the plan one flat document per person?
2. Does anything flag an overdue milestone automatically, or does a manager have to remember to check?
3. Can you see every new hire who's behind, across your whole team, in one view?
4. Does the overdue logic account for status — or would it wrongly flag something already finished late?
5. Is there one canonical version of the plan, or does your team have to pick between four fragmented variants?

The big three each pass one, maybe two. The point of an open source rebuild is to pass all five — and to let you verify that claim by reading the template's own formula.

---

OpenSource AI Pro covers open source tools and AI adoption for higher education, healthcare, and legal teams. The Template Intelligence series analyzes commercial workflow templates and rebuilds the best patterns as open source deliverables.