client website feedback workflow

Client Website Feedback Workflow: 7 Steps to Final Approval

Set up a client website feedback workflow that keeps comments in one place, settles scope, and ends in a clear sign-off, for websites and apps.

A client website feedback workflow is a fixed way to collect, sort, act on and close client comments. It turns “can we make it pop?” into a list of decisions with an owner and a status. The steps below work for a portfolio, a landing page, a store or a web app. They also cover what changes when your AI assistant builds the site and every edit goes live at once.

TL;DR

Pick one place for feedback and one person on the client side who consolidates it.
Ask for feedback by stage: structure first, then copy, then polish.
Sort every comment: bug, agreed change, question or new scope. Answer each one in writing.
Close each round with an explicit approval that names what was reviewed.
On WebsitePublisher, changes are live immediately, so agree on a batch before you apply it.

Why a feedback process matters
The seven steps at a glance
Step 1: Set scope, roles and deadlines before anyone looks
Step 2: Ask for the right feedback at the right stage
Step 3: Collect feedback in context, in one place
Step 4: Triage every comment
Step 5: Apply the changes
Step 6: Verify before you mark anything resolved
Step 7: Get a clear, written approval
What goes wrong, and what to do about it
Where our approach fits
Try it on your next client project
FAQ
Sources

Why a feedback process matters

Without a process, feedback arrives as email replies, chat messages, screenshots and phone calls. Nobody knows which version is current. One client feedback guide describes the result as a moving target scattered across channels, which leads to scope creep and delays.

Reviews are also more than opinion. The Project Management Institute treats a project review as a control point. It needs a standard format, interim objectives, a clear purpose, defined roles, named participants and assigned resolution periods. Done that way, it surfaces risk early, so you can correct course before final delivery.

Why a feedback process matters — overview diagram

A website review is the same thing at small scale. You compare what exists with what was agreed, and you decide what happens next.

The seven steps at a glance

Step	What happens	Output
1. Set scope and roles	Name the coordinator, reviewer and approver	One-page review brief
2. Stage the rounds	Structure, then copy, then polish	Round calendar
3. Collect in context	Comments on the exact page or element	One shared list
4. Triage	Bug, change, question, new scope	Labeled comments
5. Apply the changes	One owner makes the accepted edits	Updated pages
6. Verify	Reviewer repeats the task on the new version	Resolved items
7. Approve	Written sign-off for the release	Approval record

Step 1: Set scope, roles and deadlines before anyone looks

Most feedback problems start before the first draft is shown. Settle three things up front.

Who reviews and who decides

Name one person on the client side who consolidates opinions from everyone else. A website review guide recommends a single primary coordinator who gathers internal stakeholder opinions before submitting them. Without that person, you get the founder’s comment, the marketing lead’s contradicting comment and the owner’s spouse’s third opinion, all separately.

One review process describes three roles: the reviewer, the person who consolidates client decisions, and the approver. In a small business, one person may hold all three. Write the names down anyway.

What they review

Clients can review wireframes, visual design, content, a working build and final delivery. An approval workflow guide suggests defining review windows, approval methods and a primary approver in the statement of work. Put the same three items in your proposal or kickoff email.

How long they have

Give every round a start date and an end date. Shorter windows suit text. Visual reviews usually need a little longer. Pick numbers with the client, write them down and remind them once before the deadline. Slow feedback is one of the most common complaints in client work, and one approval-process guide recommends deadlines, reminders and a deliberately small group of stakeholders to reduce them.

Step 2: Ask for the right feedback at the right stage

“What do you think?” invites everything at once. Ask for one kind of feedback per round.

One client feedback process uses timed rounds, each with a start, an end, a clear scope and a decision point. Its example runs three rounds:

Structure and flow. Page order, navigation, what each page is for.
Copy and details. Wording, images, links, forms.
Final polish. Spacing, small visual tweaks. Structural changes are excluded.

The review process from Annot8 adds a useful habit: separate requirements, copy, visual design and functionality feedback, say which version and environment the reviewer is looking at, and limit the review to chosen user journeys.

A journey is a task, not a page. Try these:

“Find our pricing and contact us.”
“Buy the cheapest product.”
“Book a call from your phone.”

