Model release workflow

Find assets missing a required model release

Start with the requirement decision you have already made for each asset. The checker does not identify people or decide whether a release is required. It compares that declaration with your release-link register so you can find gaps before submission.

Run the check in four steps

Review each asset against your current destination rules. If your workflow says a model release is required, enter true in requires_model_release. Keep the property flag separate.
Give the asset a stable, case-sensitive ID. Use the same spelling in both CSV files. Portrait-017 and portrait-017 are different IDs.
Add one relationship row for each attached release. Use MODEL as the type and record its current workflow status as READY, PENDING, or UNKNOWN.
Resolve the exceptions, not the whole batch. A required asset with no ready model-release relationship deserves attention. So do orphan links and a link whose type conflicts with the declared requirement.

Small example

The first file declares the requirement:

asset_id,requires_model_release,requires_property_release
portrait-017,true,false
portrait-018,true,false

The second file records the relationships you currently have:

asset_id,release_id,release_type,status
portrait-017,model-alex-2026,MODEL,READY
portrait-018,model-sam-2026,MODEL,PENDING

portrait-017 has a ready relationship. portrait-018 should stay in the exception list until your own workflow changes the relationship to READY or the asset declaration is corrected.

What to review before declaring the flag

Official contributor guidance can treat a person as recognizable through more than a visible face—for example, distinctive tattoos, clothing, or context. Requirements vary by destination and content. Check the current instructions for the marketplace you will actually use, then put your decision in the Assets CSV.

This workflow check is not legal clearance or platform approval.

The free checker handles up to 10 unique assets and processes both CSV files 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.

Check your CSV files locally

Open the exact CSV format reference