30 Claude Prompts That Draft Contracts

You are a contracts attorney who drafts plain-English freelance agreements that protect independent professionals. <context> I need a complete freelance services agreement I can edit and send. Return it as a single self-contained document artifact (clean Markdown) with numbered clauses and bracketed placeholders, previewable instantly. </context> <inputs> - Freelancer and client names: [FREELANCER NAME] / [CLIENT NAME] - Services to be delivered: [SCOPE SUMMARY] - Fee and payment terms: [AMOUNT, MILESTONES OR HOURLY] - Timeline / term: [START DATE, DEADLINES] - Governing law / jurisdiction: [STATE OR COUNTRY] - IP ownership preference: [CLIENT OWNS ON FINAL PAYMENT / FREELANCER LICENSES] </inputs> <task> Draft the agreement with these numbered sections: Parties and effective date, Scope of services, Fees and payment (including late-payment interest), Expenses, Term and termination, Revisions and acceptance, Intellectual property and assignment, Confidentiality, Independent contractor status, Warranties and disclaimers, Limitation of liability, Indemnification, Dispute resolution and governing law, Entire agreement and amendments, and a Signature block for both parties. Use every bracketed input where relevant. </task> <constraints> - Plain English; define any unavoidable legal term in a short parenthetical. - Every variable (names, dates, amounts, jurisdiction) is a [BRACKETED PLACEHOLDER], never invented. - One self-contained document; no external references the reader cannot see. - Open with a one-line note: this is a template, not legal advice — have a qualified lawyer review before signing. </constraints> <format> Return the full agreement as a document artifact, then list the three clauses most worth a lawyer's eyes for my situation. </format>

You are a project contracts specialist who writes precise statements of work that attach to a master services agreement. <context> I need a standalone Statement of Work for a specific project. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly so I can edit deliverables and dates. </context> <inputs> - Provider and client: [PROVIDER NAME] / [CLIENT NAME] - Master agreement it falls under: [MSA TITLE AND DATE OR "STANDALONE"] - Project objective: [WHAT WE ARE BUILDING / DELIVERING] - Deliverables and acceptance criteria: [LIST] - Timeline and milestones: [DATES] - Fees and invoicing schedule: [AMOUNTS, TRIGGERS] </inputs> <task> Draft the SOW with: a header tying it to the MSA, Project overview and objectives, Detailed scope and deliverables table (deliverable, description, acceptance criteria, due date), Out-of-scope exclusions, Assumptions and dependencies, Project schedule and milestones, Fees and payment schedule, Change-request process, Roles and responsibilities (RACI-style list), Acceptance and sign-off procedure, and a Signature block. Make the deliverables table explicit and testable. </task> <constraints> - Use a clean Markdown table for deliverables and the payment schedule. - Every name, date, and amount is a [BRACKETED PLACEHOLDER]. - Keep scope and exclusions sharp so there is no ambiguity about what is and is not included. - Add a one-line note that this template is not legal advice and should be lawyer-reviewed. </constraints> <format> Return the SOW as a document artifact, then flag any deliverable whose acceptance criteria are too vague to enforce. </format>

You are a contracts attorney who structures recurring consulting retainers for advisors and agencies. <context> I need a monthly retainer agreement for ongoing consulting. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Consultant and client: [CONSULTANT NAME] / [CLIENT NAME] - Retainer scope: [WHAT THE RETAINER COVERS EACH MONTH] - Monthly fee and included hours: [AMOUNT, HOURS CAP] - Overage rate: [RATE FOR HOURS BEYOND CAP] - Term and renewal: [INITIAL TERM, AUTO-RENEW?] - Notice period to cancel: [DAYS] </inputs> <task> Draft the retainer with: Parties and effective date, Retainer scope and included services, Monthly fee, included hours, and overage handling, Unused-hours rollover policy, Term, auto-renewal, and cancellation notice, Availability and response-time expectations, Out-of-scope work and change orders, Confidentiality, IP and work-product ownership, Independent contractor status, Limitation of liability, Governing law, and a Signature block. </task> <constraints> - Be explicit about how hours are tracked, what counts toward the cap, and what happens to unused hours. - All variable terms are [BRACKETED PLACEHOLDERS]. - Plain English, one self-contained document. - Include a one-line not-legal-advice note recommending lawyer review. </constraints> <format> Return the retainer as a document artifact, then suggest two retainer terms clients most often try to renegotiate and how the draft handles them. </format>

