Querying literary agents is a numbers game dressed up as a series of individual rejections, and the writers who get through it are usually the ones who figured out the "numbers" part early. If you're tracking each query as its own emotional event instead of one data point in a larger pattern, the process will wear you down long before the math has had a chance to work in your favor.
The math, stated plainly
Published-author survey data varies, but the shape is consistent: most successful queriers sent somewhere between 50 and 100 queries before landing representation, and most of those queries were rejections, non-responses, or silence. That's not a sign you're doing it wrong. It's the base rate. A single rejection tells you almost nothing about your manuscript. A pattern across thirty queries tells you a great deal — which is exactly why tracking matters more than any individual response does.
What a query tracker actually needs to answer
A sticky note with agent names on it isn't tracking — it's a list. A real tracking system needs to answer four questions at a glance, because these are the questions that turn a pile of rejections into an actionable pattern:
- Who have I already queried, and when? The obvious one, and the one that prevents the genuinely common mistake of accidentally re-querying someone six months later.
- What did I send them? A cold query letter, a referral, a contest placement, a Twitter pitch win — the method matters, because a pattern of "referrals get responses, cold queries don't" is information you can act on.
- What happened, specifically? Not just rejected-or-not. A form rejection and a rejection with detailed feedback are different signals. A request for a partial versus a full manuscript are very different outcomes that both count as "still in progress," but shouldn't be tracked identically.
- What's due for follow-up? Most agencies list an expected response window. Once you're querying more than a handful of agents at once, remembering whose window has closed without a manual check-in becomes its own part-time job.
Reading the pattern, not the rejection
The reason tracking matters more than any single response is that it turns "I got rejected" — an emotional event you have limited control over — into "12 queries, 2 requested a partial, 0 fulls yet" — a pattern you can actually act on. If zero agents are requesting pages, the query letter or opening pages likely need work, and that's worth knowing after 15 queries, not after 80. If agents are requesting full manuscripts but passing after reading them, the problem has moved to a different part of the book, which is also useful to know precisely because it's specific.
None of that diagnostic value exists if the only record is a gut feeling that querying "isn't going well." The pattern is the whole point, and a pattern needs data across every query, not a memory of the last one.
Keeping it simple enough to actually maintain
The tracker that works is the one you'll actually update after every query, which usually means: whatever tool you already have open when you hit send. A spreadsheet with agent, method, status, and a follow-up date column covers the essentials. If you're already tracking your manuscript elsewhere, keeping the query log in the same place removes the extra step of switching tools mid-submission, which is often the actual reason a tracking system quietly stops being maintained around query forty.
Bramblequill's Query Tracker is built around exactly those four questions — agent, method, status, and follow-up — attached directly to the book you're querying, so the log lives next to the manuscript instead of in a separate spreadsheet you have to remember to open. The tool doesn't change the math. It just makes sure you can actually see it.