Pre-submission control
A release-relationship preflight for stock-photo submissions
Marketplace upload screens can help attach documents, but the cleanest time to find a missing relationship is before the batch reaches that screen. Use this preflight after editing and content review, and before final upload packaging.
The five-minute preflight
- Confirm the destination. Read its current release requirements for the kind of commercial content in your batch. Rules and submission interfaces can change.
- Finish the human content review. Decide the model- and property-release requirement for every asset. Record those two decisions as lowercase
trueorfalse. - Export the release relationships. Use one row per asset-to-release link. Preserve separate rows when an asset has several recognizable people or requires both release types.
- Run the local check. Correct invalid CSV values first, then work through missing or not-ready relationships, conflicting types, and orphan rows.
- Read back the final package. Check the actual documents and marketplace attachments. A clean CSV relationship result does not inspect signatures, dates, authority, content, or destination acceptance.
Minimal handoff example
asset_id,requires_model_release,requires_property_release
campaign-006,true,false
campaign-007,false,trueasset_id,release_id,release_type,status
campaign-006,model-release-006,MODEL,READY
campaign-007,property-release-007,PROPERTY,UNKNOWNThe second asset remains an operational exception because its property relationship is UNKNOWN. The next action is to verify the underlying record and update your register—not to assume the asset is ready.
What a clean result means
| It does mean | It does not mean |
|---|---|
| Your declared requirements have the relationships and statuses expected by this fixed workflow. | The release itself has been read or validated. |
| Asset and release IDs can be reconciled across the two files. | A marketplace will accept the content. |
| You have a smaller exception list for the final human review. | The tool determined whether a person or property needed a release. |
This workflow check is not legal clearance or platform approval.
Use the free checker for up to 10 unique assets. The CSV processing stays in your browser.
Your asset and release files are checked in your browser and are not uploaded to KurodaLab.
Cloudflare and Link/Stripe may process ordinary network, security, and commerce information when you visit, pay, recover access, or send aggregate product events. See the privacy notice for details.