Review an asset

Open work awaiting review

Open Review queue to see work shared with you. An asset remains in your awaiting list until you record a decision on its current version.

The review screen puts the creative work on the left and the review panel on the right. On a smaller screen, select Review to open the panel.

Before reviewing, check the asset title, project, status, and version in the header. Work only on the version marked Current. An older version displays a read-only banner and keeps the discussion from that earlier round.

The review panel is organized into tabs:

• Info shows project, reviewers, deadline, guest access, and related details.
• Comments contains internal threads and external guest notes.
• Checklist appears when a QA checklist is attached to the version.
• Decisions shows each reviewer’s current response and the decision history.

Use the viewer

• Decks and PDFs have page or slide thumbnails, page controls, and zoom controls.
• Images open on a single review canvas with zoom and annotation tools.
• Videos use normal playback controls and can attach feedback to a specific time.
• HTML emails can be previewed at desktop, tablet, and mobile widths. Scripts are blocked for safety, and links open in a new tab.
• Live pages can switch between desktop and mobile widths. If a site blocks the embedded preview, use Open page.

For a multi-page asset, use the thumbnail rail to move quickly between pages. The comment count on each thumbnail helps identify where discussion is concentrated. The toolbar can zoom from 50% to 200%, and page controls move backward or forward without leaving the review.

For an email or live page, inspect more than one width. Responsive layouts can hide problems that are not visible in a desktop-only review.

Leave feedback in context

Use Add a comment for general or page-level feedback. On a deck or PDF, the comment belongs to the page or slide currently open.

1. To point at a specific place, select Add pin, then select the artwork where the note belongs.
2. For a video, pause near the relevant moment and select Comment at [time].
3. Write clear, actionable feedback and select Post feedback.

Pins belong to a version: A pin records its position, page, viewport, and version. On a live page, match the recorded width and scroll position when revisiting it. Comments on an older version stay with that version.

A strong review comment identifies the issue, explains why it matters, and gives a useful next step. For example, “Increase the contrast on the pricing footnote so it remains readable on mobile” is more actionable than “This looks off.”

Use a general comment when the note applies to the whole asset. Use a pin or timestamp when location is important. Keeping the comment attached to the right context reduces back-and-forth for the creative team.

Reply, edit, and resolve

• Select Reply beneath an open thread to continue the conversation.
• You can edit or delete your own comments. Edited comments are marked; deleting removes the text but leaves a marker so the rest of the thread still makes sense.
• The thread author or a creative team member can resolve a thread. A resolved thread can be reopened if more discussion is needed.
• Use the comment filters to show open threads, resolved threads, or comments from external guests.

For decks and PDFs, the comments menu can show the current page or all pages. Selecting a numbered thread takes the viewer back to its recorded location. A resolved pin changes appearance but remains available as part of the review record.

Only edit a comment to correct or clarify your own words. Add a reply when the change is part of an ongoing discussion, because replies preserve the sequence of the conversation.

Complete checklist items

If the asset has a Checklist tab, review its required and optional items. Each item can be marked Pass, Fail, or N/A, with an optional note.

Required items must be Passed or marked N/A before the asset can reach Approved. A failed or unfinished required item does not prevent a reviewer from requesting changes; it prevents incomplete work from appearing finally approved.

For an HTML email or live page, the checklist may include a link check. Link results report the response or redirect detected for each URL. Treat the results as guidance rather than a guarantee: authenticated destinations and sites that block automated requests may need manual verification.

Record your decision

Comments are feedback, not approval. When you are finished reviewing, open the Decisions tab and explicitly choose Approve or Request changes.

1. Choose Approve if the current version is ready. Confirming records only your approval.
2. Choose Request changes if the work needs revision. Add a specific note explaining what must change, then confirm your decision.

One decision per reviewer: The asset becomes Approved only after every assigned reviewer approves the current version. One request for changes moves it to Changes requested. A comment by itself never changes the status.

Your newest decision is your current response, and earlier responses remain in decision history. If new information changes your view during the same round, record the updated decision so the current state is unambiguous.

Understand review status

• Draft: The creative team is preparing the asset. Reviewers cannot act on it yet.
• In review: The asset is shared and is waiting for one or more reviewer decisions.
• Changes requested: At least one reviewer requested a revision of the current version.
• Approved: Every assigned reviewer approved the current version.

Required guest sign-off and required checklist items also contribute to final approval when they are present. The Decisions and Info tabs show which people or requirements are still outstanding.

After you decide

You can continue reading and participating in comment threads after recording a decision on the current version. If the creative team uploads a new version, your earlier decision remains attached to the old version and the new version returns to your awaiting queue.

If you requested changes, use the next version’s comparison view to verify the revision. Marking an old comment as addressed is useful context, but you still need to record a new approval or change request on the current version.

For a complete view across both creative and reviewer responsibilities, see The review and approval process.