Skip to main content
GaliVue
GaliVue guides

A simple photo proofing workflow for photographers.

Proofing works best when each stage has one purpose: show review-ready previews, collect clear choices, then move the confirmed set into editing.

Published: 26 Aug 2026Updated: 26 Aug 2026
Quick summary

Prepare consistent previews, keep access private, make the client’s task obvious, separate browsing from final submission and preserve the resulting filenames for the editing handoff.

01

1. Prepare a review set

Remove obvious technical rejects and export previews that are fast to review. Keep the set understandable for the client and preserve filenames. Proofing is not the final edit; its purpose is to help the client make a decision without creating unnecessary file-transfer overhead.

02

2. Add protection and instructions

Use watermarking, selection limits and a private link when appropriate. More controls are not always better: only show the client what they need for the decision. A short welcome note and clear selection instructions usually matter more than extra interface complexity.

03

3. Let the client browse naturally

A proofing gallery should work well on common phones and computers. Make favourites easy to understand and keep the interface focused on images. Avoid requiring downloads or app installs just to make a selection.

04

4. Capture a confirmed selection

Separate temporary browsing from the final handoff. When the client submits, record the chosen images and their filenames. The photographer now has a stable starting point for editing instead of an evolving set of likes scattered across communications.

05

5. Continue the same project into finals

The proofing stage should not become a dead end. Carry the selection into editing, upload the finished files and deliver them privately. Keeping the whole history attached to one project makes later questions easier to answer.

!

What to avoid

  • Uploading every frame without any review
  • Showing the client too many unrelated controls
  • Making the client install an app for a simple selection
  • Treating favourites as final without an explicit submit step
  • Losing the selected filename list after proofing

What to do next

After proofing is confirmed, use filename continuity to identify the originals, complete the edits and deliver only the finished files.

Related GaliVue product pages

Related GaliVue product pages

Put the workflow into practice.

Use GaliVue’s Free Test to run one real project from preview sharing through client selection and final delivery.

See plans & start free