Worked example

A departure, start to finish

Ridgeline Communications — a 35-person telecom shop in Georgia

A field tech resigns on a Monday. Here is everything that one event sets in motion — accounts, equipment, and the legal clocks — and what the owner actually has to do (approximately one click).

This walkthrough follows a sample business. Where the engine is deterministic (statutory checklists, the filing calendar, the report arithmetic), the artifacts below are its actual output for the sample inputs — your dates and dollars come from your own setup.

1 · The manager fills the form

Every manager has the same tokenized link — no logins, no tickets. Thirty seconds of typing.

morthn.com/access/… — Ridgeline's request form

Type
Departure
Worker
Marcus Webb — Field Technician II
Effective
Jul 6
Requested by
Dana Ortiz (Ops Manager)
Reason
Resignation, two weeks notice

Nothing changes until the named approver approves.

2 · The owner gets a one-click email

The approver — usually the owner — approves or rejects from the email itself. No dashboard required. Links are single-use.

Email

[Access] ACCESS REMOVAL (departure): Marcus Webb — approval needed

Requested by Dana Ortiz (dana@ridgeline.example) · Role: Field Technician II

Approving creates the tracked revocation checklist. Nothing changes until you approve.

ApproveReject

3 · Approval explodes into the full checklist

One approval, three task classes: every system Marcus ever held access to (24-hour SLA), every asset in his hands (same SLA), and the statutory steps with the law's own deadlines. The legal items below are the actual engine output for a Georgia employer with 35 people — citations included.

Offboarding Marcus Webb — created Jul 6

Revoke Billing platform (agent) · due Jul 7 · 24h SLA

Auto-sent to Zapier — completes on confirmation callback.

Revoke Dispatch board (tech) · due Jul 7 · 24h SLA

Revoke Carrier portal (runbook step) · due Jul 7 · 24h SLA

Closed system — tracked manual step with an owner. Never silently skipped.

Recover Ford Transit #12 keys + fuel card (…4412) · due Jul 7 · 24h SLA

Recover Panasonic Toughbook (SN 8842) · due Jul 7 · 24h SLA

Final paycheck — GA: no state law — next regular payday (federal default) · due Jul 13

no state law — next regular payday (federal default) (no GA statute). Deadline shown assumes an INVOLUNTARY separation — the stricter case; quits often allow longer in this state. Cite is compilation-verified — read the statute text before quoting it to anyone.

COBRA — notify plan administrator · due Aug 5

Within 30 days of the qualifying event (29 CFR 2590.606-2); the administrator then has 14 days to send the election notice — 44 days combined when the employer administers its own plan (29 CFR 2590.606-4). Exposure: $100/day IRS excise tax (26 U.S.C. § 4980B) plus up to $110/day ERISA civil penalty (29 CFR 2575.502c-1).

Accrued PTO payout check · due Jul 9

No verified payout mandate on file for this state — payout is owed only if the employer's own policy promises it. Confirm the written policy before cutting the check.

State separation/unemployment notice · due Jul 9

Some states require giving the departing worker a separation or unemployment-rights notice at termination. Verify this state's requirement and keep proof of delivery.

4 · Anything overdue alarms — daily, loudly

A departed worker with live access, an unreturned fuel card, or a blown statutory clock is treated as an incident, not a backlog item. The daily scan emails the founder until it's closed.

Daily health scan — what it would say if the carrier portal step slipped

⚠ FAIL · Overdue revocations: 1 revocation past the 24h SLA: Ridgeline/Marcus Webb · Carrier portal (26h overdue)

5 · The audit trail is the artifact

Who requested, who approved, who executed each step, and when — per system, per asset, per statutory deadline. For a telecom shop (CPNI) that trail is the difference between a policy and proof.

The takeaway

One form and one click from the owner — and nothing about a departure is left to memory.

$1,997/mo + $1,997 one-time setup, first automation included · no long-term contract · All examples →