The camera counts shutter releases. A stock business needs to count assets that can be found, licensed, maintained, and supported by evidence. Everything between those two numbers is the production pipeline.
Name the states before counting the files.
A simple workflow can distinguish captured, ingested, reviewed, selected, technically finished, rights-cleared, metadata-complete, submitted, accepted, and licensed. The exact labels matter less than using them consistently.
One file should not appear in several states as if it were several assets. Keep a stable file identity and change its status as the work progresses.
Count bottlenecks, not just output.
If many files are selected but few become metadata-complete, the camera is not the bottleneck. If finished images wait for releases, the rights workflow is limiting production. If submissions repeatedly fail technical review, the problem belongs earlier in capture or post-production.
A weekly state count reveals where value is accumulating unfinished. That is more actionable than celebrating another large shoot.
A file becomes inventory when the business can use it—not when the camera creates it.
Separate accepted from merely transmitted.
An upload folder, metadata application, transfer queue, or marketplace submission page can each look like completion. None proves that the intended agency received and accepted the asset.
Record transmission and review outcomes separately. Preserve the agency, submission date, response, rejection reason, and any corrected resubmission without converting an in-progress state into a success.
Track the denominator behind every rate.
An acceptance rate can mean accepted files divided by captures, selections, submissions, or completed reviews. Each version tells a different story. Publish the denominator next to the percentage so the number can be reproduced.
Use the submitted set to study marketplace review. Use the captured-to-accepted path to study the entire production system. Do not compare the two as if they measured the same thing.
Finish with the retrieval test.
An accepted asset still needs a reliable master file, metadata, rights evidence, submission record, and backup. Ask whether another person—or your future self—could locate the correct version and explain its status without reconstructing the shoot from memory.
If the answer is no, the asset may be earning, but the inventory system remains fragile. Maintenance is part of production because future corrections, removals, licensing questions, and new opportunities all depend on retrieval.
The weekly pipeline count
- Captured and safely ingested
- Selected and technically finished
- Rights-cleared and metadata-complete
- Submitted, reviewed, and accepted
- Retrievable with evidence attached