Proofing

Proofing

Share the album for review before final export.

Proofing is where the album stops being an internal project and starts being a shared conversation.

It sits between internal preview and final export, and it exists so changes can be requested before the print-ready output is generated.

Proofing Workflow Demo

Switch between a few real proofing moments and see how the page changes as client review moves forward.

/ status

Client reviewing

1 active link

/ views

19

Total client views

/ comments

3

Open comments

/ spreads

26

Total spreads in review

Share link manager

ActiveClient proof link

This is the live review link. It is where views, rounds, and comment traffic start to matter.

Older links do not disappear. They move into the inactive stack so the proofing history stays readable.

Pending feedback

Spread 7

Could we swap the first kiss photo here?

Spread 12

Love this one. Just brighten the right page a touch.

Activity snapshot

Views, rounds, comments, and replies belong together. Proofing is not just one link. It is the whole conversation around that link.

The live proofing page pulls together status, share links, comment summaries, and activity into one review surface.

What This Surface Holds

The proofing page is more than a link generator.

  • The header keeps the album and review context clear.
  • The status row tells you whether the round is alive, quiet, or settled.
  • The share-link manager handles active and inactive links.
  • The comments area keeps pending feedback visible without forcing you into the full client view.
  • The activity feed helps you understand what actually happened, not what you assume happened.

What Good Proofing Looks Like

Good proofing is not “send link and hope for the best.”

  • Run a proper preview pass first.
  • Create the right share link for the right client round.
  • Watch open comments instead of chasing feedback across email threads.
  • Go back to the editor when changes are real.
  • Export only after the round is settled.

What Clients Can Do in the Review

The client view is built so feedback is visual and reversible, not a wall of text.

  • See the spread story. Every spread keeps its full history, from the original layout to each change. A client opens the spread story to compare what they asked for against what they started with, side by side.
  • Request a change on a photo. Remove it, replace it, swap two photos, or just leave a note. Each request shows up on your side with the proposed layout so you see exactly what they mean.
  • Take it back. If a client asks for something by mistake, they can cancel that single request while it is still open. They can also discard every change they made on a spread and get the page back to how you last had it.
  • Talk it through. Every note and request carries a discussion thread, so a question gets answered right there instead of in a separate email.

Once you apply a change, it is committed to the album and the client can no longer undo it from the review. That boundary keeps the history honest for everyone.

On this page