You collected the signed release on set, filed it in a folder, then exported 400 RAW files to a client, a stock agency, or an art director. Six months later, nobody can tell which images are cleared for commercial use. That is the gap model release form metadata closes. When consent information lives inside the image file, the record travels with the photo no matter where it goes.
What Is Model Release Form Metadata (and Why It Matters)
Image metadata is structured data embedded in a photo file. Most photographers use it for copyright notices and camera settings. Fewer use it to carry release status, and that is a real problem.
When a stock agency receives your files, their intake software reads IPTC and XMP fields automatically. If those fields are blank, the agency may flag the image as unreleased or default to editorial-only status. The same thing happens inside a client's DAM system. The image and its consent record travel together, or they get separated permanently.
If you shoot for stock, read the Photography Release Form for Stock Licensing guide alongside this one.
The IPTC Fields That Carry Release Status
Model Release Status: A controlled-vocabulary field. Standard values are MR-NON (no release), MR-LMR (limited release), and MR-UMR (unlimited release). Use MR-UMR for a fully signed commercial release.
Model Release ID: A free-text field for the unique identifier of the signed document. Your release file name, a job number, or a date-stamped code all work here.
Rights / Usage Terms (XMP): A plain-language description of permitted uses. Example: "Signed model release on file. Approved for commercial advertising use. Release dated 2024-08-15."
Description / Caption: Include release status as a plain note. Some systems read only this field.
The Six Data Points to Embed Before Any File Leaves Your Machine
- Release status (released / not released / limited)
- Release document ID (unique identifier matching your PDF record)
- Date signed (matches the date on the actual release)
- Subject name (as it appears on the signed release)
- Permitted use scope (commercial, editorial, or both; see Model Release Form: Commercial vs. Editorial Use)
- Photographer or studio name (the entity holding the release)
Keep the subject name consistent with the signed document. If the release says "Maria J. Santos," do not abbreviate it in metadata.
Adding Release Metadata in Lightroom, Capture One, and Bridge
Lightroom Classic: Go to Library > Metadata > Edit Metadata Presets. Create a preset called "Release, Commercial" and fill in IPTC Status, Rights, and Copyright fields. Apply it after confirming releases are signed. Use Ctrl/Cmd+S to write metadata to XMP sidecar files or directly to DNGs before you export.
Capture One: Open the Metadata tool tab. Use Styles and Presets to batch-apply a release-status template across a session. Session templates with pre-filled IPTC data save time on repeat clients.
Adobe Bridge: Select images, open the Metadata panel, and expand IPTC Extension. The Model Release Status and Model Release ID fields appear there. Select multiple files before editing to batch-apply.
In all three apps, save named presets: one for "commercial release signed," one for "editorial only," one for "no release." Apply the right preset before you export.
How a Signed Release Connects to Your Metadata
Metadata does not replace a signed release. It points to one. The signed document is the actual record. The metadata is the index card that tells anyone who opens the file where that record lives.
Here is how SignedShoot fits in: you fill the release form, the subject signs it on set, and you have a dated PDF before the session ends. That document gets a file name or ID. That ID goes into your IPTC Model Release ID field. The two records are now linked.
This linkage matters for images with complex usage scope. California Civil Code section 3344 requires written consent for commercial use of a person's likeness. New York Civil Rights Law sections 50 and 51 prohibit using someone's portrait for advertising without written permission. If your metadata says "commercial use approved" but the signed release only grants editorial rights, the signed document controls, but the metadata will create confusion downstream. If you shot brand ambassador content or a product shoot, the release scope and the metadata scope should describe the same permissions.
Quick Export Checklist
- Is Model Release Status set to the correct controlled-vocabulary value?
- Does the Release ID match the file name or reference number on the signed PDF?
- Does Rights / Usage Terms describe the permitted use in plain language?
- Are images with no release tagged
MR-NON? - Have you written metadata to the files, not just your catalog?
One pass through this list takes about two minutes per job. The release and the image file should never travel separately. Set the status field, add the document ID, and export.