We respect attorney-client confidentiality. No tracking pixels in our emails.
Contract drafting prompts require special structure to produce legally precise output. This library of 25-plus templates covers NDAs, SaaS agreements, M&A provisions, employment clauses, IP assignments, indemnification, and dispute resolution.
2026/07/29
A transactional associate spent four hours drafting a limitation of liability clause for a SaaS customer agreement. A senior partner reviewed it in ten minutes and sent back a two-line redline: the liability cap multiplier was wrong and the carve-outs for gross negligence did not match the firm's standard market position. The associate had not checked the firm's precedent library. The partner had the clause memorized.
That dynamic — associates drafting from first principles while institutional knowledge sits in precedent libraries that are rarely consulted — is one of the primary problems AI contract drafting tools are designed to solve. A well-structured AI drafting prompt can produce a first draft that incorporates standard market positions, firm precedent patterns, and jurisdiction-specific requirements. The result is faster first drafts that require less senior review time.
But contract drafting prompts require more structure than general AI queries. Jurisdiction matters. Whether the client is the customer or the vendor matters. Whether the limitation of liability should protect one party or both matters. Imprecise prompts produce imprecise drafts. This guide provides 25-plus structured templates for the most common transactional drafting tasks.
Contract drafting has always been a knowledge-intensive skill. What distinguishes a senior transactional attorney from a junior one is not facility with language — both can write sentences — but knowledge of market standards, awareness of how specific provisions interact with other parts of the same agreement, and intuition about what a counterparty will accept.
AI drafting tools are best at the first element: market standards. They are trained on large volumes of commercial contracts and can generate provisions that reflect typical market positions. They are weaker on the second and third elements, which require transaction-specific judgment.
This is why prompt structure matters for contract drafting. A prompt that specifies the deal context, the party perspective, and the preferred aggressiveness level produces an AI draft that is closer to a usable starting point. A prompt that says "draft a limitation of liability clause" produces a generic provision that requires substantial editing.
The redlining workflow matters too. AI-drafted provisions are best used as first drafts that the attorney reviews, modifies for transaction-specific context, and then submits. They are not substitutes for attorney analysis of whether the provision is appropriate for the specific deal.
Four elements that every contract drafting prompt should include:
1. Party identification. "Draft from the perspective of [CUSTOMER/VENDOR/LICENSOR/LICENSEE/BUYER/SELLER]." This is the single most important structural element. A limitation of liability drafted for the vendor looks entirely different from one drafted for the customer.
2. Jurisdiction and governing law. "Governed by [STATE] law." Commercial contracts have jurisdiction-specific variations in enforceability — California's restrictions on non-competes, New York's specific performance rules, Delaware's deference to contractual limitation of liability.
3. Deal context. "This is a [DEAL TYPE] agreement for [SUBJECT MATTER DESCRIPTION]." Context determines what provisions are standard (SaaS agreements have different baseline provisions than manufacturing supply agreements).
4. Market standard specification. "Draft using [MARKET/VENDOR-FAVORABLE/CUSTOMER-FAVORABLE] standard positions." This tells the AI where to position the negotiating levers in the draft.
See also: Spellbook vs Luminance comparison.
Template 1 — Mutual NDA for Early-Stage Business Discussions When to use: Two parties in preliminary discussions about a potential transaction or partnership, each sharing confidential information. "Draft a mutual non-disclosure agreement governed by [STATE] law. Both parties will share confidential information in connection with evaluating [TRANSACTION/PARTNERSHIP TYPE]. Include: (1) definition of Confidential Information with appropriate carve-outs for public domain, prior knowledge, and independent development; (2) two-year obligation period; (3) standard of care (same as party's own confidential information, at least reasonable care); (4) permitted disclosures (employees on a need-to-know basis, professional advisors); (5) return or destruction of confidential information on request; (6) specific performance remedy provision; (7) no license grant. Use balanced market positions appropriate for similarly situated commercial parties."
Template 2 — One-Way NDA for Vendor Evaluation When to use: Company evaluating a vendor's product or service and sharing confidential requirements or business information. "Draft a one-way non-disclosure agreement governed by [STATE] law from the perspective of [DISCLOSING PARTY/OUR CLIENT] disclosing confidential information to [RECEIVING PARTY] in connection with evaluating [VENDOR'S PRODUCT/SERVICE]. Include: (1) broad definition of Confidential Information covering business plans, technical specifications, and financial information; (2) three-year obligation period; (3) specific prohibition on reverse engineering; (4) requirement to notify disclosing party of unauthorized disclosure; (5) injunctive relief remedy without bond requirement; (6) survival clause for trade secrets. Draft with positions favorable to the disclosing party."
Template 3 — NDA with Residual Knowledge Clause When to use: Technology or IP-intensive relationship where the receiving party's employees will gain general knowledge during the engagement. "Draft a mutual non-disclosure agreement governed by [STATE] law that includes a residual knowledge clause. The residual knowledge clause should: (1) permit parties to use general knowledge, skills, experience, ideas, and concepts that are retained in the unaided memory of employees who had access to Confidential Information; (2) not apply to intentionally memorized specific Confidential Information; (3) not affect the parties' other obligations under the NDA. Explain in a brief note how courts in [STATE] have treated residual knowledge clauses and any drafting risks."
Template 4 — Limitation of Liability Clause (Vendor Position) When to use: Software vendor negotiating liability cap in customer agreement. "Draft a limitation of liability clause for a SaaS customer agreement governed by [STATE] law from the vendor's perspective. Include: (1) mutual cap on indirect and consequential damages (lost profits, loss of data, business interruption), with clear exceptions for data breach, intellectual property indemnification obligations, and willful misconduct; (2) liability cap equal to fees paid in the [12/6]-month period preceding the claim; (3) essential basis of the bargain language for enforceability; (4) survival of limitation clause. Use market-standard vendor positions. Note: flag if [STATE] has specific enforceability restrictions on limitations of liability in commercial software contracts."
Template 5 — Indemnification Clause (SaaS, Mutual) When to use: SaaS agreement requiring both parties to indemnify each other for specific risks. "Draft a mutual indemnification clause for a SaaS customer agreement governed by [STATE] law. Vendor indemnifies customer for: third-party claims that the software infringes third-party IP rights; claims arising from vendor's gross negligence or willful misconduct. Customer indemnifies vendor for: third-party claims arising from customer's use of the software in violation of the agreement; claims arising from customer's data or content. Include standard indemnification procedure (prompt notice, control of defense, cooperation, no settlement without consent). Use market-standard positions."
Template 6 — Data Processing Addendum (GDPR) When to use: SaaS vendor processing EU personal data on behalf of a customer. "Draft a data processing addendum (DPA) for a SaaS agreement where vendor processes [DATA TYPES] as a data processor on behalf of customer (data controller) under GDPR Article 28. Include: (1) subject matter, duration, nature, and purpose of processing; (2) instructions for processing; (3) confidentiality obligations; (4) technical and organizational security measures; (5) subprocessor requirements and notification; (6) data subject rights assistance; (7) deletion or return of data on termination; (8) audit rights; (9) transfer mechanism for data transfers outside the EEA ([STANDARD CONTRACTUAL CLAUSES/OTHER MECHANISM]). Draft for a [STATE] law-governed SaaS agreement with GDPR compliance as the primary objective."
Template 7 — Uptime SLA and Service Credits When to use: Customer negotiating service level commitments in a SaaS agreement. "Draft an uptime service level agreement (SLA) for a SaaS customer agreement from the customer's perspective. Include: (1) definition of "Uptime" (monthly uptime percentage, excluding scheduled maintenance); (2) uptime commitment of [99.9%/99.5%]; (3) measurement methodology and reporting; (4) service credits for failure to meet SLA (graduated scale: [X]% credit for [Y]% downtime); (5) procedure for claiming credits; (6) cap on total service credits per month; (7) sole remedy limitation (credits as sole remedy, or include right to terminate for repeated SLA failures). Note the market standard for [INDUSTRY TYPE] SaaS agreements on uptime commitments."
Template 8 — Termination for Convenience Provision When to use: Either party needing termination flexibility in a SaaS or services agreement. "Draft a termination for convenience provision for a [SaaS/SERVICES] agreement governed by [STATE] law from the perspective of [CUSTOMER/VENDOR]. Include: (1) right to terminate on [30/60/90] days written notice; (2) effect of termination on outstanding fees (prorated refund vs. no refund for annual prepaid terms); (3) data return provisions post-termination (time period for data export, deletion timeline); (4) survival of provisions post-termination. Note the market-standard position for [CUSTOMER/VENDOR] on refund rights upon termination for convenience."
Template 9 — Organization and Authority Rep When to use: Standard opening representations in any acquisition agreement. "Draft the organization and authority representations and warranties for a [ASSET/STOCK] purchase agreement governed by [STATE] law from the seller's perspective. Include: (1) due organization and valid existence; (2) authority to execute and perform; (3) no conflict with organizational documents, material contracts, or applicable law; (4) required consents and approvals; (5) binding obligation. Draft at a market-standard level of qualification (materiality qualifiers, knowledge qualifiers where appropriate)."
Template 10 — No-Material-Adverse-Change Representation When to use: Bring-down condition in acquisition agreements. "Draft a Material Adverse Change definition and closing condition for a [DEAL TYPE] acquisition governed by [STATE/DELAWARE] law. The MAC definition should: (1) define material adverse effect on the target; (2) include a standard carve-out list (general economic conditions, market-wide changes, acts of God, changes in applicable law, post-signing announcement effects); (3) include a disproportionate effect exception for otherwise excluded matters; (4) close the 'double materiality' scrape issue. Draft using Delaware-standard MAC language reflecting post-AB InBev market practice."
Template 11 — Intellectual Property Representation When to use: Technology company or IP-heavy acquisition. "Draft intellectual property representations and warranties for a [DEAL TYPE] acquisition of a [TECHNOLOGY/IP-HEAVY COMPANY] governed by [DELAWARE/STATE] law from the seller's perspective. Include: (1) ownership of material IP, free and clear of liens; (2) validity and enforceability of registered IP; (3) no infringement of third-party IP; (4) no pending or threatened IP claims; (5) employee and contractor IP assignment; (6) open source compliance; (7) data privacy compliance for IP embedded in software. Include knowledge qualification, materiality threshold, and disclosure schedule references."
Template 12 — Material Contracts Representation When to use: Any acquisition where contract assignment or consent is at issue. "Draft material contracts representations and warranties for a [DEAL TYPE] acquisition governed by [STATE] law from the seller's perspective. Include: (1) definition of Material Contract with specific categories (contracts above [DOLLAR THRESHOLD], customer contracts representing [%] of revenue, vendor contracts that cannot be replaced within [TIME PERIOD]); (2) representation that all Material Contracts are in full force and effect; (3) no material default; (4) no termination or modification rights triggered by the transaction. Include consent requirement representation and reference to consent schedule."
Template 13 — Litigation Representation When to use: Establishing the boundary of disclosed litigation in any acquisition. "Draft litigation representations and warranties for a [DEAL TYPE] acquisition governed by [STATE] law from the seller's perspective. Include: (1) no pending litigation above [THRESHOLD]; (2) no threatened litigation of which seller has knowledge; (3) no governmental investigations or proceedings; (4) no outstanding orders, injunctions, or decrees; (5) reference to litigation schedule for disclosed items. Qualify with knowledge and materiality as appropriate for market standard."
Template 14 — Non-Solicitation Clause When to use: Employment agreements in states with limited non-compete enforcement. "Draft a non-solicitation provision for an employment agreement in [STATE], where non-compete clauses [ARE/ARE NOT] enforceable. The non-solicitation should: (1) prohibit solicitation of the company's customers with whom the employee had material contact during [18/24]-month lookback; (2) prohibit solicitation and hiring of company employees; (3) [STATE]-appropriate duration; (4) include carve-out for general advertising; (5) blue-pencil or savings clause for overbroad provisions. Note: flag any [STATE]-specific restrictions on non-solicitation enforceability."
Template 15 — Severance and Good Reason Provision When to use: Executive employment agreement with separation protections. "Draft a severance and Good Reason provision for an executive employment agreement governed by [STATE] law. Good Reason definition should include: material reduction in compensation, material diminution of duties, required relocation beyond [MILES], and material breach by company. Severance should provide: [X] months base salary, continuation of benefits for [X] months, and acceleration of [PERCENTAGE]% of unvested equity, conditioned on execution of a release. Include Section 409A compliance language and clawback provision reference."
Template 16 — Confidentiality and IP Assignment in Employment Agreement When to use: Establishing standard IP ownership provisions in employment agreements. "Draft a combined confidentiality and intellectual property assignment provision for an employment agreement governed by [STATE] law. Include: (1) definition of Confidential Information; (2) obligation to protect and not disclose; (3) assignment of all inventions, works, and discoveries created during employment using company resources or relating to company business; (4) carve-out for employee inventions unrelated to company business developed entirely on personal time (comply with [STATE] statutory IP assignment limitations); (5) obligation to assist with patent prosecution; (6) power of attorney. Flag [STATE]-specific statutory limitations on employee IP assignment."
Template 17 — Technology IP Assignment When to use: Standalone IP assignment agreement for software or technology. "Draft a technology intellectual property assignment agreement governed by [STATE] law for the assignment of [SOFTWARE/PATENT/TRADE SECRET] from [ASSIGNOR TYPE] to [ASSIGNEE TYPE]. Include: (1) identification and description of the IP being assigned; (2) assignment of all right, title, and interest including patent rights, copyright, trade secrets, and goodwill; (3) consideration; (4) representations by assignor (ownership, no prior assignment, no liens); (5) obligation to execute further instruments for recordation; (6) power of attorney. Note any domain-specific assignment requirements for recorded IP."
Template 18 — Work Made For Hire and Assignment When to use: Contractor agreement where IP ownership is at issue. "Draft an intellectual property provision for a contractor agreement governed by [STATE] law that ensures the company owns all work product. Include: (1) work made for hire provision for works that qualify under the Copyright Act; (2) assignment for all work product that does not qualify as work made for hire; (3) waiver of moral rights to the extent permitted by law; (4) license-back provision if contractor has pre-existing IP incorporated in the work product; (5) contractor representation of no third-party IP infringement. Note the boundary between work-made-for-hire eligibility and assignment-only works under U.S. copyright law."
Template 19 — One-Way IP Indemnification When to use: Software or technology vendor providing IP indemnification to customer. "Draft an intellectual property indemnification clause for a software licensing or SaaS agreement governed by [STATE] law from the vendor's perspective. Include: (1) obligation to defend and indemnify customer from third-party claims that the software infringes a U.S. patent, copyright, or trade secret; (2) carve-outs for customer modifications, combination with third-party products, customer data, and use after notice of infringement; (3) remediation options (modify, replace, obtain license, or terminate with refund); (4) this section as the exclusive remedy for IP infringement claims; (5) indemnification procedure (notice, control, cooperation). Draft at market-standard vendor positions."
Template 20 — Mutual Commercial Indemnification When to use: Balanced commercial agreements where each party indemnifies for its own risks. "Draft a mutual indemnification clause for a [AGREEMENT TYPE] governed by [STATE] law. Each party indemnifies the other for: (1) its own negligence, willful misconduct, or material breach of the agreement; (2) third-party claims arising from the indemnifying party's [PRODUCTS/SERVICES/DATA]. Include: standard indemnification procedure; cap on indemnification obligations tied to the limitation of liability; survival of indemnification obligations post-termination. Note any [STATE]-specific restrictions on indemnification of a party's own negligence."
Template 21 — Data Breach Indemnification When to use: Agreements involving processing of personal data or customer confidential data. "Draft a data security breach indemnification provision for a [SaaS/SERVICES/PROCESSING] agreement governed by [STATE] law. Include: (1) obligation to indemnify for third-party claims and regulatory penalties arising from a security breach caused by the indemnifying party's failure to maintain the agreed security standards; (2) direct damages coverage for breach notification costs, credit monitoring, and forensic investigation; (3) notice and cooperation obligations; (4) carve-out for breaches caused by the indemnified party's own systems or acts. Note: flag whether this provision should be carved out from the limitation of liability."
Template 22 — Mandatory Arbitration Clause (Commercial) When to use: B2B commercial agreement where the parties prefer private resolution. "Draft a mandatory arbitration clause for a commercial agreement governed by [STATE] law. Include: (1) AAA Commercial Rules (or JAMS) governing arbitration; (2) seat of arbitration ([CITY/STATE]); (3) number of arbitrators (one for disputes under [$AMOUNT], three for disputes above); (4) confidentiality of proceedings; (5) interim relief carve-out (parties may seek injunctive relief from courts); (6) costs and fees allocation (each party bears own, unless arbitrator awards otherwise); (7) class action waiver. Note enforceability considerations in [STATE] for the specific agreement type."
Template 23 — Forum Selection and Governing Law When to use: Establishing jurisdiction for dispute resolution in any commercial agreement. "Draft a governing law and forum selection clause for a [AGREEMENT TYPE] governed by [STATE] law. Include: (1) governing law clause selecting [STATE] law without regard to conflicts of law principles; (2) exclusive jurisdiction in [STATE/FEDERAL] courts in [CITY, STATE]; (3) consent to personal jurisdiction and service of process; (4) waiver of jury trial (if appropriate for agreement type); (5) costs and fees provision. Note: flag any issues with the chosen forum for enforcement against [COUNTERPARTY DOMICILE TYPE] parties."
Template 24 — Escalation and Mediation Clause When to use: Long-term commercial relationships where preserving the relationship matters. "Draft a dispute escalation and mediation clause for a [LONG-TERM AGREEMENT TYPE] governed by [STATE] law. Include: (1) mandatory senior management escalation before formal proceedings (specify executive levels and [30]-day period); (2) mandatory non-binding mediation before arbitration or litigation (JAMS or AAA, mediator selection process); (3) confidentiality of mediation; (4) tolling of limitations periods during escalation and mediation; (5) preservation of injunctive relief rights. Note the typical timeline and cost for this type of escalation process."
Template 25 — International Arbitration Clause When to use: Cross-border commercial agreements where neither party wants the other's home court. "Draft an international arbitration clause for a cross-border agreement between a [U.S./JURISDICTION 1] party and a [JURISDICTION 2] party. Include: (1) ICC Rules (or LCIA) governing arbitration; (2) seat of arbitration ([NEUTRAL CITY — e.g., London, Singapore, New York]); (3) language of arbitration (English); (4) number of arbitrators (three for disputes above [THRESHOLD]); (5) governing law for the arbitration clause (separately from the agreement's governing law); (6) enforcement under the New York Convention; (7) interim measures. Note any treaty or regulatory restrictions on arbitration enforceability in [JURISDICTION 2]."
Scenario: Associate uses Templates 4 and 5 together for a SaaS agreement
A SaaS vendor's associate is preparing a customer agreement for a mid-size enterprise customer. The customer has pushed back on the standard limitation of liability cap and wants a broader indemnification.
The associate uses Template 4 (vendor LOL position) to generate the vendor's standard limitation of liability language, noting the essential basis of the bargain language. They then use Template 5 (mutual indemnification) to draft the indemnification clause with appropriate carve-outs. The AI outputs provide structurally correct first drafts that the associate modifies for deal-specific context — the actual fee amount, the client's preferred damage carve-out for data breaches, and the survival period.
The two AI-generated drafts take 20 minutes to produce and 30 minutes to review and modify. Pre-AI, drafting both provisions from the precedent library would have taken approximately 90 minutes.
Spellbook — Best for in-Word drafting using these templates as prompts. Fast and Word-native.
DraftWise — Best for firms with organized precedent libraries. Drafts draw from firm-specific language.
Harvey AI — Best for enterprise transactional teams with complex deal contexts.
Luminance — Best for full-document drafting and playbook-based markup review.
Robin AI — Strong for mid-market transactional drafting with collaborative review features.
See also: Spellbook vs Luminance comparison and Ironclad vs Evisort for CLM context.
Q: How should I handle deal-specific provisions that are not addressed in these templates?
A: Use the structural framework (party identification, jurisdiction, deal context, market standard) and add a fifth element: the specific deal context that makes the provision non-standard. Describe the transaction-specific consideration in plain language and ask the AI to draft a provision addressing it within the framework of the standard clause type.
Q: Can I use these templates for non-U.S. jurisdictions?
A: Yes, with substitutions. Replace governing law references with the applicable foreign jurisdiction. Use tools with strong international coverage for non-U.S. matters — Vincent AI or Leya for EU and Scandinavian jurisdictions. Note that many of these templates reference U.S.-specific legal structures (New York Convention, FAA, UCC); adapt or remove those references for non-U.S. governing law.
Q: How do AI-drafted provisions hold up in litigation?
A: AI-drafted provisions, when reviewed and approved by counsel, are legally equivalent to attorney-drafted provisions — courts do not distinguish based on the drafting tool. The risk is that AI drafts contain errors that attorney review fails to catch. The quality of the review is what determines legal enforceability, not the drafting method.
Q: What is the right level of specificity for the deal context description in the prompt?
A: More specificity produces better outputs. Instead of "a SaaS agreement," write "a SaaS agreement for cloud-based HR software provided to enterprise customers in the financial services industry." Industry context, deal size, and party type all affect what "market standard" provisions look like.
Q: Should I disclose to clients that AI tools were used in drafting their agreements?
A: Check your jurisdiction's ethics guidance. Some bars require disclosure; most do not require disclosure of drafting tools specifically (attorneys use many tools). The key obligation is that the work product meets the standard of care — AI-generated provisions that are not properly reviewed do not meet that standard regardless of disclosure.
Twenty-five structured contract drafting templates, organized by provision type and deal context, replace ad hoc prompting with disciplined transactional drafting methodology. The four structural elements — party identification, jurisdiction, deal context, and market standard — are the variables that transform a generic prompt into a legally precise drafting instruction.
Chain templates for full agreement sections: use the SaaS templates together to produce a complete commercial terms package, then use the dispute resolution templates to finalize the dispute mechanics. Use DraftWise to layer in firm precedent patterns on top of the AI-generated starting points.
All AI drafts require attorney review. The value is in the time saved on first-draft generation, not in eliminating attorney analysis of whether the provision fits the transaction.
This article reflects independent editorial analysis. LawyerAI does not accept payment for editorial coverage. Tool scores are based on methodology described in Our 5-Dimension Methodology. Last reviewed: 2026-07-29.