# AdminTalk — Outline your team's handover problem

Free discussion template · Version 1 · 26 September 2026

Complete this file on your own device. It does not send information to AdminTalk and is not a service booking or quotation. This website has no enquiry or payment form.

Use roles and fictional situations only. Do not include people's, organisations' or clients' names, contact details, internal documents, real reference numbers, passwords or confidential information.

## 1. What kind of work does the team do?

[For example, event coordination. Use a general description.]

## 2. What does the next person have to guess or ask again?

[Describe one general difficulty without an identifiable real incident.]

## 3. What should the next person be able to do after reading the handover?

[Describe an observable outcome, such as distinguishing confirmed items from pending ones and knowing which role to follow up with.]

## 4. Which part of the work is in scope? What is excluded?

In scope: [one workflow step]
Excluded: [what should not be prepared]

## 5. What needs to be agreed with the team first?

Acceptance reviewer: [role]
Follow-up point: [to be agreed, or an already agreed point]
Still unknown: [list]

Review five groups: TASK / CURRENT / EVIDENCE / BLOCKER / NEXT + OWNER.
Do not add approvals, evidence or delivery dates that have not been confirmed by the responsible person.

AdminTalk is an independent professional knowledge initiative. This template is not an employer- or institution-approved procedure.