Fieldwork / Studio

Product walkthrough · Illustrative demo

From draft
to decision.

A review should end with a clear next step. Try a proofing flow that keeps the feedback, the revision, and the decision together.

Fictional release example · October 2, 2026

Autumn open studio / InvitationReviewer view
Version 1 · In review
Fieldwork Studio / Open house

An afternoon
at the studio.

Saturday, October 17 · 2–5 pm

The time is easy to find. The address is missing.

The three steps

1. Review version 1: the invitation is missing its address.

2. Leave feedback: the comment stays attached to version 1.

3. Compare version 2: the address is added. Review the new proof before marking it ready.

What changed in this fictional release

Feedback has a place to land.

Before

Feedback arrived in messages with no reliable link to the draft. “Looks good” could refer to an older file.

After

Comments name the version reviewed. A new revision opens alongside the feedback, and the final decision applies to that revision.

Where would this break down?

Who makes the final call?

Should one named reviewer mark a proof ready, or must every invited reviewer agree?

What reopens a decision?

Should any revision require another review, or only changes the author flags as significant?