Production records become unreliable when uploaded, submitted, accepted, and published are treated as the same event. They are separate states. A clear trail prevents unfinished files from disappearing between them.
Define the states before you count the assets.
A practical sequence may include prepared, uploaded, metadata complete, release matched, submitted, under review, accepted, rejected, and published. Use only the states your workflow can verify.
A file belongs in one current state at a time for each destination. The next state should require a visible result, not an assumption that the system probably continued.
Give every finished asset a stable identifier.
Filenames can change during export or at the destination. Keep an internal asset ID that connects the source, derivative, metadata, release evidence, destination record, and later revenue.
The identifier does not need to be public or complicated. It needs to remain stable enough to resolve which exact file a status belongs to.
Save evidence at the meaningful transition.
Record the submission timestamp, destination, batch or receipt reference, file count, and visible result. When practical, retain an export report or screenshot that can be matched back to the stable IDs.
Evidence is most valuable when it is captured at the transition. Reconstructing a batch months later is slower and less reliable.
Count the state you can prove—not the action you remember taking.
Search routinely for assets that stopped moving.
Filter for files uploaded but not submitted, submitted without a review result, accepted but not visible, or rejected without a next action. These are operational queues, not vague exceptions.
A short reconciliation after every batch costs less than discovering much later that valuable work never reached the market.
Keep resubmissions connected without overwriting history.
When a file is corrected or replaced, create a new attempt under the same source relationship. Preserve the earlier result, the reason for the change, and what was different in the new version.
This makes repeated problems visible and prevents the latest status from erasing what actually happened.
Minimum submission record
- Stable asset ID
- Destination and current state
- Date and batch or receipt reference
- Evidence of the latest transition
- Next action, when one remains