Iurefficient Teams
  • Presentation
  • Articles
  • Use cases
  • Modules
  • Pricing
  • Training
  • ES
  • Law firms
  • Open the demo

Scope in writing: how to avoid the “while you’re at it”

Published on October 27, 2026 · by Iurefficient · Best practices

Scope in writing: how to avoid the “while you’re at it”

The “while you’re at it” is rarely bad faith, but it piles up unpaid work. Seven practices for writing scope so every new request can be compared against something concrete.

“While you’re at it, could you also review…?” It is the cheapest sentence to say and the most expensive one to honor. It is rarely bad faith: the client discovers a nearby need and the consultant, out of courtesy, absorbs it. Three “while you’re at it” requests later, the project carries 30% more work for the same fee. The defense is not rigidity; it is writing the scope so that every new request can be compared against something concrete.

1. Write what you deliver, not what you do

“Purchasing process analysis” describes an endless activity. “Map of the current purchasing process with timings, and a report of up to 10 prioritized findings” describes a result that can be delivered and accepted. Each deliverable gets a name, a format and an acceptance criterion: who reviews it and what makes it “done”.

2. Also write down what is out

An explicit exclusions section prevents most arguments. Examples: “does not include implementing the recommendations”, “does not include supplier interviews”, “does not include the branch network”. If the client says “I thought that was included”, there is a text to point to without having to fight.

3. State assumptions and dependencies

Many overruns come from what the client was going to provide and did not provide on time. Write the assumptions down: “the client delivers the last 24 months of sales data in week one”, “a decision-maker is available 2 hours a week”. If an assumption fails, the plan changes by right, not as a favor.

4. Put limits on what is elastic

Meetings, review rounds, document versions, number of interviews: anything elastic needs a number. “Two rounds of comments per deliverable; each additional round is quoted separately.” A visible limit turns a conversation that would otherwise feel like a personal negotiation into routine.

5. Define how a change is requested

Changes are not the problem; changes without a process are. A minimal process fits in four steps:

  • Whoever spots the request writes it down (even if it arrives in the hallway or in a chat).
  • The project lead estimates the impact on time, cost and deliverables.
  • The client decides: accept with an adjustment, postpone to a second phase, or drop it.
  • What was agreed is recorded in writing before work begins.

6. Teach your team to say “I’ll note it”

Most “while you’re at it” requests are accepted on the spot, on a call, to avoid friction. Give the team a ready answer: “Good idea, I’ll note it and tell you today how it fits.” It is not a no; it separates the request from the decision. Whoever answers this way promises nothing they cannot deliver and does not become the villain of the story.

7. Review the scope at every milestone

A scope written at the start ages. At each milestone, spend five minutes on three things: what was delivered, which changes were approved, and whether the rest of the plan is still realistic. That way the client sees the accumulated cost of their own decisions before the final invoice, not after.

A quick test

If a colleague took over your project tomorrow, could they say in five minutes what the contract delivers, what it does not, and which changes have been approved? If the answer depends on your memory, the scope is not yet in writing.

consulting scope change management best practices

← Back to the index

¿Quieres ver Iurefficient en acción?

Agenda una demostración o empieza tu prueba gratuita hoy mismo.

Solicitar demo
Iurefficient

Organization management, documents, and projects, powered by artificial intelligence.

Product

  • Presentation
  • Pricing
  • Security
  • Free trial

Iurefficient

  • For law firms
  • Articles and updates
  • News (blog)
  • Help Center
  • Contact

Legal

  • Privacy Notice
  • Terms and Conditions
  • Security

© 2026 Iurefficient. All rights reserved.

Already using Iurefficient for your law firm? Your current account includes access to Teams at no extra cost during the beta.

Made with ❤️ in Mexico