How to track your queries and submissions

A querying campaign quickly outgrows memory. With dozens of agents or magazines out, each on its own clock and its own rules, "I'll just remember" is how writers double-query an agent, miss a withdrawal after an acceptance, or let a promising full quietly age out. A simple system fixes all of that — here's what to track and why.

Why a system beats memory (and a messy spreadsheet)

The cost of disorganization is concrete: querying the same agent twice marks you as careless; forgetting to withdraw a simultaneously-submitted piece after it's accepted elsewhere burns an editor; losing track of dates means you never know which queries are genuinely overdue. A spreadsheet can work, but it doesn't do anything — it won't tell you how many queries are still out, your acceptance rate, or which submission is your oldest. The point of a system is to answer those questions for you, instantly.

What to log for every query or submission

• The work — which manuscript, story, or poem it is.
• Agent or market name — and, for agencies, which specific agent (to avoid querying colleagues).
• Date sent — the anchor for every "is this overdue?" calculation.
• Status — pending, request, accepted, or rejected.
• Response date — so you can compute days-to-reply.
• Rejection type — form vs. personal, the single best signal of whether your pitch or your pages are the issue.
• Simultaneous flag & any fee — essential for clean withdrawals and budgeting.
• Notes — partial vs. full request, personalization used, "invited to resubmit."

The numbers a good log gives you back

Once the fields are filled in, the system earns its keep: how many are still in flight (so you know when to send the next batch), your average response time (so you can tell overdue from merely slow), your request and acceptance rates, and the form-vs-personal split that turns a pile of rejections into actual diagnosis.