Handing Off an AI-Drafted File Mid-Season: The Handoff Note

A file changes hands in the middle of prep. Someone gets reassigned, someone's out for a week, a manager moves work to even out the load. The entry list an AI tool drafted looks the same whoever opened it last. What it doesn't show is which rows a person already checked, which instruction produced them, and what's still waiting on the client or the Reviewer.

That's what a handoff note is for. The outgoing Preparer writes one page from the open file, and the incoming Preparer confirms it against the file before doing any work. The tool drafts rows. People check them, decide what they mean, and pass the file to the Reviewer only when the checks are done.

When a file changes hands

The Firm picks the triggers. The list might be a reassignment, a planned absence, and a manager moving files between Preparers. The Firm can make the rule simple: any file in progress gets a handoff note before a new Preparer touches it.

This is a different record from the hand-off log in a chained workflow. That log tracks an artifact moving from one step to the next; the handoff note covers one person passing a whole file to another, at whatever point it has reached.

The note is written by the person leaving the file. If that person is gone without warning, the Firm decides who writes it instead, and the note says so at the top.

What the note covers

The Firm can keep the note to one page and five lines.

Stage reached. Where the file sits: folder set up, drafting pass run, self-review started, in review, or sent back. One stage, named the way the Firm names it everywhere else.

Last instruction run and its version. The instruction the tool ran to draft the entry list, and its version number or date. If the incoming Preparer reruns anything, they start from the same instruction, or they note that they changed it.

Rows checked and rows not yet checked. By row range, not by impression. "Rows 1 to 26 checked against the source; rows 27 to 40 not yet checked" tells the next person exactly where to pick up. A row counts as checked only if the file shows the check.

Open send-backs. The notes the Reviewer sent back that aren't cleared yet, listed by number. The handoff note points to the send-back notes and doesn't rewrite them.

Open client requests. What's been asked of the client, when, and what hasn't come back.

Anything else the outgoing Preparer wants to say goes under a short "also" line at the bottom. The five lines come first so the incoming Preparer can find them fast.

Write it from the file, not from memory

The Firm can require the outgoing Preparer to write the note with the file open, not from recall at the end of a long day. Every line points to something the incoming Preparer can find: a row range on the entry list, an instruction file with its version, a numbered send-back note, a dated client request.

If the outgoing Preparer can't point to it, the line says "not confirmed". A row they remember checking but didn't mark stays in the not-yet-checked range. Under this approach, the incoming Preparer checks that row against the source before marking it checked. Treating an unmarked row as checked can carry an unchecked figure all the way to the Reviewer.

The note gets the outgoing Preparer's name and the date. It goes into the Firm's file with the entry list, where the incoming Preparer and the Reviewer can both find it.

The incoming Preparer confirms it

Under the Firm's rule, the incoming Preparer reads the note against the file before changing anything. Each line gets a yes or a no.

The stage matches what the file shows. The instruction named on the note is the one in the folder, at that version. The rows in the checked range carry their check marks. The open send-backs are open in the file. The client requests match what was sent.

Where a line doesn't match, the incoming Preparer writes down what they found and why it differs. Any row that can't be confirmed as checked moves to the not-yet-checked range. If the outgoing Preparer can be reached, the incoming Preparer asks them; if not, the Firm decides who answers, and the question stays on the note until it's answered.

The incoming Preparer closes the confirm step with one line: who handed off, who picked up, the date, and the count of lines that matched. Only then does the work go on.

What the note is not

A handoff note isn't a review and isn't a sign-off. Writing it doesn't move a row from not yet checked to checked; only the check in the file does that. It also doesn't replace the record the Reviewer builds at the end of the file, before signing. The handoff note is written mid-file and says where things stood on one day.

A Doe example

The figures below are made up for illustration.

Jane Doe, a Preparer at Doe & Co. CPA, is moving to another client team mid-season. Her file for Doe Holdings goes to Morgan Doe. Jane writes the handoff note with the file open.

Stage: self-review started. Instruction: the Firm's statement-drafting instruction, version 3. Rows 1 to 26 checked; rows 27 to 40 not yet checked, so 26 checked and 14 open across 40 rows. Open send-backs: notes 4 and 5 from Pat Doe, the Reviewer, on an earlier pass. Open client request: one missing account statement, asked for last week. Jane signs and dates the note.

Morgan confirms it the next morning. Stage, instruction version, send-backs and the client request all match. In the checked range, row 24 has no check mark. Morgan writes that down, moves row 24 to the not-yet-checked range, and asks Jane, who says she ran out of time on it. So 25 rows are confirmed checked and 15 are left to check, still 40 in all.

Morgan's confirm line reads: Jane Doe to Morgan Doe, five lines checked, four matched, one changed (row 24). Morgan checks rows 24 and 27 to 40 against the source and works through notes 4 and 5. Pat Doe reads the entries back, clears the send-backs and signs off.

Where TracePrep fits

We've built a TracePrep plugin that drafts these steps in your Firm's workflow, while your preparer decides and your Reviewer signs off. Join the waitlist and we'll tell you when plugin access opens.

Get on the list for plugin access

This is general information, not tax or legal advice. Your licensed professional and your Firm's Reviewer are responsible for every return and every conclusion. Keep client data inside the systems your Firm has approved. As general guidance only, not advice: if you use an AI tool with client data, firms generally look for a business or commercial plan whose terms cover how that data is handled; read the vendor's current terms before you do.