TaskbyTask.Practical AI guides for work
ChatGPT · Practical walkthrough

Make a project handover someone can actually use

The classic handover is a folder link and “shout if you need anything”. Then the person who wrote it leaves on Friday, and the shouting has nowhere to go.

Task by Task13 min read + practice
Two fictional adults pass a tabbed project folder between desks, with coral unresolved-risk bookmarks and an empty keyring kept visible.

What you'll make

a one-page handover that tells the next person what to do first, what’s still open and who owns what, with proposed and missing owners kept visible.

What you'll need

ChatGPT in your work account (Claude, Gemini or Copilot also work for the pasted-text route), the current project documents and notes, a cutoff date and the name of the person taking over. Allow about twenty minutes, plus a walkthrough with them.

Example result.

As of 4 October. Current position: 10 October full rollout withdrawn (signed decision, 2 Oct). 12 October pilot only, conditional on the export retest and approval.
Open: customer-export defect. Retest required before pilot approval. Retest owner: unassigned.
Conflict: old portal retirement still documented for 31 October (Operations). Not updated since the pilot decision.
Ownership: Leah proposed as incoming lead, not yet accepted. Document access yes; production access pending via IT.
Before 9 October: Ava to walk Leah through rollback. Instructions exist; no successful rehearsal recorded.

1. Gather the current material

Open a new chat and attach the files (or paste the text): approved decisions, working instructions, open issues, key dates and known owners. Write down a cutoff date so the summary doesn’t mix different moments as if they’re all current. Note who is taking over and what they already know: someone covering a week of leave needs different detail from a permanent successor.

Don’t upload passwords, API keys or recovery codes. Describe how to request access through the normal process instead.

To practise, use the fictional project notes: a customer portal change where the outgoing lead, Ava, leaves on 9 October and Leah has been proposed to take over.

Why this works: a cutoff stops stale facts sitting beside current ones, and naming the recipient sets the level of detail.

What you should see: the project sources attached, with a cutoff date and a line about the recipient.

2. Ask for a concise handover

Use these documents to draft a handover of no more than 500 words for [recipient], as of [cutoff date]. Include the current approved scope, next steps, important dates, working references and open risks. Point to the source behind each important decision.

Distinguish accepted owners, proposed owners and unassigned work. Flag outdated claims, conflicting plans, missing access and questions the incoming person must resolve. Don't invent approvals, owners, working links or completed actions.

[recipient] is the person taking over and their role; [cutoff date] is the date from step 1.

Why this works: source references let you check each decision, and the three owner states stop a suggested name becoming an invented agreement.

What you should see: a short handover with sources beside decisions, owners labelled accepted, proposed or unassigned, and a list of conflicts and questions.

3. Check that the unresolved work stayed unresolved

Handovers fail by being tidier than the project. Read the draft for anything that has quietly been settled.

In the practice notes, a signed decision on 2 October replaces the 10 October full rollout with a 12 October pilot, conditional on a retest. An export defect is still open and the retest has no owner. The old portal’s 31 October retirement date hasn’t been changed anywhere. A useful handover flags that conflict; it doesn’t repeat the old “green” status, or cancel the retirement because that makes the story neater.

Leah can read the documents, but production access is pending. Rollback instructions exist, but no successful rehearsal is recorded. Each point stays in the handover until someone checks or resolves it.

Why this works: a newer decision doesn’t prove every dependent date was updated. The gaps between documents are exactly what the next person needs to know.

What you should see: every conflict and open item from the sources still visible in the draft.

4. Review it with the incoming person

  • Current position. Scope and dates match the latest decisions, and old status claims haven’t hidden newer risks.
  • Ownership. Critical actions have accepted owners or are plainly unassigned. A name in an AI draft isn’t a handover agreement.
  • Usability. The recipient can find the next task and open each reference in their own account. Fix access through the normal channels rather than making everything public.

Walk through important operating steps together. In the example, agree who owns the export retest, who approves the pilot and who reconciles the retirement date, and confirm Leah’s acceptance separately. Save the reviewed handover in your normal document system with its cutoff date.