You are an employment-law-aware contracts drafter who writes contractor agreements that hold up to worker-classification scrutiny. <context> I am engaging an independent contractor and want an agreement that reinforces genuine contractor status. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Hiring party and contractor: [COMPANY NAME] / [CONTRACTOR NAME] - Nature of work: [WHAT THE CONTRACTOR DOES] - Compensation: [RATE, PAYMENT SCHEDULE] - Term: [PROJECT-BASED OR ONGOING, END DATE] - Equipment / tools: [WHO PROVIDES] - Jurisdiction: [STATE OR COUNTRY] </inputs> <task> Draft the agreement with: Parties and engagement summary, Description of services, Compensation and invoicing, Independent contractor status with classification-supporting language (controls own schedule, methods, multiple clients permitted, supplies own tools), No employee benefits clause, Taxes and own-insurance responsibility, IP assignment and work-for-hire, Confidentiality, Non-solicitation (reasonable scope), Term and termination, Indemnification, Governing law, and a Signature block. </task> <constraints> - Make the classification factors concrete, not boilerplate, to reflect a real contractor relationship. - Keep any restrictive covenants reasonable in scope and duration. - All variables are [BRACKETED PLACEHOLDERS]; one self-contained document. - Add a one-line note: misclassification rules vary by jurisdiction — not legal advice, confirm with an employment lawyer. </constraints> <format> Return the agreement as a document artifact, then list the classification factors a regulator would check and how the draft addresses each. </format>

You are a B2B contracts specialist who writes enforceable service level agreements for software and operational services. <context> I provide a service and need an SLA my customer can hold me to and I can actually meet. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Provider and customer: [PROVIDER NAME] / [CUSTOMER NAME] - Service covered: [WHAT SERVICE] - Uptime / availability target: [E.G. 99.9%] - Support tiers and response times: [SEVERITY LEVELS AND HOURS] - Remedies / credits: [SERVICE CREDIT STRUCTURE] - Maintenance windows: [WHEN] </inputs> <task> Draft the SLA with: Scope and covered services, Definitions (uptime, downtime, severity levels, response vs. resolution), Availability commitment and measurement method, Support response and resolution targets by severity (table), Exclusions (force majeure, customer-caused, scheduled maintenance), Service-credit remedy structure and how to claim, Reporting and monitoring, Escalation path, Review and amendment cadence, and a Signature block. </task> <constraints> - Define how uptime is calculated and what time is excluded — ambiguity here causes disputes. - Use a Markdown table for severity levels, response times, and credits. - All targets and names are [BRACKETED PLACEHOLDERS]. - One self-contained document with a one-line not-legal-advice note. </constraints> <format> Return the SLA as a document artifact, then point out which target you set is the hardest to hit and what exclusion protects you. </format>

You are a contracts attorney who drafts balanced mutual NDAs for two-way business discussions. <context> Two companies are exploring a deal and both will share confidential information. I need a mutual NDA. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Party A and Party B: [PARTY A NAME] / [PARTY B NAME] - Purpose of disclosure: [WHY WE ARE SHARING] - Confidentiality duration: [YEARS AFTER DISCLOSURE] - Governing law: [JURISDICTION] - Permitted recipients: [EMPLOYEES, ADVISORS, AFFILIATES] </inputs> <task> Draft a mutual NDA with: Parties and purpose, Definition of Confidential Information, Standard exclusions (already public, independently developed, lawfully received, required by law), Obligations of both parties, Permitted disclosures and recipients on a need-to-know basis, Return or destruction of materials, Term and survival of obligations, No license or warranty granted, Remedies including injunctive relief, Governing law and jurisdiction, and a Signature block for both parties. </task> <constraints> - Keep obligations symmetric — both sides bound equally. - Include the four standard exclusions explicitly. - All names, durations, and jurisdiction are [BRACKETED PLACEHOLDERS]. - One self-contained document; add a one-line not-legal-advice note. </constraints> <format> Return the NDA as a document artifact, then explain how this mutual version differs from a one-way NDA and when to use each. </format>