Task-based prompts get you comments about whether the site works. Open prompts get you comments about fonts.

A short brief to send with every round

Keep it to five lines:

What you are sending (pages, version, link)
What kind of feedback you want this round
What is out of scope this round
Who consolidates comments
The deadline, and what happens if nothing comes back

Step 3: Collect feedback in context, in one place

The biggest quality gain comes from tying each comment to the thing it describes. Screenshots, PDFs and email force everyone to translate a remark into a page location, as this guide to client website feedback points out. Comments attached to the real page or element keep the context.

Pinning a note to a specific element also replaces vague remarks such as “the hero doesn’t feel right” with a clear target. Visual annotation tools that let clients pin comments on a live staging site can turn those comments into tasks assigned to owners. Some review tools can also forward feedback to project boards in Jira or Trello.

You do not need a specific tool to start. You need these rules:

Feedback lives in one agreed place. Anything sent elsewhere gets pasted there by whoever receives it.
Each comment names the page and the element.
Each comment gets a reply, even if the reply is “noted, not this round.”
Nothing is deleted. Rejected and deferred items stay visible.

The point of the whole exercise is a written record in which no note is lost silently. Context plus a record is what you are buying.

How to write comments you can act on

Share this with your client as a half-page guide.

Vague	Actionable
“Make it more modern.”	“On the home page, the services section feels dense. Can we try three cards instead of six?”
“The text is wrong.”	“On the About page, the second paragraph says 2019. We opened in 2021.”
“The button is bad.”	“The Get a quote button on mobile is hard to see against the photo.”
“Something is broken.”	“The contact form on Pricing shows no confirmation after I press Send, on my phone.”

Element-specific comments also cut the back-and-forth needed to work out what the client meant.

Step 4: Triage every comment

Not every comment is a task. Sort first, then work.

A simple scheme from one agency feedback workflow uses four labels: in scope, out of scope, bug and question. The Annot8 process uses defects, agreed changes, questions and new scope. The names differ, but the logic is the same:

Bug. Something does not work as agreed. Fix it.
Agreed change. Inside the original scope. Assign it to one owner.
Question. The comment cannot be acted on yet. Ask, and pause that item.
New scope. Not in the original agreement. Respond in writing.

Handling out-of-scope requests

Do not quietly add them. Do not flatly refuse them. Send a short written response with the extra cost and the effect on the timeline, so the client can choose. That is the approach recommended in the agency workflow above. A client who sees the trade-off in writing usually decides quickly.

Resolving conflicting comments

When two stakeholders disagree, do not pick a winner yourself. Send the conflict to the client’s coordinator with both versions and a recommendation, and ask for one decision. Record the rationale and the approver for disputed items, which is also advised in the Annot8 process. Months later, that note answers the question “why is it like this?”

Useful statuses beyond open and done:

Accepted
Deferred, with the date of the next decision
Ready for verification
Verified

Step 5: Apply the changes

Once triage is done, one person makes the accepted edits. On many projects this is where things slow down: a developer opens a ticket, waits for a build, and tells the client to refresh later.

With WebsitePublisher the work is different. Your AI assistant (ChatGPT, Claude, Gemini or another supported assistant) builds and publishes websites and apps through the WebsitePublisher connector. You describe the change in plain language, and the change is live immediately. There is no separate deploy or publish step.

That speed helps, and it changes your workflow in two ways.

Batch the changes, then apply them

Because edits are live at once, the client could see a half-finished set of changes if you apply them one by one during the review window. Collect the accepted items from triage, apply them as a group, then tell the client the new version is ready for the next round. Do not edit while the client is mid-review.

Use the browser editor for small content fixes

For typos, a changed phone number or a new photo, your client can make content and visual changes directly in the browser without starting a new AI session. We cover that approach for teams in browser-based website editing for small teams. Agree beforehand which changes the client may make alone and which go through the list. A good rule: text and image swaps can be done directly, while layout and structure go through a review round.

If you run client work across many sites, our piece on AI for web agencies covers which parts to automate and which to keep human.

Build the first draft from one brief

A clear first draft reduces the number of rounds. If you are building several pages, working from a single written brief keeps wording and layout consistent. See building a multi-page website with AI from one brief for how to set that up.

