Atarim for Clients and Stakeholders: How to Provide Clear Feedback
Point at the thing you mean, say what you want changed, and let the screenshot do the explaining.
Most feedback gets lost in translation, not in transit. “The button looks off” arrives in an email, three days later somebody asks which button, and a week disappears. Atarim removes that gap by letting you attach your comment to the exact thing you are looking at — no account, no project tool to learn, and no describing where something sits on the page.
You click the thing you are talking about. Atarim records where you clicked and what the page looked like at the time.
Most feedback gets lost in translation, not in transit. “The button looks off” arrives in an email, three days later somebody asks which button, and a week disappears. Atarim removes that gap by letting you attach your comment to the exact thing you are looking at.
You do not need an Atarim account, you do not need to learn a project tool, and you do not need to describe where something is on the page. You click it. Everything below is what you can do from there.
Opening the Project
Your team sends you a link. What happens when you open it depends on how they set the project up.
| How you were invited | What you see |
|---|---|
| A guest invite sent to your email | The link identifies you automatically, so you can comment without filling anything in. |
| A shared project link | The project opens directly. You are asked for your name and email before your first comment is saved. |
| A collaborator invitation | You set a password once, then sign in normally and receive notifications about the work. |
If you are not signed in, Atarim asks who you are before your first comment goes anywhere. A short form appears, headed Let others know who you are, with fields for your name and email address and a checkbox agreeing to the terms and conditions. Fill it in and select Save.
That is all that is required — no password, no account. Your name and email are used to attribute your comments so your team knows who left them. If you do already have an Atarim account, the same panel offers Sign in instead.




Browse Mode and Comment Mode
The bar along the bottom of the screen carries a switch between two modes. Knowing which one you are in explains almost every moment of early confusion.
| Mode | What it is for | What clicking does |
|---|---|---|
| Browse | Moving around the site as a normal visitor. | Follows links and uses the page as usual. |
| Comment | Leaving feedback. | Drops a marker on whatever you clicked and opens a comment box. |

Leaving Feedback on a Page
Clicking the element is what attaches your comment to it, so where you click matters as much as what you write.
Instructions:

You do not have to describe the location, the screen size, or the browser. That context is recorded with the task automatically — the screenshot is described in-product as a snapshot of what was seen when the task was made.
Drawing on the Screenshot
When words are doing too much work, draw instead. The comment box has an annotation control, described as annotating a screenshot and attaching it as a comment.
Instructions:


| Tool | Use it to |
|---|---|
| Arrow | Point at one specific thing. |
| Rectangle | Box off a region you are describing. |
| Circle | Ring something without hiding it. |
| Pen | Draw freehand. |
| Text | Add a label directly on the image. Double-click to edit it. |
| Move/Select | Reposition or resize something you have already drawn. |
| Pan | Move around a tall screenshot. Hold the space bar as a shortcut. |
Attaching Files to Your Feedback
Brand guidelines, a reference screenshot, a PDF of approved copy — anything that saves an explanation can be attached to the comment itself.
Instructions:

Individual files are limited to 15 MB. If a file is too large, unsupported, or a duplicate, Atarim says so rather than failing silently.
Giving Your Overall Impression of a Page
Some points are not about a particular button. “The whole page feels cramped”, or “I’m not sure who this is aimed at”, belong to the page as a whole rather than to a spot on it.
That kind of feedback goes in the Feedback tab in the sidebar. As a client or reviewer, it opens by asking What’s your first impression? and explains the order it wants things in — tell them what you think of the page as a whole first, then click individual parts of the page to comment on specific elements.
- Open the Feedback tab in the sidebar. You are prompted for your first impression of the page, with a note that your feedback is appreciated.
- Write your overall reaction in the comment box and post it. It is recorded against the page rather than pinned to an element.
- Then click individual parts of the page for anything specific.


