Blog

How to collect website feedback from many stakeholders without chaos

A board member, a marketing team, someone from legal and the founder all want a say on the same website. Each of them is right to care, and each will send notes in a different way unless you set the rules first. This guide covers website feedback with multiple stakeholders from the kickoff call to final sign-off: who reviews, who decides, how to run a round, and what to do when two people want opposite things.

Many reviewers, one website: Who reviews, who decides, and how to sign off.
The short versionName one person who makes the final call before anyone sees the site. Run each round on one review link with a deadline, and give every reviewer a short brief that says which pages and which questions are theirs. When comments conflict, tag the decision-maker in that thread and write the decision there. Close the round with an approval from each person who has to sign off, and treat anything that arrives after the deadline as input for the next round.

Why many reviewers turn into chaos

On most multi-stakeholder projects the trouble starts with how feedback arrives. The founder replies to the launch email with three bullet points. Marketing exports a PDF and draws on it. Legal sends a Word document of tracked changes to the homepage copy, written against last week's version. A board member mentions something on a call and nobody writes it down. Now you have four sources, two of them out of date, and no idea which notes cancel each other out.

Three things cause most of it:

  • Nobody agreed who has the final word, so every comment carries the same weight.
  • Feedback arrives in different places and at different times, so you can't see the round as a whole.
  • Each person reviews everything, including the parts outside their expertise, which produces overlap and contradictions.

Agree who reviews and who decides

At kickoff, before any design exists, list everyone who will look at the site and give each person one role. The most important line on that list is the decision-maker: one named person who settles disagreements and gives final approval. A team or "the board" can't do this job. If the client insists that a committee decides, ask who chairs it and make that person the contact who speaks for the group.

A simple RACI-style table does the job. It needs four columns and should fit on one screen.

PersonRole in reviewsReviewsMust approve?
Head of marketingDecision-maker: settles conflicts, final sign-offWhole site, focus on message and calls to actionYes
Founder or CEOReviewer, consulted on directionHomepage, About, pricingNo, unless agreed
Legal or complianceReviewer for riskClaims, pricing terms, privacy and cookie wording, formsYes, for their pages
Product or sales leadReviewer for accuracyFeature pages, product names, numbersNo
Board or committeeInformed, comments only on requestFinal version, one passNo
Agency PM or web leadRuns the round, replies to every commentEverythingNo

Send the table to the decision-maker and ask them to confirm it in writing. That email becomes your reference later, when a new voice appears in round three and wants to restart the homepage. Our client website approval guide covers the rest of the sign-off process, including timelines and what to do when a client goes quiet.

Run one round on one link with one deadline

A round works when everyone looks at the same version, in the same place, by the same date. In practice that means:

  1. Share one review link for the whole group, so nobody is looking at a PDF while others look at the live site.
  2. Set a deadline that falls three to five working days later, and put it in the email subject line.
  3. Say what the round is for. Round one is structure and message. Round two is wording, images and the phone layout. The final round is fixes and sign-off.
  4. Don't change the page while the round is open. If you must fix something urgent, say so in the thread.
  5. When the deadline passes, close the round, reply to every comment, and share the next version.

When everyone comments on the same page, they also see each other's notes. Marketing can reply "agreed" under the founder's comment, and legal can flag that a proposed headline makes a claim they can't approve, right where it was proposed. You get fewer duplicate comments and you find conflicts earlier. How many rounds to include in the first place is covered in our post on website revision rounds.

Ask each person to review their own area

The biggest single improvement on a multi-stakeholder project is giving each reviewer a scope. A lawyer commenting on button colours and a designer commenting on the refund policy both waste time, and both create notes you then have to weigh against the experts'.

Write a short reviewer brief and send it with the link. Keep it to one screen:

ReviewerPlease checkPlease skip
LegalEvery claim and number, pricing terms, the privacy and cookie notices, form consent wordingLayout, colours, image choice
ProductFeature names, screenshots, anything described as included or coming soonBrand tone, page order
FounderDoes the homepage say what we do in the first screen? Does the About page sound like us?Typos and spacing, which we'll catch in the final round
MarketingHeadlines, calls to action, the phone layout, every form and where it leadsLegal wording

"Please skip" matters as much as "please check". It gives people permission to leave things alone, and most busy reviewers are grateful for it. Reviewers can still flag something outside their area if it's clearly broken. The brief just stops them from rewriting it.

Clear scopes also cut down on vague notes, because people are answering specific questions. For the vague ones that still arrive, our guide to vague client feedback has replies you can borrow.

Example wording for the review request email

Here is an email you can adapt. Send it to the whole group at once so everyone sees who else is reviewing.

Subject: Website review, round 1: comments by Thursday 27 November

Hi all,

The first version of the new website is ready to review:
{review link}

This round is about structure and message: is everything
there, in the right order, saying the right things? Design
details come in round 2.

Please focus on your own area (the brief below says which
pages and questions are yours). Click anything on the page
to comment on it. There's nothing to sign up for. Please
also check the phone view.

If you agree with someone else's comment, just reply
"agreed" under it.

{Name} is the decision-maker for this project. Where
comments conflict, {Name} will make the call in the thread.

Comments by end of day Thursday 27 November, please. Notes
that come in later will go into round 2.

Thanks,
{your name}

Three lines in that email do most of the work: the deadline, the named decision-maker, and the rule for late notes. If they are written down before the round starts, nobody can feel singled out when you apply them. For the follow-up emails, such as the second round, the final sign-off and a polite chaser, use our feedback request email templates.

Settle conflicting comments in the thread

Conflicts will happen. Marketing wants a longer homepage with more proof. The founder wants it shorter. Legal wants a disclaimer under the headline that the designer would rather move to the footer. None of these people is wrong, and you are not the right person to choose between them.

