You are handing a volunteer role to someone new. Your notes contain familiar shortcuts: “usual room,” “ask the treasurer,” “list in the folder.” They remind you what to do because you already know the background. The next person needs enough context to act without reconstructing months of conversations. AI can help organize the document, provided you keep decisions and missing information visible.

This is a writing problem with a specific reader: someone taking over your role, possibly without you beside them. It complements our guide to making responsibility clear. A handover also needs locations, timing, unresolved work, and an explicit point at which the new person should ask for help.

Define the handover's limits first

Write a short scope line before drafting: “This covers the monthly community reading group's room booking and reminder email.” State what it does not cover when a reader could reasonably expect it: “Membership payments are handled by the treasurer.” This prevents a polished document from implying that the new volunteer owns every connected task.

The Australian Charities and Not-for-profits Commission recommends preparing key handover information ahead of time and combining a written document with a conversation in its handover guidance. Treat the document as something to walk through together. It should help the conversation reveal gaps, rather than make questions seem unnecessary.

Keep the source notes next to the rewrite

Here is a fictional set of notes, deliberately incomplete:

“Reading group: first Tuesday. Room confirmed for December only. Email reminder a week before. Mailing list in shared drive, access from coordinator. Pat usually collects key; January unclear. Two large-print copies requested, no confirmation yet. Don't include member details in public notes.”

A weak AI rewrite might say: “Each month, book the usual room, ask Pat to collect the key, and email all members using the shared mailing list. Large-print copies will be available.” It sounds helpful but changes the record. The room is not confirmed indefinitely, Pat has not accepted January, and the copies remain unconfirmed.

Before requesting a rewrite, replace private names and contact details with role labels where possible. Do not paste mailing lists, passwords, access codes, or personal member information into an editing tool. The draft needs to name the authorized location of information, not reproduce all the information itself.

Give AI a structure that exposes uncertainty

Use a bounded prompt: “Turn these notes into a handover for the incoming reading-group coordinator. Use sections for confirmed arrangements, recurring tasks, unresolved questions, and document access. Preserve all limits and dates. Do not invent an owner, deadline, approval, or location. Mark missing information as a question for the outgoing coordinator. Use plain sentences.”

The requested headings are doing practical work. They keep an unresolved arrangement from becoming an instruction just because both were originally in the same paragraph. You can change the headings to suit the role, but keep confirmed information separate from decisions someone still needs to make.

Review a concrete handover excerpt

A source-faithful draft could read:

Confirmed arrangement: The reading group meets on the first Tuesday. The room is confirmed for December only.

Recurring task: Send the reminder email one week before the meeting. Request access to the mailing list from the coordinator through the shared drive.

Open questions: Who will collect the key in January? Have the two requested large-print copies been confirmed? Who will arrange room bookings after December?

This is clearer, but it is still a draft. “Coordinator” might mean you or your successor. Replace that role with a precise contact route once confirmed. Add the year to December and January and the actual shared-drive location before handing it over. The original notes did not supply those details, so the editor should request them rather than guess.

Add a first-action check

Ask the incoming volunteer to describe the first thing they would do. If they say “send the reminder,” ask where the approved mailing list is and whether they can access it. If they cannot answer, improve the access instruction before adding more background paragraphs. A long history of the group will not fix a missing permission.

For unresolved tasks, agree who will resolve each question and record that agreement. A useful entry might become: “Outgoing coordinator to confirm January key collection with the venue by the agreed handover date.” Only write that once the person has accepted it. AI should not assign work on somebody's behalf.

Edit for use, then check against the source

Keep task sentences short and put the action near the beginning. Replace “It would be advisable for consideration to be given to checking availability” with “Confirm room availability.” Preserve the condition that follows it: “December is the only booking currently confirmed.” Cutting the condition would make the sentence shorter and less accurate.

You can use AI Undetectable to explore clearer wording for a non-sensitive draft. Compare the result with your source notes afterward. Natural phrasing does not establish that dates, permissions, or commitments are correct, and a detector score is not a handover quality check.

Finish by dating the document, identifying who checked it, and recording the remaining questions. Then walk through it with the next volunteer. A useful handover lets that person find the next action and recognize when they need clarification. It does not need to pretend that every loose end has already been tied up.