You can track employee onboarding in Airtable by giving every preparation task its own record, owner, due date, and completion evidence. miniExtensions can give task owners a focused portal for updating their work, while an onboarding coordinator reviews whether the new employee is actually ready to start.

This workflow is for an operations team coordinating equipment, a workspace, a welcome meeting, and a first-week plan. It deliberately excludes payroll, government identifiers, health information, and other sensitive personnel documents. Those belong in the systems your organization has approved for them.

Make ownership more useful than a single onboarding checkbox

Imagine a fictional company, Cedar Workshop, welcoming Jordan on November 18. Morgan handles equipment, Lee prepares the workspace, and Casey manages the first-week plan. A single “Onboarding complete” checkbox cannot explain why Jordan’s laptop is ready but the desk is still unavailable.

Instead, create three independently owned tasks. The coordinator can see the outstanding workspace decision without reopening completed equipment work. The intended outcome is an explicit operational handoff: each owner has reported completion, evidence is available, and the coordinator has checked the remaining dependencies. This example is a proposed workflow design, not a claim that a complete onboarding system has been tested.

Use separate records for people, onboarding cases, and tasks

Start with an Airtable base connected to miniExtensions and a small fictional dataset. Keep the people who perform tasks separate from the person being onboarded. In this example, the new employee does not log into the owner portal.

  • Task Owners: Name (single line text, primary field), Work Email (email), Team (single select), and Active (checkbox). Create one record for each individual who needs access.
  • Onboarding Cases: Case Name (single line text, such as “Jordan — November start”), Start Date (date), Coordinator (linked record to Task Owners), Readiness (single select: Preparing, Needs decision, Ready), and Coordinator Notes (long text).
  • Onboarding Tasks: Task Name (single line text), Onboarding Case (linked record), Owner (linked record to Task Owners), Due Date (date), Instructions (long text), Progress (single select: Not started, In progress, Blocked, Reported complete), Completion Note (long text), Evidence Link (URL), and Coordinator Review (single select: Pending, Accepted, Needs follow-up).

Use the Owner relationship for portal access and the Onboarding Case relationship for operational context. Do not replace Owner with a plain-text team name. The users-table documentation explains that a portal data table needs a direct linked-record relationship to its users table.

For the example, add “Prepare laptop” for Morgan, “Confirm desk” for Lee, and “Create first-week agenda” for Casey. Link each to Jordan’s case. Give each task one owner, even when several people will help. That person is accountable for providing the next update; a helper’s involvement should not make the task ownerless.

Configure a task-owner portal, not a general HR database

Create a miniExtensions Portal with Onboarding Tasks as the data table and Owner as the user field. Configure login and personal-record access before adding operational information. Follow the existing employee portal setup guide for the broader login and portal setup, but keep this portal focused on assigned preparation tasks.

In each task’s expanding form, show Task Name, Due Date, and Instructions as read-only context. Let the owner edit Progress, Completion Note, and Evidence Link. Leave Coordinator Review and Coordinator Notes out of the owner’s editable form. A staff review should remain independent from the owner’s report.

For this first version, the coordinator creates tasks in Airtable. Leave task creation disabled in the owner portal so people cannot accidentally manufacture a new checklist instead of updating the assigned one. The record creation and editing guide distinguishes portal table controls from standalone Form controls.

Do not expose the full Onboarding Cases table merely to show a start date. Put the necessary instruction or context on the task, or use an appropriate read-only lookup after reviewing what it contains. Keep case-level coordinator commentary in Airtable for this initial version. A smaller portal is easier to verify than a broad employee profile with many irrelevant fields.

For login, open Users & Login, select the email login field, and enable Two-Factor Authentication (Email verification). Use one valid email per user record.

For every private table view, open Views → Filter and Sort and set Choose Records to Display to Personal records only (linked to the logged in user). Repeat the two-user access check after adding views.

Run the handoff from preparation to review

The coordinator creates the actual checklist

Before Jordan’s start, the coordinator creates the case and its tasks, assigns each owner, and agrees realistic due dates. A reusable checklist can guide this manual step, but adding a new case does not automatically generate tasks in this design. If you later configure an automation, document and test its trigger and duplicate prevention separately.

Owners report facts, including blockers

Morgan marks the equipment task Reported complete and adds “Laptop labeled and placed with reception.” The Evidence Link can point to an approved internal handoff record. Do not put passwords, recovery codes, device enrollment secrets, or private account details in that note. The task records that provisioning work was completed elsewhere; it does not perform account provisioning.

Lee marks the workspace task Blocked and explains “Assigned desk is awaiting repair; coordinator must choose another desk.” This is useful even when the original due date has not passed. A visible blocker is more actionable than an overdue task with no explanation.

The coordinator accepts or returns the work

The coordinator reviews completion notes and sets Coordinator Review to Accepted only when the expected outcome is supported. If Morgan’s laptop is ready but no pickup arrangement exists, set Needs follow-up and clarify the missing handoff. Reported complete and Accepted remain different facts.

Create internal Airtable views for Blocked tasks, Reported complete awaiting review, and Tasks due before the start date. Review them as a routine operational step. This article does not configure notifications, so nobody should assume an owner will receive an automatic reminder.

Handle a changed start date or absent owner

Suppose Jordan’s start moves by a week after the laptop is prepared. Update the case date, then review each task deliberately. Some due dates can move; others should remain because booked workspace work still needs attention. Do not reset every completed task to Not started just because the case changed.

If Lee becomes unavailable, the coordinator assigns a new owner and records the handoff context. Verify that the replacement owner can see the task and the previous owner no longer has unintended access. Reassignment must not erase the existing completion note or make prior evidence look as though the new owner supplied it. Add a dated coordinator note when a history of ownership matters.

Check the workflow before using real employee information

  • Use two fictional owners and separate tasks. Confirm each portal view shows the intended records and no unrelated case details.
  • Open an existing task, change Progress and Completion Note, save, reload, and inspect the same Airtable record.
  • Verify that an owner cannot change Owner, Instructions, or Coordinator Review through another view or linked-record form.
  • Test a Blocked task and a Reported complete task. Confirm the coordinator can distinguish them without reading every row.
  • Reassign one fictional task and check both users again. Review every route to that task, not only the default view.

Know where the checklist stops

This structure suits a team that already coordinates operational work in Airtable and wants clear ownership without a full HR suite. It does not create employee accounts, buy equipment, reserve desks, make employment decisions, or prove that training requirements were met. Those processes need their own authorized systems and responsible people.

The useful finish line is narrower and clearer: the coordinator can explain which preparation work is done, which evidence supports it, who owns the remaining blocker, and whether the operational handoff is ready.