Proofing

Website proofing tool

Proof a website the way you proof a print job, on the real thing. Clients mark up the live site from one link, each review round stays separate, and you can see what is still open before you ask for sign-off.

01

Proof the working site, not a screenshot.

Reviewers proof the working website, with real content and real interactions, and mark up exactly the element that needs to change.

02

Keep each round separate.

Layers split a dock by build or release, so this week’s proofing round and last week’s feedback do not mix, and you share a link per layer.

03

See what is left before sign-off.

Every change has a status, from open through in review and changes requested to resolved, so the last round only covers what is still open.

04

Clients hear back without chasing.

A client who leaves an email gets one short update when the team replies to their comment or resolves it.

Keep reading

FAQs

Frequently asked questions

Short answers before you start.

What is website proofing?

Checking a website before launch the way a proof is checked before print: reviewers go through the pages, mark what needs to change, and the team works through the marks until the client signs off.

How do I get client sign-off on a website?

Run the review in rounds, resolve every comment from the round, then send the client the review link with a short sign-off message. The website review and approval process guide has one to copy.

Can I keep each proofing round separate?

Yes. Create a layer for each round or build. Its comments stay in that layer, and you can share a review link for one layer at a time.

Does the client need an account to proof the site?

No. They open the link, type a name and mark up the page. Nothing to install.