Free printable resource
Product photography production checklist
Use this five-stage checklist to record the requirements, owners, client decisions, final-file checks, and delivery record for a product photo job.
Use it with Lenso or any other toolset. No account or email is required.
Adapt it to the client agreement, current channel requirements, and the way your studio works. This ecommerce content production checklist is a starting point for product photography jobs.
Use it at the handoffs, not only at kickoff.
Start when the job is accepted, then return to the relevant stage whenever scope, proofs, approval, or delivery changes.
A checked item means the information or decision is written somewhere the people doing the work can find it. The checklist does not need to be the system of record.
- Name an actual owner for each stage.
- Record where the current evidence lives.
- Reopen an item when the requirement or decision changes.
- For a solo studio, one person can own several stages, but the handoffs should still be explicit.
- Use the agreement with the client to define scope, fees, rights, acceptance, payment, retention, and dispute terms.
Answer for the current job, not the process you intend to have later.
Job details
- Job:
- Client:
- Studio stage owner:
- Client decision maker:
- Target delivery:
- Checklist date:
- Current job record:
Write the place where the latest brief, shot list, proof decisions, and delivery record can be found.
Five job handoffs
Request and scope
Create one written reference for what the client needs and what the studio has agreed to produce. Website requests, referrals, repeat-client jobs, agency introductions, and phone calls can all reach this same stage.
- Owner
- Studio owner, producer, or account lead. Record the client decision maker separately.
- When
- Before the studio accepts the final scope or begins production.
Complete when
The studio can explain what is in scope, what is outside the current scope, who can approve it, and which outputs are expected.
- Owner
- Studio owner, producer, or account lead. Record the client decision maker separately.
- When
- Before the studio accepts the final scope or begins production.
Production handoff
Make the current plan available to the people producing the work and record departures from it before they become hidden assumptions.
- Owner
- The person coordinating production, with the current decision owner identified.
- When
- Before work begins and whenever the agreed scope changes.
Complete when
The people doing the work can identify the current requirements, and the studio can trace any departure from them.
- Owner
- The person coordinating production, with the current decision owner identified.
- When
- Before work begins and whenever the agreed scope changes.
Client review and decisions
Keep feedback attached to the correct asset or set and make the next decision explicit.
- Owner
- The studio review coordinator. The recorded client decision maker approves or requests changes.
- When
- Each time a proof or new version is shared.
Complete when
Each required asset or set has a recorded decision, and everyone can tell which version the decision covers.
- Owner
- The studio review coordinator. The recorded client decision maker approves or requests changes.
- When
- Each time a proof or new version is shared.
Final-file QA
Check the final delivery against the current approved scope rather than relying on memory alone.
- Owner
- A second person when practical. In a solo studio, use a deliberate separate pass rather than checking from memory while exporting.
- When
- After approval and before final release.
Complete when
The final set matches the current approval and can be opened, identified, and used as intended.
- Owner
- A second person when practical. In a solo studio, use a deliberate separate pass rather than checking from memory while exporting.
- When
- After approval and before final release.
Delivery and job record
Record what was delivered, to whom, when, and under which access or payment conditions.
- Owner
- The studio delivery owner or producer.
- When
- When final files are released and whenever access changes.
Complete when
The studio can identify the delivered set and reconstruct the final decision and handoff without searching unrelated messages.
- Owner
- The studio delivery owner or producer.
- When
- When final files are released and whenever access changes.
Choose one handoff
Start with the stage you cannot reconstruct.
Look at one recent product photo job. Find the first stage where the studio cannot answer the questions below from a reliable record.
- Who owns this stage?
- Which requirement or version is current?
- What decision is still open?
- What evidence marks the stage complete?
- What happens next?
Fix that stage first. If no recent example is available, begin with request and scope because the later checks need a written reference. That is a practical sequence, not a claim that intake is always the studio's largest cost.
What this checklist does not decide
This resource prompts the studio to record decisions. It does not make those decisions on the studio's behalf.
- What belongs in the client agreement
- How many change rounds are included
- Who pays for work outside scope
- Usage rights or licensing
- Product shipping, handling, or returns
- Taxes or invoice obligations
- Current Amazon, Shopify, retailer, or marketplace specifications
- How long the studio or service provider retains files
- Whether silence counts as acceptance
- Whether a written message satisfies a legal requirement
- Security or privacy obligations for a specific client
Use the actual client agreement, current channel documentation, and qualified legal or accounting advice where those questions matter.
Using the checklist does not guarantee fewer revisions, faster approval, lower cost, or a successful delivery.
About the checklist
- Is this checklist only for larger studios?
- No. A solo owner can use the same five stages. One person may own several stages, but the current requirement, decision, and completion condition should still be written down.
- Does the client need to see the whole checklist?
- Not necessarily. The studio can keep internal production and QA notes private. The client should see and confirm the scope, shot requirements, requested changes, approval, and delivery terms that require a client decision.
- Does this replace a client agreement?
- No. The checklist is an operational prompt. The client agreement defines the binding terms for scope, fees, rights, acceptance, payment, retention, and disputes.
- Should raw camera files use the final delivery names?
- Not in every studio. Source files may keep camera or capture-system names. What matters is a reliable mapping from each source file to the correct SKU, view, version, and final delivery name.
- Should clients have permanent access to every past delivery?
- Not by default. Access and retention depend on the studio agreement, storage policy, subscription state, security controls, and the service being used. Record what was delivered and explain when a secure link can expire or be revoked.
- Can I use this without Lenso?
- Yes. The checklist can work with a spreadsheet, proofing tool, shared folder, project tool, or written studio process.
- How does Lenso handle client access?
- Lenso gives invited clients project-specific access through secure hosted links. Depending on the job, clients can review proofs, request changes, approve, and download released final files. Secure links can expire or be revoked, and clients do not need a paid seat.
Practical next steps
Give the checklist a clearer source record.
Use these resources to add detail where the checklist exposes an incomplete handoff.
Product photography shot list template
Record one row per SKU and required view, including styling, retouching, output, and final naming details.
Studio workflow diagnostic
Review whether request, client-decision, final-file, and ownership handoffs are recorded consistently.
ROI calculator
Use your own measured coordination time and time-change assumption to build a transparent 12-month scenario.
When the client record needs one connected place
Lenso keeps the client side of the job attached to the work.
You can use this checklist with any toolset. Lenso is useful when a studio wants a website request or studio-entered referral, product and shot details, proof versions, client comments, requested changes, approval, optional invoices, and final files to remain connected to the same job.
The studio reviews every request. Client access is project-specific and Lenso-hosted. Secure links can expire or be revoked, and clients do not need a paid seat.
Prefer to browse first? Back to all resources