Production capacity is the amount of defined work a studio can complete with its available people, equipment, space, and time under stated conditions.
There is no universal:
- SKUs per day
- Images per hour
- Studio utilization target
- Schedule buffer
A simple packshot, reflective product, styled set, apparel job, model shoot, composite, and channel package are not equivalent units.
Build the capacity model from the studio's own completed work.
Decide what `complete` means
A capacity number is meaningless until the endpoint is defined.
Possible endpoints include:
- Capture completed
- Selected captures handed to retouching
- Proof set ready
- Internal QC passed
- Client decision received
- Final files released
Use the endpoint the schedule needs.
Do not call a capture-day count final-delivery capacity.
Choose a useful work unit
Possible units include:
- Required shot row
- Product-view combination
- Setup
- Product set
- Release batch
- Retouched file
- Final delivered output
A raw SKU count can hide several views, variants, setup changes, styling, model work, post-production, and destination outputs.
The corrected shot-list row is often a better planning input than a product count alone.
Define the work class from observed differences
A studio can create its own classes.
Possible factors include:
- Fixed or changing setup
- Product handling
- Styling
- Reflective or transparent material
- Apparel or model work
- Number of required outputs
- Composite or focus-stack work
- Retouching treatment
- Color sensitivity
- Destination package
- Internal QC method
Do not copy generic classes from another studio and treat them as a benchmark.
Use a small number of classes that explain the studio's actual work.
Separate active work from elapsed wait
Record at least three time types.
Active work
Time a person or resource is working on the unit.
Setup or changeover
Time required to prepare or reset the set, equipment, product, software, or handoff.
External or blocked elapsed time
Time waiting for product arrival, client decision, missing reference, approval, payment, an external retoucher, the upload owner, or another dependency.
Blocked elapsed time affects delivery timing.
It is not automatically productive capacity consumed by the same person.
Measure a representative history
Use several completed jobs that match the current work class.
Record:
- Job
- Class
- Products
- Required shot rows
- Setup count
- Active capture time
- Active post-production time
- Internal QC time
- Rework or correction time
- Blocked time
- People and equipment used
- Completed endpoint
- Known exception
Do not publish one anecdotal job as a studio benchmark.
Do not hide a job because it was slow.
The variation is part of the model.
Use ranges rather than false precision
For each class, record:
- Observed low
- Observed typical band
- Observed high
- Sample count
- Conditions
- Known outlier
A median or percentile can be useful when the sample is large enough.
A small studio can begin with a simple observed range.
Do not display two decimal places when the source is a rough time log.
Build the estimate from components
One planning model can be:
- Estimated active work
- =
- setup and changeover work
- +
- capture work for required shot rows
- +
- post-production work
- +
- internal QC work
- +
- the studio's chosen exception allowance
Then add external dependencies separately:
- Client review window
- Shipping or sample dependency
- External retouching
- Payment or release condition
- Destination upload
Do not combine all elapsed time into one throughput rate.
Use the current mix, not the average client
A proposed job should identify:
- Work class
- Required shot rows
- Setup groups
- Products not ready
- External collaborators
- Color-critical or composite work
- Current destination outputs
- Review method
- Delivery endpoint
Apply the relevant observed range.
Do not multiply a generic average by the total SKU count.
Capacity is constrained by the narrowest current stage
A job can have enough camera time and insufficient styling, product prep, retouching, internal QC, client review, or export capacity.
Record the current stage constraint.
Do not assume that adding a photographer increases final-delivery capacity.
Keep client response time outside staff utilization
Client review affects the calendar.
It should not be counted as active studio work.
Record:
- Proof ready
- Client review requested
- Client decision received
- Studio revision starts
Use the agreement or current job plan for review timing.
Do not publish one universal client-response deadline.
Account for unavailable or unready products
A product that is missing, damaged, mislabeled, still in transit, not approved, or waiting for a replacement can block its rows.
Record the blocked rows separately.
Do not treat them as normal throughput failure.
Make a schedule decision
The studio can choose:
When the decision is to add a second shooter or freelance help, those new hands still need named ownership on the job — product photography team roles is the map for which handoffs stay assigned after capacity help arrives.
- Accept within current capacity
- Accept with a changed date
- Split the job
- Change the required output
- Use another approved resource
- Decline
The capacity model informs the decision.
It does not make the commercial decision automatically.
"Use another approved resource" can mean a freelancer working inside the studio's own process, or it can mean sending a slice of the job to a partner studio — a different decision with its own rules for the style guide, sample custody, client disclosure, and QC.
Copyable capacity worksheet
- CAPACITY MODEL
- Period reviewed:
- Reviewer:
- Work class:
- Completion endpoint:
- Sample count:
- OBSERVED JOBS
- Job:
- Required shot rows:
- Setup groups:
- Active capture time:
- Active post-production time:
- Internal QC time:
- Correction time:
- Blocked elapsed time:
- People:
- Equipment or set:
- Known exception:
- CLASS RANGE
- Observed low:
- Observed typical band:
- Observed high:
- Conditions:
- Outliers:
- PROPOSED JOB
- Products:
- Required shot rows:
- Setup groups:
- Work class mix:
- Source readiness:
- External collaborators:
- Destination outputs:
- Review method:
- Delivery endpoint:
- ESTIMATE
- Setup and changeover:
- Capture:
- Post-production:
- Internal QC:
- Studio-chosen exception allowance:
- External dependencies:
- Current constraint:
- Proposed date:
- Decision:
Review the model after the job
Compare:
- Planned work
- Actual active work
- Actual blocked time
- Actual completed output
- New requirement
- Changed setup
- Correction
- Known outlier
Update the class only when the new data is relevant.
Do not change the benchmark solely to make an earlier estimate appear correct.
How this fits in Lenso
Lenso can provide the current job brief, product rows, shot rows, proof and decision history, final files, and delivery context.
Those records can supply inputs to the studio's separate capacity model.
Lenso does not currently calculate throughput, allocate crews, schedule sets, forecast production, or promise a delivery date.
Use a spreadsheet, scheduling product, project-management tool, or another current system for capacity planning.
Questions
How many products can a studio shoot in a day?
There is no universal number. Define the output, setup, class, and completion stage, then use the studio's own history.
Should capacity be measured in SKUs?
A SKU count can be one input. Required shot rows and setup groups often explain the work more clearly.
Should client review time be included?
Include it in delivery planning, but keep it separate from active staff capacity.
How much buffer should a studio keep?
Choose a studio-specific allowance from observed variation and risk.
Does Lenso calculate capacity?
No.