Claron
Review rounds

Client sign-off, tied to the exact version

Reviewers look at selected pages in their own time and record a decision against a chosen version.

Use a review round for sign-off without scheduling a shared session. Each reviewer approves or requests changes, and the round keeps every decision, reason and timestamp.

How a review round works

Pick the pages and the environment and version to review, then invite reviewers.

  • Each reviewer approves or requests changes, and explains what needs to change.
  • The manager sees each reviewer's decision, reason and timestamp.
  • The round completes when every active reviewer approves, or when the manager closes it.
  • Revoke a reviewer's access at any time.

Verify the fix on the fixed build

When a fix is ready, assign a verifier and choose the build or deployment that contains it. The verifier repeats the steps there and approves, or rejects with the failing step. The decision is recorded against that version.

Verification stays separate from applying a patch, changing a status or merging a pull request, so a resolved status never stands in for a human check.

Push the fix. Claron rebuilds.

Push to your project's branch and Claron rebuilds its review build by itself, then tells whoever reported the bug that the fix is live to check.

Try it in the product's own interface

Create a review round

INTERACTIVE EXAMPLE

Try the draft → invite → decision workflow.

StorefrontCreate a review round
Sandbox

New review round

Choose the version, pages, and people for this review.

Build · 7c9e4a1

Round activity

See how a draft and reviewer decisions are recorded.

1

Draft

2

Review

3

Finish

Checkout redesign

staging · 7c9e4a1

draft
/cart/checkout
Reviewer decisions0 / 2

Review the cart and checkout on mobile. Confirm the total before submitting.

A
Alex, alex@example.com
Pending
S
Sam, sam@example.com
Pending

Questions about review rounds and sign-off

Straight answers, including the limits.

Set it up

More of Claron

Weighing up other tools?

See how Claron compares with Marker.io, BugHerd and Sentry across the whole workflow.

Compare Claron