Beginner5 min readFreelance & Solopreneur AI

Keep a scope change log, not AI delivery promises

When a client asks for 'one more thing,' do not let a model invent a cheerful yes and a new deadline. Log the change, impact on fee and timeline, and written acceptance - then use AI only to format the note you already decided.

What you should be able to do

Scope changes are commercial decisions. Record what changed, what it costs in time or fee, and whether the client accepted it in writing. AI can format that log; it must not author the promise.

Saved only in this browser.
In this article

Before entering any real client information into AI, confirm authorization for the exact tool, account, data category and purpose. A paraphrase can still be confidential. Permission to publish a finished case or send a client email does not necessarily permit uploading the underlying evidence or thread to an AI provider. Use fictional or non-sensitive placeholder material in general chat; keep the actual record private otherwise.

In this invented scenario, a client messages: “Can we also add a one-pager for the sales team? Should be quick.” A draft is requested without first deciding the commercial terms. The draft says you are happy to include it in this week’s delivery at no extra cost. That sentence may be fluent. It may also be an unpaid change order you did not mean to grant.

A courteous reply can still introduce a fee or deadline you did not authorize. Decide the terms first, then check that the draft preserves them.

Why a log beats a vibe

A scope change log is a running table:

  • Date requested
  • Requested change (exact client wording if possible)
  • Impact on deliverables
  • Impact on timeline
  • Impact on fee (your assessment)
  • My decision (propose / accept within existing scope / decline / defer / clarify)
  • Change status (proposed or pending / accepted under the agreement / declined / withdrawn)
  • Required client confirmation and reference (email, ticket, signed change note)

The log gives the draft explicit terms to preserve. Warm wording is compatible with a clear paid change; the problem is an unsupported commitment, not courtesy itself.

Do not ask a model “how should I promise this extra work.” Ask it, at most, to format a change note whose fee and dates you already chose. Invented timelines in a client channel may create apparent or disputed commitments; the actual agreement and exchange determine their legal effect.

Workflow

Step 1: Capture the request in the client’s words

Copy the request into the log before drafting any reply. If it arrived on a call, write a one-sentence paraphrase and send it back for confirmation: “Capturing this as X - correct?”

Step 2: Decide impact yourself

Answer offline:

  • Does this fit the signed SOW?
  • If not, what is the time cost?
  • Does fee change, timeline change, or both?
  • Do you decline, propose a paid change, or move it to a later phase?

Check capacity and commercial terms against your own records. Do not let the model fill a missing delivery date or price.

Step 3: Optional AI format pass

Format this scope-change note for email. Keep all numbers, dates,
and decisions exactly as written. Do not add goodwill freebies,
accelerated timelines, or extra deliverables.

Change log row:
[row authorized for this environment, or fictional example only]

Step 4: Require written acceptance for paid or timeline-affecting changes

Follow the change and acceptance procedure in the actual agreement. Make the proposed scope, fee and date explicit and retain the required confirmation. A message, emoji or log entry does not have a universal contractual effect; seek appropriate advice where that effect is disputed.

Step 5: Mirror the change in the next status update

Your next client update should reference the log entry so the new scope is visible in the project narrative, not only in a side chat.

Keep the log in the same place as the SOW PDF - one folder per client. Reconcile any unlogged request or apparent agreement promptly; absence from your log does not determine its contractual effect.

The permission boundary applies to summaries as well as original threads. Rewriting a secret from memory does not clear it for upload.

Tiny changes vs commercial changes

Not every clarification needs a paid change order. Color tweaks inside an approved design direction, or fixing a typo the client introduced, may sit inside existing acceptance. Commercial changes are different: new audiences, new deliverable types, new platforms, compressed deadlines, or extra revision rounds beyond the SOW. When unsure, log it as “clarify” and send a one-line confirmation before you start the work.

Validation and fallback

Validation: every in-flight extra deliverable appears in the log with your decision, its current status and the required client confirmation. A proposed change is not an accepted one.

Fallback: if you may already have agreed to something unintended, preserve the exchange and clarify promptly. Do not assume a later correction cancels an existing commitment. Seek appropriate advice before making a disputed legal assertion.

Desk template

Use the scope change log template. Pair it with your solo AI rules so “no AI-authored promises” is a standing rule, not a mood.

Turn a pending row into a bounded reply

Invented row: “Client requests one sales sheet; outside original scope; proposed additional fee 200 units; proposed delivery moves from Friday to Tuesday; client has not accepted.” A faithful draft says: “I can add the sales sheet for an additional 200 units and deliver the full package on Tuesday, subject to your confirmation. The existing scope remains the current plan while we resolve the change.”

The log stays “proposed,” not “accepted,” until the required confirmation arrives under the actual agreement. A reply saying “happy to include it Friday” fails both the price and timing check. Check any existing promise or dispute with appropriate advice; a later log entry cannot erase it.

Read next

Continue through the same learning path with the next practical articles.