An employee’s last day can arrive before every piece of equipment reaches the office. Track offboarding equipment returns in Airtable by connecting the departure case to the employee’s assigned assets, then recording receipt and inspection for each item. miniExtensions can give the staff collecting equipment a focused portal without turning a shipment update into a completed return.

The useful outcome is a reconciled list: which items were expected, which arrived, which passed inspection, and who owns anything unresolved. Account revocation stays with IT in the systems where access actually exists.

Start with the equipment that is actually assigned

Imagine fictional company Cedar Workshop preparing for Jordan’s departure on November 20. Jordan has laptop LT-041, monitor MN-018, and dock DK-009. Sam coordinates offboarding, Morgan receives equipment, and Lee handles account access. Jordan sends the laptop and dock together, while the monitor will be collected later.

One “Equipment returned” checkbox would hide that split. Instead, Sam creates three expected-return records and assigns Morgan to inspect each one. A parcel arriving closes none of them automatically. The asset identifiers and contents of the parcel still need checking.

This design is staff-operated. Jordan receives return instructions through the company’s normal communication channel and does not need continued access to an employee portal after departure. It extends the custody history discussed in the equipment checkout guide into a departure-specific reconciliation process.

Before sharing with end users, confirm a suitable paid plan or active trial. The regular free plan is for internal testing rather than deployment to end users. Check the current extension and child-form allowances for your workspace; child forms are counted across published extensions, not separately for each one.

Separate assets, assignments, and offboarding work

Prepare a connected Airtable base and a miniExtensions workspace you can configure. Build the example with fictional records first. Keep personnel decisions, payroll, identity documents, passwords, and other unnecessary employee information out of this operational tracker.

  • Staff: Name (single line text, primary field), Work Email (email), and Team (single select). These are the people using the collection portal.
  • Employees: Employee Label (single line text, primary field) and Internal Reference (single line text). Use the minimum identifier needed to reconcile equipment.
  • Assets: Asset Code (single line text, primary field), Description (single line text), Expected Components (long text), and Availability (single select: Assigned, Awaiting inspection, Available, Repair).
  • Assignments: Assignment Label (single line text), Employee (single linked record to Employees), Asset (single linked record to Assets), Issued On (date), Returned On (date), and Assignment State (single select: Open, Return pending, Closed). Retain one record for each period of custody.
  • Offboarding Cases: Case Label (single line text), Employee (single link), Last Working Day (date), Coordinator (single link to Staff), Equipment Review (single select: Preparing, Outstanding, Reconciled), Access Task Reference (single line text), and IT Completion Confirmed On (date with time).
  • Return Items: Return Label (single line text), Case (single link), Assignment (single link), Receiver (single link to Staff), Asset Code Snapshot (single line text), Due Date (date), Return Instructions (long text), Receipt State (single select: Expected, In transit, Received, Exception), Received On (date with time), Inspection State (single select: Pending, Accepted, Follow-up), Inspection Note (long text), and Inspected On (date with time).

One case has several Return Items, each pointing to one existing Assignment. The assignment identifies the asset and employee; the return item holds the work required for this departure. Before adding one, Sam checks that the same assignment is not already represented in the case. A label alone does not enforce uniqueness.

Sam copies the asset code into the snapshot field so Morgan can read it without browsing the Assets or Employees tables. Sam also copies the relevant Expected Components into Return Instructions. These are manual copies in this design. If assignment information changes, Sam reconciles the snapshot rather than expecting it to update by itself.

Give receivers access to their work only

Create a miniExtensions Portal with Return Items as the data table and Receiver as the user field. The users-table documentation requires a direct linked relationship from each portal data table to its users table. The Receiver link supplies that relationship; a staff name embedded in a case note does not.

Under Users & Login, select Work Email as the login field and enable Two-Factor Authentication (Email verification). Use one valid email per staff record. In each private table view, open Views, then Filter and Sort, and set Choose Records to Display to Personal records only (linked to the logged in user).

Show the return label, asset code snapshot, due date, and Return Instructions as read-only context. Let receivers update receipt and inspection fields. Keep Case, Assignment, Receiver, and all employee relationships outside their editable fields. Sam creates and links records in Airtable; the receiver portal does not create new return items.

Review the table’s Create & Expand Records settings using the creation and editing guide. Disable creation and unintended mutation routes. Do not expose related tables simply to provide a detail already available on the return item. Check the expanding form and every alternate view with two staff accounts before using real records.

Reconcile the departure one item at a time

Sam first compares Jordan’s open Assignments with the equipment list Jordan and the team recognize. An old assignment for a replaced laptop needs investigation before it becomes another demand for return. Once the list is agreed, Sam creates the case, three Return Items, and a due date for each.

When Jordan reports dispatch, Sam marks the laptop and dock In transit. A shipment reference can be recorded in an optional single-line text field, but the tracker does not obtain carrier updates by itself. Morgan waits for physical arrival before recording Received On.

Morgan opens the parcel, matches LT-041 and DK-009, and compares their components with the instructions. The laptop passes the equipment check. Morgan records Accepted and the inspection time. The dock is missing its power adapter, so Morgan records Follow-up with the exact missing part. The monitor remains Expected.

Sam closes only the laptop assignment after reviewing that accepted return and recording Returned On. The asset’s next availability is a separate staff decision. A returned laptop may still need approved IT handling before reuse, so receipt should not automatically mark it Available.

Handle missing items without rewriting history

The dock exception should remain visible even if the laptop return is complete. Sam agrees a follow-up action and date with the responsible person, then adds an operational note. When the adapter arrives, Morgan checks it and records the resolution before changing Inspection State to Accepted.

If an item cannot be recovered, keep the discrepancy and the responsible team’s decision. Do not silently treat it as physically returned. Add a staff-only Resolution Note and Resolution Date to the Return Item if your process needs an approved exception. Financial recovery, deductions, and responsibility decisions belong to the appropriate company process, not an automatic consequence of a missing asset record.

Close the equipment loop separately from access removal

Sam marks Equipment Review as Reconciled only after checking every expected item against its accepted inspection or documented exception. Separately, Lee completes the access-removal work in the relevant systems and records its reference and completion confirmation. Updating this tracker does not disable an account, revoke a session, erase a device, or prove those actions happened.

Creating cases, assigning return items, sending instructions, tracking parcels, and changing asset availability are manual steps here. Reminders and checklist generation can be added through separately configured automations, with duplicate handling and failure review. A due date alone sends nothing.

Before launch, test a complete return, a missing component, an unrecognized asset, and a second receiver’s access. Confirm that one accepted item leaves the other two outstanding and that equipment reconciliation leaves the IT action independent. The result should be a clear explanation of what remains, not merely a green offboarding checkbox.