How to write a project handover note with AI

A useful project handover tells the next person where the work is, what is finished and what they should check before continuing. AI can organize your notes into that structure. The paper copy gives both people a place to mark corrections and confirm the transfer.

Start with the filled example below: a poster has been proofread, but its printed appearance and display permission remain unchecked. I would keep those two unresolved items near the top. A tidy list of completed work is less useful if the receiver misses the condition that prevents the next step.

Print the blank handover sheet · Print the filled example · Download the complete prompt. Use A4 or US Letter in portrait, or Save as PDF.

1. Write the state of the work before the story

Gather the current file names, the relevant folder location and your unresolved questions. Separate work you completed from work you only planned. Give each source note a number so you can check where the summary came from.

For a real handover, open the actual files before calling them current. A file name containing “final” does not establish approval. Record the exact version you mean and remove passwords, private contact details and unrelated material before sharing notes with an AI service.

2. Use this complete handover prompt

The book-swap poster is an invented practice example. Its file paths describe a scenario; they are not downloads or evidence of completed work. You can paste these notes unchanged to practice checking the result.

OpenAI’s prompting guidance recommends specific instructions and reviewing the output. A fixed set of fields and source IDs makes the review easier to perform.

Draft a project handover from these invented practice notes. Use only supplied facts. Return: purpose, current files, completed work, unresolved items, next actions, and receiver checks. Cite note IDs beside factual statements. Keep proposed actions separate from accepted commitments. Do not invent approvals, owners, deadlines, file access or completed checks. Draft text only; do not send it, modify files or contact anyone.
N1: Project: a community noticeboard poster for a book swap.
N2: Folder: Book-swap/poster. Files: poster-v3.pdf and poster-v3-editable.odt. These are example paths, not files supplied to you.
N3: Text proofreading is complete. The printed proof has not been checked.
N4: Permission to display the poster is pending. No approval date is known.
N5: Next proposed action: print one proof and check the date, contact line and margins. No owner has accepted this action.
N6: Do not print the full batch until display permission and the proof check are confirmed.
Finish with three questions the receiver must verify. Mark everything not stated as unknown. Do not claim you opened the example files.

3. Check the filled example against the notes

This is an editorial model of the handover, not a claim that an AI run opened or inspected those files. The three receiver questions are: Can I access both named files? Who will accept the proof-check task? Where will confirmed display permission be recorded?

An answer such as “the poster is ready to print” drops two conditions. “Alex will check it tomorrow” invents both an owner and a deadline. Correct these phrases before handing over the sheet. The summary should preserve the inconvenient gaps just as carefully as the completed work.

4. Review the paper sheet with the receiver

1. Point to the purpose and confirm that the receiver understands the intended outcome.
2. Open the exact files together, or ask the receiver to confirm access separately. Leave the check blank until it happens.
3. Read the unresolved conditions aloud. Mark whether each is still open or has new supporting evidence.
4. Ask who accepts the next action. Add a date only when agreed; otherwise retain unassigned and date unknown.
5. Write the handover date and any correction on both the paper copy and the shared record.

I would use one sheet for a small task with a few files. A larger project needs links to its existing decision log and working documentation; squeezing that history onto one page can hide important dependencies. Keep the sheet as an entry point and name the authoritative records.

5. Keep suggestions separate from the current record

OpenAI’s accuracy guidance explains that generated answers can be incorrect even when confident. In a handover, the error may be a small change in status: pending becomes approved, or proposed becomes assigned. Compare those words directly with the notes.

If the model suggests extra tasks, place them in a separate suggestions section for human review. Do not insert them into the accepted plan without agreement. Keep an old version of the handover when a meaningful condition changes so the next person can understand what was updated.

For handwritten source material, follow the transcription checking steps first. For a tool-enabled agent, use a bounded task brief: drafting a handover does not itself authorize editing project files or sending messages.

Next useful stepHow to make practice questions from notes with AI →