Change Request

A change request is anything you ask a software team to add or alter after the price was agreed and the work began.

Also known as scope change extra work request variation

Definition

A change request is anything you ask for after the price was agreed and the work began. It is the single most common reason a final bill does not match the first quote, and that is not dishonesty. It is simply everything nobody wrote down before the build started.

Here is how it happens. A clinic asks for a booking system, and the quote covers booking, cancelling and a daily list. Three weeks in, the receptionist mentions that half the patients pay in instalments, which was true on day one, but nobody said it, so nobody priced it. Instalments touch the invoice, the receipt, the daily total and the report the accountant sees, so a sentence in a meeting becomes eleven days of work.

The cure is boring and it works, and Linkysoft starts every project with it. Write down what the system will do before anyone builds it, screen by screen, in the ordinary language you would use with a friend. Then walk that list past the person who will sit in front of the software all day, not only the owner who is paying. Receptionists, storekeepers and drivers know the exceptions, and the exceptions are where the money goes.

Then agree how changes will be handled rather than pretending there will be none, because there will be some. A sensible arrangement prices each request separately, in hours, before it is started, and still lets you say no. Ask for a small budget set aside at the beginning, perhaps a tenth of the total, so the first request is not an argument. Group them too, since six small changes reviewed on one Thursday cost less than six interruptions across a fortnight, and each interruption makes someone stop and find their place again.

One honest note before you spend anything. A ready-made system avoids most of this, because the arguing already happened with somebody else. So if your clinic or shop works the way most clinics and shops do, buying one of the finished Linkysoft systems means the features are there to look at and there is nothing to describe. Custom work earns its price when your process is genuinely unusual, and that is when a custom web application is worth the extra care. Linkysoft will tell you which of the two you are before you pay for either.

Questions about Change Request

Why is my final bill higher than the first quote?
Almost always because of work nobody wrote down before the build started. The quote covered what was described, and the rest was discovered while the software was being made.
Can I avoid change requests completely?
No, and a supplier who promises none is guessing. You can make them rare and cheap by describing every screen in plain words first, and by asking the staff who will use it daily.
How should a change be priced?
Separately, in hours, and agreed before the work starts, with the right to say no. Ask for the estimate in writing, and group several small changes into one review so the team is not interrupted six times.
Does a ready-made system have change requests too?
Far fewer, because the features already exist and you can see them before you pay. Changes appear only where your way of working differs from the way the system was built.

Still not sure how this applies to your project?

Tell us what you are building and we will answer in plain language.