How Should M&A Attorneys Define Engagement Scope for an Owner-Led Business Sale?

Identify the client before assigning sale responsibilities

An owner-led transaction does not answer who the lawyer represents. Specify whether the client is the operating company, a selling shareholder, several sellers, or another entity. Record who can give instructions for that client and how authority will be confirmed. Under ABA Model Rule 1.13, an organizational lawyer represents the organization acting through authorized constituents, not automatically each owner or employee. Dual representation is subject to conflict requirements; counsel must check the applicable jurisdiction's rules and the actual relationships. [2]

Distinguish a day-to-day contact from an authorized decision-maker. A finance employee may supply records without authority to accept terms. An owner may have individual interests that require separate advice. Document how conflicting instructions will be escalated and how additional proposed clients will be assessed. Do not let a shared workspace, copied email, or attendance at a sale meeting substitute for a decision about the client relationship.

Describe legal deliverables rather than promising to handle the sale

Replace broad phrases such as transaction support with identifiable work products. A proposed scope might include confidentiality agreement review, legal comments on a letter of intent, specified seller-side diligence, negotiation of transaction documents, and preparation of closing deliverables. Identify whether counsel drafts, reviews, negotiates, or only advises on each document. These are illustrative choices, not services required in every sale; the appropriate scope depends on the transaction and counsel's competence.

For each phase, describe the expected input and the output the client will receive. For example, reviewing corporate records could produce a list of missing approvals and issues requiring resolution, rather than a certification that every company record is correct. Define whether review covers all supplied contracts or an agreed category. Include how counsel will handle an unexpected issue outside that category. ABA commentary makes clear that a limited engagement does not remove the duty of competent representation, subject to local rules. [4]

Make exclusions useful by naming the handoff

An exclusion should explain who will address the excluded work and how its results reach counsel. Consider valuation, financial statement preparation, tax structuring, employee benefits, environmental review, specialist regulatory analysis, buyer sourcing, and commercial process administration. Do not assume that all are excluded simply because the sale is owner-led. State which are included, assigned to another professional, retained by the owner, or still unresolved.

Separate a specialist's substantive work from counsel's coordination obligation. If a tax adviser develops a proposed structure, specify whether transaction counsel will incorporate approved instructions into the documents and flag unresolved legal dependencies. Record who engages the specialist and who receives the advice. A scope limitation must remain reasonable under the applicable rules; a disclaimer cannot make an unworkable allocation adequate. ABA Model Rule 1.2 and its commentary provide that model-based distinction. [1] [4]

Use plain language for the boundary: counsel is not verifying the valuation assumptions, but will review the specified legal provisions implementing the agreed consideration. An exclusion with no owner or dependency check leaves the client unable to tell whether an important task is covered.

Separate legal review, business approval, and external communication

Define who may prepare a response, who checks its legal content, who confirms its business facts, and who may send it. Reviewing a draft purchase agreement does not itself communicate the client's acceptance. Under ABA Model Rule 1.2, clients control representation objectives and lawyers consult about means, while lawyers may have implied authority to carry out the representation. A responsibility schedule should clarify operating permissions without pretending to override applicable law or professional obligations. [1]

Record the client's approval process for offers, revised economic terms, disclosure of sensitive records, and final signing instructions. Distinguish these decisions from routine correspondence that counsel is authorized to handle. Specify an escalation route when someone requests action outside the agreed authority. Keep source documents and approval records separate from tentative drafts so a recipient or software operator does not mistake a comment, summary, or uploaded file for authorization to release it.

Assign factual preparation and closing follow-through

The engagement should distinguish legal assessment from supplying company facts. Name the client contact responsible for assembling requested records, confirming factual responses, and identifying omissions. Counsel should explain what legal review of those materials includes. For a disclosure schedule, for example, an owner or designated employee may prepare factual entries while counsel reviews their relationship to the agreed representations. Neither an owner confirmation nor a lawyer's review should be described as verifying every fact unless that verification is actually undertaken.

Define closing and post-closing boundaries separately. Specify whether counsel prepares the closing checklist, coordinates signature documents, or handles identified filings. State whether later adjustment disputes, indemnification claims, retained obligations, and ongoing corporate work need another engagement. Identify who retains executed documents and follows unresolved tasks. Where receipt of specialist advice or client records is a dependency, agree how delays and missing information will be reported rather than silently treating the work as complete.