Giving Feedback on Designs and Images
Not every review is a live website. If your team has shared mockups, logos, or other images, they appear under Designs in the sidebar, and you comment on them the same way — click the part of the image you mean, and type.
Where several versions of a design exist, you can compare them, so feedback stays attached to the version it was about rather than drifting onto the next one.
Reviewing on Phone and Tablet Layouts
A layout that works on a laptop can break on a phone, and that is usually where clients spot problems first. The bottom bar carries a device menu for previewing the design at various screen sizes, offering Desktop, Tablet, and Mobile.
Feedback left while a particular view is active is recorded against that view, so “this only happens on mobile” is captured for you rather than needing to be explained.
Following What Happens to Your Feedback
Every comment you leave becomes a task in the sidebar, and each task carries a status you can read at a glance.
| Status | What it means for you |
|---|---|
| Open | Received, not started yet. |
| In Progress | Someone is working on it now. |
| Pending Review | Done, and waiting for you to look. This is your cue. |
| Complete | Finished and closed. |
Tasks also carry a priority — Low, Medium, High, or Critical — which helps the team sequence work when you have left a lot at once.
You can edit a comment after posting it, and delete one you no longer want. Deleting asks you to confirm and warns that it cannot be undone. You can also react to a comment rather than replying, which is a quick way to acknowledge something without adding to the thread.
Where Atarim’s AI Helps You
Atarim has an AI team, and two parts of it are pointed at you rather than at your agency. Neither one writes your feedback for you — they help you say what you already mean more precisely.
Claro Checks Whether Your Comment Is Clear
Claro reads your comment for how actionable it is as you post it. If it reads clearly, that is the end of it — the comment is marked as clear and nobody is interrupted. If it is ambiguous, Claro follows up with you directly rather than sending your agency away to guess.


AI Chat Inside a Task
Each task thread carries an AI control, described as somewhere to ask AI to clarify, suggest ideas, or sanity-check your thinking, based on that thread. It is useful when you know something is wrong but cannot articulate what — describe the problem loosely and work towards a specific request before your agency ever sees it.
Working a rough idea into a clear request is what this is for. Explore Collaborating With AI Inside Strategic Discovery
What the InnerCircle Is, and Why You Will Not See It
The InnerCircle is Atarim’s wider AI review team — specialists covering design, user experience, SEO, copy, and functionality — which your agency can run across a page to surface issues before you review it.
That review is a team tool, not a client one. By default, client accounts do not see the page review control or the AI-generated task markers it produces. If your agency mentions an AI review of a page, this is what they mean, and the results reach you as ordinary tasks.
If you are curious what your agency sees when they run one, the process is documented. Read Starting An AI Review
Seeing Where the Project Has Got To
If your team uses project stages, you can see the schedule rather than asking for it. The panel is headed Project Stages and Deadlines, and shows the Active Stage, any Completed Stages, and the due date for what is in flight.


Timings are shown in plain terms — how long remains, or how far past due something is — so you can judge whether your feedback is arriving in time to be useful.
Approving a Page
Where your team has enabled it, pages carry an approval status, and an approved page is labelled clearly so everyone can see it has been signed off. This replaces the “yes, that’s fine” email that nobody can find three weeks later.

Whether you can set that status yourself depends on how your team has configured the project — page status controls are not switched on for client accounts by default. If you need to sign work off formally and cannot see the control, ask your team to enable it for you.
Sign-off has a workflow behind it that your team may be relying on. Read The Client Approval Workflow
What You Will Not See
Your team can mark comments and tasks as internal. These are described in the interface as visible to administrators and team members only, and they do not appear for you.
This is deliberate and it works in your favour: it lets your team have their working conversation — estimates, technical debate, who is picking something up — without it landing in your review. What you see is what concerns you.

By default, a client account also has a simplified interface: filters, team member lists, and internal task controls are hidden rather than shown and disabled. If you need something you cannot find, it is worth asking rather than assuming it does not exist.
Internal tasks are a paid feature your team may or may not be using. See Internal Tasks
Working in Your Own Language
The collaboration interface can be shown in a number of languages, set from the quick actions menu in the bottom bar. If English is not your first language, switching before you start is worth the ten seconds — clearer feedback comes from a reviewer who is comfortable.

