The Form Rejection Letter Decoder Thingy

February 10, 2014 § 55 Comments

Form Rejection Decoder Thingy

For an Easy-to-Read Version
Use the PDF link in the Blog Post

A helpful blog entry from Brevity’s managing editor Sarah Einstein. Sarah will be talking about rejection, acceptance, and writing as part of the panel “Getting Short-Form Nonfiction to Readers: A Publication Panel” on the Friday morning of AWP Seattle:

Every couple of weeks, a writer-friend sends me an email or a Facebook message with the text of a rejection letter in it, asking me to help them decode it. Most often, they want me to help them figure out how close they got to being published, which is an impossible task. I couldn’t even tell you that if it was a submission to Brevity… ultimately, either we took the piece or we didn’t. We do have tiered rejection letters. If you got our “close but not cigar” rejection, you should probably turn around and submit that piece to five other places right away because we thought pretty hard about taking it. But if you get our standard rejection, that doesn’t mean you weren’t close. It might mean that we really liked it, but that we had recently published one that seemed too similar for us to be ready for another in the same vein. It might mean that we really liked it, but we could already tell from other choices we had made that it wasn’t going to fit well into this issue. It might mean that it is perfect for PANK / Diagram / Quarter After Eight but just not perfect for Brevity. The list of things it might mean is infinite. And the truth is, there is no way for you–the author–to know. We don’t have time to write to each author and explain why we didn’t take a piece. I wish we did. I really do. I face the same issues with my own work.

And, really, we all know that you can’t actually get any real information out of a form rejection letter. We know that the fact that it took four months to hear back from a journal might mean they spent a long time considering the work and it got pretty close, but it also might mean someone at the journal got sick/married/arrested and just fell behind. That journals don’t have secret codes embedded into the form emails that explain how to become the next Jill Talbot or Anna March. But that doesn’t stop us from looking for clues that aren’t there.

So, writer-friends, I’m giving you this little present. It’s a Form Rejection Letter Decoder Thingy (PDF link here). Surely you remember these from elementary school, when you probably called them “Cootie Catchers.” Just pick a color, pick a number, and the FRLDT will give you a perfectly possible reason that your piece was not selected for publication. Sure, the reasons it will offer you are all on the sunny side of things. It won’t ever tell you, for instance, that the editors thought your narrative was great but prose was stiff. Or the other way ’round. But since all you got was a form rejection, let’s just assume that–as is far more often the case than writers believe–the reason your piece was rejected does have everything to do with the needs of the journal and nothing to do with your work.

That said, it’s probably not a bad idea to take a second pass at revision before you send it out again. Because you always want your work to be your best.

Tagged: , ,

§ 55 Responses to The Form Rejection Letter Decoder Thingy

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

What’s this?

You are currently reading The Form Rejection Letter Decoder Thingy at BREVITY's Nonfiction Blog.


%d bloggers like this: