100 Best Gemini Contract and Agreement Drafting Prompts for Law Firms

Direct Answer

The best Gemini prompts for contract and agreement drafting for law firms are ready-to-use prompts that cover purpose, governing law, scope, liability, confidentiality, data protection, IP, termination, SLAs, audits, disputes, and governance. Use them to accelerate drafting, testing, and risk assessment while preserving accuracy and compliance.

Introduction

This page is a practical prompt library for contract and agreement drafting aimed at law firms and legal teams seeking faster, safer drafting workflows using Gemini prompts.

Each prompt is crafted to be copyable, actionable, and ready to deploy in real client engagements with clear outputs and constraints.

How to Use These Gemini Prompts

• Replace placeholders like [industry], [jurisdiction], and [data map] with your client specifics before running the prompt.
• Add or adjust constraints to match client risk tolerance and regulatory requirements.
• Request outputs in your preferred format such as clause text, tables, or checklists to fit your document templates.
• Verify generated outputs against your firm’s standards and conduct a quick risk and compliance check after each run.
• Keep a running glossary of defined terms to maintain consistency across prompts.

100 Best Gemini Contract and Agreement Drafting Prompts for Law Firms

1. Clarify contract purpose: Role: you are a contract drafting assistant. Task: summarize the contract's primary purpose and key objectives in plain language. Context: client is in [industry] and wants to [outcome]. Output format: bullet list with five items. Constraints: avoid legal jargon and include at least one risk note for each objective.
2. Identify governing law: Role: legal analyst. Task: determine governing law implications for a contract in [jurisdiction]. Context: parties from multiple states. Output format: short answer with one paragraph and one bullet. Constraints: cite potential conflicts and preferred choice of law provisions.
3. Define scope precisely: Role: contract drafter. Task: create a scope clause for a service agreement. Context: services include [services list], deliverables [deliverables], timeline [timeline]. Output format: clause text plus a brief justification. Constraints: avoid ambiguity and specify acceptance criteria.
4. Liability allocation: Role: risk counsel. Task: draft liability allocation for damages in a vendor contract. Context: [data security] and [indemnification]. Output format: two-part section with caps and definitions. Constraints: cap damages and exclude indirect loss unless expressly agreed.
5. Confidentiality specifics: Role: compliance drafter. Task: tailor a mutual confidentiality clause for a technology deal. Context: parties exchange nonpublic information including trade secrets. Output format: clause with exceptions and survival period. Constraints: define permissible disclosures and return/destruction obligations.
6. Data protection addendum: Role: data privacy advisor. Task: draft a DPA aligned with GDPR/CCPA as applicable. Context: data processing activities listed in [data map]. Output format: DPA section with roles, subprocessors, and security measures. Constraints: include breach notification timeline.
7. IP ownership terms: Role: IP counsel. Task: establish ownership and license rights for deliverables. Context: work-for-hire vs. preexisting IP. Output format: ownership table plus licensing matrix. Constraints: clarify license grant scope, exclusivity, and post-termination rights.
8. Non-solicitation guardrails: Role: HR/legal reviewer. Task: craft a fair non-solicitation clause for staffing services. Context: duration, geographic scope, and carve-outs. Output format: clause and a short impact analysis. Constraints: avoid overbroad restrictions and provide blue-pencil options.
9. Payment terms clarity: Role: finance counsel. Task: draft payment schedule for a SaaS agreement. Context: upfront fees, milestones, and late fees. Output format: payment table and definitions. Constraints: include currency, invoicing cadence, and dispute process.
10. Termination triggers: Role: contract strategist. Task: specify termination rights for material breach and convenience. Context: subscription services. Output format: termination clause with cure period and wind-down steps. Constraints: add data return duties.
11. Service levels: Role: operations expert. Task: define SLAs for uptime and support. Context: critical business functions. Output format: SLA table with measurement methods and remedies. Constraints: include maintenance windows and reporting requirements.
12. Data breach procedure: Role: security lead. Task: outline breach notification and remediation steps. Context: incident suspected within 72 hours. Output format: incident response plan excerpt and contact list. Constraints: align with applicable laws and customer notification needs.
13. Audit rights framework: Role: compliance auditor. Task: draft audit rights for vendor compliance. Context: security controls and data handling. Output format: audit clause with notice, scope, and remediation timeline. Constraints: balance vendor operations and customer assurance.
14. Change control process: Role: project counsel. Task: implement change control for project-based contracts. Context: evolving requirements. Output format: change order procedure and approval matrix. Constraints: include pricing impact and timeline adjustments.
15. Warranties list: Role: product lawyer. Task: assemble a warranties schedule for a software product. Context: performance, compatibility, and support. Output format: table with qualifier and remedy. Constraints: cap remedies and exclude lost profits unless stated.
16. Indemnity structure: Role: risk manager. Task: create indemnity clauses for third-party claims. Context: data breach and IP infringement. Output format: indemnity matrix and notice procedure. Constraints: define cap and exclusions.
17. Governing law choice: Role: jurisdiction strategist. Task: select most favorable governing law and forum. Context: cross-border sale of goods. Output format: memo with three options and final pick. Constraints: consider enforceability and cost.
18. Export controls: Role: compliance advisor. Task: add export control restrictions. Context: dual-use technology. Output format: clause plus a risk note. Constraints: reference applicable sanctions lists.
19. Assignment rights: Role: contract administrator. Task: draft assignment clause. Context: corporate restructuring. Output format: clause with notice and consent requirements. Constraints: include successory rights.
20. Subcontracting clause: Role: procurement lawyer. Task: authorize subcontracting with flow-down terms. Context: critical services. Output format: clause plus a subprocessor schedule. Constraints: require prime contractor oversight.
21. Conflicts check: Role: compliance lead. Task: perform conflicts check workflow for new client. Context: matter opening. Output format: checklist and template emails. Constraints: avoid leakage of client names.
22. Insurance requirements: Role: risk advisor. Task: specify insurance coverage for vendors. Context: limits and types. Output format: schedule with policy types, limits, and proof of insurance. Constraints: require certificates of insurance.
23. Acceptance criteria: Role: QA lead. Task: define acceptance tests for deliverables. Context: software build. Output format: acceptance criteria table and exit criteria. Constraints: include defect classification.
24. Limitation of liability: Role: liability counsel. Task: cap damages for breach of contract. Context: software services. Output format: liability cap language with carve-outs. Constraints: exclude indirect damages except for intentional misconduct.
25. Compliance mapping: Role: compliance analyst. Task: map contract obligations to regulations. Context: industry standard. Output format: obligation matrix and responsible roles. Constraints: update when laws change.
26. Residuals clause: Role: IP attorney. Task: address residual knowledge in deliverables. Context: consultant work. Output format: clause with carve-outs and ownership. Constraints: clarify what remains in consultant's head.
27. Data minimization: Role: privacy engineer. Task: limit data collection in line with purpose. Context: analytics project. Output format: data map excerpt and retention rules. Constraints: specify deletion timelines.
28. Retention periods: Role: records manager. Task: define data retention for contracts. Context: archival requirements. Output format: retention schedule and destruction method. Constraints: meet legal hold needs.
29. Open source terms: Role: software counsel. Task: manage OSS obligations. Context: vendor software components. Output format: OSS disclosure and compliance matrix. Constraints: include license compatibility.
30. Data localization: Role: privacy strategist. Task: decide localization requirements. Context: cross-border data transfers. Output format: localization decision memo and safeguards. Constraints: consider user access needs.
31. Dispute resolution: Role: dispute architect. Task: specify escalation and mediation. Context: long-term vendor relationships. Output format: dispute ladder and selected forum. Constraints: avoid court fees where possible.
32. Confidential handling: Role: information governance. Task: define handling of sensitive materials. Context: joint development. Output format: handling matrix and labeling scheme. Constraints: apply least privilege.
33. Force majeure: Role: risk manager. Task: draft force majeure events and relief. Context: supply chain disruption. Output format: events list and notice window. Constraints: require mitigation where feasible.
34. Audit trail: Role: systems auditor. Task: mandate change logs and access records. Context: enterprise software. Output format: audit log standards and retention policy. Constraints: include tamper-evident requirements.
35. Background checks: Role: HR and compliance. Task: require vendor personnel checks. Context: sensitive projects. Output format: clause and verification steps. Constraints: respect privacy laws.
36. Data return and delete: Role: data controller. Task: specify data return and deletion on termination. Context: SaaS service. Output format: data return and destruction clause. Constraints: preserve necessary backups.
37. Redaction standards: Role: information security. Task: set redaction rules for disclosures. Context: confidential documents. Output format: redaction template and examples. Constraints: balance usefulness and confidentiality.
38. Background IP carveouts: Role: IP strategist. Task: delineate preexisting IP rights. Context: joint development. Output format: IP schedule and licenses. Constraints: document ownership flow.
39. Warranty disclaimers: Role: product counsel. Task: draft explicit warranty disclaimers. Context: beta features. Output format: disclaimer list and remedies. Constraints: avoid misrepresentation risk.
40. Sublicense rights: Role: licensing attorney. Task: define sublicensing ability. Context: platform integration. Output format: license grant and sublicense terms. Constraints: require upstream approvals.
41. Data processing roles: Role: privacy controller. Task: assign DPA roles. Context: multi-entity processing. Output format: roles table and responsibilities. Constraints: include subprocessors list.
42. Remedies table: Role: commercial lawyer. Task: enumerate remedies for breaches. Context: service agreement. Output format: remedies matrix with cure periods. Constraints: specify exclusive vs non-exclusive.
43. Non-competition scope: Role: corporate counsel. Task: draft reasonable non-compete terms. Context: professional services. Output format: clause with time and geography. Constraints: ensure enforceability.
44. Transition assistance: Role: vendor manager. Task: plan transition services post termination. Context: critical operations. Output format: transition plan outline and milestones. Constraints: define success criteria.
45. Escalation contacts: Role: operations liaison. Task: build escalation matrix. Context: incident response. Output format: contact list and escalation tiers. Constraints: include on-call hours.
46. Background check liability: Role: HR counsel. Task: cap liability related to background checks. Context: employment provisions. Output format: liability limitation note and safe harbor. Constraints: comply with laws.
47. Payment dispute flow: Role: finance proxy. Task: define dispute handling for invoices. Context: recurring services. Output format: dispute process diagram text. Constraints: include timely resolution.
48. Ownership of work products: Role: IP lawyer. Task: specify ownership of deliverables produced during engagement. Context: consulting project. Output format: ownership schedule. Constraints: include work product return on termination.
49. Third-party rights: Role: contract attorney. Task: identify third-party rights. Context: licensing and use. Output format: rights checklist and notification steps. Constraints: avoid implied licenses.
50. Service continuity: Role: risk manager. Task: ensure service continuity plan in contract. Context: mission-critical systems. Output format: continuity requirements and testing schedule. Constraints: include failover responsibilities.
51. Open disputes clause: Role: litigation strategist. Task: outline dispute resolution without court. Context: cross-border contract. Output format: clause and timeline. Constraints: preserve relationships.
52. Work-for-hire clarity: Role: IP counsel. Task: clarify work-for-hire vs. assign preexisting rights. Context: software development. Output format: rights matrix and signatures. Constraints: define author attribution.
53. Quality assurance: Role: QA manager. Task: embed QA criteria in contract. Context: product release. Output format: QA criteria table and acceptance test plan. Constraints: link to defect severity.
54. Service credits: Role: commercial counsel. Task: set service credits for SLA breaches. Context: cloud services. Output format: credit calculation table. Constraints: avoid punitive penalties.
55. Data subject requests: Role: privacy officer. Task: specify handling of data subject access requests. Context: GDPR/CPRA. Output format: process flow and timelines. Constraints: verify identity.
56. Confidentiality duration: Role: security lead. Task: set confidentiality duration post-termination. Context: trade secrets. Output format: duration language and exceptions. Constraints: align with trade secret laws.
57. Export license clauses: Role: regulatory counsel. Task: incorporate export license controls. Context: sanctioned destinations. Output format: clause and screening steps. Constraints: maintain compliance audit trails.
58. Independent contractor terms: Role: labor lawyer. Task: draft IC engagement terms. Context: long-term project. Output format: clause set and payment terms. Constraints: clarify IP and confidentiality.
59. Data breach liability: Role: security officer. Task: assign breach liability responsibilities. Context: client data. Output format: liability table and notification duties. Constraints: align with regulatory timelines.
60. Remix and derivative rights: Role: IP strategist. Task: define rights to derivatives. Context: collaborative development. Output format: derivatives schedule. Constraints: clarify ownership of improvements.
61. Acceptance testing: Role: test lead. Task: plan acceptance tests for deliverables. Context: integration project. Output format: test cases list and pass criteria. Constraints: require traceability.
62. Limitation carve-outs: Role: liability expert. Task: list carve-outs to liability cap. Context: data loss. Output format: carve-out list. Constraints: specify willful misconduct.
63. Non-disparagement: Role: PR counsel. Task: draft non-disparagement clause. Context: vendor relationship. Output format: clause and safe harbors. Constraints: avoid chilling speech.
64. Cure periods: Role: contract manager. Task: set cure periods for breaches. Context: ongoing project. Output format: table of breaches and cure timelines. Constraints: align with materiality.
65. Publication rights: Role: marketing legal. Task: control publicity around engagement. Context: joint press release. Output format: publicity clause and approvals. Constraints: respect confidentiality.
66. Background data maps: Role: privacy architect. Task: create data maps for processing. Context: multi-entity data flows. Output format: data map excerpts. Constraints: keep up-to-date.
67. Test data handling: Role: QA security. Task: define test data guidelines. Context: software testing. Output format: test data policy and masking rules. Constraints: avoid real data.
68. Non-solicitation remedies: Role: employment lawyer. Task: craft remedies for non-solicitation breach. Context: staffing vendor. Output format: remedy options and caps. Constraints: proportionate relief.
69. Subprocessor list: Role: privacy lawyer. Task: maintain up-to-date subprocessor list. Context: cloud services. Output format: schedule and notification process. Constraints: add opt-out terms.
70. Audit readiness: Role: security auditor. Task: prepare for annual audit. Context: client security requirements. Output format: pre-audit checklist and evidence list. Constraints: keep artifacts organized.
71. Data subject rights: Role: privacy lead. Task: fulfill data subject requests. Context: cross-border data processing. Output format: workflow and timelines. Constraints: verify identity.
72. Warranty claim process: Role: product support. Task: define warranty claim process. Context: hardware and software. Output format: claim steps and remedies. Constraints: document eligibility.
73. Impossibility clause: Role: risk attorney. Task: insert impossibility or impracticability clause. Context: supply constraints. Output format: clause and notice requirements. Constraints: avoid ambiguity.
74. Insurance evidence: Role: risk manager. Task: require proof of insurance. Context: vendor onboarding. Output format: certificate request checklist. Constraints: expire with policy.
75. Publicity restrictions: Role: compliance manager. Task: govern logo use and statements. Context: joint marketing. Output format: restrictions and approvals. Constraints: avoid misrepresentation.
76. Redundancy planning: Role: operations lead. Task: plan redundancy clauses for critical data. Context: data centers. Output format: redundancy requirements and testing plan. Constraints: single point of failure avoidance.
77. Ethics and compliance: Role: compliance officer. Task: embed ethics standards. Context: client work. Output format: code of conduct reference and training requirement. Constraints: update annually.
78. Background check scope: Role: HR partner. Task: define background check scope for vendors. Context: sensitive roles. Output format: scope and privacy safeguards. Constraints: comply with laws.
79. SaaS data retention: Role: cloud lawyer. Task: set SaaS data retention limits. Context: regulatory retention. Output format: retention table and deletion policy. Constraints: consider backups.
80. Term sheet alignment: Role: corporate attorney. Task: align contract terms with term sheet. Context: funding round. Output format: reconciliation table. Constraints: resolve conflicts.
81. Data porting: Role: data engineer. Task: plan data export/import. Context: vendor changeover. Output format: data porting steps and formats. Constraints: preserve data integrity.
82. Escrow provisions: Role: IP/supply counsel. Task: add source code escrow terms. Context: critical software. Output format: escrow triggers and release conditions. Constraints: ensure rebuild rights.
83. Compliance training: Role: training coordinator. Task: require vendor compliance training. Context: data handling. Output format: training plan and record-keeping.Constraints: track completion.
84. Recordkeeping standards: Role: records manager. Task: define contract recordkeeping. Context: litigation hold. Output format: retention schedule and indexing rules. Constraints: secure storage.
85. Joint development rights: Role: collaboration counsel. Task: define joint IP rights. Context: co-created inventions. Output format: joint ownership and license terms. Constraints: avoid future disputes.
86. Data minimization review: Role: privacy analyst. Task: perform data minimization review. Context: data analytics project. Output format: minimization report and decisions. Constraints: log changes.
87. Open source compliance: Role: software attorney. Task: ensure OSS compliance. Context: project build. Output format: OSS inventory and remediation plan. Constraints: avoid license conflicts.
88. Audit trail integrity: Role: security auditor. Task: ensure tamper-evident logs. Context: enterprise systems. Output format: log integrity controls. Constraints: implement hashing.
89. Data localization plan: Role: privacy architect. Task: craft localization plan for data. Context: global deployment. Output format: localization map and safeguards. Constraints: data subject to local laws.
90. Rights to remedies: Role: commercial attorney. Task: define exclusive remedies. Context: service failures. Output format: remedies table. Constraints: avoid stacking conflicts.
91. Cloud compatibility: Role: cloud architect. Task: ensure contract supports multi-cloud. Context: deployment strategy. Output format: compatibility checklist and safeguards. Constraints: vendor lock-in notes.
92. Third-party collaboration: Role: collaboration counsel. Task: govern collaboration terms. Context: joint go-to-market. Output format: collaboration clause and governance. Constraints: define IP sharing boundaries.
93. Data subject withdrawal: Role: privacy officer. Task: handle data withdrawal requests. Context: marketing data. Output format: workflow and confirmation steps. Constraints: ensure baseline data remains for compliance.
94. Migration support: Role: operations planner. Task: plan data/migration support. Context: vendor transition. Output format: migration support clause and milestones. Constraints: minimize downtime.
95. Security accreditation: Role: security lead. Task: require vendor security certifications. Context: risk management. Output format: accreditation list and verification process. Constraints: renewals.
96. Audit cooperation: Role: compliance liaison. Task: commit to cooperation during audits. Context: client audits. Output format: cooperation clause and response timeline. Constraints: designate primary contact.
97. Disclosures schedule: Role: regulatory attorney. Task: manage routine disclosures. Context: regulatory filings. Output format: disclosures schedule and approval flow. Constraints: prevent leakage.
98. Data breach notification: Role: security officer. Task: define notice timelines. Context: breach incident. Output format: notification template and escalation list. Constraints: comply with laws.
99. Governing language: Role: translation reviewer. Task: ensure contract language consistency. Context: multilingual edits. Output format: language-safe clause set. Constraints: avoid misinterpretation.
100. Signature and execution: Role: contract administrator. Task: finalize execution workflow. Context: multi-party agreement. Output format: execution plan and authority verification. Constraints: ensure proper witness where required.

