Legal AI task pre-submission checklist

Confirm the submission surface

• The selected folder contains only the final deliverables required for this task.
• Source authorities, earlier drafts, build scripts, prompt history, archives and unrelated reference material are outside the submission surface unless expressly required.
• The number and type of files match the task instructions and the platform’s upload fields.
• Every required input exists in the final task slot—not merely somewhere in the project.
• For model-assisted work, confirm which required files were actually inspected. An attached file or ZIP is not proof that its contents were read.

Reconcile the task, rubric and deliverables

• Each required deliverable maps to an instruction or rubric item.
• Every MUST requirement is satisfied once; no single issue is accidentally counted twice.
• The requested format, naming convention, jurisdiction, audience and as-of date are correct.
• Any deliberate trap or ambiguity remains present after the final repair.
• Tool use in this phase complies with the current project’s written rules.

Check what one document can break in another

• Names, entity details, dates, amounts, defined terms and IDs agree across files.
• Every citation supports the proposition attributed to it—not merely a nearby topic.
• Every quotation used in a comparison or failure analysis appears in the claimed source and still means what the analysis says it means.
• Each source named in task or grader prose actually exists and is available to the model.
• No comment, emphasis, author note or conspicuous error leaks the intended answer.
• No repair silently changed the problem the task was designed to test.

Make the artifacts safe for ordinary tools

• Documents open without repair warnings; PDFs are readable; spreadsheets and delimited files parse normally.
• Document reading order still makes sense when paragraphs and tables are extracted mechanically.
• Tracked changes, comments, hidden sheets, stale names, accidental highlights and personal metadata are removed when the instructions require clean files.
• No tool name, build note, future timestamp or internal path survives in final artifacts.
• Every automated check states whether it passed, failed or could not run. A skipped check is never treated as a pass.

Do the part a checker cannot do

• Read the final work as the intended reviewer—not as the person who built it.
• Confirm the legal reasoning, authority, confidentiality and professional judgment yourself.
• Open the actual files from the actual submission surface one final time.
• Save the permitted record of what was checked and when, without retaining restricted client or platform material.

Try the private Merit sample

Merit’s browser checker is designed around the mechanical half of this list. Run a fictional family-law task with planted defects, then run its repaired version. The sample is generated and checked inside your tab; there is no signup and no upload.