Put Change Requests Through a Margin Gate Before Delivery Starts

The Signal

A customer asks for one more audience, a revised deliverable, a new integration, or an earlier deadline. The account lead says yes because the request sounds small and the relationship matters. Delivery starts before anyone checks the signed scope, available hours, vendor cost, or work already committed.

That is where margin starts disappearing. Not in one dramatic failure, but in a series of helpful decisions that never become commercial decisions.

A change-request margin gate connects the request to six facts: the original commitment, the requested change, the delivery effect, the commercial choice, the accountable owner, and the approval required before work starts. It gives the team a place to decide whether to include, trade, price, defer, or decline the work.

Why this matters now

Customer requests now arrive through more surfaces than the contract anticipated: calls, chat, project boards, support tickets, shared documents, and AI-generated notes. The faster those requests move, the easier it is for a casual sentence to become a delivery promise.

The cost is not limited to extra hours. A new request can interrupt scheduled work, pull in a senior person, extend an approval cycle, create another version to maintain, or move a deadline that affects other customers. None of that is visible if the account is measured only against the original invoice.

Federal acquisition rules use formal contract modifications and require agreement on the change and its effect in defined circumstances. A founder-led service business does not need federal paperwork. The useful operating principle is smaller: when the commitment changes, record the change and its consequence before treating it as authorized work.

The mistake to avoid

The mistake is turning scope control into a reflexive no. Customers will discover better information after work begins. Priorities will move. A useful partner should be able to adapt. The gate exists to make adaptation explicit, not difficult.

The second mistake is asking delivery to protect margin without giving delivery the commercial facts or authority. A specialist can estimate the work. The account owner can explain the relationship. Finance can show the economics. The authorized owner must decide whether the business absorbs the cost, trades another item, changes the date, or sends a price. Do not make the person doing the work negotiate all four layers alone.

Do not hide the decision in a message thread either. The thread records conversation, but it rarely preserves the final scope, price, date, owner, and approval in one usable place.

Run the change-request test

Pull the last ten requests that changed a deliverable, deadline, channel, audience, integration, reporting requirement, or approval cycle. For each request, compare the signed commitment with what the team actually delivered.

Then fill in five fields. What changed? What work or cost did it add? What existing commitment moved? Who made the commercial decision? Where did the customer accept the resulting price, trade, or date?

Use real units. Two design rounds, six engineering hours, one outside purchase, a three-day schedule move, or removal of the original report is more useful than "minor scope adjustment." If the team cannot name the unit, it cannot see the margin effect.

Now separate requests from corrections. Fixing work that failed the agreed standard is not an upsell. A genuinely new audience, integration, deliverable, or accelerated date may be. This distinction protects the customer from paying for the company's miss while protecting the company from quietly funding new work.

What stays protected

Protect the original customer promise. Do not use a change request to rewrite history or escape work already sold. Keep the signed scope, acceptance criteria, price, and target date visible beside the new request.

Protect delivery from starting on an ambiguous yes. A relationship owner may approve a no-charge exception, but the decision still needs a cost estimate, a named approver, and a statement of what happens to the schedule or remaining work. Free is a pricing decision, not the absence of one.

Protect customer trust as well. Do not surprise the customer with an invoice after the work is complete. Present the options before execution: include the change, exchange it for another item, move the deadline, price it separately, or hold it for a later phase.

The first move

Start with one active account, not the entire business. Review the last 30 days of requests with the account owner and delivery lead. Mark each as included scope, correction, approved exception, trade, priced change, deferred item, or unauthorized work.

Total the labor and outside cost attached to the approved exceptions and unauthorized work. The objective is not perfect job costing. It is to make the invisible decision visible enough to improve the next one.

The move this week

Create a one-page change record with the request, original scope reference, estimate, schedule effect, commercial option, delivery owner, approver, and customer acceptance link. Set one rule: work does not start until the record shows the decision.

Review the register weekly for a month. If the same request appears more than once, repair the upstream problem. Tighten the package, add an intake question, clarify acceptance criteria, price the option, or reserve capacity for it.

The objective is not to charge for every favor. It is to know when the business is choosing to make one, what it costs, and what stays protected after the choice.