Author Topic: Model/Property Release Workflow? (Read 3552 times)

bobbigmac · « **on:** December 30, 2011, 17:22 »

Hey all

I'm adding Model Release management to picWorkflow very soon, but since I've never shot with models so never had need for releases, I was hoping you guys would be kind enough to run me through your model release workflows, concerns and considerations?

I'm already approaching some agencies about how to streamline the release-management process between picWorkflow and them, and making it easier for photographers to organise. I'm also looking at some technical resolutions to 'lock-in' releases with images to make it an even better long-term solution, though there are some legal concerns there atm.

I really need to know everything you have to think about releases, but specifically, would be great to also hear your thougts on these questions:

What format(s) do you prefer to keep releases in, and what format do you upload them as?
Do all agencies accept all generic releases, or do some agencies have specific requirements? Which ones? and how do you manage those differences?
What data/fields do agencies need to know about each models/property?
Do you produce seperate releases for each shoot? (I vaguely remember iStock introduced a requirement for something to do with this in '09)
Do you track image-volume/acceptance-rates/rpi/other on shoots/models/locations? If not, would that be helpful to you?
Do you find much results from 'More Images from this Model' in some agencies?
A couple of agencies have added MR-via-FTP... anyone using this yet? (If so, do you prefer a 1MR-Entire batch import, or would some kind of filenaming (like with .eps) be more suitable?)
Anything else?

Thanks!!

Bob

fotorob · « **Reply #1 on:** December 30, 2011, 18:56 »

H Bob,

I have worked with about 200 models now, so maybe I can help a bit:

Quote

What format(s) do you prefer to keep releases in, and what format do you upload them as?

I use JPG, though some others use PDF as well. That's usually it.

Quote

Do all agencies accept all generic releases, or do some agencies have specific requirements? Which ones? and how do you manage those differences?

I only use one generic release form for ALL agencies and most pros do the same.

Quote

What data/fields do agencies need to know about each models/property?

Some want to know: Age (or age range), sex (male/female), ethnicity, Location

Quote

Do you produce seperate releases for each shoot? (I vaguely remember iStock introduced a requirement for something to do with this in '09)

Yes, though I try to only upload one release for ALL shots, because it gives better results for the "more of the same model" searches.

Quote

Do you track image-volume/acceptance-rates/rpi/other on shoots/models/locations? If not, would that be helpful to you?

On a basic level, I do and it has been proven very helpful for casting new models.

Quote

Do you find much results from 'More Images from this Model' in some agencies?

Yes.

Quote

A couple of agencies have added MR-via-FTP... anyone using this yet? (If so, do you prefer a 1MR-Entire batch import, or would some kind of filenaming (like with .eps) be more suitable?)

Only sometimes.

Anything else:
A batch support to add several releases to a group of images at once would be really time-saving, especially for group shots.

If you need anything more, let me know, you know how to reach me...

Best regards,
Robert

bobbigmac · « **Reply #2 on:** January 01, 2012, 12:27 »

Thanks Rob!!

I'll see how I can work all that in

Bob

MicrostockGroup Sponsors

Author Topic: Model/Property Release Workflow? (Read 3552 times)

bobbigmac

fotorob

bobbigmac

Related Topics

Sponsors

Microstock Poll Results

Sponsors