What is a Revision?

Revisions are a crucial part of any web design project. They make sure that you get the site we’ve scoped, tailored just right.

But, they are also the largest cause of scope creep and project overruns.

So, what is a revision and how can you make sure it doesn’t lead to ballooning costs?

Simply put, a revision involves making edits or changes within the existing project framework. Often, this feedback is feedback you’ll provide using our visual feedback editor.

To prevent exceeding allocated time and resources, revisions should be approached consciously. This includes aligning feedback from clients and stakeholders to minimize future unnecessary revisions.

If you’re part of a team, it’s crucial to have one team member represent the collective input of the team to ensure consistency and avoid conflicting opinions (or burning through your revision budget unexpectedly!).

Examples of Revisions vs Scope Changes

To help keep it clear what constitutes a “revision” and what constitutes a scope change, some examples may help:

Revision	Scope Change
Edits to page content	Copywriting a webpage
Changing banners	Configuring a banner plugin
Changing header graphics	Designing new headers
Adding a new page	Building a new page layout
Formatting a new page	Designing a webpage
Changing popup text	Creating and integrating popup
Updating gated content	Configuring content gates
Swapping content on a landing page	Creating a funnel

Of course, this isn’t comprehensive. But, it should it give you some sense for how to think about the feedback you give and what may or may not be included in a revision or a Support Ticket (for customers on Super Support).

Things in the left column – and those similar to it – are generally covered, while the items in the right may require a scope change, change request, or additional costs.

As we get through your project, feel free to make any requests you like, and don’t worry, a Pro will let you know if a scope change request is needed!