How a Change Request Log Stops Scope Creep on Web Projects

A website project rarely blows its budget through one big decision. It drifts through small requests that each sounded reasonable in a meeting, such as an extra form field or a new landing page. Nobody writes them down, so nobody prices them, and the launch date quietly slides. By the final invoice, client and agency remember the same project very differently.

A change request log fixes that with one shared record of every request made after scope sign-off. This guide explains what the log should capture, how each entry gets priced and approved, and who should own it. It is written for UAE business owners commissioning a website from an agency or freelancer. It suits fixed-price and sprint-based contracts alike.

What is scope creep on a website project?

Scope creep is work that enters a project without matching changes to time, cost or resources. The PMI Lexicon of Project Management Terms defines it in almost exactly those words. On a website, it arrives as small requests made in calls, chats and review comments.

The danger is not change itself, because good projects adjust as they go. The danger is change with no record, which leaves the budget and deadline fixed while the work grows. That gap eventually surfaces as rushed testing, a disputed invoice or a delayed launch.

Quick Answer

Scope creep on a UAE website project is extra work added without adjusting time, cost or resources. Change is normal, but unrecorded change is what breaks budgets and launch dates.

What should a change request log record?

Each entry needs a number, the date, the person asking and a plain description of the request. Add the reason, because a request tied to a business goal deserves different treatment from a preference. Then record which pages, templates or integrations the request touches.

Next come the estimate, the effect on the launch date and the decision. Allow only three decisions: approved, deferred or rejected, each with a date and a named approver. A simple shared spreadsheet is enough, provided both sides can see it and nobody edits closed entries.

Quick Answer

A UAE website change request log should record the request, requester, reason, affected pages, estimate, schedule impact and decision. Approved, deferred or rejected are the only three outcomes worth allowing.

How should each change request be priced and approved?

Price the change before anyone starts building it, never after the work is finished. The agency should give hours or a fixed amount in AED, plus any shift to the launch date. The client then approves in writing, and an email reply counts.

State whether the price includes VAT, since the UAE Federal Tax Authority sets the standard rate at 5%. Group small items into one weekly approval so the log does not slow the team down. Free changes still belong in the log, because their schedule impact is real.

Quick Answer

Each website change in the UAE should be estimated in AED, with schedule impact, before work starts. Record written approval and state whether 5% VAT is included in the price.

Who should own the change log?

One person on the client side should own the log and decide what enters it. That person ranks requests against the launch goal and stops colleagues sending changes straight to developers. The agency's project manager keeps each estimate and status current inside the shared log.

Agile software teams already use a similar idea. The 2020 Scrum Guide makes the Product Owner accountable for ordering the Product Backlog, even when others help maintain it. The lesson for a website build is simple: one accountable owner beats a committee of competing requests.

Quick Answer

A website change log needs one accountable owner on the client side who ranks requests. The agency project manager maintains estimates and status, like the Scrum Guide's Product Owner model.

When should a change wait until after launch?

Defer any change that is not needed for launch day and would push back the launch date. Most cosmetic tweaks, extra landing pages and new integrations fit that description well. They can ship in a planned second phase, with fresh estimates and their own approval.

Changes that fix a legal, security or core conversion problem usually belong before launch. A broken enquiry form or missing privacy notice should never wait for phase two. Keeping a visible deferred list also reassures stakeholders that their ideas were heard and recorded, not lost.

Quick Answer

Defer website changes that are not essential for launch and would delay it to a planned second phase. Fix legal, security and enquiry-form problems before launch, whatever the schedule says.

Main Takeaways

Scope creep is unrecorded change, not change itself. Keep one shared log that captures each request, its reason, estimate, schedule impact and decision. Price every change in AED before work starts, state whether VAT is included and record written approval. Give one named client-side owner the final say, and defer anything not essential for launch to a planned second phase.

Keeping your website project on budget

A change request log costs little to set up and saves arguments at the end. It turns vague memories of who asked for what into a dated record both sides accept. Start it on the day scope is signed, not when the first dispute appears. Review it weekly with your agency, and keep deferred ideas in their own visible list.

Our UAE web design contract checklist explains exactly where change rules sit within the final signed agreement. A clear website RFP also reduces changes before the build starts. Auronix Web Studio can set up a shared change log for any business website development project. Send us your brief, and we will explain how the log would work for your project.

Sources & References

Project Management Institute - PMI Lexicon of Project Management Terms, Version 5.0 (scope creep definition; last updated January 2026) - https://www.pmi.org/-/media/pmi/documents/registered/pdf/pmbok-standards/pmi-lexicon-pm-terms.pdf

Ken Schwaber and Jeff Sutherland - The 2020 Scrum Guide (Product Owner and Product Backlog) - https://scrumguides.org/scrum-guide.html

UAE Federal Tax Authority - Value Added Tax (standard rate 5%) - https://tax.gov.ae/en/taxes/vat.aspx