How Jewelry Teams Review and Approve Designs Without Endless Email Chains

If you've worked in a jewelry design team for more than a month, you know the email thread. It starts with someone sending a JPEG. Then there's a reply with a PDF that has comments pasted as text. Then someone opens that PDF in a different app and the annotations are in the wrong place. Then a new version gets sent to the wrong person. Somewhere around email 14, nobody's sure which version is current.

This is not a niche problem. It's how most jewelry design reviews still happen in 2026.

The jewelry design review workflow hasn't changed much because, until recently, there wasn't a better option built specifically for jewelry. General-purpose tools like Figma or Notion don't know what a stone setting is. Slack is where feedback goes to die. Email is worse.

Here's what a structured annotation-based review looks like in practice.

Drawing Directly on the Design

In Annotate mode, reviewers can draw freehand directly on a design image — circling the prong they want changed, tracing the area where the band width needs adjustment, marking the specific stone that's reading wrong.

You're not writing "the prong on the lower left looks too thick." You're drawing an arrow pointing at it, so there's no ambiguity about what "lower left" means in this particular image.

The pen tool has color options and adjustable size and opacity, which turns out to be more useful than it sounds. Red for critical issues, orange for suggestions, green for approved elements — teams develop their own shorthand quickly. If you make a mark and immediately regret it, Cmd+Z undoes the last stroke without clearing the whole drawing.

Attaching Context to Each Annotation

Each drawn annotation can have a text comment attached and can be assigned to a specific team member. So the drawing and the instruction are connected in one object.

The person assigned to the annotation gets a push notification. Not an email that might get buried — a notification directly linking to the annotated image so they can see exactly what needs to happen.

When the designer addresses the feedback, they mark the annotation as resolved. The reviewer can reopen it if the fix wasn't right. This resolved/unresolved state is a small thing that makes a big difference: you always know what's been actioned and what's still open, without counting email replies.

Threaded Replies Keep Context Together

Any annotation can receive reply comments, forming a nested thread. If a reviewer marks a prong for revision and the designer has a question about it, that question and its answer live in the annotation thread — not in a separate Slack conversation that future team members can't find.

The annotation history shows author names and relative timestamps, so you can reconstruct who said what and when without any effort.

Client Reviews Without Adding Them to Your Account

External clients don't need a Studio account to participate in the review. Share a project via an external token link — they get a URL, they open it, they can view all annotations and add their own.

This is useful for the typical scenario: designer creates variations, shares link with client, client marks up a couple of images with their feedback, designer gets notified, goes back and makes revisions. No account setup required, no PDF sent back and forth, no lost feedback.

Annotation deep links make this even cleaner. Every annotation has its own shareable URL that navigates directly to the correct project, variation, and annotation thread. If you want to reference a specific piece of feedback in a Slack message or email, you paste the deep link and the recipient lands exactly there.

Per-Variation Threads Stay Organized

Annotations are scoped to individual design variations, not to the whole project. If a project has 8 design variations, the annotation panel for variation 3 shows only the threads on variation 3.

This sounds obvious but it matters for multi-option presentations. When a client is reviewing five ring directions simultaneously, their feedback on each one stays separate and doesn't bleed together.

Connecting Feedback to Tasks

When an annotation requires a significant design revision, it can be linked to a task in your Studio workspace. The design team sees it in their task board alongside everything else they're working on. It gets a due date, a priority, a status.

The annotation isn't just a comment that might get missed — it's a tracked work item with an assignee and a deadline.

What This Replaces

The jewelry design review workflow described above replaces the following: emailed JPEGs, PDFs with text comments, shared Google Docs with screenshots, WhatsApp image threads with reaction emojis as feedback, and in-person sessions that have to be reconstructed from memory.

Everything is in one place. Every comment has an author and a timestamp. Every resolved issue has a record. External clients can participate without the friction of account setup.

For teams doing regular design reviews, this is the shift that changes how much time review cycles actually take.

Start a free account at studio.diatech.ai to see it in action.