FEZA innovation – Home
← All products

A delivery workflow for your photography studio

Wedding and Event Photography

Photography Studio Software

Review photographs awaiting selection, editing tasks and album approvals in one job file after the shoot. We will define the photography software we will build from your studio's shoot calendar and delivery stages.

  • Shoot teams linked to the calendar
  • Selection scoped for each client
  • Separate album and video stages
Camera, prints and an album beside a tablet displaying a photo selection
  1. Discovery
  2. Scope and quote
  3. Development

The end of a wedding shoot starts a new set of delivery tasks

Finding a weekend shoot team differs from managing weekday retouching. When couples yet to select images, albums awaiting design approval and prints still at the printer share one waiting list, responsibility can become unclear. You need to distinguish each job's stage and who must provide the next information. The software we will build will link shoot jobs, client selections and delivery stages. Recording backup status and recording an album handed to the client will be scoped as different checkpoints. Packages and payments can also link to the job.

Scattered studio tracking

  • Jobs awaiting selection and jobs awaiting retouching stay in the same note.
  • It can be unclear which album design was sent to print.

The proposed delivery design

  • Outstanding work and responsibility will be considered for each delivery stage.
  • Selected images and design approval will link to the shoot file.

An example job from wedding shoot file to album delivery

Consider a couple buying a photo and video package. Although the shoot happens on one day, photo selection and video editing may progress at different times. Explain your stages so we can choose where both tracks share information. Closing the shoot calendar entry will not mean closing delivery work. Sending chosen images to the editor, preparing the design for print and checking payments will each have their own decision points.

  1. 01

    Allocate the shoot team

    Photographer, videographer and assistant availability will be matched to shoot times. The assigned team can receive the address and schedule for the day.

  2. 02

    Move selections into editing

    A private client selection gallery can be scoped after backup status. We will define how selected images enter the retouching list using your studio's method.

  3. 03

    Track design and delivery

    Album design approval, dispatch to print and return from the printer can be separate stages. A video editing and approval track can also be designed within the job.

Scope the shoot calendar, selection gallery and printing workflow

For a solo photographer, a shoot calendar and delivery list may be the first priorities. A studio with several editors should also discuss task allocation and workload based on entered durations. We will determine the stages needed initially. Selection copies and archive files have different data requirements. Gallery copy formats, package links and client access will be defined separately. External storage for high-resolution delivery will be considered subject to provider conditions.

  1. Core studio job tracking

    Shoot and delivery lists
    We will select how packages, team assignments, shoot details and delivery stages relate in the first release.
    Image selection area
    Low-resolution watermarked copies, client selections and a selection period can enter the initial scope according to need.
  2. When the studio grows

    Editors and video workflows
    Retouching workloads based on image or job durations, video editing stages and separate responsibilities will be discussed as additional scope.
  3. Work requiring external access

    Files and stage notifications
    If your storage or messaging provider offers a connection, technical access and data fields to be transferred will be reviewed.

Different approval points for album design and wedding video editing

Photographs and video may belong to the same client, but approvals differ. Image selection and page layout matter for albums; editing, colour grading and music approval may matter for video. Describe package deliverables so we can plan waiting stages separately. Print delays should not close the video's delivery state. Workload calculations can be scoped from editor-entered durations; these are planning inputs, not delivery commitments.

Client decisions

Photo delivery workflow
Image selection and album layout approval are considered.
Video delivery workflow
Required editing and music approval steps are selected.

Production tasks

Photo delivery workflow
Retouching, page design and print tracking will be scoped.
Video delivery workflow
Editing and colour grading tasks will be defined separately.

Outstanding delivery

Photo delivery workflow
Printer returns and album delivery records can be assessed.
Video delivery workflow
Video file sharing and delivery approval can be tracked separately.

Design separate access for the couple's gallery and the editor's tasks

We will choose access to images and contact details around shoot, editing and office tasks. In the software we will build, limiting client selection links to their own job, showing editors their assignments and giving the office payment access are separate scope items. Guests may also appear in images, so sharing, retention and removal requests will be assessed under KVKK, Turkey's personal data protection law. Describe your archive routine so we can distinguish gallery use from raw-file archiving.

Shoot team information

Addresses, times and package requirements will be selected for the task. Access to other clients' galleries will not accompany this responsibility.

Editor workspace

Visibility of assigned retouching or editing files and notes will be planned. Permissions to change design versions and record approval can be separated.

Client and office boundaries

Private gallery links, sharing limits and retention needs will be assessed in the project. Your studio is the data controller for image and contact data.

