How I Track Poetry Submissions: A Judge's Simple System
A contest judge shares the five-column ledger that keeps your poems moving, your revisions honest, and your acceptance rate climbing, plus the one column almost nobody keeps.
In March a poet sent me an apology she did not owe anyone. She had entered the same poem in the same contest two months running, not as a strategy but because she kept no record of what went where. Her poem was genuinely good. The duplicate is what I remember. If you want to skip that particular embarrassment, learn to track poetry submissions the way a working writer tracks invoices: on one page, in five columns, updated the day something happens. It takes five minutes a week, and it will do more for your results than most craft advice you will read this year.
I say that as someone who reads contest entries every month. From the judging side, you can always tell which poets keep records. Their poems arrive matched to the theme, revised since the last attempt, and never twice. The poets who track are not more talented. They are simply the only ones who can see their own patterns.
Why Poets Who Track Poetry Submissions Win More Often
Memory is a flattering editor. Ask a poet how many times a poem has been rejected and they will say twice when the true number is five. Ask which version they sent in April and they will guess. A ledger does not guess. Once you track poetry submissions in writing, three things happen fast.
First, you stop wasting entries. No duplicates, no expired versions, no sending a poem about winter to a contest themed around beginnings just because it was the file on top.
Second, you start seeing which poems earn attention. A poem that reaches a shortlist in two different contests is telling you something. A poem rejected six times without a single nod is telling you something else. Without records, both poems feel the same in your head.
Third, you build patience. Submission life is slow, and the ledger turns that slowness into visible progress: rows fill, notes accumulate, and a bad month looks like what it is, one bad month inside a long game.
Talent writes the poem. The ledger builds the poet.
The Five-Column Ledger
You do not need an app, a subscription, or a database. You need one spreadsheet with one tab, or one page in the back of a notebook. Mine has five columns, and I have watched this exact layout carry poets from their first entry to their first win:
- Poem and version. Not just the title: the title plus a version number. "Salt Map v3" is a different creature from "Salt Map v1," and you need to know which one is out in the world.
- Where and when sent. Contest name and the date you hit submit. The date matters more than you think; it tells you later how long each contest actually takes.
- Deadline and results date. When the window closes and when they promise an answer. This column kills the daily inbox-refreshing habit, because you know nothing arrives before the date in the box.
- Outcome. Win, shortlist, longlist, decline, no reply. Use those five words only. "They hated it" is not an outcome, it is a mood.
- Fee and prize. What you paid and what was at stake. Over a year, this column becomes your honest accounting of whether a contest earns its fee.
Update it the day something happens, not on some future organized Sunday that never comes. The whole system lives or dies on that one habit.
The Sixth Column Almost Nobody Keeps
Here is the column that separates poets who improve from poets who merely persist: what I learned. Every time a result comes back, write one line. Not a diary entry. One line.
If the contest gave feedback, compress it: "ending over-explained, middle strong." If it gave scores, record them. Some contests hand you this column ready-made; Writory, where I read entries, returns a five-criteria breakdown to every single entrant, scoring creativity, emotion, structure, language, and theme, with entries open from the 1st to the 25th and results on the 30th. If you enter contests like that, the numbers go straight into the ledger and your weakest criterion becomes next month's revision assignment.
And if the contest said nothing at all, write your own line. Before you submit, note the thing you secretly worry about in the poem: "last stanza might be doing too much." When the decline arrives, you will be astonished how often your pre-submission worry was the poem's actual problem. You already knew. The column just forces you to say it out loud.
The Fifteen-Minute Monthly Review
The ledger only pays off if you read it. Once a month, on whatever day you like, run this sequence. It takes fifteen minutes and it is the closest thing to a coach most poets will ever have.
- Log every outcome from the month. Fill the outcome column for anything that came back, and mark anything silent past its results date as "no reply."
- Find the three-strike poems. Any poem declined three times in its current version gets flagged. Not retired: flagged. It goes back to the desk before it goes back out.
- Find the near-misses. Shortlists and longlists are green lights. Those poems go out again within the month, to a contest of equal or better standing.
- Match poems to next month's themes. Read the theme of each upcoming contest and pick from your ledger deliberately. A poem built around grief lands differently in a contest themed on memory than in one themed on renewal; the ledger lets you make that call with the whole inventory in front of you.
- Write one sentence about the month. "Two near-misses, both narrative poems; my imagist work went nowhere." Twelve of those sentences make an annual review no workshop could give you.
One Poem's Ledger, Start to Finish
Let me show you what this looks like in practice, with a poem I will call "Salt Map." Its first row: sent in January, version 1, declined, my own pre-submission note reading "ending explains itself." Second row: February, still version 1, because I ignored my own note. Declined again, and this time the feedback line said the same thing my note had said a month earlier.
The original ending ran like this:
and I finally understood that grief
is just love with nowhere left to go.
That couplet is the kind of thing that feels profound at midnight and reads like a greeting card at the judging table. It tells the reader what to conclude. So version 3 cut the conclusion entirely and ended on the poem's central object instead:
I fold the map along its whitest crease.
Salt keeps. The sea does not.
Notice what the revision trusts: the image does the grieving, and the line break carries the weight the explanation used to carry. If you want the mechanics of why that break works, the glossary entry on enjambment is a good afternoon's reading. Row four of the ledger: "Salt Map v3," sent in April, shortlisted. Row five: sent again in May, first place. The poem did not become brilliant between January and May. The ledger simply refused to let me forget what was wrong with it.
What Rejection Rows Are Actually For
A single rejection means almost nothing; one reader, one month, one field of competitors you never saw. Ten rejection rows, read together, mean a great deal. This is the quiet superpower of tracking: rejections stop being wounds and start being data points with timestamps.
Look for patterns across rows, not inside them. Do your declines cluster around one poem, or spread across everything you send? The first is a revision problem, the second is usually a targeting problem: you may be sending quiet domestic poems to contests whose past winners are loud, political, and formally wild. Reading a contest's previous winners before you enter is the single cheapest research a poet can do, and the ledger tells you which contests deserve that research because you keep going back to them.
One more thing rejection rows are for: proof of endurance. The poets I have watched win over the years all have ledgers with ugly stretches in them, five, eight, eleven declines in a row. The rows kept them honest, and the rows kept them going, because a visible streak of effort is much harder to abandon than a vague memory of trying.
The Ledger Is the Long Game
Nobody frames a spreadsheet. I understand the resistance: poets want the muse, not the bookkeeping. But every working writer I respect keeps some version of this ledger, because the alternative is submitting on vibes, and vibes sent that poet's poem to the same contest twice.
So start tonight, and start small. Open a blank sheet, type the five column headings, add the sixth if you are brave, and give the whole thing its first row: pick your strongest poem, find it a contest with a real deadline, and send it somewhere it can be read this month. One row is not a system yet. But no poet who filled one row ever seems to stop there, and a year from now that sheet will know things about your writing that you cannot see from inside it.
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.