A two-hour shoot can consume far more than two hours of business time. If the later work is omitted, an expensive production can appear efficient and a smaller, disciplined production can appear slow. Measure the complete path to a usable asset.
Include the work before and after capture.
Count concept development, research, permissions, scheduling, travel, setup, capture, breakdown, ingestion, selection, editing, rights review, metadata, export, submission, corrections, and backup.
Use a level of detail you can maintain. A few consistent categories are more useful than a perfect timer that gets abandoned after one week.
Separate shared production time from asset-level time.
Travel and setup may support an entire shoot, while retouching and metadata may belong to one file. Record both, then distribute shared time across the finished assets produced by that session.
This reveals the benefit of a well-designed series without pretending that every extra shutter release created another product.
Use a fixed definition of finished.
Decide whether finished means export-ready, submitted, accepted, published, or another precisely verifiable state. Do not switch the denominator when comparing productions.
Captured and selected files are useful pipeline counts, but they are not yet equivalent to complete inventory.
The clock stops at a defined finished state—not when the camera goes back in the bag.
Find the bottleneck before trying to work faster.
Break total time into broad stages and compare them. The expensive step may be travel, release handling, difficult selection, repetitive retouching, metadata, or corrections after submission.
Improve the stage that repeatedly controls throughput. Saving minutes during capture will not matter if every file later requires avoidable repair.
Do not let speed become the only decision rule.
A slower production may create durable, distinctive, or difficult-to-replace assets. A fast production may create many files with the same narrow use. Compare time alongside quality, rights certainty, buyer usefulness, acceptance, longevity, and revenue.
Time per finished asset is a diagnostic measure. Its purpose is to improve decisions, not to reward speed at the expense of the work.
Basic calculation
- Add shared production time
- Add file-specific finishing time
- Choose one verifiable finished state
- Count only assets that reached it
- Divide total time by that finished count