Keep the brief intact
A small studio may manage a few projects through familiar gallery and messaging tools. Once several people handle client requests and editing, each handoff needs the latest instructions and the original agreement.
Keep package agreements, image-level revision requests and delivery schedules connected across your studio team.
Keep the original scope available for every handoff.
Locate each revision by its image reference.
Keep client requests connected to the work.
Identify the next owner and remaining work.
A small studio may manage a few projects through familiar gallery and messaging tools. Once several people handle client requests and editing, each handoff needs the latest instructions and the original agreement.
A request left in a chat can miss the retoucher. An unclear package change can reopen a pricing discussion. A project marked simply “not delivered” does not explain whether the team is waiting for the client or still editing an image.
This solution focuses on studios with defined retouching packages, image-level revisions and regular handoffs between roles.
From request to action
A client asks for a more natural dress fold and less redness in the skin. The retoucher needs the image reference, the previous brief and the current approval status.
In sample project PJ-2603, image C-0305 carries the client note and revision feedback alongside the other image tasks. The team can distinguish the outstanding revision from images already confirmed.
The mechanism is practical: image references identify the work, feedback preserves the brief, and task status helps the manager plan the next handoff. Any reduction in repeated communication should be measured against the studio’s own baseline.
More natural dress folds; less red in the skin tone.
Choose an image to inspect its feedback and next action.
The operating model
| Operational question | Record to consult | Decision it supports |
|---|---|---|
| What did this package include? | Package snapshot and fee-confirmation version | Establish the agreed scope before adding work |
| Which image needs another change? | Image reference, client note and revision feedback | Brief the person handling that image |
| What has the client already approved? | Delivery version and image status | Separate accepted work from outstanding tasks |
| Who needs to act next? | Project stage, owner and agreed date | Follow up with the client or schedule production |
Rules that travel with the work
Package prices and included images can change over time. An active project still needs a reference to the agreement under which it was accepted.
The project detail displays a package snapshot with included retouches, additional-image pricing and a fee-confirmation version. This provides a starting point for discussing added work. Your approval rules for complimentary images, upgrades and specialist edits can be defined during scoping.
Ready for the next handoff
Waiting for selections, editing images and waiting for feedback call for different actions. The project register brings stage, owner, fee confirmation and revision progress together, while the photographer workspace groups outstanding work by delivery stage.
Define how workload is counted, how assignments change and how client waiting time affects internal dates before implementing scheduling rules.
A wider perspective
Pixel Perfect Photography
Workflow illustration based on the published case.
Pixieset serves photography delivery and client collaboration. In its public client guide, Pixel Perfect Photography explains favorites, PIN-based downloads and access to print purchases. The business mechanism extends the handover of files into a service experience where clients can choose, receive and purchase finished work. Pixel Perfect’s client guide
Pixieset links favorite lists with image comments, keeping instructions attached to their subject. Its free entry option and subscription tiers allow photography businesses to test the gallery experience and upgrade for capacity or features. Proofing documentation, pricing
For a studio evaluating software, this establishes a useful starting point: assess standard gallery capabilities first. Then check whether configuration or integrations can support your package approvals, retoucher assignments and existing business systems. The published client guide does not establish a financial return for your studio.
Choose the right approach
| Your situation | A sensible evaluation path |
|---|---|
| One person handles a small number of projects | Test an established gallery product first |
| The gallery works, but a few handoffs remain manual | Assess configuration, exports or a focused extension |
| Multiple roles need specific approval, revision and integration rules | Define the gaps and scope a tailored system |
Compare storage, project migration, training, maintenance and future changes alongside subscription or development costs. Use one representative project to test the fit before expanding the scope.
A practical first release
Bring one package, an anonymized delivery history and a typical revision. Establish three acceptance questions: can the team find the agreement, attach the request to the right image and identify the remaining work?
Wavesteam can use these examples to define roles and rules, design the workflow, and proceed through development, testing, acceptance and launch. Client selection, notifications, payments and file delivery can be assessed as separate integration requirements.
The demo illustrates management screens and business relationships. Production use requires account access, image storage and backup arrangements. Payments and notifications in the demo are simulated.
Start by assessing project links and image references. Deeper integration depends on the gallery’s interfaces, file naming and ongoing cost.
Define which active projects and historical records need to remain accessible. Confirm which image relationships, agreements and notes can be exported from the original tools.
Agree who approves the change, which work is retained and what creates a new task or charge. Use specific examples as acceptance criteria.
Establish the current reasons for rework and communication volume, then compare during a pilot. The system provides traceability; results depend on the workflow and adoption.
Related solutions
AI, capital-markets docs, OCR, vision, IoT and membership operations — composable for your industry.

Manage group-ticket entitlements, entrance checks and attendance reporting around the rules of your venue.

Connect exhibition listings, personal visit plans and editorial updates so audiences can plan a visit with the right information.

Help shoppers move from a room brief and budget to comparable furniture options, a 3D preview and a store appointment.
More natural dress folds; less red in the skin tone.