Input contract

Prepare the two CSV files

Save both files as UTF-8 comma-separated values. Headers may appear in any order, but every required header must be present exactly once and extra headers are rejected. Empty rows are not accepted.

Assets CSV

One row represents one asset. Use the exact headers below. Boolean values must be lowercase true or false.

asset_id,requires_model_release,requires_property_release
asset-001,true,false
asset-002,true,true
asset-003,false,false

Column	Accepted value
`asset_id`	A non-empty identifier, up to 256 Unicode characters after normalization.
`requires_model_release`	`true` or `false`
`requires_property_release`	`true` or `false`

Release Links CSV

One row represents one asset-to-release relationship. Repeat an asset_id when an asset links to several releases. Repeat a release_id when your own record legitimately covers several assets.

asset_id,release_id,release_type,status
asset-001,model-001,MODEL,READY
asset-002,model-002,MODEL,PENDING
asset-002,property-002,PROPERTY,READY

Column	Accepted value
`asset_id`	The corresponding non-empty Assets CSV identifier.
`release_id`	A non-empty release-record identifier, up to 256 Unicode characters after normalization.
`release_type`	`MODEL` or `PROPERTY`
`status`	`READY`, `PENDING`, or `UNKNOWN`

Identifier rules

IDs are case-sensitive: Asset-01 and asset-01 are different.
Whitespace at the outside of an ID is trimmed. Internal spaces remain part of the ID.
Use stable record IDs rather than names or filenames that change from export to export.
Do not place release documents in either CSV. The checker needs relationship identifiers, types, and statuses only.

Common validation failures

Using TRUE, Yes, or blanks instead of lowercase booleans.
Using model or ready instead of the uppercase accepted values.
Adding spreadsheet index columns or notes that are not part of the exact header set.
Linking to an asset ID whose spelling or letter case differs from the Assets CSV.

The free checker processes up to 10 unique assets locally in your browser. It checks user-declared workflow relationships; it does not inspect release documents.

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.

Open the free checker