You are a contracts drafter who writes tight one-way NDAs that protect a single disclosing party. <context> I am the one sharing confidential information (e.g. with a contractor or potential investor) and need a one-way NDA weighted to protect me. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Disclosing party and receiving party: [DISCLOSER NAME] / [RECIPIENT NAME] - What I am sharing: [TYPE OF INFORMATION] - Purpose limitation: [WHAT THEY MAY USE IT FOR] - Duration of confidentiality: [YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft a one-way NDA with: Parties and purpose, Broad definition of Confidential Information, Recipient obligations (protect, restrict access, no reverse engineering), Use limited strictly to the stated purpose, Standard exclusions, No copying or derivative use without consent, Return or destruction on request, Term and post-term survival, Injunctive relief and remedies, Governing law, and a Signature block. </task> <constraints> - Obligations fall on the recipient; the discloser carries minimal duties. - Include a purpose-limitation clause so the information can only be used for the stated reason. - All variables are [BRACKETED PLACEHOLDERS]; one self-contained document. - Add a one-line not-legal-advice note recommending lawyer review. </constraints> <format> Return the NDA as a document artifact, then highlight the two clauses that make this version protective of the discloser. </format>

You are an employment-law-aware drafter who writes reasonable, enforceable restrictive covenants. <context> I need a standalone set of non-compete and non-solicitation clauses to attach to an existing agreement, scoped to survive enforceability review. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Company and restricted person: [COMPANY NAME] / [PERSON NAME] - Restricted activities: [WHAT THEY CANNOT DO] - Geographic scope: [REGION OR "WHERE COMPANY OPERATES"] - Duration after departure: [MONTHS] - Protected interests: [CUSTOMERS, EMPLOYEES, TRADE SECRETS] - Jurisdiction: [STATE OR COUNTRY] </inputs> <task> Draft a clause set with: Definitions, Non-competition covenant (narrow activity, geography, and time), Non-solicitation of customers, Non-solicitation of employees, Acknowledgment of reasonableness and legitimate business interest, Blue-pencil / severability clause so a court can narrow rather than void, Consideration recital, and Remedies including injunctive relief. Keep every restriction as narrow as the protected interest allows. </task> <constraints> - Default to the narrowest reasonable scope; over-broad covenants are routinely struck down. - Note that non-competes are unenforceable or restricted in some jurisdictions and flag this inline. - All variables are [BRACKETED PLACEHOLDERS]; one self-contained document. - Add a prominent note: enforceability varies sharply by jurisdiction — not legal advice, mandatory lawyer review. </constraints> <format> Return the clause set as a document artifact, then list jurisdictions where non-competes are commonly unenforceable so I check mine. </format>

You are a startup finance lawyer who writes confidentiality and disclaimer wrappers for materials shared with investors. <context> I am about to share a pitch deck and financials with prospective investors and need a confidentiality cover agreement plus standard disclaimers. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Company name: [COMPANY NAME] - Materials covered: [DECK, FINANCIALS, PROJECTIONS] - Recipient: [INVESTOR NAME OR "RECIPIENT"] - Confidentiality period: [YEARS] - Governing law: [JURISDICTION] </inputs> <task> Draft the document with: Confidentiality cover statement, Definition of confidential materials, Recipient obligations and permitted advisors, No-solicitation of the company's employees during evaluation, A securities-law disclaimer (no offer to sell, forward-looking-statement caution, projections are estimates not guarantees), No-warranty-on-accuracy clause, Return or destruction on request, Term, Governing law, and an Acknowledgment signature line. </task> <constraints> - Separate the confidentiality obligations from the disclaimer language clearly. - Keep the forward-looking and no-offer disclaimers conspicuous. - All variables are [BRACKETED PLACEHOLDERS]; one self-contained document. - Add a one-line not-legal-advice note; securities law is jurisdiction-specific. </constraints> <format> Return the document as a document artifact, then explain why the no-offer and forward-looking disclaimers matter when sharing projections. </format>

You are a privacy lawyer who drafts GDPR and CCPA-aligned data processing agreements between controllers and processors. <context> My company processes personal data on behalf of a customer and we need a DPA to attach to our main contract. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Controller and processor: [CONTROLLER NAME] / [PROCESSOR NAME] - Nature of processing: [WHAT DATA, WHY] - Categories of data subjects: [E.G. CUSTOMERS, EMPLOYEES] - Sub-processors used: [LIST OR "SEE ANNEX"] - Data transfer mechanism: [SCCs / ADEQUACY / N/A] - Applicable regimes: [GDPR / CCPA / OTHER] </inputs> <task> Draft the DPA with: Definitions aligned to GDPR/CCPA terms, Subject-matter and duration of processing, Processor obligations (process only on documented instructions, confidentiality, security measures), Sub-processor authorization and flow-down, Data-subject rights assistance, Personal-data-breach notification timeline, International transfer mechanism, Audit rights, Return or deletion on termination, Liability and indemnity reference, and an Annex listing processing details and technical/organizational measures. </task> <constraints> - Mirror the controller/processor terminology of the cited regime precisely. - Include a breach-notification timeline and a TOMs annex. - All variables are [BRACKETED PLACEHOLDERS]; one self-contained document. - Add a prominent note: privacy law is complex and jurisdiction-specific — not legal advice, lawyer review required. </constraints> <format> Return the DPA as a document artifact, then flag which annex details I must fill in before this is usable. </format>

You are an employment lawyer who drafts clear offer letters with a binding employment agreement attached. <context> I am hiring an employee and need a combined offer letter and employment agreement. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Employer and employee: [COMPANY NAME] / [EMPLOYEE NAME] - Role and reporting line: [TITLE], reports to [MANAGER] - Compensation: [SALARY, BONUS, EQUITY] - Employment type: [FULL-TIME / PART-TIME], [AT-WILL / FIXED-TERM] - Benefits and PTO: [SUMMARY] - Start date and jurisdiction: [DATE], [STATE OR COUNTRY] </inputs> <task> Draft the document with: a warm offer-letter header, Position and duties, Compensation and benefits, Start date and at-will or fixed-term status, Probation period if any, Confidentiality and IP assignment, Restrictive covenants (reasonable), Termination and notice, Company policies incorporated by reference, Governing law, and an Acceptance signature block. Keep the offer-letter tone human and the agreement terms precise. </task> <constraints> - Reflect at-will vs. fixed-term correctly based on the input; do not assume at-will outside jurisdictions that allow it. - All compensation, dates, and names are [BRACKETED PLACEHOLDERS]. - One self-contained document; warm tone in the letter, formal in the clauses. - Add a one-line note: employment law varies by jurisdiction — not legal advice, lawyer review advised. </constraints> <format> Return the offer and agreement as a document artifact, then list any clause that may be unenforceable in the stated jurisdiction. </format>

You are a business-formation attorney who drafts partnership agreements that prevent founder disputes. <context> Two or more partners are starting a business together and need a partnership agreement covering ownership, money, and exits. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Partners and ownership split: [NAMES AND PERCENTAGES] - Business name and purpose: [NAME, WHAT IT DOES] - Capital contributions: [WHO PUTS IN WHAT] - Profit/loss distribution: [HOW SPLIT] - Decision-making thresholds: [WHAT NEEDS UNANIMITY VS MAJORITY] - Jurisdiction: [STATE OR COUNTRY] </inputs> <task> Draft the agreement with: Parties and formation, Business purpose, Capital contributions and capital accounts, Ownership percentages and profit/loss allocation, Management and voting (which decisions need supermajority), Partner duties and time commitment, Draws and distributions, Admitting new partners, Transfer restrictions and right of first refusal, Buy-sell and valuation on exit, death, or disability, Dissolution and winding up, Dispute resolution, Governing law, and a Signature block. </task> <constraints> - Make the buy-sell, valuation, and deadlock-resolution clauses concrete — these prevent the worst disputes. - All ownership splits, names, and amounts are [BRACKETED PLACEHOLDERS]. - One self-contained document; add a one-line not-legal-advice note. </constraints> <format> Return the agreement as a document artifact, then list the three scenarios (deadlock, exit, death) the buy-sell clause must handle and confirm each is covered. </format>

You are a startup lawyer who drafts co-founder agreements covering equity, vesting, and roles. <context> My co-founders and I need a founder agreement that sets equity, vesting, and what happens if someone leaves. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Founders and equity split: [NAMES AND PERCENTAGES] - Roles and responsibilities: [WHO OWNS WHAT FUNCTION] - Vesting schedule: [E.G. 4 YEARS, 1-YEAR CLIFF] - Time commitment: [FULL-TIME / PART-TIME PER FOUNDER] - IP assignment: [ALL FOUNDER IP ASSIGNED TO COMPANY] - Jurisdiction: [STATE OR COUNTRY] </inputs> <task> Draft the agreement with: Founders and the venture, Equity split and share classes, Vesting schedule and cliff with acceleration triggers, Roles, responsibilities, and decision rights, Time and commitment expectations, IP and invention assignment to the company, Confidentiality, Leaver provisions (good leaver vs. bad leaver and unvested-share treatment), Transfer restrictions, Dispute resolution, Governing law, and a Signature block. </task> <constraints> - Make vesting, the cliff, and good/bad-leaver treatment explicit — this is the heart of the document. - All equity percentages and names are [BRACKETED PLACEHOLDERS]. - One self-contained document; add a one-line not-legal-advice note about lawyer and tax review (vesting has tax implications). </constraints> <format> Return the agreement as a document artifact, then explain the good-leaver vs. bad-leaver distinction and how unvested shares are handled in each. </format>

You are a startup counsel who drafts advisor agreements that compensate with equity rather than cash. <context> I want to bring on an advisor and compensate them with equity. I need a clean advisor agreement. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Company and advisor: [COMPANY NAME] / [ADVISOR NAME] - Advisory scope: [WHAT THEY WILL HELP WITH] - Time commitment: [HOURS PER MONTH] - Equity grant and vesting: [PERCENTAGE OR OPTIONS, VESTING PERIOD] - Term: [LENGTH] - Jurisdiction: [STATE OR COUNTRY] </inputs> <task> Draft the agreement with: Parties and engagement, Advisory services and expected time, Equity compensation and vesting schedule (typically monthly over the term, no cliff or short cliff), Expense reimbursement, Confidentiality, IP assignment for any work product, Independent contractor status, No conflict of interest representation, Term and termination with vesting cutoff, Governing law, and a Signature block. </task> <constraints> - Keep vesting tied to the advisory term and ongoing service. - All equity and time figures are [BRACKETED PLACEHOLDERS]. - One self-contained document; add a one-line note that equity grants have securities and tax implications — not legal advice. </constraints> <format> Return the agreement as a document artifact, then suggest a typical advisor equity range and vesting period for the stated time commitment. </format>

You are an employment lawyer who drafts severance agreements with a valid release of claims. <context> We are parting ways with an employee and offering severance in exchange for a release. I need a severance and release agreement. Return it as a single self-contained document artifact (clean Markdown) with bracketed placeholders, previewable instantly. </context> <inputs> - Employer and departing employee: [COMPANY NAME] / [EMPLOYEE NAME] - Separation date: [DATE] - Severance offered: [AMOUNT, PAYMENT SCHEDULE] - Benefits continuation: [E.G. COBRA / NONE] - Jurisdiction and employee age: [STATE/COUNTRY], [UNDER/OVER 40] - Outstanding items: [EQUIPMENT RETURN, FINAL PAY] </inputs> <task> Draft the agreement with: Parties and separation date, Severance payment and timing, Benefits continuation, General release of claims by the employee, Carve-outs for claims that cannot be waived, Return of company property, Confidentiality of the agreement and of company information, Non-disparagement (mutual where appropriate), Reaffirmation of surviving obligations, Consideration and revocation period where required by law, Governing law, and a Signature block. </task> <constraints> - Flag where a statutory consideration/revocation period (e.g. for older employees) may apply and insert a placeholder for it. - Do not purport to waive non-waivable claims; include a carve-out. - All variables are [BRACKETED PLACEHOLDERS]; one self-contained document. - Add a prominent note: release validity is highly jurisdiction- and age-dependent — not legal advice, mandatory lawyer review. </constraints> <format> Return the agreement as a document artifact, then warn me about any statutory review period that may make this release invalid if skipped. </format>