Official recipe

Prepare an employee-approved offboarding knowledge handoff

A departing employee’s useful work can be scattered across folders, while a broad handoff risks including unrelated or confidential material that successors should not receive.

Read original recipe

Proposed inputs

Name
Resource manifest
Owner
Employee
Minimum scope
Eight fictional document titles and descriptions
Quality check
Include authorship, dates and access labels.
Name
Handoff scope
Owner
Manager and employee
Minimum scope
A specific work area and time range
Quality check
Exclude personal and unrelated folders.
Name
Recipient list
Owner
Manager
Minimum scope
Named successor roles for the exercise
Quality check
Separate summary recipients from document permissions.

Access and setup — proposed or unknown

Proposed minimum: Use a local fictional manifest; open no real employee files.
Track permission review separately from content approval.
Compatibility unknowns: Unknown: connector coverage, indexing freshness, authorized roles and trigger configuration; deeper setup pages were unavailable.
External actions requiring approval: Real source access, disclosure, document permission changes and notifications.

Detailed steps and output format

At a glance

Suggested result: A draft handoff inventory with resource links, proposed work categories, missing context, intended recipients and an approval checklist.Suggested; untested.
Tool: ServiceNow; offboarding knowledge-transfer AI agentsSource-named; check current access.
Suggested inputs: Resource manifest; Handoff scope; Recipient listProposed; access notes below.
Human review: Proposed: confirm the employee, date scope, permitted document sources and recipients. Preserve employee review and separate file-level permissions; approving a summary must…
Read full note
Proposed: confirm the employee, date scope, permitted document sources and recipients. Preserve employee review and separate file-level permissions; approving a summary must not silently broaden document access.
Suggested boundaries; source approvals below.
Setup notes: Use a local fictional manifest; open no real employee files. Track permission review separately from content approval.Guide notes; proposed setup untested.
Cost: Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth: Source-linked example · suggestions untestedDepth does not establish successful execution.

Check source evidence and limits ↓

Function and scope

People, Administration · Single task

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

A departing employee’s useful work can be scattered across folders, while a broad handoff risks including unrelated or confidential material that successors should not receive.

Suggested task · untested

Proposed: Prepare a bounded transfer inventory for the employee to correct before any sharing.

What you could produce

A draft handoff inventory with resource links, proposed work categories, missing context, intended recipients and an approval checklist.

Where these suggestions come from

Core problem: Our suggestion; no result reported by the source
Agent job: Our suggestion; no result reported by the source
Expected output: Our suggestion; no result reported by the source
Relevant job roles: Our suggestion; no result reported by the source
Benefit type: Our suggestion; no result reported by the source

Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original decision guidance and first check are proposals. The source supports the attributed task; this guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

Document ownership alone does not establish relevance, currency or permission to share. A useful handoff needs those distinctions.
An inventory can help the employee explain which resources matter and what a successor still needs to ask.

Why an agent / simpler alternative

Useful judgment: Group unevenly named resources and surface unclear ownership or context.
Simpler alternative: Use an employee-curated folder and a short checklist when the relevant documents are already known.
Unsuitable when: Departure circumstances are disputed or the task would expose restricted employee or customer information.

Expected deliverable and review checks

Proposed artifact: A draft handoff inventory with resource links, proposed work categories, missing context, intended recipients and an approval checklist.
Critical checks: Each resource retains its exact identity and access label.
Unclear authorship or relevance is flagged.
Unapproved items remain withheld from the sharing packet.
Missing output evidence: Unknown: no actual tenant output or completed run independently inspected.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Eight invented resources including two similar authors, one restricted file, one stale procedure and one item without an owner; employee review is simulated only.
Acceptance checks: Separate withheld material.
Preserve links and uncertainty.
Produce a review packet without sharing or changing access.
Stop conditions: Real employee files, credentials, disputed departure details or any outbound disclosure.

Tasks: Planning & operations

Useful for: Operations manager

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

ServiceNow; offboarding knowledge-transfer AI agentsIndependent testing: No

Failure handling, costs and limits

Failure signals and proposed responses

Signal
Similar employee names
Why it matters
Wrong-author documents can leak information.
Proposed response
Require a stable employee identifier.
Signal
Restricted resource mixed in
Why it matters
A summary can reveal content even without a file link.
Proposed response
Exclude it pending the owner’s decision.
Signal
Stale or orphaned document
Why it matters
Successors may inherit unusable instructions.
Proposed response
Flag currency and ownership questions.

Effort and cost — unknown

Setup work: Agree on scope, exclusions and recipient authority.
Ongoing review: Employee reviews categories and missing context.
Unknowns: Unknown: connector entitlements, indexing work and review effort.

Limits

A complete inventory does not establish that knowledge has been understood or transferred.

Full source evidence

Official recipe · Tool workflows

Original task title: Prepare an employee-approved offboarding knowledge handoff

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://www.servicenow.com/docs/r/employee-service-management/journey-designer/offboarding-knowledge-x-agentic-wf.html?contentId=YmXa_~_SmUmRJWjPNucmpg ↗

Attributed to: ServiceNow Product Documentation

Official recipe

Original action type: tool_action
What the source reports: Creates a knowledge-transfer record for a departing employee and requests employee approval before sharing it with the manager.
Source outcome limits: The original researcher read the public body; a separate reopen failed. Retained excerpts support record creation and employee approval. Setup, connectors, completed transfer and retained knowledge remain unverified.
Evidence attribution caveat: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: Employee approval is requested before sharing the knowledge transfer with the manager.
Named tools: ServiceNow; offboarding knowledge-transfer agentic workflow.
Model or version: Unknown
Publication date: Unknown
Source last checked: 2026-10-14
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed: have the local process owner verify language, access, work rules and retention. Canadian execution and tenant availability are unverified.
Recommended approval boundaries: Proposed: confirm the employee, date scope, permitted document sources and recipients. Preserve employee review and separate file-level permissions; approving a summary must not silently broaden document access.