How to Use Poetry Contest Feedback (Not Just Read It)
Most poets read contest feedback once, feel something sharp, and change nothing. A judge shares a working system for converting scores and comments into actual revisions, plus when to ignore feedback entirely.
A poet I will call Daniel entered the same contest four months in a row and scored between 6.2 and 6.5 every single time. Four different poems, four nearly identical scorecards. When he finally wrote to me, frustrated, I asked him one question: what did the feedback say each month? He admitted he had skimmed each report once, on his phone, within ninety seconds of the results going live, and never opened any of them again. Daniel had paid for a diagnosis four times and never once taken the medicine. Most poets handle poetry contest feedback exactly this way, which is why most poets plateau. Reading feedback is an event. Using it is a practice, and the practice has rules.
Why Most Poetry Contest Feedback Gets Wasted
Feedback arrives at the worst possible emotional moment: the same instant you learn you did not win. Whatever the judge wrote, you read it through a fog of disappointment, and disappointed readers do two predictable things. They dismiss ("this judge clearly did not understand the poem") or they collapse ("I knew it, I am not a real poet"). Both responses feel like processing. Neither one touches the poem.
There is a third failure mode I see in poets who are past the emotional stage: obedient editing. They treat every comment as a command, change everything the judge flagged, and produce a draft with no fingerprints on it. A poem revised by committee of one stranger is usually worse than the original, because the judge's comments were observations about effects, not instructions about causes.
Feedback is not a verdict on your talent. It is a map of where one careful reader's attention snagged.
Hold that sentence, because everything below depends on it. A snag is data. What you build from the data is still entirely your call.
The 48-Hour Rule: Separate the Sting from the Signal
Here is the protocol I give every poet I mentor, and I follow it myself when my own work comes back with notes.
First read, results day: read the feedback once, fast, and then close it. Your only job on day one is to notice your emotional reaction without acting on it. Do not open the poem. Do not draft the defensive email. I have written that email, by the way, early in my career, to an editor who had called my ending "unearned." She replied with one line: "Read it again in a month." A month later the ending was, in fact, unearned. I cut four lines and the poem was published the following year. She had been right in October; I was only able to know it in November.
Second read, 48 hours later: print the feedback or put it beside the poem on a real screen, and read it as if it were about someone else's work. The 48-hour gap is not arbitrary politeness toward yourself. It is the time it takes for "how dare they" to decay into "huh, interesting." Signal survives the two days. Sting mostly does not.
Learn to Read a Scorecard Like a Judge Writes One
Numbers carry more information than poets extract from them. Writory, where I judge, returns a five-criteria breakdown to every entrant: creativity, emotion, structure, language, and theme. Whatever contest you enter, the categories rhyme with these, and the shape of your scores matters more than their average.
- High language, low emotion is the most common winning-adjacent shape. It means your lines are polished and your poem is a beautiful sealed box. The fix is almost never more craft; it is more risk.
- High emotion, low structure means the feeling arrived but the container leaked: endings that trail off, stanzas broken by habit rather than design, a middle that repeats the opening's work.
- Low creativity with everything else high is the gentlest way a scorecard can say "I have read this poem before." Your execution is fine; your angle of approach is the one everyone uses.
- One score far below the rest is a gift. Four strengths and one repeated weakness is the fastest improvement profile in poetry, because you know exactly where to aim.
Daniel, from my opening, had that last shape: strong language and theme, and a structure score that sat two points under everything else, four months running. His poems did not need to be better. They needed to end better. Once he saw the pattern, one month of studying the turn, the volta, in poems he admired did more for him than a year of general effort.
The Feedback Ledger: A Five-Step System You Can Start Tonight
One scorecard is an anecdote. Five scorecards are a curriculum. This system turns them into one.
- Log every piece of feedback in one document. Date, contest, poem title, scores, and the judge's comments copied verbatim. Verbatim matters; your paraphrase will soften whatever hurt.
- Tag each comment as CRAFT, CLARITY, or TASTE. Craft comments name mechanics (flat verbs, broken meter, weak line breaks). Clarity comments mean the reader got lost. Taste comments express preference ("I wanted more nature imagery"). Only the first two categories are automatically actionable.
- Hunt for repeats across different judges. One judge flagging your endings is an opinion. Three judges across three contests flagging your endings is a fact about your poems, and facts about your poems are precious and rare.
- Convert each repeated note into a revision question, not an instruction. "Ending feels rushed" becomes "What does my last stanza know that my first stanza does not?" Questions produce your solution. Instructions produce the judge's.
- Revise one poem, then re-enter it or send it out again. Feedback without a second attempt is a closed loop. The revision, resubmitted, is the experiment that tells you whether you understood the note.
That fifth step is where the whole system pays off, and it is the one poets skip. If your contest allows revised work in later cycles, send the stronger draft back into the arena and compare the two scorecards. Two data points on the same poem teach more than ten on different ones.
A Worked Example: One Comment, One Real Repair
Let me show what step four looks like on actual lines. Suppose the feedback says: "The poem tells me the grief instead of letting me feel it, especially at the close." Here is the kind of ending that earns that note:
And now that she is gone forever,
the sadness overwhelms my heart.
I will miss her every day.
The obedient revision deletes "sadness" and "grief" and calls it done. The question-led revision asks: where in the physical world does this specific grief live? The poet remembers, say, that her grandmother salted everything too heavily. Now the ending can become:
I cook her soup the way the recipe says.
It tastes like someone politely
pretending to be my grandmother.
I add more salt. Then more.
No emotion words survive, and the grief has tripled. The judge's comment did not contain that soup. Your life contained the soup; the comment only told you where to dig. That is the entire relationship between feedback and revision, and it is why the ledger asks questions instead of taking orders. For more repair patterns like this one, the exercises in our writing tips library pair well with a fresh scorecard.
When to Ignore Feedback Completely
Yes, sometimes. A judge is one reader on one afternoon, and honest judges will tell you we misread poems occasionally, especially subtle ones, especially at hour three of a scoring session. Ignore feedback when it fails all three of these tests: it appears only once across multiple readers, it conflicts with your poem's central intention rather than its execution, and acting on it would make your poem more ordinary. A comment that says "consider a more conventional structure" about a poem whose meaning depends on its fractured form is a taste note wearing a craft costume.
But be ruthless with yourself about which test you are applying. "This contradicts my intention" is a legitimate reason. "This hurt my feelings" is not, and the two impersonate each other constantly. The 48-hour rule exists precisely to help you tell them apart.
The Poets Who Improve Are Simply the Ones Who Loop
After several years of judging, I can tell you the real difference between the poets whose scores climb and the poets who plateau, and it has nothing to do with talent. The climbers close the loop: read, wait, log, question, revise, resubmit. The plateaued poets read once and write something new, carrying every old weakness forward into fresh material like furniture into a new apartment.
Daniel, for the record, placed in the top ten his sixth month, with a structure score that finally matched the rest of his card. The poem was not smarter than his earlier work. He was simply the first version of himself who had actually read his own instructions. You have probably already received yours. Go open them again, slowly this time, and start the ledger tonight.
By Team Writory, for Writory.
Enter a Writory poetry contest
Enter the September contest and have your own poem read and scored. That first entry makes you a Writorian.