Build the proof set, open permitted downloads, release the gallery, and confirm the client can see it.
Dashboard
Welcome back, FinalFlo
Use the highlighted action to move this shoot forward through FinalFlo.
Client delivery handoff.
Build the proof set, open downloads, release the gallery, and confirm the client can view it.
Share package and gallery strip.
One clear decision before photos leave FinalFlo.
Warm Family style
Ready for AI review
Permission-based download
This panel shows the actual uploaded image before culling, editing, or delivery.
FinalFlo will show the real uploaded images here when previews are available.
Let's create something amazing today.
Capture. Cull. Create. Deliver. All in one powerful platform.
FinalFlo will show the next move after files enter the pipeline.
Upload files to complete Preview before AI Culling.
Upload, cull, finish, proof, deliver, then test the result.
Select a gallery photo to download proof, mark a favorite, or share through Flow Connect.
Photos waiting on review, touchup, or recovery.
QR-ready images in client proofing.
Client-approved images ready to archive or deliver.
People captured through Flow Connect.
Review proof-ready photos, build client output, release downloads, and export the manifest.
No client-ready file selected
Run Signature Finish or build client output to prepare gallery files.
Build the proofing set, capture client decisions, unlock downloads, and keep revision notes attached.
Client proofing board.
Give the client a clear place to favorite, approve, request revisions, and unlock downloads.
Save the client contact, unlock access, review requests, and open the portal handoff.
Current client
Keep the job deadline, reminders, and next schedule move visible before delivery.
Delivery calendar
Choose a deadline so FinalFlo can show urgency, reminders, and the next schedule move.
Send the invoice, collect payment, confirm release permission, and download the handoff packet.
Payment hold
Clear the business side before delivery.
Track proof score, evidence, revenue, forecast risk, and launch readiness for the current shoot.
Current shoot health
Run proof and simulation to see what FinalFlo can show today.
Save studio defaults, check storage, protect the catalog, and keep the current job recoverable.
FinalFlo workspace settings
These defaults keep the current shoot, storage path, and catalog protection easy to find.
Run this when the browser proof is ready to become an authenticated server workflow.
Build a handoff packet that maps this browser workspace into future shared database records.
Save the current shoot package, search saved sessions, reopen a client job, or continue the next workflow step.
Johnson Family / Family Preview
Save this client shoot so it stays easy to reopen, cull, proof, and deliver.
No photo selected yet.
Upload photos to start the FinalFlo path.
AI Studio Assistant
Next best action
Run AI Culling to sort the shoot into keeper, reject, recovery, and touchup folders.
FinalFlo will surface deadline, retouch, client, backup, and delivery holds here.
Start a shoot pipeline.
Select JPEG, RAW, TIFF, PSD, DNG, sidecars, or camera originals, then add the chosen files into the client pipeline.
Files move through the engine.
Camera files landing on the server.
Choose a shoot folder, camera card, or multiple photographer files to see the correct intake route.
Advanced Step Controls
Vault intake API waits until photographer files are selected.
Queue a RAW/source file to see the worker handoff.
Live server deployment health.
Decision folders before editing.
Run the cull, review the strongest signals, and send keepers toward Signature Finish.
Run AI Culling to see whether the selected photo should be kept, reviewed, rejected, recovered, or sent for touchup.
Apply the photographer's look.
Apply the FinalFlo look, clear style holds, and send proof-ready files into Flow Connect.
Capture the manual edit, save a reusable recipe, train the style, or create a retouch work order.
Touch up one image.
The preview responds to manual settings so the photographer stays in control after AI auto-fix.
Manual settings
Save the edit recipe, sync the photographer style, build export presets, and send the finished output toward Flow Connect.
Selected photo ready for edit handoff.
Save a recipe, sync style memory, then build the export package.
Client versions before delivery.
Save the photographer's edit recipe, build style memory, apply it across the shoot, and download the style profile.
Save the photographer's style.
When the image feels right, save the settings as a reusable editing profile for future shoots.
AI fixes first, manual control stays open.
Decide what AI can safely fix.
Teach FinalFlo the photographer's look.
Keep the whole shoot locked to the saved look.
Promote polished files before retouch slows them down.
Manual fixes before delivery.
Who owns the manual fixes.
Final check before QR Ready.
Move finished touchups back to proofing.
Assign the next owner across the studio.
Clean up and send one image fast.
Select a photo to see whether it can be processed now or needs RAW preview conversion first.
Proof of what left the studio.
Confirm the job is delivered, protected, and archive-ready.
Check the gallery before it leaves.
Create client-ready versions before Flow Connect.
Catch every hold before the client gets the link.
QR photo handoff.
Scan link: finalflo.app/f/johnson-preview
Valid email unlocks download.
Delivery stays connected.
Favorites, approvals, revision notes, and download readiness stay attached to the photo.
What the client sees after unlock.
Build and release the delivered package to preview what the client sees.
Client-facing status before the link is sent.
Release only when proofing is clean.
Follow-up messages for gallery delivery.
What clients ask for after proofing.
Sort client notes into the right lane.
Email, QR, and download activity.
What leaves the studio.
Protect the job before archive.
Find and restore stored sessions.
Deliverables for this session.
Clear the business side before delivery.
What happened in this job.
Let FinalFlo move the job forward.
One ordered lane for the next build and test actions.
What needs attention right now.
Business health for this job.
Keep the studio on schedule.
One-page job summary for the team.
Run the engine proof, simulate the full photo path, package demo evidence, and prepare the launch proof.