Hand over the promises. Keep the loose ends visible.

Transfer the next job, not the whole sales history

The receiving team needs enough context to lead the next conversation without making the customer repeat the sale. Start with the customer's intended outcome, purchased scope, accountable people, and next milestone. Then list each commitment or unresolved expectation separately, with a reference a colleague can actually check.

Keep confirmed, unclear, and not-discussed items distinct. Avoma's handoff playbook uses this distinction to avoid turning missing information into apparent agreement. In this checker, confirmed means a named person says they checked the source. It is not a verification performed by the tool.

• One row per commitment or clarification action, with a stable ID.
• A source reference: a document section, email, or call timestamp.
• A delivery or clarification owner, next-action date, and receiving owner.
• An explicit confirmation state and work status.
• A note explaining completed or cancelled work, so closed items do not disappear.

Nine records. Six need review. Here is the answer.

Use the fictional sample with a review date of August 29, 2026. It has nine records, eight distinct IDs, seven open actions, one completed item, and one cancelled draft. Six records have ten flags. Two open actions are overdue. These are authored teaching materials checked by deterministic rules, not reported results from running an AI model.

The checker retains both C-105 records, including their different dates. It also retains the completed and cancelled records. A tidy summary that quietly dropped those rows would make the handoff harder to audit.

• Record 2, C-102: the initial data import has no owner and is two calendar days past its August 27 date.
• Record 3, C-103: the integration question is explicitly unclear and has no receiving-owner acknowledgment. Its September 10 date is a clarification deadline, not a delivery promise.
• Record 4, C-104: the sponsor item is marked confirmed but lacks both a source reference and a human confirmer.
• Records 5 and 6, C-105: the training action appears twice, with September 3 and September 17 dates. A person must decide what those versions mean.
• Record 9, C-108: the billing contact was not discussed, and the clarification date is one day past due.
• C-101, C-106, and C-107 have no structural flags under these rules. That is not proof of the underlying facts.

Prepare a reviewable copy of your records

Map a copy of your export to the sample's twelve columns: commitment_id, customer, commitment, source_ref, confirmation, confirmed_by, delivery_owner, due_date, priority, status, received_by, and status_note. Include every header, even when some cell values are unknown. The tool rejects missing, duplicate, or extra column names instead of quietly dropping data. Keep your untouched source export separately.

Use confirmed, unclear, or not_discussed for confirmation; critical, high, or normal for priority; and open, complete, or cancelled for work status. Leave missing names and dates blank. Exact placeholder names or references such as TBD, unknown, and unassigned are also flagged. Do not fill gaps with plausible guesses to obtain a cleaner report. A person should set the priority and record the source review.

Choose an explicit review date and use YYYY-MM-DD for due dates. The checker supports up to 10,000 data records and 1,000,000 UTF-8 bytes per CSV. It runs the stated checks in the page without reading source links, contacting your CRM, or sending messages.

Resolve the findings without rewriting the history

Start with unclear priorities and the critical items in the reviewer queue. Open work needs an owner, a next-action date, and an acknowledgment from the receiving owner. Confirmed work also needs a source reference and the name of the person who checked it. A repeated ID is always flagged, even when the two records look identical; the checker does not know whether it is a repeated export or two distinct actions.

An open item is overdue when its valid due date is earlier than the selected review date. An item due on that date is not overdue. Completed and cancelled items are not counted as overdue open work, but they still need the appropriate identity and closure information. A cancelled draft needs an explanation, not an invented delivery commitment.

In the practice kit, explicit fictional review addenda resolve ownership, clarify expectations, and authorize revised dates. The corrected input has eight records and no structural flags. The disappearance of a flag means the supplied fields now satisfy a rule; it does not establish that someone read the cited source or approved the handoff.

Let AI draft from the reviewed register

AI can help turn a reviewed register into an internal handoff note, but polished language can conceal uncertainty. Give the assistant an approved copy of the register and its gap list together. Ask it to keep every ID, owner, date, and unresolved item traceable. Do not provide confidential sales material to an external tool unless your organization permits it.

A useful drafting instruction is: Draft an internal sales-to-CS handoff from these records. Separate confirmed commitments from unclear and not-discussed items. Preserve the IDs and source references. Include the next owner, action, and date, plus every unresolved flag. Do not infer scope, commercial terms, dates, customer statements, or approvals. Do not send anything.

If you review the note in Word, Anthropic documents selected-text edits, comment threads, and tracked-change mode. Those features help review a document; they do not prove its claims. This checker works without an AI subscription, and the downloadable examples are not copies of a native product's output.

Keep a source register and a dated review snapshot

Before kickoff, have the receiving owner confirm what they now own and what they still need answered. Save the checked register and gap export with the chosen review date. Edit the original twelve-column register when the sources change, then run the check again. The exported report includes extra audit columns and is a snapshot, not a replacement input schema.

The full CSV keeps every supplied record and finding. On-screen tables show at most 100 records and abbreviate long cells. A subsequent customer transition should reuse the structure and rules, not the previous customer's dates or promises. Track recurring gaps to decide which fields sales should capture earlier.