Final document review
Legal Document Final Review Checklist: Before Sending or Filing
A practical final review checklist for checking the approved version, outgoing files, attachments, redaction, hidden data, recipients, and completion proof.
Prepared and reviewed by the Law Firm Training Manual Editorial Team. Read our editorial and correction standards or report a correction.
Update note: Initial publication. Professional-conduct, metadata, Florida E-Filing, Microsoft Word, and Adobe redaction sources were checked on October 2, 2026.
On this page
Review the exact copy that will leave the firm
Final review is a go-or-no-go check of the actual email attachment set, secure-share package, service package, print set, or filing upload. Reviewing the editable source is not enough when conversion, signing, redaction, assembly, renaming, or upload can change what the recipient receives.
This quality-control step does not replace substantive approval or authorize a final checker to make legal decisions. Confirm the purpose, destination, channel, deadline, responsible reviewer, and approval evidence before beginning the production review.
- Identify the authoritative approved version and freeze unapproved changes.
- Assemble the exact outgoing package before checking it.
- Stop if approval, destination, or the controlling version is unclear.
Verify names, numbers, dates, and package completeness
Compare party and entity names, matter or case number, court and county, dates, amounts, defined terms, quotations, citations, and cited authorities with the approved sources. Proofreading from memory or from another draft can repeat the same error.
For citations and authorities, staff verification is mechanical: confirm the source exists and that names, quotations, pinpoints, and links match the approved source. The responsible lawyer decides legal relevance, interpretation, and sufficiency.
Match the complete package to the approved instructions or manifest. Confirm signatures, certificates, exhibits, schedules, attachments, referenced materials, labels, sequence, and required pages. Open each attachment rather than relying on its filename.
- Use a manifest for a multi-file email, service package, or filing.
- Verify the first and last page of every final file as well as the attachment order.
- Return substantive or factual uncertainty to the responsible reviewer.
Inspect the rendered output after conversion or assembly
Open every finished file and check pagination, headers, footers, margins, orientation, image quality, searchable text, bookmarks, hyperlinks, signatures, and any required format or size limit. A source document that looked correct can produce a damaged PDF or incomplete upload.
Compare the exact outgoing copy with the approved version after each material transformation. If a last-minute change occurs, repeat every gate affected by that change rather than relying on the earlier review.
- Do not infer readability from a thumbnail or portal filename.
- Confirm that exhibits and signature pages remain attached and correctly ordered.
- Regenerate and recheck when conversion changes content, layout, or links.
Validate confidentiality, redaction, comments, and hidden data
Identify confidential, protected, or unnecessary sensitive information and apply only the authorized treatment. A visual box, highlight, crop, or image overlay is not necessarily true redaction. Validate the finished copy by testing whether removed content can still be found, selected, copied, extracted, or exposed through layers or attachments.
Microsoft explains that No Markup only changes the view; tracked changes remain until accepted or rejected. Check comments, revisions, document properties, hidden text, prior content, and other metadata under the firm’s approved process. Inspect or sanitize a copy when the tool may make irreversible changes.
- Keep the controlled working original separate from the sanitized outgoing copy.
- Resolve tracked changes and comments rather than merely hiding them.
- Reopen and retest the final output after redaction or metadata removal.
Verify recipients, permissions, and destination independently
Check recipients, domains, court, county, case, filing event, service list, permissions, link access, subject line, attachment names, and delivery settings against an authoritative source. Autocomplete, a previously selected case, or inherited permissions are not independent verification.
Keep destination review separate from document review. A correct document can still be sent to the wrong person, uploaded to the wrong case, shared too broadly, or delivered through a route that does not satisfy the approved instruction.
- Read the destination and attachment or upload list line by line before release.
- Test secure-share access without widening permissions reflexively.
- Obtain any second review required by firm procedure or the responsible lawyer.
Use a deliberate go-or-no-go pause
Release only when the required approval, version, completeness, confidentiality, destination, and format gates pass. Deadline pressure is a reason to escalate a failed gate promptly, not authority to send or file a defective, incomplete, or misdirected package.
The final checker should describe the exact failed condition and preserve the package. The responsible lawyer resolves legal, substantive, confidentiality, filing, and service issues; an authorized supervisor may resolve production, routing, permission, or workflow issues within firm policy. Do not repair a substantive issue silently or invent approval because the delivery window is closing.
- Stop on any material uncertainty about approval, content, confidentiality, or destination.
- Record who cleared the issue and which version was approved.
- Repeat affected checks after every correction.
Preserve proof and verify the later status
After sending or filing, watch the system response for failed delivery, permission warnings, upload errors, correction queues, or rejection messages. Save the sent message, delivery record, share audit detail, submission receipt, filing identifier, acceptance notice, or other completion evidence in the approved matter location.
Submission is not always acceptance, and a sent message is not proof that an attachment was usable. Update the matter with the status, time, owner, next action, and any monitoring responsibility required for the delivery channel.
- Keep transmission, filing, service, court delivery, and acceptance evidence distinct.
- Assign who monitors the next system or recipient response.
- Do not close the task while a rejection, correction, or access issue remains open.
Continue with the related workflow
Use these guides when the next step moves from general verification into a specific filing or scheduling workflow.
Final document send-or-file checklist
Use this as a conversation starter with the person responsible for the work. Replace general language with the firm’s actual systems, owners, and procedures.
- Purpose, authority, destination, channel, deadline, and substantive approval are confirmed.
- The approved delivery route and any service or filing instruction are confirmed.
- The authoritative approved version and exact outgoing package are identified.
- Names, entities, matter or case number, court, dates, amounts, citations, and authorities are verified.
- Attachments, exhibits, signatures, certificates, schedules, and required pages match the approved manifest.
- Every final file was opened after conversion, signing, redaction, or assembly.
- Pagination, headers, footers, links, bookmarks, orientation, images, searchable text, format, and size are checked.
- Confidential and sensitive information received the authorized treatment.
- True redaction was applied and the outgoing copy was tested for recoverable content.
- Tracked changes, comments, hidden text, properties, and unintended metadata were addressed.
- Recipients, domains, permissions, court, county, case, filing event, service list, and delivery settings were independently verified.
- The exact outgoing copy matches the approval and instructions.
- Every failed gate was resolved and affected checks were repeated.
- The final go-or-no-go pause and required second review passed.
- Transmission or filing proof was saved, and later acceptance or access status has an owner.
- The matter record shows the current status, time, owner, and next action.
Official references
These primary sources support the general operational controls discussed above. Check their current versions and follow the governing court, judge, clerk, software, and firm procedures for the actual work.
- Rules Regulating The Florida Bar — Rules 4-1.1, 4-1.6, and 4-5.3
The Florida Bar
- Ethics Opinion 06-2 — Electronic Documents and Metadata
The Florida Bar
- Training Materials and Manuals
Florida Courts E-Filing Authority
- Accept or Reject Tracked Changes in Word
Microsoft Support
- Redact Sensitive Content in PDFs in Acrobat Pro
Adobe Acrobat
Related lesson previews
Practice one workflow at a time
Final Quality Control
Review a Document Before Sending or Filing It
Use the FINAL CHECK workflow to review the exact outgoing copy, verify approval and completeness, remove unintended confidential or hidden content, confirm the destination, and preserve proof.
Preview lessonDocument Status
Distinguish Draft, Signed, Filed, and Entered Documents
Recognize a document's actual status and label or store it without overstating what happened.
Preview lessonE-Filing Preparation
Prepare Documents for Electronic Filing
Build and quality-check a complete, searchable, accessible Florida court filing package before entering the E-Filing Portal.
Preview lessonPDF Safety
Redact Confidential Information from a PDF
Permanently remove authorized content, sanitize hidden information, and test the saved release copy for recovery.
Preview lessonDocument Collaboration
Use Track Changes and Comments Without Losing Control of the Draft
Use the CONTROL workflow to preserve one authoritative Word draft, make edits and questions reviewable, reconcile branches, and produce separately labeled redline and clean copies after markup and metadata checks.
Preview lessonVersion Control
Name and Version Draft Documents
Keep one authoritative working document with a clear name, recoverable history, controlled review copies, and protected record milestones.
Preview lesson
