# Salesforce handover working kit

Provided by aprity — https://www.aprity.ai/resources/salesforce-handover-kit/
You may copy and adapt this template for your own work. No registration required.
This is a blank working template, not a customer case study or certification.
Keep completed copies in an approved private workspace. Never include secrets or customer records.

## 1. Scope and evidence baseline

- Organisation / environment:
- Capture date and timezone:
- Metadata retrieval or scan reference:
- Included component types and versions:
- Excluded or inaccessible components:
- Retrieval errors / known limitations:
- Outgoing technical owner:
- Receiving technical owner:
- Business owner(s):
- Approved evidence location:

## 2. Critical process map

| Process | Trigger | Expected outcome | Objects | Business owner | Evidence | Review status |
| --- | --- | --- | --- | --- | --- | --- |
| To complete | | | | | | NOT_REVIEWED |

Use VERIFIED_FROM_SOURCE, OWNER_CONFIRMED, REQUIRES_RUNTIME_VERIFICATION or NOT_REVIEWED.
An owner confirming intent is different from source evidence showing configuration.

## 3. Configuration record — copy for each selected component

- Component API name / type / version:
- Source location and capture date:
- Entry conditions:
- Fields read:
- Fields written:
- Branches and exceptions:
- Referenced components:
- External boundaries requiring investigation:
- Source-supported explanation:
- Business context supplied by / on:
- What has not been established:
- Reviewer and review date:

## 4. Operational responsibilities

| Area | Owner | Runbook location | Last reviewed | Open question |
| --- | --- | --- | --- | --- |
| Scheduled jobs | | | | |
| Integrations and failures | | | | |
| Release process | | | | |
| Incident escalation | | | | |
| Access requests and revocation | | | | |
| Recovery procedure | | | | |

Reference approved credential-management procedures. Do not paste passwords, tokens or keys.

## 5. Open questions and proposed work

| ID | Observation / source | Question or proposed action | Owner | Priority | Due date | Acceptance evidence | Status |
| --- | --- | --- | --- | --- | --- | --- | --- |
| H-001 | | | | | | | OPEN |

A missing reference in a metadata sample does not prove a component is unused.
Keep proposed changes separate from approved changes and completed verification.

## 6. Receiving-team walkthrough

- Selected process and reason for selection:
- Participants and date:
- Can the receiver locate the relevant component and version?
- Can the receiver explain the entry conditions and relevant branches?
- Can the receiver identify the source of each material statement?
- Can the receiver identify the owner of an unanswered business question?
- Where did the documentation fail to answer the question?
- Corrections or follow-up work agreed:

## 7. Scope acceptance

- Scope reviewed:
- Evidence reviewed:
- Remaining conditions / exclusions:
- Accepted by / role / date:
- Next review trigger:

Acceptance applies only to the stated handover scope. It is not proof of defect-free execution.

## 8. Change record

| Date | Component / process | Change | Evidence baseline | Reviewer | Next action |
| --- | --- | --- | --- | --- | --- |
| | | | | | |