A process that keeps this calm:

  1. Keep the disagreement in one thread on the element it's about. If a second comment on the same point appears elsewhere, link to the first one.
  2. Summarise the two positions in a short reply, neutrally, in one or two sentences each.
  3. Tag the decision-maker and ask for a choice by a date. Offer a recommendation if you have one, with the reason.
  4. When they decide, write the decision and the reason in the thread, then resolve it.

The last step is the one teams skip, and it causes most of the repeat arguments. If the decision lives in a phone call, the person who lost it will raise it again in round three, honestly believing it was never settled. A written decision on the comment itself is easy to point to. It also helps whoever picks up the project later.

Some conflicts aren't preferences. If legal says a claim can't go live, that is a constraint, and the decision-maker's job is to choose among the options that respect it. Say so in the thread so the discussion stays on the right question.

Keep sign-off clear with approvals

"Looks good" in a reply-all email isn't sign-off. It's unclear which version it refers to, and you can't tell whether the other approvers saw the same thing. Agree at kickoff which people must approve, then ask each of them for an explicit approval on a specific version.

A few rules that keep sign-off clean:

  • An approval belongs to one version. If you change the page afterwards, the next version needs its own approval, even for small changes.
  • Approvers sign off on their area. Legal approving the pricing page doesn't mean legal approved the homepage photography.
  • The decision-maker approves last, once every open comment is resolved or moved to a later list.
  • Keep a record you can find in six months: who approved, which version, and when.

What to do with late feedback

Someone will send notes the day after the deadline, often the most senior person on the project. Ignoring it is risky, and accepting it without question resets the round. Here is what tends to work:

  • Read it straight away. If it points to a real problem, such as a legal issue, a wrong price, a broken form or something that would embarrass the company, fix it now.
  • If it's a preference, add it to the next round, or to a post-launch list if the site is already in final sign-off.
  • Reply to the person and say where their note went and when it will be looked at.
  • If the late note reopens a decision that was settled and recorded, point to the thread and ask the decision-maker whether they want to reopen it. Reopening is fine, but it is a change with its own time and cost.

If the same person is late every round, talk to the decision-maker about it. Often the fix is a 20-minute walkthrough at the start of the round, so the busy reviewer gives their notes live and you add them to the page.

Where HTMLAnnotate fits

You can run everything above with email and a shared spreadsheet, and plenty of teams do. A feedback tool makes it easier to hold the rules, mainly because everyone comments in one place. Here is what HTMLAnnotate does that maps to this process, and no more.

  • One link for the whole group. Paste the staging or live address, or upload an HTML file or PDF, and send the review link. Reviewers enter a name and email once and need no account or extension.
  • Comments pinned to the page. Each note sits on the heading, button or image it's about, and desktop, tablet and phone views keep their own comments, so the phone check doesn't get mixed in with desktop notes.
  • @mentions in the thread. Type @ to tag a teammate or anyone who has already commented, so you can pull the decision-maker into a conflict and they get an email.
  • Labels. Tag threads by area, for example Legal, Copy or Brand, and filter the list to see what each reviewer still needs to look at.
  • Replies and resolve. Write the decision in the thread and resolve it. Everyone in that thread gets an email when it's done.
  • Approvals per version. Reviewers press Approve, you get an email, and you can see who approved, when and on which version. A new version on the same link starts clean and needs its own approval, and earlier versions keep their comments.
  • Closing a round. A switch pauses new comments while you work on the changes, and reviewers can still read everything.
  • Teams. Team-only comments stay between you and your colleagues, which suits internal notes like "client will push back on this". Pro can add a second person, and Team holds up to 25 people.

On the free plan, review links last up to 14 days and each page keeps up to 3 versions, which covers a short project. For a longer project where you want the sign-off record to stay available, Pro links last until you delete them. Plans and prices are on the pricing page, and you can try the review page on a sample site at the live demo before sending anything to a client.

Questions

Who should make the final decision on website feedback?

One named person, agreed before the first review. On agency projects this is usually the client's project lead or marketing head. In-house, it is often the head of marketing or whoever owns the site's budget. Committees can advise, but one person settles conflicts and gives the final approval.

How many stakeholders should review a website?

As few as you can while still including everyone who could block the launch. A common pattern is three to six active reviewers per round, each covering their own area, plus people who are told about the round but only comment if something is wrong in their field.

How do you handle conflicting feedback from stakeholders?

Keep both comments in the same thread, tag the decision-maker, and ask for a choice with a deadline. Once they decide, write the decision in the thread and resolve it. Avoid settling it yourself in a side email, because the person who lost the argument will not see the reasoning.

What do you do with feedback that arrives after the deadline?

Read it straight away in case it is a real problem, such as a legal issue or a broken page. If it is, fix it. If it is a preference, log it for the next round or the post-launch list, and tell the person where it went. Agree this rule at kickoff so it doesn't feel personal.

Should every stakeholder approve the website?

Every person whose area carries risk should approve, for example legal for claims and terms, and the decision-maker for the whole site. Other reviewers can comment without approving. Write down who must approve before you start, so you know when a version is finished.

Do stakeholders need an account to leave feedback in HTMLAnnotate?

No. Reviewers open the link, enter a name and email once per browser, and click anything on the page to comment or press Approve. Only the person sharing the page needs an account.

How long should a stakeholder review round take?

Three to five working days suits most rounds. Shorter rounds get skipped by busy senior people, and longer ones invite a second wave of opinions. Put the deadline in the email subject line and in the review brief.

Run your next stakeholder round on one link. Reviewers click the page to comment, with no account, and approve each version when it's right.

Start a free review