Batch preparation

Map model and property releases across a photo batch

Folders tell you where documents live. A relationship table tells you which document supports which asset. That distinction matters when one release covers several files or one photograph needs more than one release.

A repeatable mapping method

Export one inventory row per asset. Choose IDs that survive renaming and write the two requirement flags from your completed content review.
Make the second file a relationship table. Each row joins one asset_id to one release_id. Multiple people in an image normally mean multiple model-release rows in your register.
Keep types and statuses exact. Use MODEL or PROPERTY, then READY, PENDING, or UNKNOWN. These values are uppercase.
Run the audit before packaging the submission. Work from the prioritized exceptions rather than manually reopening every file.

Example: two assets, three relationships

asset_id,requires_model_release,requires_property_release
shoot-2408-001,true,true
shoot-2408-002,true,false

asset_id,release_id,release_type,status
shoot-2408-001,model-jordan-01,MODEL,READY
shoot-2408-001,property-loft-01,PROPERTY,READY
shoot-2408-002,model-jordan-01,MODEL,READY

This is a many-to-many map: the first asset uses two release records, while the model record is reused for the second asset. Reuse a record only when your underlying release and destination rules support that use.

Three mistakes the table exposes

Pattern	What to check
Required, no linked record	Find the document, correct the declaration, or hold the asset.
Link to an unknown asset ID	Correct a case mismatch or remove an orphan relationship.
Wrong relationship type	Check whether the row was labelled `MODEL` instead of `PROPERTY`, or vice versa.

IDs are trimmed at their outer edges and Unicode-normalized by the checker, but they remain case-sensitive. Keep the original identifiers consistent rather than relying on normalization to repair a register.

This workflow check is not legal clearance or platform approval.

The free checker supports up to 10 unique assets, with no release documents uploaded.

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

Copy the exact two-file schema