With one month to go in our current reading period, we’ve received 229 submissions. Of those submissions, we’ve already declined or withdrawn 148. There are 63 pieces in process right this minute, and that will change by the time this post goes live.
Every reading period, we see some of the same trends, not all of them good trends. Since we want you to succeed as poets, want to get submissions that both make us honored to do this work and make you honored to be part of it, we thought it was time to talk about what makes us love our poets.
Submitting work is not always the fun part of being a writer. Okay, maybe it’s never the fun part unless the work is accepted. Acceptances are fun. Acceptances are what we all strive for.
When editors have the opportunity to say yes to a piece, they sometimes do a little dance.
When editors have to say no, for any reason, it makes them a little sad. Much of their sadness, and yours, dear submitters, could be prevented with simple attention to guidelines, details, and a respectful tone.
Let’s start with those guidelines. You’ve read it and heard it over and over: read the guidelines before submitting. It usually goes with the advice to read the publication to which you are submitting. This is really important. If you’ve read Gyroscope Review at all, you will notice that we publish contemporary poetry. We don’t publish work that sounds like it was around in Shelley’s time or harkens back to Beowulf. We seldom publish pieces that rhyme. We’re picky about pieces that have racist or sexist undertones, don’t care for gratuitous sex, aren’t fond of political rants even though those are tempting at this point in history. So, tone and form are something to study.
Our guidelines also point out some housekeeping items. Every reading period, we have someone who sends us a piece that we like, that we accept, and then we get an email that says, oops, someone else already accepted that piece. We take simultaneous submissions, but we want you to do your part. And what is your part? Tell us immediately if a piece you’ve sent us gets accepted elsewhere. We spend a lot of time reading, thinking, and Google-checking work. If we’ve done all that and made a decision only to learn you forgot to tell us that this piece is no longer available, that’s not respecting our time. Respect needs to go both ways.
While we are on the subject of knowing and sharing the status of your own poems, don’t resubmit something we’ve already rejected. Chances are pretty good we’ll remember the piece and wonder what you were thinking.
Another housekeeping item in our guidelines that someone ignores every reading period is when a submission contains more than one poem in a single document. We have our system set up for one poem in document = one submission. Why? Because when we vote on each poem, we need to be able to filter between accepted and declined. If everything is in one document, we can’t do that on a poem-by-poem basis. Therefore, multiple poems in one document means they will automatically be declined. And don’t think that you can submit one big document four times to make up for there being four poems in that document. One poem in one document = one submission. No exceptions.
Now, can we talk about appearance? We know you play with fonts sometimes. They can make writing something fun, shake things up a little but. We do it ourselves – on our own computers for our own amusement. When submitting, stick to a standard Times 12 pt font in basic black. A piece submitted in purple Comic Sans is distracting and takes us out of the piece. We sit there and wonder, why purple? Why Comic Sans? Just don’t.
And now a little bit about respecting our decisions for our own journal. Let’s say you send us a piece and we have to say no. Maybe our rejection has come to you on a bad day and you rapid-fire write a response telling us we don’t know good poetry from a hole in the ground. And then you hit “send.” When we open that email, are we likely to take pity on you and your submission? Nope. Are we likely to think, oh, that poet must be having a bad day and give you a pass on your rudeness? Nope. Are we likely to remember who you are? Oh yes. Yes indeed. And when we see your name in the slush pile in a future reading period we may not read your work with as much enthusiasm as someone else’s.
Now, if you had sent us a different email that asked us if we could give you more feedback on why your poem did not make the cut, would we be likely to answer? Yes, we would. There are hordes of reasons why pieces get rejected on any given day. Maybe we already have lots of pieces in the same vein. Maybe your piece, though wonderful, is better-suited to a different season. Maybe you’ve submitted four pieces, and we’ve already accepted three. Perhaps the subject matter just doesn’t fit with our vision for Gyroscope Review. And maybe the piece honestly could benefit from revision.
If you have a piece that gets rejected and you are going to revise it, give it enough time. A revision done within hours of a rejection is too fast. You know how a good stew slow cooks for hours so all the flavors can blend? Good poetry is like that: it needs simmering time for all the nuances and metaphors to come together into a delicious stew of lines that makes the reader want more. It cannot be rushed. If you try to shortcut revision, you will end up with an inferior piece lacking in essence.
And what about sending us something else if we decline your work? You are welcome to do that, but please take a moment or three to think about why we said no to your poems. Think about whether the next batch of work you want to send us looks just like what we’ve already rejected. Think about whether we are a good fit for you.
We should tell you that we have accepted a piece or two – or, well, 18, if you want exact numbers. We expect to at least triple that by the time we go to press; we expect just as many submissions during the last month as we’ve had up to now. So, you still have a shot if you like Gyroscope Review. Get writing. We’re waiting.
Still not sure? Ask us questions at firstname.lastname@example.org. We will answer.
Images courtesy of Pixabay.com.