The language is set for the project rather than for you personally, so ask your team if the option is not available. Learn More About Best Practices For Client Communication
Writing Feedback Your Team Can Act On
The tools handle where. You still handle what. A few habits separate feedback that gets actioned from feedback that generates three follow-up questions.
| Instead of | Write | Why it lands better |
|---|---|---|
| “Make this bigger” | “This heading should be larger than the paragraph under it so it reads as a title” | Describes the outcome, so the team can achieve it their way. |
| “I don’t like the colour” | “This green isn’t in our brand palette — guidelines attached” | Replaces taste with a rule anyone can apply. |
| “This is broken” | “Selecting this on mobile does nothing” | Says what you did and what happened. |
| “Fix the header, add testimonials, and the form’s wrong” | Three separate comments | Each becomes its own task and can be closed independently. |
| “Move it up a bit” | “This should sit above the pricing table” | Removes the guesswork about how far. |
| “As discussed” | The actual decision, written out | Your comment outlives everyone’s memory of the call. |
Faster feedback loops come from clearer feedback, not from more of it. Explore Tips For Faster Feedback Loops
Example Use Cases
| Situation | What to do |
|---|---|
| First look at a new homepage | Review in Desktop, then Mobile. Comment on elements as you go rather than writing everything up afterwards. |
| The wrong brand colour throughout | One general task for the page, with your brand guidelines attached, rather than a comment on every element. |
| A layout problem that is hard to describe | Annotate the screenshot with a rectangle and one sentence. |
| Something that only breaks on a phone | Switch to Mobile first, then comment. The view is recorded with the task. |
| Reviewing several logo drafts | Comment on each design in the Designs sidebar so feedback stays tied to the right version. |
| Checking whether your notes were done | Look for tasks marked Pending Review — those are waiting on you. |
Known Limitations
FAQs
Do I need an account to leave feedback?
No. You are asked for your name and email so comments can be attributed, but no password or account is required.
Where do I leave feedback about the page as a whole?
In the Feedback tab in the sidebar, which asks for your first impression before you start commenting on individual elements.
Will the team know which comments are mine?
Yes. The name and email you enter are used to attribute your comments, and guest comments are labelled as such.
Can I edit a comment after posting it?
Yes, and you can delete one too. Deleting asks you to confirm and cannot be undone.
Do I have to explain where on the page I mean?
No. Clicking the element records the position, and a screenshot of the page as you saw it is captured with the task.
How do I know my feedback was actioned?
Watch the task status. Pending Review means the work is done and waiting for you to check it.
Can I comment on a phone or tablet layout?
Yes. Switch the device preview in the bottom bar first, and your comment is recorded against that view.
Can I attach my brand guidelines?
Yes, provided attachments are enabled on your team’s plan. The limit is 15 MB per file.
Can I see the team’s internal discussion?
No. Internal notes and tasks are visible to administrators and team members only.
Why is Atarim suggesting changes to my comment?
That is Claro checking how clear your feedback is. You can preview a suggestion, accept it, or dismiss it — your original wording stands if you want it to.
Does the AI rewrite my feedback without asking?
No. Suggestions are shown to you and applied only if you accept them. Previews are visible to you alone.
Can I see the project deadlines?
Yes, where your team has set up project stages. The panel shows the active stage, completed stages, and what is due.
Can I use Atarim in a language other than English?
Yes, where your team has enabled the language setting for the project.
Common issues
- Clicking a link leaves a comment instead of opening the page — you are in Comment mode. Switch to Browse, navigate, then switch back.
- You cannot find where to leave general feedback — it is the Feedback tab in the sidebar, not a button in the bottom bar.
- “Comments disabled” — your team has turned collaboration off for this project. You can still view existing tasks.
- Your comment box will not submit — empty comments cannot be posted.
- A warning about a missing attachment — your comment mentions a file you did not attach. Add it, or select submit again to post anyway.
- Your file was rejected — check the size, 15 MB per file, and that the type is supported.
- You lost a comment you were writing — a task is only saved once you post the first comment. Choose Keep Editing rather than Discard Task.
- The page will not load — usually the site’s own security settings. Report it to your team, or see Troubleshooting Websites That Aren’t Loading.
- You cannot see the approval control — page status is not enabled for client accounts by default. Ask your team.
- Claro flagged your comment and you cannot respond — this can happen when commenting as a guest. Sign in if you have an account, or ask your team to relay it.
- You are not getting any email updates — you are commenting as a guest rather than a signed-in user. Use Sign in if you have an account, or ask your team for a collaborator invitation.
Conclusion
Click the thing, say what you want to happen, and leave one point per comment. That is the whole method. The screenshot, the position, the device, and the page are all recorded for you, which means the effort you save on describing things can go into being clear about what you actually want.
Reviewing visually rather than by email is what removes the back-and-forth. Explore Reducing Feedback Cycles With Visual Collaboration
Tips & best practices
- Give your overall impression first, then comment on specific elements.
- One point per comment. Three requests in one comment reliably get one answer.
- Describe the outcome you want, not just what is wrong.
- Review in Mobile before you sign anything off.
- Annotate when a sentence is doing too much work — an arrow is faster to read.
- Attach the reference rather than describing it.
- Give feedback during the stage it relates to, not after it closes.
- Sign in rather than commenting as a guest on any project running longer than a week — that is what gets you notified of replies.
- Check for Pending Review tasks regularly — those are waiting on you.