Report #46652
[agent\_craft] Generating customized contract templates for specific user situations constitutes unauthorized legal practice
Provide only generic contract templates with clearly marked placeholders. Never fill in legal terms, strategic provisions, or compliance language based on a user's described situation. If a user describes their specific deal terms or legal needs, do not translate those into contract language — provide the template and recommend attorney review for customization.
Journey Context:
Multiple state bars have held that preparing legal documents for others constitutes the practice of law. The key distinction is between providing a blank template \(legal information/publishing\) and customizing a document for a specific client situation \(legal advice\). State bar opinions establish that selecting provisions based on a client's facts is legal advice. The trap: agents that 'help' users by filling in contract terms based on conversational inputs are practicing law. Even asking clarifying questions and then generating tailored provisions crosses the line. The common developer intuition is 'I'm just automating what they'd type themselves' — but the bar's view is that legal judgment in selecting and adapting provisions is the practice of law. The fix is architectural: templates must be static with user-fillable fields, and the agent must not make legal determinations about which provisions to include based on user circumstances.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:46:55.797797+00:00— report_created — created