A query letter opens a professional conversation
A query letter is a concise introduction to a book and its author sent to a publishing professional who has asked to receive submissions. Its job is not to explain every chapter or prove that the manuscript will become a bestseller. It should make the project easy to understand, show why it fits the recipient's list or interests, and invite the reader to look at the pages or proposal according to the current submission guidelines.
That purpose helps you separate a query from other book documents. A synopsis tells the full story, a proposal develops a nonfiction project for a publishing decision, and a cover letter may accompany a requested file with different instructions. A query letter is a focused sales and context document. It gives a busy reader the information needed to decide whether the project belongs in the next stage of consideration.
Confirm the project before you draft
Write the query after the manuscript or proposal is ready for the kind of submission you are making. Confirm the title, genre or category, word count, format, target audience, and one-sentence premise. For nonfiction, clarify the book's subject, proposed audience, authority, and practical promise. For fiction, clarify the protagonist, central conflict, stakes, point of view, and ending. You do not need every detail in the final letter, but you need a stable project to describe accurately.
Check the recipient's current guidelines before personalizing the letter. Requirements can differ about subject lines, sample pages, attachments, exclusivity, requested materials, and the number of agents or editors contacted. Treat those instructions as part of the project brief. A polished query sent in the wrong format still creates avoidable friction, while a clear letter that follows the request signals that you can manage professional details.
Identify the book's most specific hook
The hook is the concise reason the book creates curiosity. It may be a protagonist facing an unusual problem, a conflict between two compelling forces, a distinctive setting, a practical transformation, or a question with consequences. Start with the detail that makes this project different from a broad category description. A novel is not only a romance, mystery, or fantasy; a nonfiction book is not only about productivity, history, or craft.
Draft several hook sentences and test each one against the manuscript. Does it name the right person or reader? Does it imply the central pressure? Does it suggest what could be lost or gained? Does it promise the experience the pages actually deliver? Avoid relying on adjectives such as gripping, powerful, or unforgettable unless the sentence also gives the reader concrete information. Specific nouns and verbs let the project create its own energy.
Pitch fiction through protagonist, conflict, and stakes
A fiction query usually needs to orient the reader around who the story follows, what disrupts that person's situation, what they want, and what stands in the way. Introduce the protagonist through a role, desire, or problem that matters to the plot. Then show the central conflict and the consequence of failure. The pitch can mention the key relationship, mystery, threat, or moral choice that gives the story its shape without summarizing every subplot.
Protect the reading experience while making the stakes clear. You can reveal the setup and the major decision the protagonist faces without listing every twist or explaining the ending in detail, unless the recipient specifically requests a synopsis. The query should leave the reader with a compelling question about how the situation will resolve. Make sure the question belongs to the manuscript, not to a surprise the book never actually explores.
Present nonfiction through audience and outcome
A nonfiction query should explain which readers the book serves, what problem or opportunity it addresses, and what the reader will understand or do after reading it. Name the book's approach, perspective, method, or argument without reproducing the table of contents. If the book responds to a specific gap, habit, misconception, or audience need, make that connection concrete. The goal is to show why this book should exist and why you are positioned to write it.
Separate a credible promise from an exaggerated one. A practical book can offer a framework, process, or set of decisions without promising that one method will solve every reader's situation. Explain the useful change the book is designed to support and identify the evidence or experience behind it. When a topic includes professional, legal, medical, or financial risk, describe the scope carefully and make clear where qualified review or specialist guidance is needed.
Use comparison titles with a clear purpose
Comparison titles help a recipient place the project in a current market and understand the audience you hope to reach. Choose books that share a meaningful trait with your project, such as tone, readership, premise, approach, format, or subject. Then explain the relationship in a short phrase. A comparison is useful when it gives context; it is weak when it is only a list of famous books that the project does not resemble in any practical way.
Keep the comparison focused on what the reader can expect rather than claiming that the book will dominate the market. For fiction, the comparison may combine a tonal or thematic reference with a premise-specific distinction. For nonfiction, it may identify a familiar approach and the audience, angle, or application your book adds. Recheck publication dates and recipient preferences when the submission requires current comparisons, and do not let this paragraph take attention away from the book itself.
Write an author bio that supports the project
The author bio should give the reader the information that makes your relationship to this particular book clear. Mention relevant professional experience, research, publication history, audience, community, or lived knowledge when it supports the project. A fiction bio can be brief and may include writing credits, genre-specific experience, or a detail that helps establish your connection to the story. A nonfiction bio should make authority and access understandable without turning into a full résumé.
Do not apologize for a short bio or fill space with unrelated accomplishments. A query is not a contest to include every credential. Choose the facts that answer the recipient's likely question: why is this author the right person to write this book, reach these readers, or speak to this subject? If the project involves claims that require expertise, be direct about what you know and what you have consulted or verified.
Make the opening and subject line do their jobs
The subject line and opening should help the recipient identify the project quickly. Follow the requested format first, then include the title, category or genre, and any other requested information. In the opening paragraph, state the reason for contacting this person if there is a genuine connection, such as a request, referral, event, or specific interest in the project. Personalization should be accurate and restrained; a generic compliment can make the letter feel automated.
Do not bury the book under a long explanation of your writing journey. The recipient needs context, but the project should arrive early. A direct opening creates confidence because it respects the reader's time and makes the letter scannable. Read the first paragraph alone and ask whether someone who has not seen the manuscript can tell what kind of book is being offered and why the message is addressed to them.
Handle sample pages and requested materials carefully
A query letter is only one part of a submission package. The recipient may request sample pages, a synopsis, a proposal, a full manuscript, or additional information in a particular order or file format. Prepare those materials before sending the query so the handoff is calm and consistent. Use the same title, author name, genre, word count, and project description across the letter and attached documents unless the guidelines call for a different presentation.
Proof the actual files you plan to send. Check that the opening pages begin where you intend, the synopsis or proposal matches the current manuscript, the filename is professional, and private notes or tracked changes are removed. Never assume that a previous attachment is still the right version. A submission workflow should make it difficult to send an old draft, an incomplete sample, or production comments meant only for your own revision.
Revise for clarity, accuracy, and restraint
Revise the query in separate passes. First check the project facts: title, word count, category, premise, character names, audience, and materials. Then check the pitch for sequence and logic. Can the reader see the situation, pressure, and stakes without rereading? Next, remove repeated claims, vague praise, unnecessary backstory, and sentences that describe the query instead of the book. Finish with a line edit for rhythm, grammar, names, and formatting.
Read the letter aloud and ask another trusted reader to summarize the project after one pass. Their summary will reveal whether the central hook is visible or whether a memorable side detail has taken over. Do not keep adding information to solve every possible question. A query succeeds through selection. Its purpose is to create an accurate, appealing doorway to the manuscript, not to replace the rooms beyond it.
Organize query materials in Awtter
In Awtter, keep the query letter connected to the manuscript version it describes. Use the Binder for the book's chapter structure, Notepad for the approved premise, audience, comparison notes, and author-bio facts, and History or snapshots for the draft state used in a submission. Organize can help you find repeated project terms and confirm that the query, synopsis, and opening pages use consistent names and language.
Create a separate working section for submission materials so private revision notes do not enter the exported package. When the manuscript changes, mark which query paragraphs need review instead of assuming that the old letter still fits. A visible relationship between the source draft and the submission copy makes it easier to update the hook, word count, sample pages, and synopsis together while preserving the version you already sent.
Use a query-letter checklist
Before sending, confirm that the query follows the recipient's current instructions, names the correct person, identifies the project clearly, and uses a concise subject line. Check that the opening hook is specific, the fiction pitch includes protagonist, conflict, and stakes, or the nonfiction pitch includes audience, problem, approach, and author authority. Verify the comparison titles, bio, word count, genre, sample pages, synopsis, proposal, filenames, and contact details.
Then send the letter only when the materials are ready and the project facts are stable. Keep a simple record of the recipient, date, version, requested materials, and response status, but do not treat silence or rejection as a verdict on your worth or the final potential of the book. A query is a professional invitation. Write one that represents the actual project with precision, follow the process carefully, and keep revising the manuscript according to the work it still needs.