QueryManager vs QueryTracker: What They Are and When to Use Them

Writers preparing to query literary agents for the first time encounter both QueryManager and QueryTracker in short order — and frequently conflate them, assume they serve the same purpose, or wonder whether they need accounts on both. The confusion is understandable: the names are similar, both appear in the context of querying, and neither tool announces its function with particular clarity to newcomers.

They are, however, almost entirely unrelated. One is a tool built for agents. The other is a tool built for writers. Understanding the distinction changes how you approach both.

QueryManager: the agent's submission inbox

QueryManager is a platform that literary agents use to receive, organise, and respond to query submissions. When an agent adopts QueryManager, they configure a custom submission form — specifying exactly what they want writers to send (query letter, synopsis, first pages, genre, word count) — and embed that form on their agency website or submission guidelines page.

As a querying writer, your interaction with QueryManager is brief and transactional: you find an agent's submission page, fill out their QueryManager form, attach whatever materials they've requested, and submit. You'll typically receive an automated confirmation email. That's largely the extent of it from the writer's side.

What happens after you submit is entirely on the agent's end. QueryManager gives agents a dashboard for tracking their query inbox — marking queries as read, requesting materials, rejecting, or flagging for follow-up. You don't have a QueryManager account. You don't log in to check your submission status. You submit through their form and then wait.

When you'll encounter it: On the submission guidelines or "Query Me" page of agents who use the platform. Not all agents use QueryManager — many accept queries by email, and others use competing submission management tools. Whether a given agent uses QueryManager is determined entirely by their agency's preferences.

QueryTracker: the writer's research and tracking database

QueryTracker is a tool built entirely for querying writers. Its core function is twofold: it provides a searchable database of literary agents and their submission preferences, and it gives writers a system for tracking their own query submissions across multiple agents.

The agent database on QueryTracker aggregates information about hundreds of agents — what genres they represent, their submission requirements, their response time statistics (derived from data contributed by the community of users), and notes from other writers who have queried them. This research function is QueryTracker's most distinctive value: before querying an agent, a writer can look them up on QueryTracker to check recent response rates, see whether other writers have received requests or rejections in similar timeframes, and read community notes that sometimes contain genuinely useful detail about what a given agent is currently seeking.

The tracking function allows writers to log each query they send — the agent, the date submitted, how they submitted (email, QueryManager form, another portal), and the outcome — and to maintain a running view of where their manuscript stands across all active submissions. It is, in essence, a submission spreadsheet with agent intelligence built in.

When you'll use it: Throughout the entire querying process. Many writers begin using QueryTracker during the research phase, weeks or months before sending their first query, and continue using it to track submissions until they either sign with an agent or decide to stop querying.

Side by side

"If there's a book that you want to read, but it hasn't been written yet, then you must write it."

— Toni Morrison, widely attributed; consistent with Morrison's documented interviews

Morrison's observation is often quoted as encouragement toward the act of writing. It applies equally to what querying asks of a writer: the book exists. The work of finding it a home is a separate labour, with its own tools, its own rhythms, and its own patience required.

How they fit together in practice

In a typical querying workflow, QueryTracker and QueryManager don't interact — they simply appear at different moments in the same process.

A writer uses QueryTracker during the research phase to identify agents who represent their genre, review response statistics, read community notes, and build a prioritised query list. When it's time to submit to a specific agent, the writer goes to that agent's submission guidelines and follows whatever process the agent requires. If the agent uses QueryManager, the writer fills out the QueryManager form and submits there. If the agent accepts email queries, the writer sends an email. If the agent uses a different portal entirely, the writer uses that.

After submitting, the writer returns to QueryTracker and logs the submission — noting the date, method, and any relevant details. If a response arrives (a rejection, a request for more material, or a full manuscript request), that gets logged too. QueryTracker's community statistics are populated by writers doing exactly this, which is why the response time data is reasonably reliable as a rough guide.

The practical upshot: QueryTracker is where you do your homework and keep your records. QueryManager is a door you walk through when a specific agent has installed it. You do not need to think of them as competing options, or as tools that duplicate each other's function. They operate in entirely different lanes.

A note on other submission portals

QueryManager is not the only submission management tool agents use, and first-time queriers sometimes encounter others — Submittable (more common for literary magazines and small presses than for agent queries), publisher-specific portals at larger agencies, or agency-built systems. The underlying logic is always the same: the portal exists to organise the agent's incoming queries, and the writer's role is to use it to submit and then wait. What varies is the interface and what specific materials each agent requests.

QueryTracker, by contrast, remains a constant in the writer's workflow regardless of how each individual agent accepts submissions. It doesn't matter whether you submit by email or through QueryManager or through any other portal — the submission gets logged in QueryTracker the same way.