WordPress 7.1 Notes vs Client Review Tools: What Changes for Agencies
WordPress 7.1 is due on 19 August 2026, and it brings the biggest upgrade yet to Notes, the commenting system that first landed in WordPress 6.9. The headline addition is a suggestion mode: a collaborator can propose a change to your wording and an editor accepts or rejects it in a click.
If you run an agency and you currently pay for a client review tool, that raises a fair question: does core now do the job for free? Here is an honest answer, including the parts where core wins.
What WordPress 7.1 actually adds to Notes
Per the official Roadmap to 7.1, the Notes work includes:
- Notes on specific content within a block, and across multiple blocks (inline notes)
- Rich text formatting inside notes
- Suggestion mode, with an “apply suggestions” action
- @mentions to tag collaborators
- Emoji reactions on notes
- Notifications for replies and follows
Worth noting the roadmap’s own caveat: everything on it is “being actively pursued, but doesn’t necessarily mean each will make it into the final release.” Real-time collaboration in particular still has open strategy questions. Treat the list as intent, not a guarantee.
Taken together it is a genuinely good asynchronous review system, and if your feedback loop is between people who all have logins on the site, it may well be all you need. That is a real thing to say out loud: for internal teams, core is about to be very good, and free.
The distinction that matters: who is giving the feedback
Notes live in the block editor. To leave one, a person needs a WordPress user account on your site with editing access, and they need to be comfortable working inside the editor. That is exactly right for writers, editors and developers on the same team.
It is usually the wrong shape for a client. Most agencies do not want to create editor-level accounts for a client’s marketing manager, and most clients do not want to learn the block editor to say “this headline should be shorter”. There is also the awkward fact that a client with editor access can change things you did not ask them to change.
And Notes are attached to blocks in the editor, not to the rendered page. A client reviewing a site is reacting to the thing the public will see: spacing, a sticky header, how a section behaves on their phone. Plenty of that feedback has no block to attach itself to.
Core Notes vs a client review tool
| WordPress 7.1 Notes | A client review tool like Reviso | |
|---|---|---|
| Who it is for | Logged-in collaborators with edit access | Clients and stakeholders with no account |
| Where feedback happens | Inside the block editor | On the live rendered page, at any screen size |
| Account needed | Yes, a WordPress user | No, a share link |
| Suggest wording changes | Yes (7.1) | Yes |
| Works with Bricks and Elementor pages | Blocks only | Yes, native to Bricks, Elementor and Gutenberg |
| Formal client approval and sign-off record | No | Yes, timestamped, with a PDF certificate on Pro |
| Feedback across a whole site or many sites | Per post or page | Whole-site reviews |
| Price | Free with WordPress | Free core plugin, paid tiers |
So should you drop your review tool?
Use core Notes if your review loop is internal, your content lives in blocks, and everyone involved already logs in. It is free and it will be well made. Genuinely, use it.
Keep a dedicated client review tool if the person you need feedback from is a client, if the sites you build use Bricks or Elementor rather than blocks, or if you need the round to end with a recorded approval you can point at later. That last one is the gap core has never tried to fill: Notes are a conversation, not a sign-off.
The honest read is that WordPress 7.1 does not replace client review, it raises the baseline for internal collaboration and makes the boundary clearer. Suggestion mode is a good feature, and core having it proves the feature was never the hard part. The hard part is getting useful feedback out of someone who does not work in WordPress, and then closing the round.
What we are doing about it
Reviso already works this way: your client opens a link with no account, pins comments on the live page, can propose replacement wording in place, and approves the page when it is right, leaving a timestamped record. We will be testing against 7.1 through its beta cycle so the two sit together cleanly rather than competing for the same panel, and where core does a job well we would rather point you at core than pretend otherwise.
If you want the client side of this now, the free plugin covers unlimited sites, or see how it compares to other client feedback tools.