Changing SOW after starting work on it

[northernladuk]

Nothing wrong with it but at some point there is a line where the SOW just becomes and paperwork veil for D&C. You'll know if the client is operating like that quick enough with constant requests for this and that and at that point you need to have a good think... but until you spot it then what they are proposing is not a problem.

[jamesbrown]

Perfectly normal. Definitely want to change the SoW, but a new one vs. a modded one is a details issue.

[eek]

Do what the client wants - and it makes sense to me

More work required so SoW changed to reflect the additional work identified. As the vast majority of the work is the same it's a change not a complete rewrite.

[zonkkk]

After discussing, agreeing and quoting for a piece of work for one of my clients, I started to work on it.

The project manager wants me to do some extra work that is closely related to what I am currently doing but has not been quoted for. They don't want to raise a new SOW to run in parallel with the old one, but change the old one for which I will send an updated quote. They say they prefer to do this as the new SOW would look too much like the first one and it may raise questions in an audit.

Is this normal practice?