Sending a script seprate after a responce from the sent query letter to the producer
I have a question. Could it be possible if I can send the script after a responce from a producer, because I am afriad that he or she might steal my work, if I attach my script to the query letter
I wouldn't attach a script to a query, they are almost always deleted unread. So yes, if the producer responds favorably to your initial query and wants to take a look at the script then you fire it over... although I suggest holding off queries until the strike ends.
If the producer asked for the script you send a PDF, and you CC yourself. You don't attach the script to a letter. As far as the producer stealing your work --- do you really think your script is so amazingly wonderful that it's perfect for stealing? Do you really think a legit producer would risk their career over the stealing a script? If the producer did steal it, and make it, you sue them after it's released and made money so you'll have a payday.
The best way to protect your work is by registering it with the US Copyright Office. It's what I typically do before pitching or sharing the logline with the public. If you've not already done this, I would contact them if you have any questions. They've been very helpful to me in the past. https://www.copyright.gov/
Yes, don't send the script unless it's requested. You should receive a non disclosure agreement to sign before sending it over. And always make sure the work you're sending out is registered somewhere for your extra protection like the WGA or Library of Congress.
I received a notification of a comment that per Stage 32 policy, violated community guidelines and as a result was deleted, despite being edited. Once notification has gone out, the person to whom the disparaging comment was directed at has already been sent the comment. Per S32 guidelines: a community violation includes "Comments made to demean other members for lack of experience or skill." Please be mindful of this policy when commenting. No matter the subject of the post, we're here to uplift and encourage. Thanks.
Just another version of the same response. Think of it as pizza. Someone puts a menu in your letterbox (query letter). You are interested you order a pizza.
Imagine if someone just turned up with a pizza.
Plus no one steals. Even if someone could give me a well research case, it is so statistically insignificant, don’t worry.
1 person likes this
I wouldn't attach a script to a query, they are almost always deleted unread. So yes, if the producer responds favorably to your initial query and wants to take a look at the script then you fire it over... although I suggest holding off queries until the strike ends.
1 person likes this
If the producer asked for the script you send a PDF, and you CC yourself. You don't attach the script to a letter. As far as the producer stealing your work --- do you really think your script is so amazingly wonderful that it's perfect for stealing? Do you really think a legit producer would risk their career over the stealing a script? If the producer did steal it, and make it, you sue them after it's released and made money so you'll have a payday.
1 person likes this
register with WGA
2 people like this
The best way to protect your work is by registering it with the US Copyright Office. It's what I typically do before pitching or sharing the logline with the public. If you've not already done this, I would contact them if you have any questions. They've been very helpful to me in the past. https://www.copyright.gov/
2 people like this
I agree that you shouldn't send the script until it's specifically requested
3 people like this
Yes, don't send the script unless it's requested. You should receive a non disclosure agreement to sign before sending it over. And always make sure the work you're sending out is registered somewhere for your extra protection like the WGA or Library of Congress.
2 people like this
Only send it if a producer asks for it you should not send before it's requested.
1 person likes this
I received a notification of a comment that per Stage 32 policy, violated community guidelines and as a result was deleted, despite being edited. Once notification has gone out, the person to whom the disparaging comment was directed at has already been sent the comment. Per S32 guidelines: a community violation includes "Comments made to demean other members for lack of experience or skill." Please be mindful of this policy when commenting. No matter the subject of the post, we're here to uplift and encourage. Thanks.
1 person likes this
Only send scripts if you've been asked to, otherwise you wont be taken as a serious writer...
1 person likes this
Just another version of the same response. Think of it as pizza. Someone puts a menu in your letterbox (query letter). You are interested you order a pizza.
Imagine if someone just turned up with a pizza.
Plus no one steals. Even if someone could give me a well research case, it is so statistically insignificant, don’t worry.