Best Practices

• Keep prompts modular by separating scope, risk, and compliance into distinct prompts for reuse.
• Log outputs in a prompt library with versioning and client-specific notes to enable reuse and auditing.
• Pair prompts with a human review step to catch nuanced legal interpretations and enforceability issues.
• Favor explicit output formats (tables, clause blocks, checklists) to ease drafting and review.
• Regularly update prompts to reflect changes in laws and regulations and maintain accuracy.

Common Mistakes to Avoid

• Using vague terms like good or adequate instead of precise standards in clauses.
• Overloading prompts with too many topics, which reduces accuracy and increases review time.
• Neglecting jurisdiction-specific requirements or data protection laws in prompts.
• Failing to specify output formats, causing inconsistent drafting across engagements.
• Assuming readers will supply all placeholders without guidance, leading to incomplete outputs.

FAQ

What makes Gemini prompts effective for contract drafting in law firms?

Gemini prompts provide structured, repeatable prompts that reduce drafting time, improve consistency, and support compliance checks when tailored to the firm’s standards.

How should I customize prompts for a specific client industry?

Replace placeholders like [industry], [services], and [data] with client specifics, adjust constraints to industry norms, and add jurisdiction-specific rules.

Can these prompts handle multi-jurisdiction contracts?

Yes, by including prompts that specify governing law, venue, and cross-border considerations, and by adding subprocessors and localization requirements as needed.

What output formats work best with these prompts?

Clause blocks, tables, checklists, and annotated notes align well with typical contract templates and review workflows.

How do I ensure prompts stay compliant over time?

Maintain versioned prompts, review outputs against current laws, and subscribe to regulatory updates relevant to your practice areas.

Are these prompts suitable for junior attorneys?

Yes, prompts are designed to be explicit and explain terms clearly, with defined outputs to support learning and drafting accuracy.