Start with the boundary
A paralegal at a small litigation office gets a call from opposing counsel's assistant on a Thursday afternoon: "Can you confirm which documents went out in your second production, and how they were sent?" The paralegal remembers a drive link emailed a few weeks ago. The responsible lawyer remembers a disc that went by courier. The numbering ranges are in a spreadsheet on a former assistant's desktop, and the cover letter is somewhere in a shared inbox. Answering a simple question takes most of an afternoon.
That scene is an original illustration, not a TwoQM client and not a measured result. What was missing was a record the office could open and trust.
TwoQM has written about consultation intake and document collection, client portal document checklists, conflict-check intake fields, and trust-account receipt logging handoffs. This piece is about something later in a matter: the administrative log of what the firm sent out in discovery, so staff can answer "what went out, when, how, and to whom" in minutes.
What gets produced, what is withheld, how documents are designated, and when anything is due are decisions for the responsible lawyers under the rules and orders that apply to each matter. This article does not address those questions, and software should not either. A production log records what people did after those decisions were made. It is not a substitute for the lawyer's judgment, the case file, or the review platform the firm already uses.
Why production records drift
Most small firms do not lack care. They lack one place for the facts:
Scattered steps. Numbering happens in one tool, the transfer happens by email or courier, and the cover letter lives in the document system.
Ranges kept in personal files. The numbering ranges for each volume sit in a spreadsheet one person maintains.
Delivery proof in inboxes. Download confirmations, courier receipts, and "received, thanks" replies stay in whichever inbox got them.
Supplements that blur together. When a production is supplemented or corrected, nobody records which earlier volume it relates to.
What each production log entry records
A practical log has one entry per production volume, and every field is a fact someone can verify:
Matter and volume: the matter number and the volume label the firm assigned.
Numbering range: the first and last page or document identifiers, copied from the numbering tool rather than retyped from memory.
Counts: documents and pages as reported by the tool that prepared the volume.
Designations as applied: the confidentiality labels the responsible lawyer directed, recorded as directed, never chosen by the system.
Sent to: each recipient as listed on the cover letter.
Method and date sent: secure link, physical media, or other method, with the date and the named staff member who sent it.
Delivery proof: the courier receipt, download confirmation, or acknowledgment, attached to the entry.
Cover letter and related log: links to the cover letter and to any withheld-documents log the lawyer prepared, stored where the firm already keeps them.
Relates to: for supplements or replacements, the earlier volume it relates to.
The log points to files; it does not need to copy them. Documents stay in the review platform and document system your firm already approved.
Audit-friendly by design
"Staff can audit" means the log shows its own history:
Add, don't overwrite. A correction is a new, named line that says what changed and why. The original entry stays visible.
Named people at each step. Prepared by, approved to send by (the lawyer or the person the firm designates), and sent by are separate fields.
Role-based access. Staff can add entries for their matters. Only designated people can mark a volume as approved to send.
A short open-items view. Volumes prepared but not yet sent, sent without delivery proof, or supplements with no "relates to" link.
When someone asks what went out, the answer is one search by matter.
Where connected systems and automation help
Most firms already run a practice management system, a document system, and a review or numbering tool. Connected systems work can pull the matter list from practice management, receive the numbering range and counts from the tool that prepared the volume, and link the cover letter from the document system, if those systems allow it. Whether your current software supports those connections is confirmed during scoping.
Ordinary business automation handles reminders: alerting the named owner when a volume has sat in "prepared" or has no delivery proof after a period the firm chooses, and sending the responsible lawyer a weekly list of open items.
Where AI helps, and where it stops
AI integrations can draft a plain-language summary of a matter's production history for a lawyer to review, suggest which earlier volume a supplement might relate to for staff to confirm, and prepare a first Spanish draft of an internal note that a bilingual team member edits. A person reviews every draft.
AI does not decide what is produced or withheld, apply designations, evaluate privilege, calculate deadlines, or send anything to anyone. Those stay with the firm's lawyers and the staff they direct.
Where to start this week
Pick one active matter. List every production volume, then try to find the numbering range, date sent, method, recipients, and delivery proof for each. Whatever took longest to find is the first field your log needs.
TwoQM builds connected systems, automation, and custom software for law firms in the Rio Grande Valley and beyond. If your production records live in several inboxes and one person's spreadsheet, TwoQM can scope a production log around the tools you already use. Pricing explains how business apps, systems, and custom software are scoped. TwoQM builds tooling; it does not give legal advice, and no software makes a firm compliant on its own. Nothing here is legal advice.
Describe Your Production Tracking Workflow · Explore connected systems