A File Cover Sheet the Firm Can Adapt for AI-Drafted Files

In this method, the Firm gives the Reviewer a cover sheet that answers a few opening questions. Who worked on it? Which version of the Firm's instructions did the AI pass use? Where are the question log, the hand-edit log, the coverage sheet and the review notes? And where does the file stand right now?

A file cover sheet for an AI-drafted file puts those answers on a page at the front of the file. In this method, the Firm keeps the page and the Preparer fills it in by hand as the file moves. The plugin drafts; the Firm's preparer prepares; the Reviewer signs off. The cover sheet is a person's page inside that chain, kept in whatever systems the Firm already uses.

This piece gives a paste-ready cover sheet, status-line wordings the Firm can adapt, a fill-in order and a Doe example.

Where the cover sheet sits

The cover sheet says who is on the file, which instructions the AI pass used, where each log lives and where the file stands. It doesn't say what was checked or whether an entry is right.

The sign-off packet is a different page. In this method, the Firm puts the packet together at sign-off to show what was checked, and the cover sheet points to the records the Firm draws on for it.

Across files, a status board shows where every file stands on a single page. The cover sheet is the page for this file, and its status line can use the board's stage words.

In this method, the Firm uses the close-out checklist after the signature to gather the signed records, and the cover sheet goes into the closed file as the Reviewer signed it.

The cover sheet

The Firm can paste this table into its procedures and add lines. The table holds names, instruction details, log locations, written log statuses, a file status and update details.

In this method, a blank line means the step hasn't been written down yet. A log the file doesn't need gets a written line, such as "no hand edits," so a reader can tell "not needed" from "not written yet."

The Preparer writes each log's location or a written log status from the table, keeping the log's contents in the log.

Status-line wordings the Firm can adapt

The status line is the Firm's own sentence about where the file stands. In this method, the Preparer rewrites it when the file changes stage or hands, and initials the last-updated line. A starting set:

• Drafted; Preparer reading the entry list. The AI pass is done, and the Preparer is working through its entries.
• Questions out to the client. The question log has open rows, and the line points to it.
• Waiting on client documents. Something the file needs hasn't arrived yet, and the status line can say what was asked for.
• Preparer's checks done; with the Reviewer. The file has gone to the Reviewer.
• Sent back by the Reviewer. The review notes say what came back and why.
• Reopened under the Firm's steps. A document or entry changed after sign-off; the line points to the reopen log, and the Reviewer signs off on the whole updated file before it's done.

The Firm can rename any of these. Whatever words it picks go on the Firm's own list, so everyone reads a cover sheet the same way.

A fill-in order the Firm can adopt

In this method, the Firm fills the cover sheet as the file moves, not at the end. The Firm can set a different order; these steps are one way to write it down.

1. When the file opens, the Preparer writes the client file, Preparer and Reviewer lines.
2. After the AI pass, the Preparer writes the name of the Firm's instructions and the version the pass used, as the Firm's own instruction list names it.
3. As each log starts, the Preparer writes where it lives. A log the file doesn't need gets a written line instead of a blank.
4. Each time the file changes stage or hands, the Preparer rewrites the status line and initials the last-updated line.
5. Before sending the file to the Reviewer, the Preparer opens each pointer and checks that it leads to the current log.
6. The Reviewer reads the cover sheet first, then the file, and sends back any line that doesn't match what the file shows.
7. The Preparer corrects the line by hand, and the Reviewer reads the change before signing off on the whole file.

What the Reviewer does with it

In this method, the Reviewer starts with the cover sheet.

The cover sheet is the Preparer's page, not a decision on the file. A pointer that leads to the wrong log, a version that doesn't match the entry list, or a stale status line goes back to the Preparer like any other review note. The Reviewer signs off on the whole file, cover sheet included. No file is done without the Reviewer's sign-off.

When the file changes hands

In this method, the outgoing Preparer writes the handoff note, and the incoming Preparer reads the cover sheet first. In this method, the incoming Preparer updates the Preparer line and status line by hand, then initials the last-updated line.

The Reviewer line stays as written unless the Firm names a different Reviewer. If the log locations are unchanged, the incoming Preparer keeps the pointers as written; otherwise, the incoming Preparer corrects them by hand.

A Doe example

The names and file below are made up for illustration.

Jane Doe, a Preparer, opens the synthetic Doe Holdings file and starts its cover sheet. She writes the client file name, herself as Preparer and Pat Doe as Reviewer. After the AI pass, she writes the Firm's name for its instructions and the version label she believes the pass used.

As the file moves, Jane fills in the pointers. The question log sits in the client folder beside the entry list. The hand-edit log starts when she corrects a drafted label by hand. She runs the coverage check and writes where the coverage sheet lives. The review notes line reads "no notes yet." As the file changes stage, Jane rewrites the status line by hand and initials the last-updated line: "Drafted; Preparer reading the entry list," then "Questions out to the client," then "Preparer's checks done; with the Reviewer." Before sending the file to Pat, Jane opens each pointer and checks that it leads to the current log.

Pat opens the file and reads the cover sheet first. The version label on the cover sheet doesn't match the label on the entry list. Pat doesn't guess which is right. She writes a review note and sends the line back to Jane, who updates the review notes pointer and changes the status line to "Sent back by the Reviewer."

Jane opens the Firm's instruction list and the entry list. The version line Jane wrote on the entry list when she ran the pass shows the right label; she had copied an earlier label onto the cover sheet. She corrects the instruction line by hand, sets the status line back to "Preparer's checks done; with the Reviewer," and initials the last-updated line.

Pat reads the corrected line, then the rest of the file, and clears her note. The status line still reads "Preparer's checks done; with the Reviewer," which is where the file stands when Pat signs. Pat signs off on the whole file, cover sheet included.

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. In TracePrep's workflow, the plugin drafts, the Firm's preparer prepares, and the Firm's Reviewer signs off. Access to the plugin is by waitlist. Keep client data inside the systems your Firm has approved.