Fix the framework, number requests, and dictate findings by item.

Dictating Due Diligence Checklists works best when the framework is fixed before the first item is spoken. Decide what the checklist covers: corporate records, contracts, employment, real property, intellectual property, litigation, or finance. Choose whether the checklist follows a request-list structure, a question-and-answer structure, or a findings memo organized by category. Identify the deal stage and the reader, because a checklist for an initial request reads differently from one prepared for a signing committee. Write the framework, the categories, and the intended reader at the top of the file. A checklist with no framework grows into an uneven list that misses a category and repeats another.
Set the materiality threshold and the exception rule before drafting. Decide which items are required for every target and which apply only when a trigger is present, such as a regulated license or a government contract. Decide how an item is marked when the target has no responsive document: not applicable, missing, or waived with a reason. Decide who can waive an item and whether a waiver must be approved in writing. These rules keep the checklist consistent across targets and reviewers, and they prevent the quiet drift that happens when each reviewer invents a personal standard for what counts as complete.
Map the checklist to the transaction documents. Note the representations and warranties the checklist must support, and note the conditions to closing that depend on a document. If the deal has a virtual deal room, note the folder convention so each item can point to a location. If the deal has a disclosure schedule, note how the checklist findings will feed it. A checklist built from the deal documents, rather than from a generic template alone, produces findings that the drafters can use directly. It also shows which categories deserve a deeper review because a representation depends on them. If a representation has no matching item, add one now rather than discovering the gap during drafting.
Assign owners and a review rhythm. Name the person who prepares each category, the person who reviews it, and the person who resolves an open item. Set a date for the first complete pass and a shorter window for updates as new documents arrive. Decide how the checklist version is controlled, since a checklist that changes without a version number is hard to reconcile with earlier findings. Keep the framework note, the materiality rules, and the owner list in one file. A checklist is a working instrument, and its value depends on someone being able to say, at any moment, which items are complete and who is responsible for the rest.
Build the request list with stable numbering before you dictate any findings. Give each item a number that includes the category, a sequence, and a short label, so a reviewer can cite an item without quoting it in full. Group the items in the order a reviewer would work: entity and charter, minute book, capitalization, material contracts, employment, property, intellectual property, litigation, tax, and finance. Keep one item per line and one question per item. Reserve a block of numbers for each category so later additions do not force a renumber. A compound item that asks for three things is hard to close, because it can be partly answered and partly missing, and the status becomes ambiguous.
Write each item as a request a target can answer without guessing. Name the document type, the period, and the signatory where relevant. For example, ask for the charter and all amendments as filed, rather than for corporate formation documents. Ask for contracts above a stated value and for the amendments and side letters that modify them. Ask for the schedule and the documents that support each entry. A precise request reduces follow-up rounds, and it makes a missing response visible, because the reviewer can compare what was asked with what arrived. Where a period matters, state it as dates rather than as a number of years.
Add the tracking fields each item needs. Record the target entity, the category, the request date, the owner, the status, the document received, and the reviewer. Add a field for the follow-up date and a field for the reason an item is open. If several targets are being reviewed in parallel, add a target column so the same item can be tracked separately for each entity. Keep the list in a format that can be filtered and sorted, because a checklist that can only be read in one order becomes unusable once a deal has more than a few dozen items. Freeze the column set once the list is in use, so a status update does not move a value into the wrong field.
Pilot the list on one target before sending it broadly. Send the list to the target's contact, ask for a response on a small subset, and note where the request was misunderstood. Revise the wording of any item that produced a question, and add a note to any item that produced a partial response. Check that the numbering survives the revision, because renumbering after findings have been recorded breaks the link between the list and the notes. A pilot round on one target is cheap, and it prevents the same confusion from repeating across every entity in the deal. Record the pilot responses in the tracking fields, so the first real round starts from a tested list.
Dictate findings against the numbered list, one item at a time, in list order. For each item, state the number, the status, the document reviewed, the date, and a one-sentence finding. Then state the follow-up, if any. Keep the finding factual: what the document says, what it does not say, and what remains missing. Do not merge two items into one note, even when the same document answers both, because the reviewer needs a separate status for each. A findings note that follows the list order can be compared with the list line by line, and a gap is visible immediately rather than at the end of a long memo. If a note runs long, split it into a status line and a separate exception entry under the same item number.
Use a small, fixed vocabulary for status. Choose labels such as complete, missing, not applicable, partial, and needs review, and define each one in the framework note. Do not invent a new label mid-review. If an item is partial, state what was received and what is still outstanding. If an item is not applicable, state the reason. If an item needs review by a specialist, name the specialist and the question. A controlled vocabulary makes the checklist sortable and lets a reader count open items without reading every note. Print the definitions on the first page so every reviewer applies the same meaning.
Capture exceptions and red flags in the same note, not in a separate document. When a document reveals a change of control clause, a missing consent, an expired license, or a litigation hold, record the item number, the document, the page, and the consequence the reviewer should consider. Keep the observation factual and cite the source. Do not characterize the risk in strong terms without the document behind it. A checklist that carries its exceptions next to the item is far more useful at the drafting stage than one that buries them in a narrative memo that no one can reconcile with the list.
Close each dictation block by checking the last few items against the documents. Confirm that the status matches the document, that the citation points to the right page, and that the follow-up names a person and a date. Correct errors while the source is open. If an item produced a long note, consider whether it belongs in a separate exceptions memo and whether the checklist should carry only a short pointer. Keep the checklist readable. A checklist that becomes a second memo loses the one quality that makes it useful: the ability to see, at a glance, what is complete and what is not.
Verify the citations before the checklist leaves your desk. Read each finding and confirm the item number, the document name, the date, and the page. Confirm that the document cited is the version in the deal room and not an earlier draft. Check that a finding described as complete is supported by the document and that a finding described as missing was actually requested. Voiskey helps at this stage because it learns names, jargon, acronyms, and spelling preferences, so entity names and defined terms stay consistent across hundreds of items. Download Voiskey before the citation pass and dictate corrections at the insertion point rather than retyping notes. Sample at least one item from each category, because errors cluster in the categories with the most documents.
Check the arithmetic and the counts. Count the items by status and confirm that the totals match the list. Confirm that every item has a status and an owner, and that no item was left blank. If the checklist reports a percentage complete, confirm the calculation and the denominator. Counts are the first thing a reader checks, and a mismatch between the summary and the list undermines confidence in the findings. Recalculate after any late addition, and note the date of the count so a later reader knows which version it describes. If the totals do not match, find the item with the missing or duplicated status before publishing anything.
Check the open items against the follow-up log. Confirm that each open item has a named owner, a request date, and a follow-up date. Confirm that items marked not applicable have a reason, and that items marked partial state what is outstanding. Review the exceptions list and confirm that each one points to an item and a page. Voiskey adapts punctuation, formatting, and tone to the document you are working in, so checklist notes read consistently even when several reviewers dictated different categories. Download Voiskey when a deal team maintains checklists across several targets and wants one editing routine.
Record the verification and the version. Keep a log with the reviewer, the date, the items sampled, and any correction made. Note the checklist version and the date of the count. If a correction changed a status, record the reason so the change can be explained later. Voiskey turns spoken requests into AI-ready prompts, including file names, paths, and commands, so the log entry and the file name can be dictated in one pass. Download Voiskey and attach the log to the checklist so the review can be reconstructed when a drafter asks why an item was marked complete.
Issue the checklist with a short cover note that states the version, the date, the scope, and the summary counts. List the categories, the number of items, and the number open. Point the reader to the exceptions memo if one exists. Name the person who maintains the list and the person who approves a status change. Send the same version to everyone who will rely on it, and keep a record of distribution. A checklist that circulates without a version number creates the worst outcome in a deal: two reviewers working from different lists and disagreeing about which items are closed. Confirm that the cover note uses the same counts as the list it describes.
Track closure on a fixed rhythm. Review the open items at each deal meeting, update the status, and record the follow-up date. When a target delivers a document, mark the item partial or complete the same day, so the list does not fall behind the deal room. When an item is waived, record the approver and the reason. When a new item is added, add it at the end of its category with a new number rather than renumbering the list, so earlier findings remain traceable. Closure is a habit, not a final push before signing. If a target sends a revised document, record the revision date and recheck the item it affects.
Feed the findings into the deal documents. Use the checklist to support the disclosure schedule, the representations, and the closing conditions. Note which items remain open and which are acceptable with a specific disclosure. Voiskey supports 100+ languages and translation when a target or a counterparty works in another language, and it adapts formatting to the document. Download Voiskey to prepare the cover note and the cross-reference list in the same pass. A checklist that is linked to the documents it supports saves the drafters from rebuilding the same analysis under deadline. Keep the checklist version that supported the schedule, so a later question can be traced to the exact list.
Review the checklist after the deal closes. Note which categories produced the most open items, which requests were misunderstood, and where the numbering or the status vocabulary failed. Update the template, the item wording, and the tracking fields. Keep a lessons note with the template so the next deal starts from a better list. Voiskey supports a team plan with shared vocabulary and workflows, which helps when a deal team runs checklists across many targets and wants consistent terms. Download Voiskey and keep the template and the note together for the next transaction. Close the note with the next review date so the checklist does not sit unchanged between meetings.
Voiskey is an AI voice typing app for the desktop. Press a shortcut and speak a finding for an item, and the text appears at the insertion point in the checklist you already have open. It removes filler words, stutters, false starts, and grammar slips, so each item note lands as clean text that you then check against the document.
Yes. Voiskey learns names, jargon, acronyms, and spelling preferences, which helps when a request list repeats target names, defined terms, and document titles across many items. You still confirm each name and citation against the source, and a fixed numbering scheme keeps the list stable as findings are added.
Press a shortcut and speak the item note, and the text appears at the insertion point. Voiskey removes filler words, stutters, and false starts and adapts punctuation and formatting. The polish step is where you confirm the status, the document, the page, and the follow-up owner. At up to 220+ words per minute, the routine produces a full draft for the citation check.
Yes. Voiskey is system-level, so text appears at the insertion point in whatever app or text field holds the checklist. You speak findings and corrections directly into the list and revise them in the same place, with no separate suite to open. The workflow is Speak-Polish-Type-Edit, so fixes land in the version that will be issued.

Download Voiskey for Mac and Windows and keep every draft moving from first note to final check.
Use it across macOS, Windows, iOS, and Android