Skip to content

The client changed their mind after we started and there's no change control

The specification moved, the work followed, and the cost and time effect was never captured before it did.

01The instruction lands
02The change priced
03The price agreed
04Into the account
You are here: The job is being redesigned in fragments, unpriced.

What's happening?

The client's changes arrive as conversations and revised finishes schedules, the site accommodates them because accommodating is the culture, and the account absorbs each move without a price ever being put in front of the person who moved it. By the end, the job has been redesigned in fragments - and the argument is about all of it at once, from memory, against a client who remembers asking for less.

Change control is a courtesy to both sides, not bureaucracy: each change captured when it is asked for, priced - even roughly - before it is built, and put back to the client as a decision rather than a surprise. Clients sometimes say no to prices; they always dispute surprises. The registers service is that discipline run for you: every change logged, priced and chased to an instruction, so the account grows with signatures on it.

The solution

Every change priced as a decision, not discovered as a surprise.