Value-added services and the drift in scope

A commercial category, not a technical one

What counts as value-added is defined by the agreement, not by the nature of the task. Applying a label is standard work in an operation designed around it and an exception in one that was not. The practical test is whether the activity was resourced in the solution design. If it was not, it needs its own trigger, its own rate and its own capacity, however trivial the task looks on paper.

The difference between a task and a specified service

A task is described by what someone does; a service is described by what has to be true when they finish. Specifications that hold up include the input condition, the finished condition, the tolerance for defects, what happens to rejects, who supplies consumables, and the notice needed to schedule the work. Without those elements a provider is quoting on an impression, and the first batch that arrives in unexpected condition turns into a variation request.

Change control and the favour that never ended

Most drift starts helpfully. A site agrees to a small extra step for a promotion, nobody raises a variation because the volume is trivial, and the step survives the promotion by years. Multiplied across a long agreement, these accumulate into an operation that is materially more expensive to run than the one that was priced. A lightweight change process, in which any new step is recorded even when the rate stays unchanged, keeps the record honest without making the site bureaucratic.

Where the work belongs in the network

Postponing configuration until demand is known works only if the work is done somewhere close enough to demand to be useful, and by a party equipped to do it. Placing it at a central site keeps unit costs low but reintroduces the lead time postponement was meant to remove; placing it at a market-facing site does the reverse. This is a network design judgement, and it is worth taking before choosing which provider performs the work.

Frequently asked questions

Why do providers price small additional tasks at what feels like a high rate?

Because the cost is rarely in the task. Scheduling it, briefing a team, staging the stock, sourcing consumables and moving goods off the normal flow all consume more than the few seconds of work itself. Rates that look disproportionate usually reflect disruption rather than effort.

Should value-added work sit in the main agreement or in separate orders?

A framework in the main agreement with per-project specifications works well. The framework fixes how work is requested, scheduled, priced and accepted; the individual specification carries the detail that changes each time.

How can a client tell whether drift has happened?

Compare the current activity list at the site against the schedule that was priced. If operations describes steps that appear nowhere in the agreement, the operation has moved. That comparison is worth running at least at each commercial review.