How do I share a dashboard design with a client for review?

The most reliable approach is a shareable link they open in a browser and click to leave notes on the charts — no Figma account, no downloaded file. Alternatives: a Figma view-and-comment link (requires an account), or a PNG/PDF emailed to them (works, but feedback arrives unanchored to any specific element).

How do I get specific feedback on a dashboard instead of vague notes?

The tool determines the specificity. Email produces "the chart on the right feels off." A pinned comment produces "revenue bar — change color to brand blue." Element-anchored review tools force specificity by requiring the reviewer to click the exact element before typing — they physically have to point at it.

Can a client comment on a dashboard design without a Figma account?

Not natively — Figma requires an account to comment. The workaround is exporting the frames and sharing via a review tool with guest commenting. The client opens a link, clicks the chart they mean, and the note lands pinned there — no Figma, no account.

What questions should I ask when presenting a dashboard design for feedback?

Three that produce usable answers: "Can you find the metric you'd check first on a Monday?" (tests hierarchy), "Is there a number you'd want broken down further?" (tests completeness), and "Is anything missing you'd need to make a decision?" (tests gaps). These are harder to answer vaguely than "What do you think?"

How do I get feedback on a Tableau or Looker dashboard design?

Neither has native comment-on-element features for external reviewers. Screenshot the dashboard at its most representative state, export as PNG or PDF, and share it via a review link. The reviewer clicks the panel they mean — no Tableau or Looker account required.

How do I manage multiple rounds of feedback on the same dashboard design?

The main risk is version confusion — client leaves feedback on v2 while you're on v3. Keep all rounds on one link by pushing updates in place so comments accumulate in one thread. If you go the file route, name exports clearly (dashboard-v2-2026-06-20.pdf) so the client knows which version they're commenting on.

drafty

How to get feedback on a dashboard design

Quick answer

To get feedback on a dashboard design, share the Figma file with comment permissions, export frames as PNG or PDF and email them, paste the live URL into an annotation tool, or share a link your client opens in a browser and clicks to pin notes on the charts. The last option is the only one that doesn't require an account, an extension, or decoding "the chart on the right."

Step 1

Share the Figma file with comment permissions

Open the file, click Share, set the link to "can comment," and send. Anyone with the link enters comment mode (press C), clicks a chart or panel, and pins a note — threaded, anchored to the exact frame element, resolvable from the sidebar. The catch: commenting requires a Figma account. The common complaint from Figma's own forums is that non-designer stakeholders — finance leads, sales reps, account managers — won't make one. If your client is a designer or a tech-comfortable PM, this is the cleanest path. Otherwise, expect a support call before they've left a note.

Step 2

Export frames as PNG or PDF and send the file

Select the frames, open the Design panel, scroll to Export, choose PNG or PDF, and click Export. Email the file or drop it in a shared folder — no Figma account required. The feedback loop is where this breaks: clients paste red circles over the chart in Keynote, or type a vague bulleted list in a reply. You get three things anchored to nothing. For one round on a single frame it's manageable. Dashboard designs rarely get one round — they get four, and version confusion compounds fast when every email has a different PNG.

Step 3

Paste the live URL into a browser annotation tool

If the dashboard lives at a real URL — a Looker embed, a Tableau Public link, a Retool app, a v0-generated data page — paste it into a browser-based annotation tool. The reviewer clicks any chart element on the live page and pins a note to the actual DOM state, not a frozen screenshot. This matters for interactive dashboards: a note on a date-range dropdown that says "default to current month" lands on the dropdown, not on wherever it sat in a screenshot taken with a different filter. Practical catch: most tools here (BugHerd, Marker.io) require a browser extension or a script tag on the page — neither works behind a VPN or on the client's phone.

Step 4

Share a link your client marks up with no account

Export the dashboard as PNG or PDF, drop it into a review tool that supports guest commenting, and share the link. Your client opens a URL in their browser, clicks the chart or panel they mean, and pins a note there — no Figma account, no extension, no file to download. This is where most freelance designers and data consultants end up after running the other three methods. The note lands anchored: "revenue bar — change the color to brand blue" arrives on the revenue bar, not buried in an email paragraph. Every revision round lives on the same URL, so you and the client always know which version the feedback refers to.

The faster way

If you're exporting the dashboard just to share it, skip the email step. Drop the PNG, PDF, or live URL into Drafty and share the link. Your client clicks the exact chart they mean — the revenue panel, the filter bar, the KPI tile — and pins a note right there. No Figma account, no extension. Every comment is anchored and threaded. When you push a new version, it lives on the same URL — no confusion about which file is current.

Open a live demo

Questions

How do I share a dashboard design with a client for review?: The most reliable approach is a shareable link they open in a browser and click to leave notes on the charts — no Figma account, no downloaded file. Alternatives: a Figma view-and-comment link (requires an account), or a PNG/PDF emailed to them (works, but feedback arrives unanchored to any specific element).
How do I get specific feedback on a dashboard instead of vague notes?: The tool determines the specificity. Email produces "the chart on the right feels off." A pinned comment produces "revenue bar — change color to brand blue." Element-anchored review tools force specificity by requiring the reviewer to click the exact element before typing — they physically have to point at it.
Can a client comment on a dashboard design without a Figma account?: Not natively — Figma requires an account to comment. The workaround is exporting the frames and sharing via a review tool with guest commenting. The client opens a link, clicks the chart they mean, and the note lands pinned there — no Figma, no account.
What questions should I ask when presenting a dashboard design for feedback?: Three that produce usable answers: "Can you find the metric you'd check first on a Monday?" (tests hierarchy), "Is there a number you'd want broken down further?" (tests completeness), and "Is anything missing you'd need to make a decision?" (tests gaps). These are harder to answer vaguely than "What do you think?"
How do I get feedback on a Tableau or Looker dashboard design?: Neither has native comment-on-element features for external reviewers. Screenshot the dashboard at its most representative state, export as PNG or PDF, and share it via a review link. The reviewer clicks the panel they mean — no Tableau or Looker account required.
How do I manage multiple rounds of feedback on the same dashboard design?: The main risk is version confusion — client leaves feedback on v2 while you're on v3. Keep all rounds on one link by pushing updates in place so comments accumulate in one thread. If you go the file route, name exports clearly (dashboard-v2-2026-06-20.pdf) so the client knows which version they're commenting on.

Keep exploring

Annotate a dashboard Annotate a chart Design feedback tool Get feedback on a Figma design

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo