Best Prompts for Legal and Compliance

Signed contracts create work long after signature. Renewal windows, notice periods, reporting duties, audit rights, insurance requirements, data handling terms, and approval conditions can sit across the main agreement, schedules, and amendments. When those obligations remain in a folder, teams may discover them only when a deadline or request arrives.

AI can prepare a structured extraction for review. It cannot determine the final legal meaning of a clause or replace advice from qualified counsel. The output is an administrative first pass, not legal advice.

Why ordinary prompting fails

“Summarize our obligations” is too broad. It can blur duties with rights, omit conditional language, ignore amendments, and convert a nuanced clause into an absolute deadline. It may also assign an internal owner who is not named in the contract.

The prompt must preserve exact language, connect every item to a location, distinguish contractual parties from internal responsibility, and surface conflicts for legal review.

Reusable prompt

Copy
ROLE
You are a contract review assistant preparing an obligation register for qualified legal or compliance review. This is not legal advice. Do not interpret enforceability, resolve ambiguity, or make legal conclusions.

REQUIRED INPUTS
1. Complete executed agreement and all schedules, exhibits, statements of work, and amendments: [attach]
2. Document hierarchy or order of precedence, if stated: [details]
3. Our contracting entity and counterparty: [names]
4. Effective date and known term dates: [details]
5. Obligation categories to extract: [renewal, notice, reporting, payment, security, privacy, audit, insurance, etc.]
6. Preferred date format and internal owner taxonomy: [details]

STEPS
1. Inventory every document, signature status, date, and relationship to the agreement.
2. Identify clauses that impose duties, conditions, deadlines, recurring events, approvals, restrictions, or required records on either party.
3. Capture triggering event, timing rule, recipient, method, dependencies, remedy or consequence if expressly stated, and source citation.
4. Distinguish our obligations, counterparty obligations, mutual obligations, rights, and optional permissions.
5. Apply amendments only where their effect is explicit; otherwise show the conflict.
6. Calculate dates only when all inputs and the contractual rule are unambiguous, and show the calculation.
7. Flag legal interpretation questions and missing documents for counsel.

OUTPUT FORMAT
- Notice: “Administrative extraction for review, not legal advice”
- Document inventory
- Obligation register table: ID, responsible contractual party, obligation, trigger, due rule, calculated date if supported, frequency, recipient, method, dependencies, consequence expressly stated, source, confidence
- Rights and options table
- Renewal and termination calendar
- Conflicts, ambiguities, and missing materials
- Questions for qualified counsel
- Suggested internal owner: blank unless supplied taxonomy supports a recommendation; label any recommendation “for confirmation”

EVIDENCE AND UNCERTAINTY RULES
- Quote or closely paraphrase without dropping qualifiers, exceptions, or defined terms.
- Cite document, section, page, and amendment where applicable.
- Never invent a deadline, cure period, consequence, or internal owner.
- Keep “shall,” “may,” “must,” and “commercially reasonable” distinct.
- Do not decide which conflicting clause controls unless the documents explicitly resolve it.
- Mark OCR uncertainty and unreadable text.
- Treat calculated dates as provisional until reviewed.

What to provide

Provide the executed set, not merely the latest PDF found in email. Include amendments, schedules, statements of work, referenced policies, and any notice details incorporated by reference. Identify your legal entity because a corporate group may have several related companies with different duties.

If the files are scans, run approved OCR and retain page images for checking. Define the categories that matter to the review, but allow an “other obligation” category so unusual duties are not discarded. Supply internal owner categories only as suggestions; the contract usually names a party, not the employee responsible inside that party.

How to review the output

Legal or compliance reviewers should verify every high-impact item against the executed text. Check definitions, exceptions, survival clauses, and amendments. Confirm that notice timing uses the correct trigger and method. “Within 30 days after receipt” is not the same as “30 days after sending.”

Recalculate dates, including rules for business days, holidays, deemed receipt, and automatic renewal. Confirm whether an item is an obligation, a condition to exercise a right, or simply permission. Review OCR flags against the image because a single missed word can reverse meaning.

After legal validation, business owners can confirm responsibility and tracking cadence. Keep a link to the source clause in the final register.

Where it fails

Extraction is unreliable when the document set is incomplete, unsigned drafts are mixed with executed versions, or referenced materials are unavailable. Complex clause interaction may require legal interpretation that no prompt should conceal.

This approach does not assess enforceability, privilege, governing law, regulatory duties outside the contract, or whether a clause is acceptable. It should not send notices, update a system of record, or trigger payments without human approval. Confidential documents also require approved storage, access, retention, and model settings.

Practical takeaway

Contract extraction is most useful when it creates a reviewable source map, not when it promises a final answer. Preserve clause language, dates, and uncertainty, then have qualified counsel validate the register. Try this prompt in Agentic Workers on one low-complexity executed agreement before applying it to a larger contract set.

<!-- X derivative: Contract obligation extraction should preserve qualifiers, cite every clause, show provisional date calculations, and remain explicitly subject to qualified legal review. -->