How to check website changes before client approval

Before approving a website change, open the original request and the updated page together. Check the exact result the client asked for, then look at the surrounding content and any links or interactions the change affects.

Agree on the requested result

Start with the requested outcome, including replacement wording and reference images. If the comment leaves room for interpretation, agree on what should change before approving the work.

DesignLoop keeps the original screenshot with the comment. The website annotation guide explains how to leave requests that are easy to check later.

Check the page the client will see

Open the intended preview or live website. Confirm you are checking the updated version at the same device size as the original request. If a change affects a menu or form, use it yourself to reach the state the client described.

DesignLoop’s Compare view places the original screenshot beside the current page result. Request a fresh check if the website has been updated since the comparison was made. A screenshot helps with appearance; test actions such as submitting a form on the website itself.

Website change checklist

Use the checks that apply to the request. This checklist covers a round of client changes; a full website launch needs broader testing.

Change	What to check before approval
Replacement copy	The wording matches the client’s suggestion, including punctuation. Read it in context for awkward breaks.
Image replacement	The correct image appears, important details remain visible, and the crop works on mobile.
Layout or spacing	The requested area fits at the relevant screen size without hiding or overlapping nearby content.
Button or link	The label is correct and the destination opens as intended.
Menu or form	The requested action works. Check the open menu or form confirmation as well as the initial view.
Removed content	The content is gone and there is no empty space or broken reference left behind.

When a change needs another pass

For example, a client might ask for a longer heading. The new wording can be correct on desktop but push the main button off-screen on a phone. Check both sizes before approving the request.

Ask for the specific remaining change on the same feedback item. Keep the original comment available so everyone can see what has already been addressed. A new, unrelated request belongs in its own comment.

Keep final approval with the owner

When work comes from a connected coding tool, the owner can inspect private progress and submitted screenshots on the Implementation board. Ask for a screenshot at the device size that prompted the request when that helps the review.

Mark an item implemented only after the result matches the request. If another pass is needed, request changes while leaving the client feedback open. The owner controls the final status clients see.

For review rounds, client access, and pricing, see the website feedback tool overview.