Scope is the contract, and scope keeps moving

The documents an engagement runs on

Firms in this segment usually have good master agreements and no process at all for everything that hangs off them. That is where the leakage is.

• Master services agreements — Negotiated once per client, then relied on for years. The terms your delivery teams actually depend on need to stay findable without re-reading the whole document.
• Statements of work — Generated under the MSA with the rate card, liability position and IP terms inherited, so a partner is not renegotiating settled terms on every phase.
• Change requests — The most common document and the least controlled. Each one attaches to the clause it modifies, so the current scope is one thing rather than an SOW plus a stack of emails.
• Engagement letters — Issued from your standard form with the engagement terms filled from the conversation that produced it, rather than retyped from the last one.
• Client paper you did not write — Procurement sends their supplier terms. The assistant compares them clause by clause against your standard position and escalates the deviations that actually matter.
• Renewals and extensions — Retainers, managed services and multi-phase programmes where the extension window comes out of the executed agreement rather than out of someone's recollection.

Scope creep is a document problem

Nobody loses margin because they agreed to extra work. They lose it because the extra work was agreed in a conversation and never made it into the contract that the invoice has to rest on.

• A change modifies the deliverables clause — An agreed change request resolves against the scope it affects, so the current scope of work is a single readable thing rather than a base SOW plus amendments to reconcile.
• Client agreement is evidenced — The approval binds to a version and an identity, so when the invoice is queried the question of whether the client agreed has a recorded answer.
• The conversation stays attached — The discussion that produced the change sits beside the clause it changed, so the rationale survives the delivery team rotating off the engagement.
• The pattern becomes visible — When the same scope change recurs across engagements, that is a signal about your SOW template rather than a run of bad luck.

What the assistant takes off your billable people

None of this requires judgement about the engagement. It requires someone to produce a document, send it, chase it and file it — which is exactly the work worth handing over.

• Generate the SOW from the MSA — Parties, rate card, liability position and IP terms are inherited from the master agreement. The only new content is the scope, the timeline and the price.
• Negotiate the ordinary deviations — Where the client's procurement team pushes on payment terms or a service credit, the assistant responds inside the mandate your firm set and settles it without a partner's involvement.
• Escalate what actually matters — Liability caps, IP ownership, exclusivity and anything else you gate come back as a decision with the clause, the delta and your standard position attached.
• Get it signed in the same room — Signature happens where the negotiation did, with identity capture, so the engagement can start without a separate round of document wrangling.
• Keep the commitments — Deliverables, milestones, notice periods and the renewal window are extracted from the executed agreement, so the engagement's obligations are data your delivery team can read.

Your firm's positions, stated once per client

Most of these are decisions your firm has already made informally. Writing them down is what lets the assistant act without asking.

• Your paper: Master agreement and SOW templates in your clause library
• Your paper: Standard rate card and the discount band you will go to
• Your paper: Your liability and IP positions as approved language
• Your paper: An engagement letter form per service line
• Your mandate: Payment terms you accept without asking
• Your mandate: Service credits and remedies within a band
• Your mandate: Liability caps and IP ownership as gated clauses
• Your mandate: Turn and spend caps per engagement
• Your gates: Which partner approves which clause
• Your gates: Which deviations always stop the run
• Your gates: Which service lines run supervised rather than freely
• Your gates: Who is notified when a change request is agreed

What partners ask us

• Our MSAs are all different. Does the SOW generation still help? Yes, because the inheritance is per client rather than per firm. Each client's SOWs are generated under that client's master agreement, so the rate card, liability position and IP terms carried through are the ones you actually negotiated with them.
• Can the assistant handle a client's procurement portal? It handles their paper, not their portal. When procurement sends their supplier terms, the assistant compares them against your standard position, negotiates inside your mandate and escalates the material deviations. Where the client insists on their own system for the final signature, you keep the record of the negotiation that produced it.
• What stops a change request being agreed without a price? You gate it. A change request can be configured so that it cannot be accepted without a priced position and a named approver — and gating attaches to the clause, so no autonomy setting overrides it. That is usually the single most valuable gate a services firm sets.
• Does this replace our practice management system? No. It covers the agreement — the MSA, the SOWs, the change requests and the obligations that come out of them. Your own systems read that record over the Model Context Protocol surface with scoped credentials, so the engagement data can reach whatever you run for time and billing.