A property release checklist for stock-photo batches

Checklist

1. Review recognizability and ownership context. Look closely at private interiors, distinctive buildings, artwork, designed objects, and locations that are central to the image. Current platform guidance—not this checker—should inform the requirement decision.
2. Declare that decision per asset. Set requires_property_release to true only when your workflow has determined the asset requires one. Do not combine it with the model-release flag.
3. Assign a stable release ID. A name such as property-studio-north-2026 is easier to trace than a filename that changes during export.
4. Map every covered asset. Reuse the same release_id on multiple relationship rows when one document genuinely covers those assets under your policy. Mark each row PROPERTY.
5. Keep unfinished paperwork visible. Record it as PENDING or UNKNOWN. Do not label it READY merely to clear the exception list.

Example for one location

asset_id,requires_model_release,requires_property_release
kitchen-wide-042,false,true
kitchen-detail-043,false,true

asset_id,release_id,release_type,status
kitchen-wide-042,property-kitchen-2026,PROPERTY,READY
kitchen-detail-043,property-kitchen-2026,PROPERTY,READY

Both assets point to the same property record. That mapping is useful only if your records show that the document really covers both images. The checker verifies the relationship you supplied; it cannot inspect the document or the scene.

Quick exception order

1. Handle declared requirements with no relationship first.
2. Then review relationships that are still PENDING or UNKNOWN.
3. Finally, clean up orphan links and incorrect MODEL/PROPERTY designations.

This workflow check is not legal clearance or platform approval.

The free checker handles up to 10 unique assets, locally in the browser.