Why this works: only the recipient can tell you whether the handover answers their first questions.

What you should see: a handover the recipient has used to find the next task, with acceptance recorded outside the draft.

Check the result

  • Every decision has a source and a date, and nothing older contradicts it without being flagged.
  • Each critical action is marked accepted, proposed or unassigned.
  • No credentials appear anywhere in the pack.
  • Every link opens for the recipient in their own account.

The usual failure: the draft makes the project sound more finished than it is. It repeats an old “green” headline, drops a dependent date the new decision didn’t mention, or writes a proposed owner as the owner. Spot it by checking each status word and each name against the newest source that mentions it.

Which statements in this handover make the project sound safer or more complete than the sources show? Quote each statement, name the source that contradicts or fails to support it, and propose a corrected line.

Check the corrections against the originals yourself.

Worked example: a pilot that didn’t cancel a retirement

Fictional example. The practice notes, cut to the essentials:

18 Sept, approved plan: full rollout 10 October; old portal retirement 31 October; Operations owns retirement scheduling.
26 Sept, status: green, full rollout ready.
2 Oct, signed decision: 12 October pilot only; full-rollout date withdrawn. Customer-export defect open; retest required before pilot approval. No retirement change recorded.
3 Oct, operating notes: Ava can demonstrate rollback before leaving 9 October. Instructions exist; last successful rehearsal not recorded.
3 Oct, draft: Leah proposed as incoming lead, not accepted. Export retest owner absent.
4 Oct, access: Leah can read documents; production access pending via IT.

The first draft opened: “Project is green. Pilot launches 12 October and the old portal retires on 31 October as planned. Leah now owns the project.”

  • The failure. Three tidy claims. “Green” is from 26 September, before the defect. The pilot is conditional, not launching. “As planned” hides that the retirement date was set for a full rollout that’s been withdrawn. Leah hasn’t accepted.
  • The repair. The repair prompt quoted all three and pointed to the 2 October decision and the 3 October draft. The corrected handover is the example result at the top of this page.
  • What the walkthrough settled. Ava’s departure date makes the rollback walkthrough urgent. It doesn’t make anyone the owner; that needs Leah’s agreement, recorded separately.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Optional training: Reconcile the sources before drafting

For a complex project, ask for a source index and a reconciliation log first, then draft from the checked log.

As of [cutoff date], create a source index: title or link, date, purpose and authority of each source. Then list superseded claims, unresolved conflicts, missing materials and access gaps, with the source behind each. If sources conflict, use explicit authority and supersession evidence; the newest sentence doesn't automatically win. Before drafting anything, list the questions that could block a safe handover, separated for the outgoing lead, the incoming lead and the approving owner.

For more on deciding which of two recorded decisions is current, see Find the latest agreed decision across meetings and Slack.

Optional training: Add an open-action register with closure evidence

Once the reconciliation is right, add a register the successor can work from.

From the checked reconciliation, build an open action and risk register: action or risk, evidence, owner status (accepted, proposed or unassigned), timing basis, dependency, next check and closure evidence. Mark unknown deadlines as unknown. End with a handover acceptance checklist and leave unchecked anything not yet confirmed.

The closure-evidence column is what makes it useful. “Export issue done” is weak. A retest record, its result and the required approval give the successor something concrete to look for.

Optional training: Decide how to share it

If the work lives in a ChatGPT project, you can share the project itself (Share in the project). Members can see its chats, files and member list, and every member can view and download the project’s files. Members with chat access can use the chats, files and instructions; edit access also lets them change instructions, manage files and invite others.

That’s often broader than a successor needs. A standalone reviewed handover, saved in your document system with links to only the files they’re allowed to see, may be the better choice. Never put credentials in either.

Sources

Optional analytics

With your permission, Google Analytics uses cookies to measure visits and which guides people read. It stays off until you accept. Use Analytics choices in the footer to change your choice. Rejecting after accepting refreshes this page. Privacy details.