Working freelancers who need contract clauses written today, not next week. Copy these prompts into ChatGPT, fill in your project details, and get professional contract language you can send to clients immediately.
These prompts pair well with Jasper AI for Freelancers-specific tone control, or Copy.ai for fast iteration.
Payment Terms and Late Fees
You are a freelance contract lawyer writing a payment clause for a creative services agreement.
Project type: {web_design / copywriting / consulting / development / marketing} Total project value: {dollar_amount} Payment schedule: {50_25_25 / net_30 / milestone_based / upfront} Late fee structure: {percentage_per_month / flat_daily_rate / compounding} Currency: {USD / EUR / GBP / CAD} Client industry: {startup / enterprise / nonprofit / agency} Rush job: {yes / no}
Write a 150-200 word payment terms clause that specifies invoice timing, payment deadlines, and late fee consequences. Include language that protects against scope creep affecting payment schedules. Use professional but firm tone that doesn’t sound threatening.
When to use it: When a client wants to discuss payment terms and you need specific language that protects your cash flow without killing the deal.
Pro tip: If the client is a startup, add “payment terms survive company acquisition or ownership changes” to prevent new management from resetting your payment schedule.
You are drafting an invoice dispute resolution clause for a freelance graphic design contract.
Freelancer specialty: {graphic_design / web_development / content_writing / photography / marketing} Typical project length: {1_week / 1_month / 3_months / ongoing} Client size: {small_business / mid_market / enterprise / startup} Dispute history: {first_time_client / repeat_client / referred_client} Payment amount: {under_5k / 5k_to_25k / over_25k} Timeline pressure: {flexible / moderate / urgent}
Write a 100-150 word clause covering what happens when a client disputes an invoice. Include a mandatory 10-day discussion period before any payment holds, requirement for written dispute reasons, and consequences for frivolous disputes. Keep the tone collaborative but protective.
When to use it: When you’re working with a new client who seems hesitant about payment terms or has a history of challenging invoices.
Pro tip: Add “disputed work continues unless both parties agree to pause” so clients can’t stop paying you while claiming they need to “review everything.”
You are writing an expense reimbursement clause for a freelance consultant working on client premises.
Service type: {strategy_consulting / technical_consulting / training / audit / implementation} Travel required: {local_only / regional / national / international} Typical expenses: {software_licenses / travel / materials / subcontractors / equipment} Expense threshold: {dollar_amount_requiring_approval} Client expense policy: {strict / standard / flexible / undefined} Project duration: {weeks / months / quarters} Payment method: {direct_reimburse / add_to_invoice / upfront_allowance}
Write a 120-180 word expense clause that covers pre-approval requirements, documentation standards, and reimbursement timing. Address what happens when client-requested changes increase costs. Use clear, specific language that prevents expense disputes.
When to use it: Before starting any project that might involve software purchases, travel, or subcontracting work to other specialists.
Pro tip: Always include “emergency expenses under $200 can be incurred without pre-approval” so you’re not texting clients about urgent Uber rides or software subscriptions.
You are creating a currency fluctuation protection clause for an international freelance project.
Base currency: {USD / EUR / GBP / CAD / AUD} Client currency: {different_from_base_currency} Project value: {dollar_amount} Project length: {weeks / months / quarters} Payment frequency: {weekly / monthly / milestone} Exchange rate risk: {low / moderate / high} Fluctuation threshold: {percentage_that_triggers_adjustment}
Write a 100-140 word clause that handles currency exchange rate changes during longer projects. Include a threshold percentage that triggers rate adjustments and specify who bears minor fluctuation risk. Keep language simple enough for non-financial clients to understand.
When to use it: Any project over 60 days with international clients, especially during periods of economic uncertainty or high currency volatility.
Pro tip: Set the fluctuation threshold at 5% - high enough that you’re not constantly adjusting rates, low enough that you don’t eat a huge loss if currencies swing hard.
You are drafting a partial payment protection clause for a freelance project that’s been scoped in phases.
Total project phases: {number_of_phases} Phase duration: {days_or_weeks_per_phase} Deliverable type: {design_files / written_content / code / strategy_docs / training} Client approval process: {single_stakeholder / committee / legal_review} Phase dependencies: {sequential / parallel / mixed} Risk level: {low / medium / high} Prior relationship: {new_client / returning_client / referral}
Write a 140-200 word clause that protects you if a client cancels mid-project. Cover payment for completed phases, work-in-progress compensation, and file/asset ownership during partial completion. Use language that’s enforceable but doesn’t scare clients away.
When to use it: Any multi-phase project where you’re worried about client budget changes, internal politics, or shifting priorities killing the project halfway through.
Pro tip: Include “work-in-progress is billed at 50% of phase value if cancellation occurs mid-phase” so you’re not working for free on abandoned projects.
Scope and Revision Management
You are writing a scope change management clause for a freelance web development project.
Project type: {website_build / app_development / ecommerce_site / redesign / maintenance} Original scope complexity: {simple / moderate / complex / enterprise} Change request frequency: {rare / occasional / frequent / constant} Client decision makers: {single_contact / small_team / large_committee} Timeline flexibility: {fixed_deadline / flexible / ongoing} Budget sensitivity: {fixed_budget / flexible_budget / cost_plus} Integration requirements: {none / third_party_apis / legacy_systems}
Write a 160-220 word scope change clause that defines what constitutes a change, requires written approval for modifications, and establishes billing for additional work. Include language about timeline impacts and minimum billing increments. Keep tone professional but firm about change control.
When to use it: Before starting any project where the client has said “this should be straightforward” but you suspect hidden complexity or changing requirements.
Pro tip: Always include “verbal requests are not binding until confirmed in writing” because clients will try to sneak in changes during casual conversations.
You are creating a revision limit clause for a freelance logo design contract.
Design package: {logo_only / logo_plus_brand / complete_identity / refresh} Included revisions: {number_of_rounds} Client stakeholders: {owner_only / small_team / board_approval / public_input} Timeline: {rush / standard / flexible} Revision complexity: {minor_tweaks / major_changes / complete_overhauls} Additional revision rate: {hourly_rate / flat_fee / percentage} Design approval process: {single_stakeholder / committee / legal_review}
Write a 120-160 word revision clause that clearly defines what counts as one revision round, distinguishes between minor tweaks and major changes, and sets expectations for additional revision billing. Include timeline impacts of excessive revisions.
When to use it: Any creative project where client feedback will come from multiple stakeholders or where you suspect the client doesn’t have a clear vision yet.
Pro tip: Define “minor revision” as changes that take under 30 minutes - this prevents clients from calling a complete color scheme overhaul a “quick tweak.”
You are drafting a project requirement documentation clause for freelance technical consulting.
Consulting type: {system_integration / process_improvement / technical_audit / implementation / training} Requirement complexity: {well_defined / partially_defined / discovery_needed} Client preparation: {fully_ready / partially_ready / starting_from_scratch} Documentation standards: {formal / informal / agile / waterfall} Stakeholder access: {guaranteed / limited / uncertain} Change frequency: {stable_requirements / evolving / completely_fluid} Success metrics: {defined / undefined / disputed}
Write a 180-240 word clause that establishes client responsibility for providing accurate requirements, defines what happens when requirements are incomplete or change frequently, and protects against scope creep from poor initial documentation. Address timeline and cost impacts.
When to use it: Technical projects where client requirements gathering is incomplete or where you’re walking into an organization that hasn’t done their homework yet.
Pro tip: Include “requirements discovery time is billable at standard rates” so clients can’t expect you to spend weeks figuring out what they actually need for free.
You are writing a creative approval and sign-off clause for freelance marketing content creation.
Content type: {blog_posts / social_media / email_campaigns / web_copy / ads} Content volume: {single_pieces / batches / ongoing_production} Approval chain: {direct_client / marketing_manager / legal_review / executive_approval} Brand guidelines: {strict / flexible / nonexistent} Revision expectations: {minimal / moderate / extensive} Timeline constraints: {tight_deadlines / standard / flexible} Content performance risk: {low / medium / high}
Write a 140-180 word approval clause that establishes clear sign-off procedures, defines approval timelines, and addresses what happens when multiple stakeholders provide conflicting feedback. Include protection against indefinite revision cycles.
When to use it: Content projects with multiple approvers, strict brand guidelines, or clients who tend to micromanage creative decisions.
Pro tip: Add “conflicting feedback from multiple approvers pauses work until unified direction is provided” to avoid getting caught between warring internal factions.
You are creating a deliverable specification and acceptance clause for freelance project management consulting.
Project deliverables: {process_docs / training_materials / system_setup / reports / frameworks} Deliverable format: {documents / presentations / software_setup / training_sessions} Quality standards: {client_defined / industry_standard / consultant_standard} Testing requirements: {user_acceptance / pilot_program / full_rollout} Acceptance timeline: {immediate / testing_period / stakeholder_review} Rejection criteria: {objective_standards / subjective_approval / performance_metrics} Remediation process: {revision / replacement / refund}
Write a 200-260 word clause that defines exactly what you’re delivering, how acceptance works, what constitutes reasonable rejection, and remediation procedures. Protect against subjective rejections while acknowledging legitimate quality concerns.
When to use it: Complex consulting projects where deliverable quality might be subjectively judged or where client expectations aren’t clearly defined upfront.
Pro tip: Always include “acceptance is deemed granted if no written feedback is provided within 10 business days” to prevent projects from hanging in approval limbo forever.
Intellectual Property and Usage Rights
You are writing a copyright ownership clause for freelance graphic design work.
Design type: {logo / website / marketing_materials / packaging / illustrations} Usage scope: {single_company / multi_brand / resale_rights / exclusive_worldwide} Industry: {technology / healthcare / finance / retail / nonprofit} Competition concerns: {direct_competitors / industry_wide / no_restrictions} Derivative works: {allowed / restricted / prohibited} Attribution requirements: {portfolio_use / public_credit / no_attribution} Transfer timing: {upon_payment / upon_delivery / upon_launch}
Write a 150-200 word copyright clause that clearly transfers rights upon final payment while reserving your portfolio and promotional rights. Address derivative works and specify any usage restrictions. Keep language clear enough for non-legal clients.
When to use it: Any creative project where the client will own the final work and you need to clarify what rights transfer when and what you retain.
Pro tip: Always reserve “portfolio use and case study rights” even in full copyright transfers - you need proof of your work for future marketing.
You are drafting a work-for-hire classification clause for freelance software development.
Software type: {web_app / mobile_app / plugin / integration / automation} Code ownership: {full_client_ownership / shared_components / consultant_retains_framework} Open source components: {extensive / minimal / none} Competing client risk: {high / medium / low} Proprietary methods: {consultant_keeps / transfers_to_client / shared_license} Future modification rights: {client_only / consultant_maintains / shared} Documentation ownership: {client / consultant / shared}
Write a 180-240 word work-for-hire clause that transfers code ownership while protecting your pre-existing intellectual property and development methodologies. Address open source component licensing and future modification rights.
When to use it: Software development projects where code ownership needs to be crystal clear and you want to protect proprietary development frameworks or methodologies.
Pro tip: Include “pre-existing consultant IP remains consultant property” to protect frameworks and code libraries you brought to the project.
You are creating a limited usage license clause for freelance photography services.
Photography type: {headshots / product_photos / event_coverage / architectural / lifestyle} Usage scope: {website_only / all_marketing / print_and_digital / social_media} Geographic limits: {local / national / international / worldwide} Time limitations: {one_year / five_years / unlimited / campaign_specific} Exclusivity: {exclusive / non_exclusive / limited_exclusivity} Modification rights: {no_changes / minor_edits / full_editing} Resale restrictions: {prohibited / allowed / royalty_based}
Write a 140-180 word usage license clause that grants specific usage rights while retaining copyright ownership. Define permitted uses, geographic and time restrictions, and modification limitations. Address stock photo licensing and resale restrictions.
When to use it: Photography projects where you want to retain copyright but give clients clear usage rights for their business needs.
Pro tip: Specify “high-resolution files provided only for licensed uses” to prevent clients from using your premium images for purposes outside their license scope.
You are writing a confidentiality and non-disclosure clause for freelance business consulting.
Business information type: {financial_data / strategic_plans / customer_lists / processes / technology} Information sensitivity: {highly_confidential / moderately_sensitive / standard_business} Competitor risk: {direct_competitors_exist / industry_risk / low_risk} Information access level: {executive_level / operational_details / full_company_access} Project duration: {short_term / medium_term / long_term / ongoing} Post-project restrictions: {one_year / two_years / five_years / indefinite} Information return: {all_materials / copies_destroyed / digital_wipe}
Write a 200-260 word NDA clause that protects client confidential information while preserving your ability to use general industry knowledge and work for other clients. Define what constitutes confidential information and specify post-project obligations.
When to use it: Consulting projects where you’ll access sensitive business information, customer data, or proprietary processes that competitors could use.
Pro tip: Always carve out “publicly available information and general industry knowledge” from confidentiality restrictions so you can continue working in the same industry.