Freelancers and saying no?

[RangerWickett]

This is just a general question to anyone who has an opinion. What do you think is the best way to handle a submission that you are not interested in? Should you send a reply saying no and explaining why, or just say no, or not reply at all?

What if the idea is interesting but you're too busy or it's not your bag?

What if the submission is so poor that you would never consider using it?

I'm curious both about how publishers handle this, and how freelancers feel about it.

 

[Dannyalcatraz]

What do you think is the best way to handle a submission that you are not interested in? Should you send a reply saying no and explaining why, or just say no, or not reply at all?

and

What if the submission is so poor that you would never consider using it?

I think that the minimum you owe the freelancer is a polite refusal, even if it is a form letter. An explanation could benefit both you and the freelancer down the road if it is constructive and not dismissive or intentionally abusive. Your response could turn a so-so writer into a good one, or merely reinforce bad behaviors or attitudes.

Remember, word of mouth is the strongest form of advertising out there. If you tick someone off, they'll tell everyone they can how you wronged them.

Bad submissions? You can opt to direct them to another outlet & wish them luck. If you have more time, offer constructive criticism- politely, of course- and tell them your "door is always open" to future submissions that meet your guidelines.

If it is something truly awful, simply tell them that their submission was not something your company would publish. Period. Don't volunteer your opinion. Don't give them other contacts. Don't wish them luck. If they continue sending submissions to you, check 'em out. If the quality never improves, you can always send a final letter to them to cease submitting their work to you, and quietly make use of your shredder...or a hamster.

What if the idea is interesting but you're too busy or it's not your bag?

Tell them their concept has merit, and tell them about other potential outlets. If you think its really good, and you have some pull with those other outlets, contact someone with the manuscript- after asking the freelancer if its OK to forward it (some people get paranoid, and you never know someone's past history)- and then give that contact the scoop.

 

[Morrus]

I wouldn't offer feedback on a bad submisison unless it's specifically asked for. A polite "No thanks" is sufficient. If they ask why, then you can tell them politely that the submisison did not meet standards, but I see no reason to do so otherwise. You'll just wind up upsetting people.

 

[Vigilance]

What if the idea is interesting but you're too busy or it's not your bag?

I would say exactly that- it's a good idea but not what you company does.

I have even gone so far as to point some submission writers in the direction of a company that I thought might be interested on occasion.

What if the submission is so poor that you would never consider using it?

In this case I would simply say "not interested at this time" unless they specifically asked for feedback. In that case I'd be as brief as possible, perhaps something like "I think a better grasp of the nuts and bolts of the rules is in order" or something like that.

I'm curious both about how publishers handle this, and how freelancers feel about it.

 

[Stormborn]

Having gotten a few of these in the past I would say the way to go is:

1. Do send a reply. Not hearing is worse than a "no" to me.
2. Come up with a form that basically says:

"Thank your for your submission. We are not interested at this time."

3. While that is sufficient you can choose to add one of the following:

A Your submission does not fit in with our product line.
B Your submission does not meet the standards of our writer's guidelines (and provide link).
C We are interested in your submission but we do not have a place for it in our schedule at this time. If you like we would be glad to take another look at it in 6 months (or whenver.)


I find that havign a reason is helpful. This has come up more often with fiction that my RPG writing, but I can think of one story in particular that I got lots of rejection letters for that ranged from a simple "Thanks but no thanks" to several "we like it but cant use it, try someone else". The later are encouraging. When I first started writing I got a responce back that had a form sheet with boxes that said "Your manuscript has been rejected becasue:" and then boxes checked off for whatever reason. That wasn't as helpful, but at least it was a reply. I hate not hearing back from publishers.

 

[HalWhitewyrm]

Do send a reply (it's good manners), thank them for their time and interest in your project, and politely tell them that their submission was not accepted (if you want, a simple one sentence reason like Stormborn suggest could go here). Always encourage them to try the next time you have an open call as well, say thanks again and wrap it up.

This formula has worked for me just great, and I learned it from having it sent to me. It tells the author 'thanks, but no thanks' in a nice way that still encourages them to try again next time.

 

[Wycen]

I'll jump on the "send a reply" bandwagon. Good or bad, I think most people would at least like some sort of response.

 

[Wystan]

I would say to send a reply. I would also say that if you do accept it use it...

 

[Scribe Ineti]

Rejection is part of the writing business. Freelancers should be prepared for it. Happens to everyone. A simple form letter or a quick "Thank you for your submission but we are passing on it at this time" is more than sufficient.

 

[DaveMage]

"We thank you for submitting your material, but it does not suit our present needs."