The paper argues that AI can assist legal work in emerging companies and venture capital, but cannot substitute for professional legal judgment. It maps AI use onto the existing ABA Model Rules of Professional Conduct, and it applies those duties to specific transactional document types.<\/span><\/p>\n At the center of the framework are five factors for deciding whether AI should draft or review a given document:<\/span><\/p>\n The paper then applies the framework to specific documents in the venture capital and emerging companies space, rating each as high, moderate, or low for AI suitability. Basic C-corporation formation documents, board minutes, and non-disclosure agreements come out as highly suitable for AI-generation. Employment offer letters come out moderate. LLC formation documents (including operating agreements), shareholder agreements, and merger and acquisition agreements come out low.<\/span><\/p>\n<\/p>\n The five factors are a good rubric. They accurately capture the variables that are helpful in determining whether a document is a good candidate for automation.<\/span><\/p>\n Standardization is the right first question.<\/b> Documents that follow a standard form are more suitable for AI drafting than documents that don\u2019t. The paper\u2019s rating of basic C-corp formation documents as highly suitable is straightforward. Articles of incorporation with the Secretary of State are close to a UCC filing: the same document over and over, with the names changing. The primary risk driver is clerical accuracy and jurisdictional rules, and AI grounded in the right jurisdictional context handles both well.<\/span><\/p>\n The paper treats the risk drivers document by document. <\/b>For each document type, the paper identifies what specifically could go wrong. Clerical errors, missed compliance requirements, mistaken tax treatment, or over-simplification of a negotiated point. This is more useful than a blanket judgment about whether AI is safe. It gives lawyers something concrete to check against.<\/span><\/p>\n The framework anchors to existing ethical duties. <\/b>The paper doesn\u2019t invent new rules. It applies existing <\/span>Model Rules of Professional Conduct<\/span><\/a>\u2014including Comment 8 to Rule 1.1, which covers the duty to keep abreast of the benefits and <\/span>risks of relevant technology<\/span><\/a>\u2014to AI use. That\u2019s the right foundation. The obligations already exist. What\u2019s needed is guidance on how they apply to AI in transactional legal workflows.<\/span><\/p>\n The paper treats AI primarily as a document generator. That\u2019s a familiar frame, and it’s one most bar guidance has used so far. But it\u2019s a subset of what AI does in a modern legal workflow, and the ratings in the paper\u2019s document-by-document table reflect that narrower view. Three of the ratings deserve reconsideration.<\/span><\/p>\n LLC formation documents can be rated higher.<\/b> Consider LLC formation documents, rated low for AI suitability. The paper suggests AI is fine for a starting point and some clause suggestions, but not much beyond that. That rating assumes AI is working in a vacuum, with no client context.<\/span><\/p>\n That\u2019s not how legal AI tools like <\/span>Clio Work<\/span><\/a> actually function. LLC operating agreements have real variation, but the variation is rules-based: manager-managed or member-managed, tax treatment (partnership, S-corp, C-corp), voting rights, distribution rules, buyout terms. Law firms have been automating these choices through document assembly for years. AI is document assembly with better context awareness. If a system already knows the client\u2019s tax goals, the intended management structure, and the equity split, drafting the agreement becomes a straightforward extension of the intake process.<\/span><\/p>\n Employment offer letters carry more context than the moderate rating suggests.<\/b> The paper rates these moderate for AI suitability, with the primary risk driver as compliance with employment laws. That\u2019s understated. Employment offer letters carry significant context, such as prior inventions clauses, cross-jurisdictional hiring, non-compete enforceability, whether the hire is a leadership position or a front-desk role, what stock and benefits are on the table. A golden parachute for an incoming executive is a very different document from an offer letter for an entry-level sales rep. Without the client context to distinguish, AI drafts of employment letters can be a bigger risk than AI drafts of LLC operating agreements. If anything, the rankings for these two document types should be flipped: LLC formation rated higher (given proper client context) and employment offer letters rated lower.<\/span><\/p>\n M&A drafting deserves more credit once the negotiation is settled.<\/b> The paper rates M&A agreements low because the transaction structure and negotiated risk allocation require human judgment. That\u2019s true of the negotiation, but it\u2019s less true of the drafting once the negotiation is settled. If the transaction structure has been worked out in a letter of intent, and the risk allocation has been decided in principle, the actual drafting is the mechanical part. That\u2019s exactly the work at which AI is good. Reserving M&A for humans conflates the negotiation stage with the drafting stage.<\/span><\/p>\n \t\t\t\t \t\t\t\t\t\t The five-factor framework judges AI one document at a time. But AI in legal practice rarely works that way. A lawyer\u2019s matter builds from intake through drafting through review, and AI is most useful when it can move with that context. A better framework would look at where AI fits in the whole matter, not just where it fits in one document.<\/span><\/p>\n A workflow-based system stores that context and gives the AI access to it. So the LLC agreement isn\u2019t being drafted from scratch by a model that knows nothing about the client. It\u2019s being drafted from the client\u2019s tax preferences, management structure, planned capitalization, and negotiated deal points, all already in the record. Drafting becomes a natural extension of the work the lawyer has already done.<\/span><\/p>\n The paper\u2019s framework doesn\u2019t account for this because it treats each document as an isolated task. Intake, case management, document generation, and review are connected steps in the same matter, and a workflow-aware AI system is aware of all of them. <\/span>Clio Work<\/span><\/a> is one implementation of that principle. It ties together intake, <\/span>matter context<\/span><\/a>, and AI drafting so that a document is generated with the full record of the matter instead of from a blank prompt.<\/span><\/p>\n This is why the debate over which documents are \u201cAI-suitable\u201d and which aren\u2019t can land in the wrong place. The suitability of AI drafting depends less on the type of document than on the context the AI has access to. Give an AI the client\u2019s tax planning conversation, and drafting an LLC operating agreement is straightforward. Give it a blank prompt and a form template, and even a C-corp filing can go wrong.<\/span><\/p>\n The second part of the paper argues for a national framework governing AI use in legal practice. That\u2019s the harder problem, and the paper is right that the <\/span>current state of guidance is fragmented<\/span><\/a>. State bars, courts, and individual judges have each issued their own guidance, standing orders, or <\/span>ethics opinions<\/span><\/a>, and the pieces don\u2019t line up. That fragmentation makes it hard for lawyers to know what\u2019s expected.<\/span><\/p>\n The structural reality is that the United States doesn’t have a national legal regulator. The ABA writes Model Rules. States decide whether to adopt them. There is no federal bar to enforce a uniform AI standard, and there\u2019s no realistic path to one. Any national framework would need to work through state bars, state legislatures, or state supreme courts, which is the same path the current guidance is already taking. The paper\u2019s regulatory instinct is right, but there\u2019s a more actionable target within reach.<\/span><\/p>\n \t\t\t\t \t\t\t\t\t\t Better guidance on existing duties is the first step.<\/b> Federal Rule of Civil Procedure 11 (for court filings) and the duty of candor to the tribunal already require lawyers to verify what they file. What\u2019s missing is guidance on how those duties translate into an AI workflow: What does verification look like when a first draft is AI-generated? What does lawyer supervision require when the work is being done by a tool rather than a junior lawyer? The paper takes some steps in this direction, but state bars, courts, and organizations like the National Center for State Courts or the Uniform Law Commission are the right venues for making the guidance operational.<\/span><\/p>\n Record-keeping standards are the practical fix.<\/b> Bar associations already regulate lawyers\u2019 record-keeping in specific areas (trust accounting is the obvious example). A similar approach would work for AI. Rather than regulating the tools, regulate what lawyers need to keep as a record of AI use: the prompts, the intermediate outputs, the final document, and which templates or firm-approved workflows were used. Clio Work, for instance, keeps a full audit trail of each AI action taken on a matter. That kind of record makes AI use defensible under scrutiny, whether the scrutiny comes from a bar complaint, a malpractice claim, or a court\u2019s standing order. Standards for that record could come from state bars without requiring a national framework.<\/span><\/p>\n Celebrate successful AI use as much as caution about misuse.<\/b> The paper spends most of its regulatory analysis on what could go wrong. One paragraph in the report is titled \u201cAI as a Driver of Access and Innovation,\u201d and it\u2019s immediately followed by a return to risk. The Model Rules already frame this as a two-sided obligation. Comment 8 to Rule 1.1 asks lawyers to understand the risks <\/span>and<\/span><\/i> the benefits of technology. Bar guidance is strongest when it does both. Bar associations that only publish warnings without also celebrating successful use may be chilling innovation more than they realize.<\/span><\/p>\n Bar associations sit at the closest point to where AI actually gets used, and they have the authority to move without waiting for the ABA or federal action. Five recommendations follow from the analysis above.<\/span><\/p>\n The NYC Bar\u2019s paper opens a conversation the profession has needed for a while. The five-factor framework is a useful rubric, and the committee is right to map AI use onto existing Model Rules of Professional Conduct.<\/span><\/p>\n The framework needs more in two directions. The first is workflow. AI does its most useful work when it can see the whole matter, not one document at a time, and the ratings for LLC formation, employment offer letters, and M&A drafting shift once client context is in the picture. The second is regulation. A national AI framework for lawyers likely isn’t coming through federal channels, but state bars, courts, and practice management advisors can do the work that a national framework was meant to do.<\/span><\/p>\n Where the paper ends, the state-level work begins. If bar associations set the standard, technology providers will build to it.<\/span><\/p>\n\n","protected":false},"excerpt":{"rendered":" What the NYC Bar\u2019s new AI framework proposes The paper argues that AI can assist legal work in emerging companies and venture capital, but cannot substitute for professional legal judgment. It maps AI use onto the existing ABA Model Rules of Professional Conduct, and it applies those duties to specific transactional document types. At the […]<\/p>\n","protected":false},"author":1,"featured_media":7073463,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[97],"tags":[1685,13782,14075,15935,67206],"dealstore":[],"offerexpiration":[],"class_list":["post-7073462","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-legal","tag-bars","tag-framework","tag-lawyers","tag-nyc","tag-transactional"],"yoast_head":"\n\n
Where the NYC Bar\u2019s framework works<\/span><\/h2>\n
Where the framework is too narrow<\/span><\/h2>\n
The workflow question the framework leaves open<\/span><\/h2>\n
![\"Track](\"https:\/\/www.clio.com\/wp-content\/uploads\/2026\/04\/Blog-Word-Document-Comparison-1-750x422.png\" "\\"Blog")
<\/p>\n<\/p><\/div>\n<\/p><\/div>\nThe call for national AI rules meets the state-by-state reality<\/span><\/h2>\n
![\"\"](\"https:\/\/www.clio.com\/wp-content\/uploads\/2026\/05\/Standard-jpg_Blog-Law-Firm-Compliance-750x422.jpg\" "\\"AI")
<\/p>\n<\/p><\/div>\n<\/p><\/div>\nWhat bar associations should do next<\/b><\/h2>\n
\n
Moving AI guidance forward<\/span><\/h2>\n