Free self-assessment

Studio workflow diagnostic

Answer eight questions about how a product photo job moves through your studio, from the first requirements to client review, final files, and the next handoff. You will get a practical result and a clear place to start.

No account or email required. Your answers and score stay in this browser and are not submitted to Lenso.

Check four handoffs in the job.

This is a simple reflection tool created by Lenso. It looks at whether important requirements, decisions, and final-file context are recorded consistently. It is not an industry benchmark and it does not estimate hours, margin, revenue, or return on investment.

  • Request and requirements
  • Client review and decisions
  • Final files and repeat context
  • Visibility and ownership

Answer for a normal client job, not the best or worst example.

Answer scale: Consistently · Sometimes · Rarely or not yet

Consent-based site analytics may record that the assessment was started or completed, but never your answers or result.

Assessment

Request and requirements

Before work begins, the products or SKUs, required views, references, deadline, and output specifications are recorded in a shared place.
Website requests, referrals, and repeat-client jobs follow the same minimum intake standard before the studio accepts or starts the work.

Client review and decisions

Client comments stay attached to the correct proof or version instead of being split across email, chat, and separate file links.
Requested changes and approvals are recorded as explicit decisions, including which proof or version they apply to.

Final files and repeat context

The studio can identify the approved final files, naming rules, output specifications, and delivery status without searching old messages.
When a client returns, the studio can find the prior requirements, decisions, and delivery context before setting up the next job.

Visibility and ownership

The current owner, status, open decision, and next step are recorded somewhere the studio can rely on, not only in one person's memory.
A colleague, freelancer, or future you could understand the job's requirements and recent decisions without a separate verbal reconstruction.

How the result is calculated

Each answer receives 0, 1, or 2 points. The eight questions are weighted equally, for a maximum of 16. Each of the four areas has a maximum of 4 points.

The questions, score bands, and recommendations are an editorial framework created by Lenso. They are not based on an industry dataset and they do not estimate time saved, cost, margin, revenue, revision count, or return on investment.

Use the result as a prompt for a real conversation with the people who run the work. A low-scoring area may be intentional, may be handled well in another tool, or may matter less than a different handoff in your studio.

Your answers and score remain in the browser and reset when the page is refreshed or closed.

13 to 16 - Consistent across most stages

Your answers suggest that the main job context is usually recorded and easy to follow. Review the lowest-scoring area for the next improvement rather than replacing a process that already works.

9 to 12 - Some handoffs are inconsistent

Several parts of the job are documented, but at least one handoff still depends on follow-up, memory, or a separate channel. Start with the lowest-scoring area.

5 to 8 - Several handoffs need structure

Important requirements or decisions are not recorded consistently across the job. Pick one area, define the minimum information it must hold, and assign an owner before changing tools.

0 to 4 - Start with one shared foundation

Most of the job currently depends on informal handoffs. Begin with a repeatable intake record, then add explicit review decisions and a final-file record. Do not try to replace every tool at once.

About this diagnostic

Is this an industry benchmark?
No. The score compares your answers with this page's simple point model. It does not compare your studio with other studios.
Does the score measure profitability?
No. The diagnostic does not know your costs, job volume, team size, client mix, pricing, or margins. It only reflects how consistently the eight handoffs are recorded, based on your answers.
Do I need Lenso to improve the result?
No. A disciplined mix of spreadsheets, proofing tools, shared folders, and written processes can improve these handoffs. Lenso is one option when you want the client-side context connected in the same job.
Are my answers saved?
No. Your answers and score stay in this browser and reset when the page is refreshed or closed.

Practical next steps

Work on one handoff at a time.

These resources can help you define a clearer starting point without changing your entire tool stack.

Product photography shot list template

Use one row per SKU and required view to record backgrounds, styling notes, output specifications, and file names before production begins.

Product photography production checklist

Review ownership and completion conditions from request and scope through client decisions, final-file QA, and delivery records.

Product photography terms

Use plain-language definitions for SKU, shot list, proof, revision scope, approval, deliverable, naming convention, and usage rights.

When the handoff needs one connected place

Lenso connects the client side of the job.

This diagnostic works with any toolset. Lenso is useful when a studio wants a website request or referral, product and shot details, client review, approval, optional invoice, and final files to stay attached to the same job.

The studio reviews every request. Clients use a secure Lenso-hosted area and do not need a paid seat.

Prefer to browse first? Back to all resources