AI contract review: a checklist for checking the output
Review AI contract summaries against the actual agreement, including definitions, exceptions, missing schedules, and questions for a lawyer.
40 PRACTICAL GUIDES
Technology & law
guides.
Check AI outputs, preserve digital evidence, and organize copyright, privacy, and data-breach questions.
Browse this topic ↓Original examples · Official sources
Choose the question you need to answer
40 guidesHow to fact-check an AI summary of legal documents
Use a claim-by-claim audit to catch missing dates, changed speakers, unsupported conclusions, and omissions in an AI document summary.
An AI legal research log that keeps sources traceable
Track research questions, jurisdictions, source dates, case status questions, and verified passages when using AI for legal research.
Before sending an AI-written demand letter: review checklist
Check an AI demand-letter draft for invented facts, unsupported legal claims, inaccurate totals, private information, and unintended commitments.
Checking an AI medical chronology for record errors
Audit an AI treatment timeline for service dates, provider identity, copied diagnoses, missing records, and unsupported causation statements.
AI transcript summaries: check speakers, timing, and uncertainty
Review AI summaries of interviews or meetings without losing speaker identity, corrections, uncertainty, or the context surrounding a statement.
Questions to ask a legal AI vendor about data retention
Compare AI vendor terms for retention, model training, deletion, subcontractors, access controls, and export without relying on a privacy slogan.
Checking facts extracted by AI from a document bundle
Verify AI-extracted dates, amounts, names, and references across a document bundle while preserving missing values and duplicate records.
How to spot false certainty in an AI legal answer
Identify unsupported percentages, missing jurisdictions, invented facts, and assumptions hidden inside confident AI legal explanations.
Prepare an AI-assisted case summary for a lawyer
Create a short, source-linked handoff that distinguishes verified facts, AI suggestions, missing records, and the decisions you need help with.
AI-generated images and copyright: records to keep
Document human edits, source materials, prompts, and tool terms before asking about copyright protection for an AI-assisted image.
AI music rights: organize the composition and recording
Separate lyrics, composition, vocals, samples, generated audio, and production edits when preparing a rights review for AI-assisted music.
Voice and likeness replicas: a consent review checklist
Organize the scope, uses, duration, approval rights, and deletion questions for a proposed AI voice or likeness replica.
Deepfake scam evidence: what to preserve and verify
Document a suspected synthetic voice or video scam without assuming a detector result proves how it was made or who created it.
Prepare a report about an impersonation account
Collect profile URLs, screenshots, misleading messages, and report references before asking a platform to review an impersonation account.
Before a DMCA notice: organize the ownership and URLs
Prepare an ownership record and precise location list before reviewing an online copyright takedown request with qualified help.
AI-assisted creative work: questions for a client agreement
Clarify AI use, source assets, deliverables, permissions, revisions, and ownership questions before a creative project begins.
Software handoff: organize licenses and third-party code
Build a practical inventory of dependencies, notices, source code, generated contributions, and licensing questions before delivering software.
Build a clear comparison file for a copyright concern
Compare original and disputed material with dates, URLs, permissions, and context before deciding whether a copyright claim is appropriate.
AI-generated code: keep a provenance and review record
Track generated code, human edits, dependencies, testing, and licensing questions without assuming functional code is legally cleared.
Text messages as evidence: preserve the conversation
Organize a message thread with timestamps, sender context, attachments, and missing portions before preparing it for a dispute.
Email evidence: preserve headers, attachments, and context
Create a reliable email record that distinguishes display names, addresses, message headers, attachments, and the surrounding correspondence.
Screenshot evidence: keep the URL, date, and surrounding page
Capture online material with enough context to explain where it appeared, when it was viewed, and what the screenshot does not show.
Exporting cloud files for a dispute: a version checklist
Keep cloud-file versions, access context, comments, and export limitations visible when preparing documents for review.
Dashcam footage after an accident: preservation checklist
Preserve dashcam footage, timestamps, camera settings, and surrounding clips without editing away context or assuming the camera clock is correct.
File metadata in a dispute: what it can and cannot show
Understand creation dates, modification dates, location fields, and hashes without treating metadata as automatic proof of authorship or truth.
PDF redaction: check the text is actually removed
Prepare a redacted working copy, inspect hidden text and attachments, and verify the final PDF before sharing private records.
Chat exports for disputes: keep attachments and thread structure
Organize a workplace or service chat export with channels, participants, timestamps, attachments, and gaps clearly documented.
Location history as evidence: document the limits
Record how location data was collected and what its accuracy, timing, account access, and gaps allow you to conclude.
Electronic signatures: records to keep with the agreement
Preserve the signed version, audit trail, signer context, attachments, and consent questions when reviewing an electronically signed agreement.
Received a data breach notice? Build a response record
Verify a breach notice, identify the information involved, record protective actions, and track questions without assuming every exposure caused identity theft.
How to check a data breach settlement notice
Verify the case, court documents, administrator, eligibility language, and deadlines before trusting a data breach settlement message.
California privacy access requests: prepare the right details
Organize a CCPA access request with the correct business, account context, date range, verification process, and response record.
California data deletion requests: track scope and exceptions
Prepare and track a California privacy deletion request without confusing account closure, marketing opt-out, and deletion of personal information.
Data broker removal requests: keep a verifiable log
Track broker listings, official removal routes, identity checks, and follow-up without paying for promises that every copy will disappear.
Read an app privacy policy with a data-flow checklist
Compare an app's permissions, data uses, sharing, retention, and controls before putting sensitive dispute information into it.
AI hiring concerns: records to prepare for review
Document an automated hiring process, assessment barriers, communications, and accommodation questions without assuming the software alone proves discrimination.
Biometric data collection: questions before enrollment
Ask about face, voice, or fingerprint collection, storage, purpose, alternatives, retention, and sharing before using a biometric feature.
Ransomware incident documentation for a small business
Keep a factual incident timeline, affected-system list, response decisions, costs, and adviser contacts during a ransomware response.
Cookie and tracking complaints: document the actual interaction
Record a website's consent choices, policy version, account state, and observed behavior without claiming a browser observation proves a privacy violation.