Step 6: Verify before you mark anything resolved

“Resolved” should mean the agreed outcome was checked, not that someone made an edit. The Annot8 process says a follow-up review should link to the accepted changes and ask reviewers to repeat the relevant task on the new version.

A workable follow-up message looks like this:

Round 2 is ready: [link]. We made the 9 changes you approved (list attached). Please repeat the “book a call on mobile” task and mark each item verified or reopen it by Friday. Anything not in the list is for round 3 or a separate estimate.

Tools that let reviewers suggest changes, let an owner accept or reject them and then record a timestamped approval show the same idea: every state change leaves a trace.

Accessibility checks fit well here, since they are testable pass/fail items. Our website accessibility checklist for developers gives 25 tests you can add to a verification round.

Step 7: Get a clear, written approval

Define what counts as approval before the project starts. Options include written email confirmation or a portal approval. The approval workflow guide also notes that teams may add a silence-as-approval clause to the statement of work. If you use one, make sure the client has agreed to it in writing and knows the deadline. Keep every approval in one place.

The final sign-off note should name four things, following the Annot8 process:

The release or version approved
The scope completed
Known remaining issues
The approver

Deferred requests stay on the list with the next decision point. They are not dropped, and they are not smuggled into this release.

A sign-off template

Approval: [Client] website, round 3 Approved: all pages in the attached list, reviewed [date]. Completed: the 14 accepted changes from rounds 1 to 3. Known issues: blog layout on small tablets, scheduled for the next phase. Deferred: store filters, to be decided on [date]. Approved by: [name, role]

What goes wrong, and what to do about it

Feedback never arrives. Set the deadline, send one reminder, and follow the approval clause you agreed. Shrinking the group of reviewers helps more than chasing.

Feedback arrives in five places. Reply once in the agreed place with the pasted content, and ask the client to use it from now on. Do this politely every time. It takes a few rounds to stick.

The client re-opens structure in the polish round. Point to the round brief. Offer to log it as new scope with cost and timing.

Edits keep arriving after approval. Treat them as a new request. The sign-off note makes the line clear.

Comments contradict each other. Escalate to the coordinator, record the decision and move on.

Where our approach fits

We built WebsitePublisher around a simple idea: you should be able to describe a website or app in plain language, have your AI assistant build it, and keep changing it without being locked into one AI session. For feedback workflows, three things follow from that:

Speed between rounds. An accepted batch of edits can be live in the time it takes to describe it.
Control for the client. Content and visual edits can be made in the browser.
Freedom of tool. You can use different AI assistants on the same project.

The flip side is discipline. Fast edits make it tempting to change things during a review. A fixed round structure is what keeps that speed useful instead of chaotic. The process in this article is tool-agnostic. Use whatever comment tool your clients will actually open, and keep the decision record yourself.

Try it on your next client project

If you build client sites, landing pages, stores or web apps, you can have your AI assistant build the first version through the WebsitePublisher connector and run these review rounds on top. See how it works, and see the pricing page for plans, including a free one.

Websitepublisher

The first round is the cheapest place to test your process. Send the brief, collect comments in one place and close the round with a written decision.

FAQ

How many revision rounds should a website project include?

Three is a common structure: structure and flow, copy and details, then final polish. Write the number and the scope of each round into your agreement. Anything beyond that becomes a new request with its own cost and timeline.

Who should give feedback on the client side?

One coordinator should consolidate everyone’s opinions and submit a single list. In a small business, that person is often also the approver. Without one, you receive conflicting comments from several people and have to referee them.

Is email good enough for website feedback?

Email works for decisions and approvals, but it is poor for page-level comments. Clients end up describing locations in words, and your team has to guess. Comments tied to the exact page or element keep context, and a shared list keeps the record in one place.

What if a client keeps asking for more changes after approval?

Treat each one as new scope. Reply in writing with the added cost and the timeline effect, and point to the sign-off note that lists what was completed. Deferred items stay on the list with a date for the next decision.

Does a platform where edits go live immediately change the review process?

Yes, slightly. Since edits go live as soon as they are made, apply accepted changes in a batch between review windows rather than one by one. Agree in advance which small content edits the client can make directly in the browser.