Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.shootbin.com/llms.txt

Use this file to discover all available pages before exploring further.

When a shoot is ready for client eyes, Shootbin’s review workflow keeps both sides in sync. You send the project, your client annotates and responds, you revise and send again — and the cycle repeats until everything is approved. Every step triggers email and in-app notifications so nothing falls through the cracks.

How the review loop works

The proofing cycle follows a clear back-and-forth pattern between you and your client:
  1. You upload photos and organize them into albums inside a project.
  2. You send the project for review — your client receives a notification and can start leaving feedback.
  3. Your client annotates photos, approves or rejects selects, and either sends the project back to you or marks it complete.
  4. If they send it back, you make revisions, upload updated photos, and request review again.
  5. The loop repeats until your client marks the project complete.
Clients cannot take review actions (send back or mark complete) until you have explicitly sent the project for review using “Request Review”.

Photographer actions

1

Request Review

Open your project and click Request Review. This publishes the current state of the project to your client and sends them an email notification plus an in-app alert. The project is now out for review.
2

Revoke Review

If you need to pull the project back before your client responds — for example, to swap out a photo — click Revoke Review. This closes the active review round and returns the project to draft state. Your client receives a notification that the review has been temporarily closed.
3

Make revisions and re-send

After your client sends the project back with feedback, upload revised photos and address any open annotations. When you’re ready, click Request Review again to start the next round.

Client actions

Once a project is out for review, your client has two ways to respond:

Send Back For Edits

The client has feedback that needs attention. The project is returned to you with any annotations and approval decisions already in place. You receive an email and in-app notification.

Mark Complete

The client is happy with everything. The project is marked as complete. You receive a notification confirming the sign-off.

Review rounds

Each time you click Request Review and your client responds, that counts as one review round.
On Pro and Agency plans you can set a maximum number of review rounds per project. Once the limit is reached, the client can no longer send the project back — they can only mark it complete.To configure the limit, go to your project’s Settings page and find the Max Review Rounds section. Choose a preset from the dropdown or leave it at “No limit”.Review round presets let you save commonly used round counts as named presets in your account’s Studio settings, then apply them to any project with a single click — no re-entering numbers each time.
Use review round limits to set clear expectations with clients upfront. Include the round count in your contract so both parties know how many revision cycles are included.

Notifications

Both you and your client are notified at every transition point:
EventWho is notified
You click Request ReviewClient receives email + in-app notification
You click Revoke ReviewClient receives email + in-app notification
Client clicks Send Back For EditsYou receive email + in-app notification
Client clicks Mark CompleteYou receive email + in-app notification
In-app notifications appear in the notification bell in the sidebar. Unread notifications show a red badge.