What is Query Letter?
A query letter is the selective submission letter or form response used to persuade a literary agent or other appropriate publishing recipient to consider a book. It presents the hook/pitch, essential manuscript metadata, relevant positioning and author proof, while remaining only one possible component of a larger Manuscript Submission package.
What good query letter looks like
A strong query makes the book legible and compelling within the recipient’s requested form, keeps the pitch selective rather than recounting the full ending, uses accurate metadata and relevant author proof, follows current submission instructions, and does not substitute for requested sample pages, Synopsis, proposal, or manuscript file.
- Recipient fit: follow the current submission route and include personalization only when it is specific, true, and useful.
- Project identity: title, category/genre, approximate word count, age range or audience when relevant, and completion/status when requested.
- Pitch: present the central character/problem, goal or reader promise, escalating pressure, and meaningful stakes without summarizing every subplot or chapter.
- Positioning: use comp titles or concise market context when they clarify audience and shelf rather than merely name famous books.
- Author proof: include only credits, expertise, lived connection, platform, or debut context that helps evaluate this project.
- Close and materials: state requested attachments/pages only as needed, thank the recipient, and avoid demands or sales predictions.
A practical structure to follow
Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.
- Recipient fit: follow the current submission route and include personalization only when it is specific, true, and useful.
- Project identity: title, category/genre, approximate word count, age range or audience when relevant, and completion/status when requested.
- Pitch: present the central character/problem, goal or reader promise, escalating pressure, and meaningful stakes without summarizing every subplot or chapter.
- Positioning: use comp titles or concise market context when they clarify audience and shelf rather than merely name famous books.
- Author proof: include only credits, expertise, lived connection, platform, or debut context that helps evaluate this project.
- Close and materials: state requested attachments/pages only as needed, thank the recipient, and avoid demands or sales predictions.
Choose the right approach
Use the task, reader, and relationship among ideas to choose a structure instead of forcing every situation into one formula.
| Approach | Use it when | Why / what to watch |
|---|---|---|
| You need the full recipient-specific package/workflow | Use Manuscript Submission. | The query is only one possible component. |
| You need the persuasive letter/form pitch | Use Query Letter. | Own the hook, selective pitch, metadata, positioning and author proof. |
| You need to format the manuscript/sample pages | Use Manuscript Format. | Query prose and manuscript-file presentation are separate deliverables. |
| You need to reveal the complete plot and ending | Use Synopsis. | A query pitch creates selective interest; a synopsis lets the evaluator inspect the whole arc. |
| You need the author-credential paragraph specifically | Use Query Letter Bio. | Keep proof selective and relevant. |
| You need current market comparisons | Use Query Letter Comp Titles. | Verify the comparison job rather than stuffing titles into the query generically. |
Diagnose a weak draft quickly
Use the symptom first: identify what feels wrong, inspect the underlying writing decision, then make the smallest revision that fixes the real problem.
| Draft problem | What to inspect | Revision move |
|---|---|---|
| Recipient | Does this person actually request a query, and in what field/channel? | Follow the submission specification. |
| Hook/pitch | Can the book premise and central pressure be understood without recounting every turn? | Keep the query selective. |
| Metadata | Are title, category/genre, word count and other requested facts accurate? | Verify against the actual manuscript/project. |
| Positioning | Do comps/audience claims perform a specific credible comparison job? | Remove decorative or inflated positioning. |
| Author proof | Is every credential/platform fact relevant and verifiable? | Prefer a simple debut statement to weak padding. |
| Package boundary | Have you accidentally pasted a synopsis or full manuscript into the query itself? | Return extra deliverables to their requested fields/files. |
See the difference: before and after
A direct contrast makes the writing decision easier to see. The goal is not to copy the stronger sentence, but to understand which underlying choice changed.
The writer tries to fit the full plot, ending, three pages of biography, sample pages and every marketing idea into one “query letter.”
The query gives a clear hook/pitch, accurate manuscript metadata, specific positioning and concise relevant author proof, while the synopsis and sample pages remain separate requested deliverables in the submission package.
Why this is stronger: A query persuades the recipient to engage with the project; it does not replace every other submission document.
Revision rule: Keep the query selective and route complete-story, manuscript-file and proposal material to their own requested components.
How query letter changes by situation
The core principle can stay the same while the best execution changes with audience, format, evidence, genre, stakes, or length. Use these variations to adapt the technique rather than copying one pattern everywhere.
| Context | What changes | Practical adjustment |
|---|---|---|
| Email letter | Salutation/close and concise body may be appropriate. | Follow attachment/pasted-page rules separately. |
| Portal form | Hook, synopsis-like pitch, bio, comps and metadata may be separate fields. | Preserve each field’s job. |
| Referral/request context | Mention the legitimate context concisely if relevant. | Do not let warm-up displace the book. |
| Debut author | A concise honest debut bio is acceptable. | Do not invent credentials. |
| Nonfiction expertise/platform | Proof may carry more acquisition weight. | Keep claims relevant, current and verifiable. |
What to learn next
These links follow the writing decision rather than alphabetical similarity. Use them as a short path from the current concept to the next structural, evidence, revision, or publishing decision.
How to write query letter step by step
- 1Read the specific agent or agency submission instructions before drafting the final version.
- 2Write the book’s premise and stakes in plain language before compressing them into query length.
- 3Choose whether metadata/comps or character/premise should lead based on the project and recipient instructions.
- 4Build the pitch around the main causal line; remove secondary characters, lore, chapter lists, and ending explanation unless explicitly required.
- 5Choose comp titles by audience/category and comparison dimension, then verify title, author, year, and relevance.
- 6Add a short bio containing only decision-relevant proof; a simple debut statement is acceptable when stronger credentials are absent.
- 7Audit names, word count, category, personalization, attachments, and submission requirements separately for every recipient.
21 Query Letter examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
A museum archivist discovers that a supposedly lost painting has been hanging in a local courthouse for thirty years—but proving it may expose the forgery that built her mentor’s career.
When a night-shift courier receives a package for a tenant dead for a decade, returning it draws him into a surveillance network connected to his missing sister.
A burned-out school counselor inherits a rural motel where every guest leaves behind one memory they can no longer recall.
A climate reporter investigating a vanished river gauge learns the missing data was removed by the same engineer who designed the city’s new flood defenses.
A wedding photographer realizes one guest appears blurred in every image, including photographs taken years before the guest was born.
A language teacher accepts a translation job for a private peace summit and discovers one disputed phrase could restart the conflict.
Query Letter templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
Dear [Agent],\n\nI am seeking representation for [TITLE], a [word count]-word [genre/category] in which [hook]. [Pitch paragraph.]\n\n[Relevant bio/credentials.] Thank you for your time and consideration.
[TITLE] is a [word count]-word [genre] that will appeal to readers of [comp 1] and [comp 2] because [specific shared appeal].
When [inciting event], [protagonist] must [goal], but [obstacle]. If [failure], [stakes].
Common mistakes to avoid
- Treating the query as a universal template that overrides an agent’s current submission instructions.
- Using a rhetorical question, autobiography, or generic praise before the recipient knows what the book is.
- Turning the pitch into a full synopsis with every character, twist, chapter, or ending beat.
- Using blockbuster comps as quality claims instead of explaining a realistic audience or reading-experience comparison.
- Padding the bio with unrelated jobs, weak platform numbers, apologies, or unverifiable expertise.
- Sending stale metadata, misspelled names, wrong pronouns/titles, or materials the recipient did not request.
Final revision checklist
- Does the opening make the purpose clear quickly?
- Is every important claim, detail, or example doing a distinct job?
- Could a reader misunderstand any pronoun, transition, time reference, or instruction?
- Is the tone appropriate for the relationship and situation?
- Can you remove repetition without removing necessary context?
- If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Questions about Query Letter
What is Query Letter?
A query letter is the selective submission letter or form response used to persuade a literary agent or other appropriate publishing recipient to consider a book. It presents the hook/pitch, essential manuscript metadata, relevant positioning and author proof, while remaining only one possible component of a larger Manuscript Submission package.
What makes Query Letter effective?
A strong query makes the book legible and compelling within the recipient’s requested form, keeps the pitch selective rather than recounting the full ending, uses accurate metadata and relevant author proof, follows current submission instructions, and does not substitute for requested sample pages, Synopsis, proposal, or manuscript file.
How do I write Query Letter?
Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.
What should I avoid when writing Query Letter?
Treating the query as a universal template that overrides an agent’s current submission instructions. Using a rhetorical question, autobiography, or generic praise before the recipient knows what the book is. Turning the pitch into a full synopsis with every character, twist, chapter, or ending beat.
How long should a query letter be?
Follow the recipient’s guidelines; many effective queries are concise and fit comfortably on one page or a few short paragraphs.
Should I mention every subplot?
No. Focus on the central protagonist, conflict, stakes, and the information needed to understand the book’s primary hook.
Should a query letter reveal the ending?
Usually the query pitch does not need a full synopsis-style ending, but conventions vary by category and submission guidelines. Follow the agent or publisher’s requirements.
How personalized should a query letter be?
Personalization is useful when it is genuine and relevant. Forced praise or generic references are weaker than a concise reason the project fits the recipient.