Use Case

Scheduled Offboarding

Use chat-to-action to plan, approve, execute, validate, and document offboarding, as a single governed workflow triggered on the target date, with a complete evidence package on completion.

Book a demo Read docs

Why it matters

Planned departures rarely produce planned offboarding, the work still happens last-minute.

Organizations know weeks in advance when a contractor's engagement ends, when an employee gives notice, or when a fixed-term role transitions. But the offboarding still happens reactively: IT gets a ticket the day before or after, works through a manual checklist without documentation, and produces an inconsistent result. When an auditor reviews the access removal record for that person, the answer is often 'we think we removed it', not a signed evidence bundle.

✓Planned terminations, contractor end dates, and role transitions are all foreseeable events
✓Manual offboarding checklists produce inconsistent, undocumented results
✓Last-minute access revocation misses accounts and SaaS seats that require advance notice or workflow time
✓Without a structured process, the evidence of offboarding completion does not exist as a structured artifact

How Nuxari helps

The governed approach

Natural Language Request

Describe the offboarding in plain language: who, when, which systems. The AI assistant drafts a structured workflow covering all detected access in scope.

Checklist Generation

The workflow includes a checklist of every access item to be revoked, based on what the connectors observe as the user's current access across all connected systems.

Approval and Scheduling

The workflow is submitted to an IT approver. Once approved, execution is scheduled for the defined date, giving the team and the user defined notice.

Execution and Validation

On the target date, all revocation actions execute in sequence. After completion, each system is re-queried to confirm that access is removed.

Notification Delivery

The departing user, their manager, and the IT team receive notifications at defined points, scheduled, confirmed, complete.

Evidence Package

On completion, a full offboarding evidence bundle is assembled: checklist, approval, per-system execution logs, validation results, and control mapping.

Scheduled Offboarding

Schedule offboarding once. Nuxari queues the workflow, waits for the approved time, executes, validates, and reports.

Scheduled Offboarding

Workflow

How the lifecycle runs

01
Offboarding request is submitted via chat-to-action
The manager or HR team submits: 'Offboard c.morgan@example.com on 2026-06-30. Their contract ends on that date.' The assistant drafts a structured workflow.
02
Checklist is generated from observed access
Connectors identify all access c.morgan holds: Entra ID account, M365 license, GitHub membership, and any cloud roles. The checklist covers each item.
03
Workflow is reviewed and approved
The IT manager reviews the checklist and approves the workflow. The approval is recorded with scope, approver identity, and timestamp.
04
Notifications are sent
c.morgan receives a notice that their access will be removed on 2026-06-30. Their manager and IT team receive confirmation of the scheduled workflow.
05
Execution runs on the scheduled date
On 2026-06-30, access revocation executes across all systems in the checklist. Each step is logged with status and system confirmation.
06
Validation confirms completion
After execution, each system is re-queried. Access confirmed removed per system is checked off. Any system where access remains triggers a follow-up alert.
07
Evidence package is assembled and stored
Workflow draft, approval, notification record, per-system execution log, validation results, and control mapping are assembled into a signed evidence bundle.

Example scenario

Contractor offboarding on a confirmed end date

A contractor's engagement ends on 2026-06-30. The manager submits the offboarding request one week in advance. The workflow is approved, scheduled, and executed with full validation.

Illustrative example. Not real customer data.

Demo · Illustrative only

01Manager: 'Offboard c.morgan@example.com, contract ends 2026-06-30'
02Assistant: workflow drafted, Entra ID, M365, GitHub, Slack (4 systems)
03IT Manager reviews checklist and approves
04c.morgan notified: 'Your access will be removed on June 30'
052026-06-30 09:00 UTC: workflow executes
06Entra ID account deleted; M365 license reclaimed; GitHub access revoked; Slack deactivated
07Validation: all four systems re-queried, access confirmed removed
08Evidence bundle assembled: 4 execution logs, 4 validation records, 1 approval record