Internal review, proofing & delivery

This is the heart of the org workflow: photos come in, your team decides what's good enough to show, the client picks their favourites, and you hand over a finished gallery — each step gated so nothing reaches the client before it's ready. Web

Internal review (team approval)

On the event's edit page, turn on Internal review — "Manager approves or rejects photos before the client sees anything." The event then gains a Review phase.

During review, your team works through the incoming shots and, per photo:

• Approve — it gets a ✓ Approved badge and can move on to the client.
• Reject — it gets a ✗ Rejected badge and is held back.
• Undo — reset a photo back to pending.

Only approved photos flow into the client-facing proofing gallery. This is the quality gate a solo photographer does by eye; for a team it's an explicit, auditable step.

Retouching notes

While reviewing, anyone can leave a Retouching note on a photo — a short instruction back to the editor ("crop tighter", "fix white balance"). The notes travel with the photo so whoever does the edit sees exactly what was asked.

Client proofing

With Client proofing on, the client opens the gallery and hearts their favourites, exactly as in the solo flow (see Proofing & client delivery for the guest experience and the ZIP/CSV export of selects). The difference in an org event: when internal review is on, the client only ever sees the approved set.

Confirm delivery

When the edits are done and uploaded (the Final upload phase if you use Finals delivery), click Confirm delivery. This:

• marks the event Delivered, and
• emails the linked client a "Your photos are ready" message with a link to the finished gallery.

Until you confirm, the client never sees an unfinished set — the gallery respects the event phase (see Projects & event phases).

Next: Reports & analytics.