A delivery revision after the wedding album has been approved

Replacing an image in an album prepared for print differs from a request during draft design. Linking design versions, client approval and the work sent to print can scope this distinction. You decide when a revision creates a new task and who authorises printing. Video corrections can remain outstanding independently of album decisions. Keeping earlier approval while reviewing a new request helps identify the version an editor should work on. Additional work's effect on packages and payments will be discussed under your studio's terms.

Uncertainty after approval

  • A new image request arrives while the editor follows the earlier approval.
  • The printed album and revised draft are shared under the same name.

Records selected for revisions

  • Approved versions and new change requests can be separated.
  • A return-to-print decision can link to an additional editor task.

Match archive locations and delivery stages for earlier shoots

Importing only client names does not explain an outstanding album. Shoot dates, packages, latest completed stages and archive locations need to be understood together. We will identify missing stages from anonymised job lists. Uploading raw files and importing records of where files are stored are different scope options. Share your archive structure so we can separately choose checks for gallery copies and outstanding deliveries.

  1. 01

    Separate outstanding deliveries

    Jobs already shot but awaiting selection or printing can be classified. The latest stage of each job will be planned for verification against sample records.

  2. 02

    Map archive locations

    Disk and folder definitions will be assessed against job files. Missing locations and repeated job names will be reviewed before import.

  3. 03

    Review file connections

    External storage access conditions will be discussed if your provider permits connections. Copy formats and failed-transfer checks will be scoped separately.

Explore studio tasks through web development and automation examples

A selection gallery needs scope for client communication; editor lists need scope for production work. The service and project pages below can help discuss how users hand over the same job. We will work from your own photo archive and album stages. Marking waiting points in a sample job makes the scope discussion concrete.

Define delivery scope using a sample package and album stages

Start with your blank shoot form, package contents and stage list. Explain how image selections and design approvals are obtained, and who takes over video work. For the software we will build, we will prioritise the delivery type with most waiting work. Archive records, galleries and external file connections will be separate scope elements.

  • List photo and video delivery steps separately.
  • Identify revision decisions and print approval permissions.
  • Prepare a sample job record without personal images.

The development proposal will follow selected delivery workflows and technical dependencies. Subscription arrangements and support boundaries will be discussed in writing.

How we work

We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.

  1. 01

    Discovery

    We listen to how your business works, your team and the tools you use today.

  2. 02

    Scope and quote

    Modules, priorities and price are set out in a written quote.

  3. 03

    Development

    We show working versions at short intervals and move on with your feedback.

  4. 04

    Setup and migration

    We move your existing records across and help your team get started.

  5. 05

    Support

    We run the software on a subscription and keep it up to date and secure.

Frequently asked questions

What happens if the couple don't make their selection on time?

Automatic reminders, recorded on the job, can be part of the scope. If your contract sets a selection period, the software can also be designed to tell the couple, once it has passed, that the delivery date has moved, which helps prevent disputes later.

Do we have to upload every photo in full resolution?

No. Low-resolution, watermarked copies are enough for a proofing gallery. Your raw files can stay in your own archive, with the drive each job sits on recorded in the job. A cloud storage connection for full-resolution delivery can be scoped separately.

We have a video team too. Can video delivery be tracked?

Video can be designed as its own delivery pipeline, with stages such as editing, colour grading and music approval. Photography and video sit under the same job but move through separate flows.

Can retouching workload be planned realistically?

A plan is only as realistic as the time entered. You enter the time per frame based on your editor's real pace, and the weekly workload is calculated from it. If the time is set shorter than reality, the plan will mislead you.

How is album printing tracked?

The design sent to print, the print lab and the expected return date can be recorded. An album that has not come back stays open on the list, which makes forgotten albums easy to spot in a busy season.

Can a change after album approval become a separate task?

New image or layout requests can be scoped as revisions separate from the approved design. Print status and the decision-making role will be considered together; the working version will follow your studio's workflow.

Can the album remain open after the video has been delivered?

Photo and video workflows can be assessed with separate completion states. After video delivery, album selection, design or printing may remain open. We will define package completion criteria around your studio's delivery method.

How is the price set?

After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.

Do we receive the source code?

In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.

Who is responsible for what is done with the software?

We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.

Related products

Let's review outstanding work from shoot to delivery

Share your studio's stages so we can scope gallery, editing and printing priorities.

  • Shoot teams linked to the calendar
  • Selection scoped for each client
  • Separate album and video stages