Attach an AI task-and-review responsibility schedule

An AI task-and-review schedule is a written record of each proposed assisted task, its operator, permitted source material, accountable reviewer, and output restrictions. It should implement the existing engagement rather than add open-ended legal services. ABA Formal Opinion 512, issued July 29, 2024, explains that lawyers remain responsible for their work and cannot substitute generative AI for professional judgment. It is model-based guidance; counsel should check current local requirements before adoption. [3]

For an illustrative internal engagement checklist, the source of truth is the signed engagement letter and approved amendments. A designated staff member may use a permitted tool to produce a draft list of included deliverables and exclusions. The responsible attorney compares every entry to the governing text, checks that no exclusion disappeared, and approves the internal record. The output cannot amend the engagement or be sent as legal advice without lawyer review.

For an illustrative contract-summary task, the source of truth is the identified executed contract, including amendments. The operator requests quoted provisions and document locations, not a conclusion that the business can be sold without consent. The reviewing lawyer checks parties, versions, exceptions, and the provisions relevant to the agreed legal task. Missing pages or ambiguous terms go to counsel for manual analysis. The client or its authorized representative retains the applicable business decision; the tool cannot approve disclosure or negotiate terms.

Choose AI inputs and permissions before processing client information

A general clause allowing technology use is not a substitute for evaluating a particular AI tool. Formal Opinion 512 calls for understanding relevant terms and policies and assessing confidentiality risks before inputting representation information. In its discussion of self-learning tools, the opinion requires informed consent under the described circumstances and says general engagement-letter boilerplate is insufficient. Consent and communication duties depend on the facts, applicable rules, and client requirements, not a universal permission formula. [3]

Document which information may be processed, who may access inputs and outputs, whether information is retained or used for training, and what contractual restrictions apply. Ask a qualified technical reviewer to resolve uncertain settings or terms. If those questions remain unresolved, keep client information out of the proposed task and use synthetic material or a manual workflow. Removing obvious names does not establish that the remaining information is suitable for upload.

Keep buyer-facing drafts separate from internal legal analysis and release them only through the agreed human approval path. Tool selection, client consent, and access restrictions do not guarantee confidentiality, privilege, security, or compliant results. Counsel should assess the specific sharing arrangement under the governing law before relying on it.

Trial narrow tasks and define when assistance stops

Start with a narrow trial using synthetic records and a manually prepared expected result. For a scope checklist, plant a clear exclusion and an approval requirement. For a contract summary, include an amendment that changes a consent provision. Require the output to identify its source locations and flag missing information. The reviewing attorney checks for invented obligations, omitted exceptions, incorrect parties, outdated versions, and wording that turns a tentative issue into a legal conclusion.

Stop the trial if the tool invents authority, cannot trace a material statement to the source, omits a critical qualification, or receives information outside its approved permissions. Stop live use when the task expands beyond the engagement, the tool's relevant terms change, or the assigned lawyer cannot complete the agreed review. Resume only after the responsible humans resolve the issue and authorize the revised workflow. Formal Opinion 512 supports verification tailored to the task and tool, not uncritical reliance on fluent output. [3]

Keep scope changes and software roles explicit

Agree how new requests will be assessed, priced, assigned, and documented before they become routine work. Examples include adding another seller, requesting specialist advice, or asking counsel to administer disclosures previously assigned to the owner. ABA Model Rule 1.5 addresses communication of scope and fee or expense arrangements, preferably in writing, with a stated existing-client exception; local requirements may differ. [5] Record material scope changes and unresolved responsibilities, not just revised billing estimates.

Acquivo is a software platform that delivers the entire sell-side M&A process, valuation, marketing materials, buyer matching, and deal management, on one platform for business owners, M&A attorneys, and boutique investment banks.

Acquivo is user-operated software with no success fee. It does not represent clients or provide legal advice. The responsibility schedule described here is a recommended implementation framework, not a claim about built-in AI features. Before sale activity starts, counsel and the client should be able to identify the included legal work, every material handoff, and the human responsible for reviewing each proposed assisted task.