Queryfest, part XXX: is it a mirage, or do I spy the finish line at long last?


No, you’re not seeing things, campers: this is indeed the last Queryfest post. It’s been a long time coming, as the song would have it, and we’ve wandered down a few side paths along the way, but this is, as they say, it.

Yes, I’m relieved, too. Of all the unpleasant tasks that fall to the lot of the aspiring writer, composing query letters is perhaps the most universally-resented necessity. (Synopsis-writing would be first by a mile, but not all aspiring writers are aware that the more successful they are in getting published, the more often they will to have to churn out synopses.) Not only do most writers of book-length works feel, justifiably, that if their talents leaned in the direction of one-page documents, they would have gone in for writing brief epistolary novels, if not short-form poetry — they believe, and not entirely unreasonably, that the ability to write an engaging letter is not the best proof that one can write a novel. Or a memoir. Or a book proposal.

While that may well be true, there’s a pretty good reason that agencies expect anyone who intends to work with them to learn how to write a professional-sounding query: it’s quite an efficient means of assuring that the writers they pick up will have gained at least a minimal working knowledge of publishing. Think about it: as we have seen throughout this series, in order to whip up a solid query letter, a writer must figure out her book’s category, do a bit of research on what agents represent that type of book, come up with a 30-second pitch of the book’s premise or argument (try timing a dramatic reading of the descriptive paragraph sometime), ponder the book’s selling points and/or one’s own platform, and include a SASE.

Honestly, would you have known to do any of that just because you had the inspiration and persistence to write a book? Indirectly, the agent of your dreams has prompted you to take a crash course in many of the skills you will need to become a happily-published author.

Oh, you thought I had lingered on the constituent parts of the query for months on end because letter-writing fascinated me?

To demonstrate just how far we have all come over the course of Queryfest, here is one final example, written by yet another brave, generous, and naturally creative member of the Author! Author! community, A. Verage Reader. I was delighted to see A’s query pop into my inbox: not only does her book sound like a real page-turner, but she has also, like so many well-meaning, talented aspiring writers across the globe, submitted a query that presents our hypothetical agent, Hawkeye McAgentson of Picky & Pickier Literary Management, with a quandary: should she base her decision to request pages upon the story A is telling in her query, or upon how she presents it and herself?

And already, the intrepid few who have been following this series from the very beginning fling your hands into the air. Yes, thoughtful, sharp-eyed, and faithful readers? “But Anne,” you point out, “realistically, would Hawkeye be the one making this decision? Yes, her staff might pass the most successful queries on to her, but Hawkeye is usually busy selling her clients’ books to read every query personally, isn’t she? So wouldn’t the first-round weeding out be performed by our old pal and nemesis, Millicent the agency screener?”

Quite right, Queryfest stalwarts, and since this often comes as a gigantic surprise to first-time queriers, how glad I am that you reiterated it. Contrary to popular opinion, most well-established agents simply do not have time to read the thousands of queries they receive, much less to narrow down those thousands to the three or four manuscripts they can reasonably take on per year. That’s why agencies employ Millicents, to reject the overwhelming majority of queries and submissions. That way, the agent can concentrate upon reading the tiny percentage of manuscripts and book proposals that Millie deems well-written, written well for the target audience (not always the same thing), market-ready, something the market is ready for (see last parenthesis), and a storyline or argument likely to interest Hawkeye.

I know, I know: having to make it past Millicent’s notoriously nit-picky scrutiny can seem like an insurmountable barrier. Most queriers would prefer that Hawkeye read every single query and submission herself — or, better still, just allowed potential clients to send the first 50 pages instead of a query. Honestly, though, when yours is one of the dozen or so on Hawkeye’s desk, you’ll be deeply grateful to Millicent for freeing up her boss’ schedule enough to read your work closely.

In that spirit, let’s slip into Millicent’s reading glasses and take a gander at A’s query. If you could request manuscripts from only a couple of the several hundred queriers who contacted Hawkeye this week, would you say yes to this one? (As always, if you are having trouble seeing the details, try holding down the COMMAND key and pressing + to enlarge the image.)

Actually, that was sort of a trick question, wasn’t it? Naturally, Millicent could not have said yes to this query: I don’t employ a Millicent, for the exceedingly simple reason that I am not an agent. I am a freelance editor. And even if I were an agent, I would expect my Millicent to be aware that the proper formal salutation for a lady with a Ph.D. is Dear Dr. Mini.

Actually, the only people I make call me Dr. Mini are medical doctors. It bugs them to such an astonishing degree that as both a trained social scientist and a writer of comedy on serious issues, I feel an intellectual duty to try to find out why.

So had A. sent me this query, I would not have been in a position to give her the answer she wanted. By the terms of this contest, though, she did not send it to me — she sent it to Hawkeye. While the address (or, in this case, non-address) at the top clearly indicates that she intended to mail it to me.

This, I’m afraid, is usually an instant-rejection offense — and far more common than any of us would like to think. Oh, it’s a completely understandable faux pas: A. was probably printing out several queries at once, and the one for this Mini person accidentally ended up in the envelope addressed to Picky & Pickier. Happens all the time. Yet you can hardly blame Hawkeye’s Millicent from taking umbrage at being expected to read a paragraph about how much A. admires somebody else’s blog.

Not that somebody else isn’t flattered, of course. Heaven help A., though, if Hawkeye happens also to blog.

I’m harping on this not only because it is one of the most common (and least-often acknowledged) reasons queries get rejected, but also because about a third of the brave, generous souls who volunteered their query letters for scrutiny here stumbled into precisely the same trap. So, reliably, do between a quarter and a third of the entrants of any writing contest: the rules call for one thing, and the entrant does something else. Care to guess what that means for the contest entries in question?

Uh-huh: “Next!”

Actually, the response should be closer to, “Hey, thank you for saving me some time!” In practice, queries, submissions, and entries that do not conform to expectations, especially when the recipient has taken the time to list those rules for all to see, are a positive boon to overworked professional readers. Millicent, her Aunt Mehitabel, the veteran contest judge, and Maury, their cousin who works as an editorial assistant in a small publishing house, can simply reject all of those documents at first glance. That takes much, much less time than reading them in their entirety — and leaves extra time in their respective days to devote to the queries, submissions, and entries that did follow the rules.

In case I’m being too subtle here: read any submission guidelines carefully before you seal that envelope or hit SEND. Assuming that you know what they call for — or, as many aspiring writers presume, wrongly, that every agency or contest out there must necessarily want to see precisely the same things — can be exceedingly costly. Invest the time in double-checking.

Do I hear some tender-hearted souls out there sighing? Yes, I feel sad for all of the good writers with fine books who get rejected on the basis of simple mix-ups, too. Tell you what: let’s pretend that I gave A. the pep talk in that last paragraph before she sent in her query. Let’s further assume that Hawkeye actually does write a blog aimed at helping potential clients, because, honestly, it’s less work for me that way.

Here’s what the query might have looked like in that alternate reality. Again, if you were Millicent, how would you respond?

Do I sense some hesitation out there? “Gee, Anne, I want to read this query with the attention it deserves, but having read so many similar letters throughout the course of Queryfest, I’m afraid I find the presentation here a trifle distracting. Why, for instance, is the date located in the bottom margin, rather than the top, where it belongs? Why, too, is it in a different font? Speaking of fonts, this doesn’t look like 12-point in either Times New Roman or Courier, the standard fonts for the U.S. publishing world. If I had to take a wild guess, I would say it was Calibri 11 point. While I am nit-picking about format, why are the closing and contact information tabbed to 2.5″, rather than halfway across the page? And shouldn’t A. have left room for a signature?”

Congratulations, hesitators: you have begun looking at pages like a screener. Yes, the formatting is off here; the type is indeed too small for any writing intended for submission to an agency. While neither will necessarily present a reading problem — the content of the letter is perfectly clear here, right? — both would raise some reasonable concerns about whether the manuscript being queried would be in standard format. Millicent would have some legitimate reason to expect that it wouldn’t.

And why is that a problem, long-time readers? Chant it with me now: even the most talented writer unfamiliar with the norms of publishing will be more time-consuming for an agent to represent than a similarly-talented writer who has done his homework. The single quickest way for Millicent to judge this is to check how closely the submission adheres to standard format for book manuscripts.

So, again, Millicent may have a reason to say, “Thank you for saving me some time!” That’s sad, because an easily-fixed set of presentation problems have prevented a reading of A’s query on its content.

On the bright side, the choice of typeface was probably not what put Millicent off this version. While not adhering to the industry-standard fonts is seldom a deal-breaker in a query (as it can be in a submission), it’s undeniably true that to the pros, a query in those fonts just seems more professional than one that isn’t.

Don’t not sure why? Okay, here’s A’s query again, with nothing changed but what the hesitating many pointed out. If you were Millicent, would you feel more confident that the writer of this version would be able to send you a manuscript in standard format, or the writer of the original?

Ah, that looks more familiar, doesn’t it? But now that the non-standard formatting no longer distracts your eye, Millicent-of-the-moment, do you notice anything else? Here’s a hint: the overwhelming majority of queries exhibit this problem to a greater or lesser extent.

If, after you perused A’s query carefully, you flung your hand into the air and cried, “There are quite a few typos here — missing commas, misspelled words, and a misused semicolon. Oh, hey, there’s also a dropped word or two. And is it me, but is there an extra space in the non-standard sign-off?” give yourself a gold star for the day. Millicent is constantly astonished at how many queries are apparent neither spell-checked nor proofread.

And no, in response to what half of you just thought very loudly indeed, performing the former does not obviate the necessity of performing the latter. Spell-checkers are not infallible; neither are grammar-checkers. (For some reason that surpasses human understanding, mine is constantly urging me to use the wrong form of there, their, and they’re and telling me that reflexive pronoun use is always wrong.) There is, I’m afraid, just no substitute for good, old-fashioned proofreading.

Why? Well, now that we know that conclusion-jumping is part of Millie’s job, what do you think she might reasonably assume about a manuscript if the query for it contains misspellings and typos?

Yep. And since an unproofed submission is likely to get rejected, anyway…

Given the grave importance of getting the small details right, how does one maximize the probability of catching small problems before sending off that query, campers? That’s right: since every syllable an aspiring writer submits to an agency is a writing sample, it’s worth your while to re-read your query IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD. It’s simply the easiest way to catch typos, spacing problems, and missing words.

Yes, your neighbors may think you’re a little strange, but hey, no one said the path to publication was easy.

Before I show you A’s query again with that array of minuscule problems corrected, there’s another element in that last draft that might raise Millicent’s delicate eyebrows, as well as her doubts about the manuscript’s being in standard format. Any guesses? There’s another gold star at stake.

If you leapt to your feet and cried, “Why, I had not thought about it on earlier read-throughs, but the numbers under 100 are presented in this query as numbers. In standard format for book manuscripts, those numbers would be written out in full: eighteen, not 18,” help yourself to a gold star out of petty cash. As counterintuitive as it may seem, queries are frequently judged as though they were manuscripts; not doubling a dash would be a red flag, too.

Yes, really. Millie’s boss is not going to have time to proofread her clients’ work before submitting it to a publishing house.

So let’s take this query seriously as a writing sample and buff away those little problems, shall we? While we’re at it, let’s change that closing to something more traditional for a formal letter. Do you want to ask for a partial now, Millicent?

Stronger, but I have to say, this version still feels a bit minimal to me. Not merely because there’s quite a bit of room left on the page — a temptation to add plot elements that most queriers would not be able to resist — but because the wording in the opening paragraph and the target audience paragraph are a little, well, ungraceful. Almost as if providing this information were not a compositional pleasure, but an irksome requirement.

Imagine that. Why, an innocent bystander might almost think that writing a query is just an annoying hoop through which aspiring writers have to leap in order to gain a fair reading of their manuscripts.

Surprisingly often, queries make that pervasive attitude quite apparent — and that’s never helpful to a book’s chances. Even if the querier in question happens to phrase distaste for the entire process beautifully, it’s not Millie’s fault that the system is set up this way, is it?

Besides, a flat telling does not show off anyone’s writing to its best advantage. That is, alas, the case here: the writing in those informational paragraphs would not match the tone or writing style of the book description. Based on them alone, Millicent would have a hard time figuring out what A’s writing style was.

Another problem: the importation of generic elements. As we have discussed many times throughout Queryfest (although, in fairness, after A. sent in her query for critique), Millicent sees that line about the word count in about half of the queries that cross her desk: apparently, it’s in quite a few boilerplates floating around out there. That doesn’t mean it is well-written, or that including will, as so many new queriers evidently believe, make your letter sound professional. At this point in querying history, it just sounds like someone else’s writing — and not very interestingly-phrased writing at that.

Why is that problematic? Pull out your hymnals and sing along, Queryfesters: contrary to popular opinion amongst queriers, a query is a writing sample. Since stock phrases are, by definition, not original writing, it’s a better use of page space to write your letter from scratch.

At the risk of repeating myself, I always advise against including word count in a query unless an agency’s submission guidelines specifically ask for it. Fortunately, A’s word count is well within the expected range for her chosen book category, but being much under 60,000 words (estimated at 250 words/page in Times New Roman x the number of pages in the manuscript) or over 100,000 provides Millicent with, you guessed it, a legitimate reason to reject the query.

“Why, thank you!” she exclaims. Or she should.

Since a query is in fact a writing sample, I hesitate to rework the phraseology in order to encourage Millicent to spend more time with this letter: after all, she wants to know what A. sounds like on the page, not me. Far be it from me, too, to compound the already widespread problem of generic query phrasing by adding a new prototype to the mix.

Were I A., however, I might express these sentiments rather differently. A great start: being more specific about why this book is right for Hawkeye. This is something you might like to represent does, you must admit, does beg the question, “Okay, why?” (And what, Millicent wonders, prevented A. from querying her boss before?)

And a forest of hands sprouts in the ether. Yes? “You’ve lost me, Anne,” weary queriers the world over protest. “I get that it’s worth my while to personalize each query slightly, but A. has already done that: she brought up Hawkeye’s blog. Since she’s a long-time reader, does she honestly need to paraphrase the agent’s expressed protagonist preferences, too?”

It’s not strictly necessary, perhaps, but why pass up the opportunity to help Millicent gain a sense of what’s special about this storyline — or a dandy opportunity to say, essentially, “Hey, Hawkeye, I’ve not only read your blog — I have absorbed what you have been saying. Here I am, demonstrating that. Wouldn’t I be good at incorporating your feedback as my client?”

Sound like a tall order for a non-obsequious first paragraph? Not at all: the key lies in specificity, combined with a professional tone. And speaking of creating a professional impression, since the YA market is aimed at readers from 13 to 17, is it really necessary for A. to point out that her book is geared toward that age range?

Seems less forced now, doesn’t it? In this version, the reader’s focus is right where it should be: on the story.

So let’s talk about how A. might render that more appealing to everyone’s favorite screener. To get us started, let’s take a few steps back. Remember a few minutes ago, when I mentioned the desirability of reading one’s query IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD before sending it off? Give that a try now, please.

It’s not always clear to whom they refers, is it? That’s quite common in book description paragraphs, I’m sorry to report: because queriers are so eager to cram as much of the storyline as possible into the letter, they frequently include so many plot twists and introduce so many characters that Millicent can’t follow what’s going on.

That’s a real shame here: A. has worked in some delightfully unexpected specifics into this description, but they are getting lost. While that line about the father’s body and the mother’s mind is quite nice, the book description leaves us guessing why going to Poland will remedy the situation; indeed, the phrasing of that third sentence could be interpreted to mean that the mother is left with only one choice, not Meghan. Why Poland, and not, say, Belgium? While we are speculating, what is a Holy Apprentice, and why is it capitalized?

I have no idea; I’m merely asking what Millicent would. Not having read the manuscript in question — which sounds awfully darned exciting, I would only be guessing on these points. So please forgive me, A., if I get the plot wrong as I polish out the question-raisers.

I’m going to begin by highlighting those thus eye-catching bits about the parents and the possessed teddy bear. And while I’m at it, I shall to remove the impression, created by the repeated use of to be, that this is a story that’s told, not shown. More sentences in the active voice will also convey the subtle impression — and, I suspect an accurate one — that this is a fast-paced book.

Ha! If you were looking for additional evidence that it’s significantly more difficult to catch typos on a backlit computer screen than in hard copy, seek no more: as I was tinkering with the text, I noticed that I had missed that problematic punctuation and structure in the last sentence of the fourth paragraph. I shall go ahead and correct it now; let this be a lesson to us both. While I’m nit-picking, I’ll move A’s e-mail address to beneath her phone number. Millicent is more likely to look for it there.

Again, I don’t know if this is how the plot progresses; I have not read the book. Neither has Millicent, though, and she can judge its potential only by what is actually in front of her: the query. Best of luck with it, A!

Now that we have applied Queryfest principles to a wonderfully broad array of readers’ letters to agents, let’s turn our attention to the bigger picture. What have we learned on a larger level about querying?

Six things, I hope — no, make that seven. And just to keep things interesting, the first few may on the surface appear to be mutually contradictory.

First, a successful query letter must contain certain elements, elements that are surprisingly often absent in the prototypes one finds floating around the web. The most frequent omission: a polite opening that gives the agent at least some vague sense of why you picked her, out of all of the agents currently treading the earth’s crust, to approach.

Or, indeed, giving her some clue of what you think she represents. Millicent’s constantly asking herself, “What makes this querier think my boss would be remotely interested in this type of book? As far as I know, she has never sold anything like it.”

I think we all know why that query showed up on her desk: someone did not do his homework well enough to learn that agents specialize. Or to understand why it’s in any querier’s best interest not to make an agent guess why his manuscript would be a good fit for the agency.

Oh, there are some good reasons explanations on these points tend to turn up in prototypes: it’s not a one-size-fits-all feature. A writer would have to do some actual research, not only investing time in learning about each agent he approaches, giving some serious thought to what kind of book he has written, and figuring out the best matches. That’s a far cry from the extremely limited plug-your-book-category-into-a-search-engine research from which most first-time queriers derive their query lists.

Which leads me to Overarching Lesson #2: Because the single easiest kind of query to reject is one for a type of book an agent does not represent, personalized queries tend to work much better than generic ones.

“Oh, great,” I hear the masses mutter. “I’ve been working for months, even years, to get my basic query letter down to a single page without cheating on the margins or font. Are you gearing up to tell me that I will need to write an entirely fresh missive for every single agent I approach?”

Not entirely, no: as we saw in today’s extraordinarily fruitful example — thanks again for volunteering, A! — only the first paragraph would have to alter, in most instance. Unless you plan to gain a new credential or two between the time you send Query A and when you pop Query B into the mailbox, you should be able to use the bulk of a well-written query repeatedly. However, it’s never, ever, EVER a good idea to use an entire query letter again wholesale.

Why not, you ask? Do I hear sweet music in the distance? Like any other reader, individual agents have individual likes and dislikes. As a logical result, there is no such thing as a query letter that will please every agent currently in practice.

That’s why, in case you had been wondering, I have devoted so many months to Queryfest: my aim has been not to help you construct a generic letter that will work for every agent to whom you might conceivably decide to send it, but to assist you in ferreting out problems with the personalized missives you’re constructing for each one. Yes, you may well reuse sentences and even entire paragraphs from letter to letter, but as anyone who has had much contact with agents can tell you, these people are not generalists.

What? Still too subtle? Okay, I shall hoist a brick through the nearest window: while Millicents share common pet peeves, each agent, and thus each Millicent, is looking for slightly different things in a query letter.

Stop groaning; it wouldn’t have made good strategic sense to send an identical letter out to everyone, anyway, for reasons we have been discussing for months now. Besides, there is no such a thing as a universally perfect query letter, one that will wow every agent currently hawking books on the planet. It is logically impossible: agents represent different kinds of books, so the moment you mention that your book is a Gothic romance, it is going to be rejected by any agent who does not represent Gothic romances.

It honestly is as simple as that sometimes. Coming to grips with that — and doing the research necessary to avoid knee-jerk rejection — will make you a much, much happier querier than if you cling to the unfortunately ubiquitous belief that the only reason queries ever get rejected is due to some fundamental flaw in the book.

That can happen, of course, but the vast majority of the time, other problems send Millicent’s hand flying toward the form-letter rejection pile. Even if your query side-steps all of the usual pitfalls, however — and I hate to tell you this, because the arbitrary forces of chance are hard to combat — even if your letter is precisely what your targeted agency’s screener has been told to seek amongst the haystack of queries flooding the mailroom, it might still end up in the reject pile if the screener or agent is having a bad day.

What factors might produce that outcome, you ask with fear and trembling? A million and one that are utterly outside the querier’s control.

If the agent has just broken up with her husband of 15 years that morning, for instance, it’s probably not the best time to query her with a heartwarming romance. If she slipped on the stairs yesterday and broke both her wrists, she’s probably not going to be all that receptive this week to even the best knitting book in recorded history. And if he has just sprained his ankle in tripping over that stack of manuscripts he meant to read two months ago, it’s highly unlikely that any query is going to wow him within the next ten minutes, even if it were penned by William Faulkner, Toni Morrison, and William Shakespeare in an unprecedented show of time-traveling collaboration.

No writer, however gifted, can win in such a situation; even the query that wins most will lose some. Don’t squander your precious energies worrying about it.

That being said, a strategic-minded querier can avoid sending e-mailed queries or submissions over the weekend, the most popular time to hit the SEND button: Millicent’s inbox is pretty much guaranteed to be stuffed to the gills on Monday morning. Ditto with the first few days after her boss has returned from a writers’ conference, Labor Day, or, heaven help us, the single heaviest querying time of all, immediately after January 1. Best to avoid slipping anything you want her to approve under her nostrils then.

Unless, of course, she’s just fallen in love, or her college roommate just won the Pulitzer Prize in journalism, or she’s found a hundred-dollar bill on the street. Since you probably will not be the first to know if any of those things happens, though, you can’t possibly plan your querying schedule around them. I feel another aphorism coming on: as there will inevitably be aspects of querying success that you cannot control, you will be a significantly happier writer in the long run if you accept that there is inevitably an element of luck involved — as well as writing talent, marketing savvy, and query-construction skill.

To be brutally honest, the luck part took me quite a long time to accept myself. I once received a rejection from an agent who had taken the time to hand-write at the bottom, This is literally the best query letter I have ever read — but I’ll still have to pass. As if that was going to make me feel any better about being rejected.

Can you wonder that this compliment annoyed me far more than it pleased me? Like so many queriers, my mind flooded with resentful questions. Had the agent just completed a conference call with every editor in the business, wherein they held a referendum about the marketability of my type of novel, voting it down by an overwhelming margin? Had she suddenly decided not to represent the kind of book I was presenting, due to a mystical revelation from the god of her choice? Or had the agent just gotten her foot run over by a backhoe, or had gotten engaged five minutes, or decided to lay off half her staff due to budget problems?

Beats me; I’ll never know. Which is kind of funny, because I’ve had some very nice chats with this agent at conferences since.

Whatever was going on at that agency, it was beyond my control. Until I am promoted to minor deity, complete with smiting powers, recipes for infallible love potions, and telepathic control of the mails, I just have to accept that — ready for Overarching Lesson #3? == a writer has no way of affecting when any query (or manuscript, or published book) is going to hit an agent, editor, contest judge, reviewer, or reader’s desk.

Admittedly, as an agented writer, I do have some control over when my agent sees my manuscripts — but even then, it’s up to him when to read them. You can lead a horse to water, etc.

My advice: concentrate on the aspects of the interaction you can control. Like, say, the matters we have discussed today. Or the writing in your query.

Why? We have only to consult Overarching Lesson #4: since every syllable of a query packet is a writing sample, it makes sense to regard the descriptive paragraph not just as a super-fast plot summary, but as an invitation to show off your storytelling skills.

As we saw in today’s example, in an otherwise laudable attempt to try to place as much of the plot or argument in front of Millicent, many queriers simply try to do too much on the querying page. Honestly, all that’s required at this stage is a lively, book-category-appropriate description of the premise, presenting your protagonist as an interesting person in an interesting situation (for fiction), you as an interesting narrator of your experiences as an interesting person in an interesting situation (for memoir), or your credentials as the world’s best person to argue about an important issue or event (for nonfiction).

Piece o’ cake, right?

Not really, but truly, it’s not as hard as most queriers make it for themselves. Just tell your story in your own voice, rather than in generic-sounding summary statements: it’s the best way to convince Millie that you are one heck of a storyteller.

Above all, be original — and yes, I’m aware that’s not very common querying advice. Consider, however, overarching Lesson #5: as tempting as it may be to make your book sound like a recent bestseller (or to claim it’s the next one), hard-sell techniques do not work in queries or pitches. Since you have so little time to impress an agent, it’s better strategy to use it not to sound like everybody else.

Or, to put it bit more bluntly: if your query does not make it plain how your book is unique, it’s probably not going to impress Millicent. Trust me on this one.

But don’t beat yourself up if your best efforts doesn’t hit a home run every time. Recall, please, Overarching Lesson #6: because of OLs Nos. 1-5, queries get rejected all the time for reasons that have nothing to do with the writing quality or marketability of the book in question. It does not follow logically, then, that if a query gets rejected, the book is necessarily not ready for publication — or, as many disappointed queriers assume, that a rejection from one agency equals a rejection from the industry at large.

Yes, I know: it doesn’t feel like that when you’re trying to work up energy to send out Query #19 right after Rejection #18 arrives. It can seem almost impossible to pick yourself up, dust yourself off, and proceed to the next name on your agent list right away, but believe me, the longer that rejection sits on your desk, the harder it will be to work up energy to do it at all.

Please, for your own sake, don’t give yourself time to talk yourself out of sending the next one. Keep pressing forward, and bear in mind Overarching Lesson #7: the only manuscript that stands no chance whatsoever of interesting an agent and getting published is the one that sits in a drawer, perpetually unqueried.

I wouldn’t kid you about that. So try. And keep trying. Your writing is worth it.

Oh, and pat yourself on the back for being serious enough about your writing career to have plowed all the way through Queryfest; it has been a long, hard road. But you don’t come to Author! Author! just to pass the time, right? Keep up the good work!

Queryfest, part XXIII: Grace is in the details. So, today, is Catherine.

Have you been finding the real-world examples we’ve been examining of late constructive, campers, or have you been twiddling your thumbs, tapping your fingers, and wishing with all of your might that Queryfest might end, so we might get back to discussing craft? Or — and I must admit, I would have begun suspecting this, had I been on the reading end of Author! Author! for the last couple of months — have you begun speculating that I’ve been stretching our discussion of querying out as long as possible in order to discourage all of you from sending out letters to agents before the Great New Year’s Resolution Paper Flurry of 2012 roars to a close?

Okay, I’ll admit it: I have been dragging my feet a trifle, but I honestly have been extremely busy. I’m running an editing special on query packets this month and next, and honestly, I’ve been swamped. (There are a few slots still available, should you be interested, but they’re booking up fast.) I have been enjoying showing you just how big a difference a few relatively minor revisions in a query letter can make to how it strikes the weary, over-taxed eyes of our old pal, Millicent the agency screener.

For those of you new to the mysteries of querying, Millicent is the collective moniker of the legions of sharp-eyed, hard-working, literature-loving (yes, in spite of everything) assistants employed by agencies large and small to process the thousands upon thousands of query letters they receive each year. At most agencies, Millicent is also the first reader of requested manuscripts, winnowing the hundreds of submissions down to the few that her bosses, the agents to whom aspiring writers address their queries, have time to read. In a very real sense, then, Millicent is the audience at whom a savvy querier or submitter should be aiming his efforts.

Most aspiring writers are a trifle shocked to learn of Millicent’s existence; pretty much every writer tends to assume that the agent of his dreams has time to peruse, if not each and every query sent to her attention, at least one’s own. That’s the agent’s job, isn’t it, to seek out exciting new literary talent?

Actually, it isn’t, at least not primarily. A traditional agent — as opposed to the kind that makes a living not by selling books for authors, but by other means such as charging for manuscript feedback or taking kickbacks for referring aspiring writers to editing services — makes money only when he sells his existing clients’ manuscripts or book proposals. He takes a percentage of the advance, as well as any royalties. (If you’re not sure of the difference or how published authors get paid, you might want to check out the ADVANCES and ROYALTIES AND HOW THEY WORK categories on the archive list conveniently located at the bottom right-hand side of this page.) Going through queries and submissions, then, as well as working with clients in order to get a work ready for submission to publishing houses, is essentially done on spec in anticipation of future earnings.

That means, in practice, that while landing an exciting new voice or great book concept (or, even better, both in the same work) is potentially lucrative for an agency, getting paid in the short term depends mostly upon hustling to promote the manuscripts and proposals it currently has under contract, making sure that the publishers of existing clients’ books deliver advances and royalty checks on time (not a foregone conclusion in every instance, alas), and, ideally, helping already-established clients crank out more books for eager audiences. Because all of that is awfully darned labor-intensive, even a very successful agency typically takes on only a handful of new clients per year.

Which means, to be blunt about it, that a good agent usually doesn’t have nearly enough time to screen all of the queries aimed at him — and the more commercially successful his clients are, the more likely that is to be true. (Oh, you think Stephanie Meyers’ agent doesn’t receive a significantly higher volume of queries than your average bear?) Thus Millicent: while her boss concentrates on near-term profits, she performs the long term-oriented task of sifting through the mountains of queries and hills of submissions to come up with the happy few most likely to — pardon my being crass about it — rake in some dosh down the line.

Her efforts — and they are often substantial — free the agent of your dreams to concentrate on his current client list. That may be a touch frustrating when a writer is first trying to catch an agent’s eye, but believe me, you’ll be grateful for it once you’re gracing that client list.

I always like to remind aspiring writers of that around this time of year, when so many creative minds first tackle (or re-tackle) the daunting, lengthy, and often soul-compressing task of approaching agents with a first book. The Millicents of the world do not, by and large, enjoy rejecting writers, nor do they generally make the rules that determine what is and is not a rejection-worthy offense in a query, but it is in fact their job to reject virtually everything that comes across their desks.

That’s just how the system works, I’m afraid. An aspiring writer can waste a lot of time and energy in resenting that, without doing herself or her book any good.

In fact, most do. As any talented listener who has ever spent more than forty minutes at a writers’ conference knows, it’s not at all uncommon for even very ambitious writers to devote a far greater proportion of her oomph to complaining about how difficult it is to land an agent than to walking up to agents to pitch or sending out queries. Indeed, it’s not unheard-of for a genuinely gifted writer to send out only one, two, or twelve queries, then give up entirely, switching all of the energies previously expended in trying into seething and feeling hurt.

I’m not judging that response; I would be the last to deny that rejection hurts. It’s hard not to take personally. However, as a professional writer, I’m here to tell you that frequent rejection isn’t the exception for successful writers; it’s the norm. It often takes an agent dozens of submissions to sell a client’s book; agented writers pitch book ideas to their agents and editors all the time, only to see them shot down.

They don’t stop trying, you see. Nor should you. Yes, you’re probably going to get rejected a few times, but you can’t succeed if you don’t try. And keep trying, even if it takes a hundred queries. (Not at all an unusually high number for first-time authors these days, by the way.)

Chant it with me now, long-term readers: the only manuscript that stands no chance of getting published is the one that the writer, sometimes for excellent reasons, has stopped sending out. Or never worked up the nerve to send out in the first place.

It also helps to be humble enough — and professional enough — to be open to the possibility that the query itself, and not the book it presents, is what is tripping Millicent’s infamously sensitive rejection response. As we’ve seen throughout this series, it isn’t always the big faux pas that send her reaching for the form-letter rejection pile; it’s frequently the small gaffes.

Or, more commonly, a collection of them. Query red flags, like manuscript problems, are as sociable as ants: Millie rarely sees one traveling alone.

Bearing that in mind, I’d like to present you with another quite good querying effort by a brave and generous Author! Author! reader, a clever, creative soul I shall dub Catherine T. Great. From a writerly perspective, what I’m about to show you is not only good; it’s borders on the superlative. Just you wait and see.

Yet to Millicent’s finely-honed eye, the query that follows suffers from a number of small maladies. Not a single one of these problems would necessarily constitute a severe enough pneumonia to make us despair of the patient’s chances, perhaps, but taken together at the end of a long, tiring day of querying, the symptoms might well prove fatal to the chances of what genuinely sounds like an interesting book.

Our goal today, then, will be to ferret out and clear out those minuscule ailments, so that the patient may thrive.

So dig out your reading glasses, please, and see if you can diagnose the problems, as well as the strong points of this letter. As always, I apologize for the bizarre blurriness my blogging program lends to page shots (as opposed to photographs, which it passes along to you in loving detail); to try to ease it, I shall try making the pictures a little bigger this time around. If you are still having trouble seeing individual words or formatting specifics, please try holding down the COMMAND key and pressing + to enlarge the image.

Pretty darned persuasive, is it not? Let’s pause for a moment to consider why. It’s upfront about why Catherine decided to query Hawkeye — the reference to one of her client’s books is professionally flattering without coming across as at all obsequious — makes the book category clear, and goes above and beyond in providing a second parallel published book. Obviously, this is a writer who has done her homework (although I, for one, would have liked to know why the book would appeal to Ms. Revis’ readers, I must confess). It’s properly formatted, polite and professional in tone, and includes credentials relevant to publishing. The book’s description is a trifle on the long side, but it presents a compelling story arc.

Heck, she even came up with a title for Brilliant Author’s work that elicited a bona fide chuckle from me — and believe me, after six and a half years of coming up with querying examples for aspiring writers, I welcome a query effort that makes me chuckle. Well done, Catherine!

Yet despite all of these very positive elements, it contains two common problems — one structural, one creative — that might well give Millicent pause. Hint: we talked about one of them at fairly great length last time.

Hark! Do I hear a fairly hefty percentage of you leaping to your feet, exclaiming vigorously, “I see it, Anne! Catherine included that unnecessary cliché about the manuscript’s being complete,” you’ve already earned your gold star for the day. Chant it with me, recent post-rememberers: since a US-based agent could not possibly sell — or even submit to editors at publishing houses — an unfinished first work of fiction, agencies do not accept partial novel manuscripts. Therefore, any query for a fiction manuscript is assumed to be for a completed manuscript.

How I — and everyone currently working at any agency in North America — wish that logic were more widely known. The Internet, however, has an intriguing habit of making bad examples and ill-informed advice at least as pervasive as good examples and expert advice. Trust me, “But I saw an example online that did it that way!” carries precisely no weight with Millicent — or, indeed, anyone who reads for a living.

Sorry to be the one to break that to you. But while I’m at it, may I caution against the utterance of any sentiment that remotely resembles, “But my mom/husband/wife/best friend/writers’ group loved my book!” in the presence of anyone who has ever set foot in a literary agency? Not to cast aspersions upon those who love you, but from the pros’ point of view, non-professional assessments of literary quality tend not to be worth the paper they are written upon.

I have some bad news about the Easter Bunny, too, as well as George Washington and that cherry tree. I don’t want to shatter too many of your illusions in one day, though, so I’ll hold off on those.

Do I spot some raised hands out there? “But Anne,” Catherine’s well-wishers across the globe call out, and with good reason, “I’ll fess up: I thought that complete at X words was required verbiage for a query, too. How else would one work in the information about length gracefully?”

Oh, I don’t know — how about by constructing a graceful, original sentence, rather than lifting one somebody else wrote? English is a marvelously complex language that permits a great variety of sentence construction, after all, and part of the writer’s task in the query letter is to convince Millicent that he can, you know, write.

As I’ve mentioned before, it’s a myth (and, since the rise of the Internet, an astonishingly pervasive one) that every agent currently treading the earth’s crust demands to see a word count in the query. Some do, of course, but they tend not to be particularly shy about expressing that preference: if its inclusion is important to them, they will mention it in the agency’s submission guidelines.

And if they do not bring it up specifically — or if, as is more often the case, the agency has not posted guidelines for queriers more prescriptive than please query before sending materials — it’s honestly not going to help you to include the word count unless it falls smack dab in the middle of the normal range for your chosen book category. If it’s much longer or much shorter, including it could provide Millicent with an additional reason to reject the query.

Which, naturally, is why agencies that ask for this information want to know: because so many first manuscripts are in fact quite a bit longer or quite a bit shorter than the norms for the category (usually the former, for fiction), having this information handy in the query can save Millicent quite a bit of time — and the agency an entire step — in the rejection process. That’s just common sense: instead of being charmed by the query, requesting the manuscript, and waiting until it arrives to discover it’s a five-pound behemoth that would be astronomically expensive to print (or a six-ounce novella not long enough to hold hard covers apart), a Millicent at a word count-requesting agency can simply glance at those numerals and reject the project immediately.

Lucky for her that she didn’t have a chance to fall in love with your writing first, eh?

In Catherine’s case, even though her word count isn’t large enough to risk knee-jerk rejection, the book is on the longer end for YA. So if Hawkeye’s agency didn’t insist in its guidelines upon seeing those digits, is it really the best strategy for her to include them?

Check those guidelines carefully. It’s in your interest to verify the querying requirements of every single agent you plan to approach, anyway, to ascertain that they don’t want you to send additional materials — an author bio, for instance, or some special length of synopsis.

I know, I know: the let’s-use-a-template mentality would prefer that every agency in creation did in fact expect precisely the same elements in a query, or in a query packet, for that matter. A simple perusal of any fifteen agency websites featuring submission guidelines, however, will abundantly demonstrate that’s not the case.

And before anyone out there bellows, “But I saw something on another website that said my query would be doomed if I didn’t include the word count,” remember, folks, the vehemence with which a piece of querying advice is presented is not a particularly good indicator of how helpful that advice will be in practice. Especially, as in this case, when literally millions of queriers have taken the same piece of advice, rendering screening annoyingly repetitious for Millicent. “What on earth,” she mutters over the 78th iteration of complete at X words she’s seen in a morning, “makes them think they need to tell me something this obvious? And why oh why do 99% phrase it exactly the same way?”

This is not, of course, the intended effect. Quite the opposite, in fact. Like many aspiring writers, Catherine almost certainly included this stock phrase because she saw — although not here at Author! Author! — a template that featured it, and concluded, not unreasonably, that it was just necessary industry-speak that would elevate her query from the intriguing to the intriguing and professional.

Instead, it tells Millicent something completely different: despite Catherine’s genuinely impressive magazine credentials — did you catch that glorious platform paragraph? — she probably doesn’t know very much about how book-length fiction is sold or how agencies work. Perversely, that perception might actually make that magazine background work against Catherine at the query stage. Millicent might well conclude that her boss, or at any rate someone at the agency, would have to invest additional time in training such a client in the differences between what the magazine world expects in a manuscript and what book publishers do.

Counterintuitive, isn’t it? Contrary to popular opinion, not every piece of writing intended for publication should be formatted identically, nor is all publishing one big industry. What’s appropriate in a submission, or even in a query, depends entirely upon the venue. Agents deal with book publishers, by and large, so they expect their clients to adhere to the norms of that industry: reasonable, right? It’s equally reasonable for magazines to expect submitters to adhere to short story format, newspapers to look for A.P. format, and academic journals to adhere to their own esoteric standards.

So while Catherine’s extensive experience working with text intended for publication and producing print-ready work under deadlines undoubtedly constitute fine arguments for snapping her up as an agency client, presenting that information to Millicent immediately after having used a phrase that she has come to associate with those brand-new to book publishing might create an unintended effect. Specifically, the impression that while this is a writer accustomed to adhering to an industry’s writing expectations, she might experience some difficulty switching to Millie’s boss’ expectations.

Especially, as in this case, when that phrase appears at a rather odd point in the letter. Does anybody see a problem — from Millicent’s speed-reading perspective, that is — with where the information in that paragraph falls?

In case that last sentence was too subtle: why might it be to Catherine’s advantage not to make Millie read almost to the end of the query — or, if it’s an e-mailed query, to force her to scroll down — before conveying that information?

If you have been jumping up and down for the last few lines, exclaiming, “I know! I know! Millie won’t necessarily read that far to find out the book category,” feel free to raid the gold star cabinet again. Remember, a screener at an agency of any stature has to read through a LOT of queries in a day, and it’s her job to reject as many as she reasonably can, as fast as humanly possible.

And what’s the single simplest ground upon which to reject a query? Shout it out, Queryfest faithful: if the query appears to be for a book in a category Millicent’s boss doesn’t represent.

Yes, sometimes even if it doesn’t appear from the first paragraph that the letter’s been correctly targeted. Remember, if Millicent finds a rejection trigger early in a query, she’s not necessarily going to have the time to read on for others. In the midst of a busy day, she’s far, far more likely simply to stop reading and stuff a form-letter rejection into the enclosed SASE. (Catherine’s been redundant here in mentioning the SASE in the body of the letter and writing Enclosure at the bottom, by the way; once would have been sufficient.) Or, as is even more common these days, just to hit the DELETE key or toss the query into the recycling bin.

Fortunately for Catherine and her book — which, again, sounds like a good read — this dreadful fate is not all that hard to avoid. As is, alas, all too often the case with good writers who have just taken advice from too many sources, ironing out the wrinkles to present the book more pleasingly to Millicent’s eye can be done with very few keystrokes.

Stop laughing; it’s true. Just a few very minor revisions would make an immense difference here. Even just altering what we have talked about so far — taking out the stock phrasing and the word count, making it easier for Millicent to tell the book category from the get-go, removing the redundancy about the enclosure — would improve this query’s chances. Take a gander:

Stronger, isn’t it? That took less than a minute’s worth of keystrokes to accomplish.

I sense some nervous shifting in desk chairs out there in the ether. “But Anne,” YA writers across the globe point out, “I recognize that this version is tighter — it did seem a trifle conceptually redundant in the first to mention the book category twice. In Catherine’s defense, though, she did tell Millicent right off the bat the first time around what the book category was: YA. So why not just say that in the first paragraph, rather than specifying that it is YA science fiction?”

Good question, chair-shifters, and one that deserves a direct answer: because just as not all science fiction is aimed at a YA audience, not all YA appeals to science fiction readers. Nor do all YA-representing agents handle SF or fantasy aimed at that demographic. I must confess, though, from the description in the query, I’m not entirely sure why she has labeled this story as YA science fiction, rather than placing it the more capacious umbrella of YA fantasy. It’s entirely possible that this story contains elements that would make it fit more comfortably into the SF world — like, say, the cryogenically frozen space travelers featured in Across the Universe – but as the lengthy description doesn’t bring up any SF-specific elements, I suspect Millicent might be perplexed by the category choice.

And while we’re at it, the king’s answer lies within what? The garden, or Matty?

To be fair, since Catherine has clearly done her homework about this agency, she knows that Hawkeye does indeed represent YA fantasy and adult SF, so she probably could have gotten away with this particular ambiguity in her query were it not for a storytelling choice in the descriptive paragraphs. Any guesses why Millicent needed to know before the description that this book was SF or fantasy?

At the risk of running out of gold stars, help yourself to three if you bounded from your chair to cry, “Because while the first descriptive paragraph reads like YA, it does not read like either SF or fantasy!” For some reason that defies Millicent’s understanding, writers aiming at YA subcategories stumble into this pothole all the time: in their laudable attempt to present the premise in an engaging YA voice, they tend to give short shrift to the specialty elements.

I hear you giggling, but you’d be astonished at how many YA romance queries omit the romance (one of the reasons I didn’t transplant the with romance elements part of the original science fiction justification, incidentally), how many YA paranormals neglect to bring up the werewolf until the last sentence of the description, how many YA fantasies neglect to mention any fantastic plot points, and so forth. It’s as though these queriers believe that there’s just one big YA category that covers every single literary possibility for readers aged 13-17, and that a commitment to representing YA means swearing off the ability to specialize in certain voices or subject matter.

If that last paragraph made you gasp in terror, clutch your writhing entrails, and wish devoutly that you’d done a touch more research on what those agents you just queried had sold recently, well, you’re not alone. YA-screening Millicents are constantly overwhelmed with masses of queries that betray a belief that YA agents don’t specialize.

See now why I was so adamant about Catherine’s stating the subcategory in paragraph 1? Even if Millicent happened to be intimately familiar with both Brilliant Author and Beth Revis’ excellent efforts to entertain the youth of this part of the universe, it isn’t her job to guess that despite the fact that Matty’s story is presented at first as straightforward YA — it isn’t hard to imagine this story set in any strict school, is it? — he’s living in a fantastic world. It’s the descriptive section’s job to demonstrate it, and to do it right away.

Not having read the manuscript in question (which, again, sounds like a hoot, Catherine) and having no idea what the Hill is (when it first appears in the description, it seems to be Matty’s school, but by the end of the paragraph, it appears to be a regional designation), I’m reluctant to make up SF or fantasy elements to add to that paragraph. I can suggest a revision strategy, though: why not just beef up the initial description of Matty to include some off-world tidbit? Like, perhaps, this:

Sixteen-year-old Mars resident Matty Ducayn is a disappointment to everyone who knows him. As the son of The Hill’s commandant, he is expected conform to a strict, unspoken code of conduct. Small acts of defiance over years—like playing in the dirt and walking on the grass—have earned him a reputation for being unruly, but it’s his sarcastic test answers that finally push his masters over the edge. After his preparatory school expels him, he’s summoned by his sponsor…the king…to answer for the offense.

Doesn’t leave Millicent in suspense for long, does it? Again, that’s a huge improvement, given that this change required precisely six keystrokes.

While we have that excerpted paragraph in front of us, though, may I ask you a favor? Will you rise from your chair, back up an additional few feet from your computer screen, and take another look at that paragraph, please?

Tell me, what was the first thing that struck your eye? If it was those two rather perplexing sets of ellipses, you’re not alone. Yes, YA is on the whole quite a bit more open to what columnist Herb Caen used to call three-dot journalism than adult fiction (or nonfiction, for that matter), but here, those dots just don’t make sense. What, Millicent is left to wonder, is Catherine trying to say that could not have been adequately conveyed by the grammatically-correct commas:

After his preparatory school expels him, he’s summoned by his sponsor, the king, to answer for the offense.

Since the query is peppered with other, correctly used ellipses, what Millicent is most likely to conclude is twofold: first, Catherine really likes herself an ellipsis — and that the manuscript being queried is stuffed to the proverbial gills with ‘em. While neither would necessarily strike someone reading the book itself as problematic, if Catherine has used them discreetly and effectively throughout, repeating a stylistic trick several times within a space of text as short as a query implies that the author may use them that frequently on the manuscript page.

And if you’re not sure why that might present a problem, back up again and take a peek at the previous examples. That many ellipses on any given page of a published book would be mighty eye-distracting, wouldn’t they? Like most literary slight-of-hand, a device like this works best if it is used sparingly; indulge in it too much, and the reader’s eye begins to skim past it.

Again, though, not having read the manuscript in question, I’m reluctant to draw any conclusions whatsoever about how it is written. Millicent, I need hardly tell you, is not so shy. So let’s, just for the sake of appeasing her, limit the ellipsis use to once on the page, where removing it would make the greatest difference.

While I’m removing eye-distracters, I’m going to go ahead and excise the extra s in the possessive in that first paragraph. Yes, recent changes in journalistic practice have rendered forming a possessive by adding ‘s to — shudder — any noun, regardless of whether it happens to end in an s or not, but to most of us who read for a living, it still looks wrong. (Mostly because it would have been considered flatly and unquestionably wrong 20 years ago.) To us, the rule change just seems like a concession to those incapable of understanding a rule containing more than one element.

I was, fortunately for the Author! Author! community, brought up to exercise kind forbearance toward those wolf-raised miscreants who objected to punctuation that could not be applied identically in every instance. Millicent might, too, if she did not enjoy the good luck of being trained by a grammar rule-hugger, and her boss might well be too busy to care.

When people do object to rule-flattening, however, they tend to object to it pretty violently, so why take a chance in a query? Or, for that matter, tempt Millicent’s ire by adopting the AP style of capitalizing the first letter after a colon, as if it were the beginning of a new sentence? (See earlier section on different types of publishing embracing different standards.) For the sake of Millie’s blood pressure, I’m going to alter that, too.

That little peroration out of my system, let’s turn again to the query page. What jumps out at you now?

It was the dashes, wasn’t it? (And wasn’t it amazing how little difference removing those ellipses made to the actual meaning of those sentences?) This time around, it’s not just the frequency with which Catherine uses them here that would strike Millicent as odd, but the fact that she does not present them consistently. Half the time, they show up as emdashes, those long lines stretching from one word to the next, but the other half, they consist of two dashes, with no spaces between them and the words on either side.

In a book manuscript, neither would be correct: in standard format, dashes are doubled, with a space at either end. Care to extrapolate what Millicent’s assumption about the manuscript might be, based upon how dashes are used here?

Uh-huh: it would require proofreading, something not all agencies are willing to invest time in doing for their clients. So let’s go ahead and make those dashes both manuscript-friendly and consistent, shall we? Since the book’s title contains an unexplained-and-offbeat punctuation choice, Catherine will be best off if it’s the only one in the letter.

I’m also, for the sake of consistency, regularize the number of spaces after periods and colons: in the original query, sometimes it was one, sometimes two. While I’m at it, I shall correct the incorrect article in the platform paragraph, add the missing one, and introduce some clarifying commas.

Ah, that’s better: without the visual distractions, it’s easier to concentrate on the content of the letter. As a fringe benefit, the offbeat punctuation in the title now comes across as a definite authorial choice made by a rule-savvy writer, rather than — and I’m sorry to put it this way, Catherine, but it is how many Millicents might have seen it before — as a typo.

And speaking of typos, did you catch the one that I missed last time around? I’ll add the missing preposition in the next version.

Own up, now: you’re surprised that a query this good from the get-go could benefit from this much tinkering, are you not? That’s the difference between how Millicent — and any well-trained professional reader — looks at a page and how most people do. To those with the eye, these small changes make a world of difference, elevating the query several notches up the professionalism scale.

Believe it or not, I could tinker with this more — personally, I think that including a few vivid, one-of-a-kind specifics would make this letter even better, but lacking those, I’m not going to impose my guesses upon Catherine’s plot. A dandy place to start: how about adding a sentence showing Millicent how Matty’s world differs from ours?

Ah, you will say, but how would Catherine find the space to include her unique details? To an editor’s eye, the answer’s simple: since including so much of the plot here renders causation a trifle unclear, cut a bit of it out. Remember, the point of a book description in a synopsis is not to summarize the plot, but to present the premise and central conflict, preferably while depicting the protagonist as an interesting person in an interesting situation.

Here, the description not only achieves all that, but goes considerably farther, suggesting how the central conflict gets resolved. While that’s not inherently problematic, Millicent’s expecting this part of the query to run only 3-4 sentences long. She seldom objects to queries on the ground that they are too short, if you catch my drift. She also tends to prefer descriptive sentences in the active voice to ones whose structure implies that things happen to the protagonist, rather than the protagonist’s propelling the plot along.

So despite the fact that I suspect the cuts I am about to make will cause Catherine to clutch her heart and murmur, “Sacre bleu! But it’s an essential twist, I tell you,” I invite the rest of you to consider whether tightening the lengthy description genuinely sacrifices much of this query’s original charm. In order to sweeten the trade-off a little, I’m going to use a bit of that freed-up space to show Millicent why I think, based upon what I know of this storyline, this book might appeal to readers of Beth Revis’ work.

Oh, and before I show you the revised version, allow me to ask: had you noticed that title of this book appeared in capital letters (one acceptable means of designating a title), while the other titles appeared in italics (a different means of same)? Millicent would have. Again, consistency is the querier and submitter’s friend: professional readers’ eyes automatically zoom in on the unexpected.

What, you may be asking, is the mystery of the vanished Januaries? Beats me; I was merely searching for shorthand for that rather confusing (for someone who has not read the manuscript, anyway) bit about the search. It’s a nice phrase, though, isn’t it, and one that whets your appetite to read the manuscript?

It just goes to show you: sometimes in a query, less actually is more, as long as it is clearly presented. It’s not the book description’s job, after all, to depict the central conflict in its entirety, after all; that’s the manuscript’s job. All the query has to do — and it’s a tall enough order without adding requirements, thanks — is intrigue Millicent enough that she will ask to see pages.

After that, Catherine, your story and voice will be able to grab her even more thoroughly, right? So why give away so much in the query?

Please join me in thanking Catherine for helping me illustrate yet again something that Millicents know only too well: to a professional reader, the details of a query can do as much toward demonstrating the writer’s professionalism and writing talent as the broad strokes of description can do to convey the plot. A savvy querier can use that to her advantage: since the overwhelming majority of queries have red flags imbedded in their details, if not also in the larger points, a query whose details are selected with care can shout from even the very bottom of Millicent’s daily reading allotment, “Hey, take this one seriously.”

Remember, Millicent doesn’t have much upon which to base her opinion of your writing. Make sure that every syllable of what she does see works to your advantage.

Thanks again, Catherine, and everybody, keep up the good work!

Queryfest, part XX: tying yourself up in knots to please that agent, or, they couldn’t possibly mean what they say, could they?

If you’ll forgive my getting personal for a moment, have you ever been in a relationship — romantic, friendly, coworkerish — with someone who was just positive s/he knew precisely what you wanted without ever having asked you what your actual preferences were? You’d never gone downhill skiing, perhaps, because you’re secretly afraid of heights — and suddenly, that surprise weekend getaway finds you clinging for dear life to a ski lift, while your beaming significant other repeatedly congratulates himself upon broadening your horizons. Or you’d successfully avoided your sociopathic cousin Bertrand for the last decade, and your matron of honor abruptly announces at the rehearsal dinner that her wedding present to you involves flying Bertrand from New Zealand for your special day, along with his paranoid wife, a teenage son far too fond of matches, and a border collie whose psychological problems defy categorization by even the best scientific minds. Or a member of your book club turns to you at the end of a cookie-fueled discussion of LITTLE DORRIT to ask smugly, “You know how you always claim walnuts don’t agree with you? Well, they do: those brownies you wolfed down were stuffed to the gills with ‘em. I knew you’d just never had them handled right.”

She’ll continue in this vein as you gasp for air, frantically signaling that your tongue is swelling to Godzilla-like proportions. If you are fortunate enough to share a book club with someone who recognizes anaphylactic shock when she sees it, your friendly baker will keep chattering all the way to the emergency room. She honestly means well.

Oh, their intentions are so good, these desire-anticipators, and their methodology so bad. The coworker given to bringing you back a latte every time she runs out to pick one up for herself does it to make you happy, after all; the fact that she just can’t seem to remember that you’re lactose-intolerant doesn’t detract from the purity of her intention, does it? What a nit-picker you are; she said she was sorry. Oh, and once you get over that gastric upset, don’t forget to reimburse her for the drink.

Of course, not all desire-anticipation attempts result in disaster, or even lifelong resentment. Tammy’s tendency to push hot milk on you did get you to try that lactase supplement, after all, and now you can eat ice cream. Aren’t you pleased about that? Perhaps you actually had never enjoyed a properly-presented walnut, and the allergen that sent you to the hospital when you were ten had been a misdiagnosed cashew. What a relief to know what to avoid. It’s possible that Bertrand’s wife has finally found a medication that works for her, and your second cousin’s arson conviction was entirely baseless. Aren’t you ashamed for having prejudged them? And maybe, just maybe, once you’re on top of that mountain, you’ll realize that a baseless fear had prevented you from discovering the one sport for which you have genuine Olympic potential.

Or maybe not. Either way, your learning curve probably would have been quite a bit more pleasant had your well-wisher simply asked you what you wanted before imposing it upon you.

“Ah,” desire-anticipators across the globe cry in unison, “but we don’t have to ask: some of us just pay attention. And don’t underestimate our memories. If you liked sauerkraut on your hot dog when I took you to a ball game back in 1982, you must still like it, right? It wouldn’t be baseball if you didn’t get your smothered wiener. Wait here; I’ll grab you one.”

Uncle Henry, is that you? And is this a good time to mention that for the subsequent ten years, I gobbled up those hot dogs only because it seemed to be so important to you? I loathe sauerkraut. While we’re at it, can we have a serious talk about those sherry-marinated beets you love to make for Thanksgiving?

It’s hard to fault the motivations of the Uncle Henrys of this world, but from the receiving end, it’s easy to spot the flaw in their logic. I ate a hot dog with sauerkraut once in my extreme youth, and against my own better judgment; therefore, I must always want to eat them should similar circumstances recur. By the same token, if I succumbed to a craving for a hot-fudge sundae yesterday — which I didn’t, because I’m lactose-intolerant, Tammy — I must perforce want one in every dessert course from now until the end of time. No more zabaglione for me. And if I was charmed by the giant pretzel my SO brought home on a whim one rainy afternoon last year, I will be equally charmed if he wakes me up by bouncing into the house with one after his 6 a.m. run tomorrow.

What do you mean, I’m unreasonable if I don’t want a pretzel smothered in mustard for breakfast? Or as a midnight snack? Or as a chaser to that enormous beet salad I had for lunch, because Uncle Henry was over?

If I am ever unreasonable on such occasions, it’s when desire-anticipators insist that I must want something, because everybody wants it. All the world loves chocolate, right? I must be kidding about only liking it for the first couple of bites. Every woman loves both shopping and shoes — so why didn’t I want to devote a couple of hours to trying on stiletto heels while I was on crutches? And since every possessor of a pair of X chromosomes must desperately want to get married (to someone, anyone; have you met my recently-divorced Cousin Bertrand?), why do fully half of us back away precipitously when the bride is about to fling her bouquet? Why, in fact, did all of the bridesmaids at my college friend Janet’s wedding retreat beneath a nearby awning, to remove any possibility of catching hers? I’ve seen more popular influenza.

Janet’s still pretty mad about that, speaking of lifetime resentments. As the person she had chosen to read the Shakespearean sonnet during the ceremony — Let me not to the marriage of true minds admit impediments — obviously, it was my duty to risk life and limb to snag those flowers. And want to, darn it. In the 22 years since, I’ve simply commissioned the nearest little girl to catch the bouquet for me. No one is fleeter of foot than a 9-year-old in pursuit of a pretty bouquet.

Except the ones who don’t like flowers. They exist, you know.

Of course, there are plenty of tastes that are pretty close to universal. It’s hard to find someone who hates every conceivable variety of pie, for instance, and virtually everyone dislikes being told what to do if the order seems unreasonable. (Yet for some reason that beggars understanding, no fewer than sixteen brides of my acquaintance have asked me to read the same Shakespearean sonnet at their respective weddings. Presumably, some standard wedding-planning guide listed it as one of the more acceptable secular readings amongst a startlingly small array. Either that, or there’s something about me that makes people take one glance in my direction and murmur automatically, “Let me not to the marriage of true minds admit impediments.” Perhaps I should stop writing it in permanent marker on my forehead.)

“Okay, Anne,” lovers of universally-applicable rules concede reluctantly, “I shan’t ask you to read it at my wedding to your cousin Bertrand. (Why hadn’t you ever mentioned what a charming man he is, by the way?) But if I may be prosaic for a moment, is there a particular reason that you’re going on about this type of assumption in the midst of a series on querying?”

Why, yes, there is, rule-huggers — and, as it happens, a darn good one. All too often, queriers new to the game (and a surprisingly hefty percentage of those who have been at it a while) will glance at submission guidelines and murmur, “Oh, they couldn’t possibly be serious about saying they want to see only a query. I’ll just tuck my synopsis into the envelope.”

Or, since the rise of e-mailed queries, “Oh, this agency says it won’t open attachments, but they also say they want the first ten pages. They couldn’t possibly want to see improperly-formatted text; I’ll just attach a Word document, anyway.”

Or, in the rare case where an agency does want pages sent as attachments with a query, “Oh, the guidelines say they want just the first ten pages, but the whole 30-page chapter is one file. They couldn’t possibly expect me to reformat my manuscript. I’ll just go ahead and attach that.”

Or, in response to any specified maximum length for a query or submission packet, “Oh, they say they want five pages, but the first scene ends on page 6. They couldn’t possibly want to stop reading in mid-scene. I’ll just go ahead and send all six pages.”

Or, after perusing an agency website or agent’s conference bio, “Oh, this agent doesn’t list any clients in my book category, and her blurb doesn’t mention that she’s looking for my kind of writing, but her name turned up in a database/in the index of one of the standard guides to literary agents as representing books like mine. She can’t possibly have stopped representing that type of book. I’ll just go ahead and query her anyway.”

Or, the most common query faux pas of all, “Oh, I don’t need to check whether this agency has posted specific guidelines for what it wants to see in a query packet; everyone wants the same thing. Although the agent of my dreams blogs regularly/gives classes on querying at conferences/is extremely vocal in interviews easily found on the web, I don’t need to do any research; he couldn’t possibly harbor individual preferences. I’ll just send him precisely what I’m sending everyone else.”

They are, in short, indulging in desire-anticipation, rather than treating each individual agent as, well, an individual. And we all know how folks on the receiving end of that kind of assumption tend to like it, don’t we?

I said, don’t we? I don’t care that Cousin Bertrand told you otherwise. Like most of the query advice-givers out there, he’s just telling you, probably quite authoritatively, precisely what you want to hear: that what would be the least amount of trouble for you is the path you should pursue.

And let’s face it, all of the tacks above involve far, far less work for the querier, submitter, or contest entrant than investing the time in finding out what each agency or contest rules ask to see. That doesn’t mean, however, that an agency that goes to the trouble of posting guidelines, an agent who announces what she does not want to see this year, or a contest that posts rules all entrants must follow couldn’t possibly mean it. While admittedly, sometimes neither provides especially clear guidelines — we’ve all seen the ever-popular and extremely terse agents’ guide listing query with SASE — in publishing circles, people are presumed to be able to express themselves lucidly in writing.

If they say they want it, believe them. And if they say they don’t want it, believe that, too. These are individuals, entitled to individual tastes, after all; if someone doesn’t eat walnuts, why would you waste your valuable baking time offering him brownies stuffed to the gills with them? Wouldn’t it in the long run be a more efficient use of your time and energies to figure out who the brownie lovers are and share the fruits of your labors with them?

Contrary to astoundingly pervasive popular belief amongst aspiring writers, it’s not the norm for agents to pick up a query for a book in a category they don’t habitually represent, scan it, and cry to the skies, “I don’t have the connections to sell this book, but I like the writing and the premise so much that I’m going to sign this writer anyway!” Nor are they much given to exclaiming, “Oh, this query packet contains many more pages/elements/a batch of chocolate chip cookies that our guidelines did not request, presumably to give the writer an unfair advantage over everyone who did follow our clearly-stated rules, but that doesn’t matter. We have all the time in the world to lavish on writers who can’t or won’t follow directions.”

That last bit caused many of you to do a double-take, didn’t it? “But Anne,” desire-anticipators ask in quavering tones, “I’ll admit that I’ve murmured one or more of the sentiments above whilst pulling together query packets, particularly when I’m trying to send a whole bunch out at once — as I often do, say, immediately after New Year’s Day — but it never occurred to me that anyone would think I was trying to take unfair advantage by ignoring the rules. I meant well. In fact, I thought I was following directions; I just didn’t know that there were different sets of them.”

I know you meant well, step-skippers, but frankly, Millicent the agency screener doesn’t know you as well as I do. Neither does her aunt, Mehitabel the veteran contest judge, when faced with a contest entry a page and a half longer than the rules allow. While it would be nice if they could give you and aspiring writers like you the benefit of the doubt, there are simply too many aspiring writers like you competing for too few slots for them not to regard inability to follow stated directives as an instant-rejection offense.

Yes, no matter why the querier, submitter, or contest entrant did not adhere to those rules. To see why, let’s take another look at those six types of trouble-saving, desire-anticipating practices, comparing the writer’s logic to Millicent’s.

The extra element adder says, “Oh, they couldn’t possibly be serious about saying they want to see only a query. I’ll just go ahead and send along anything else I think might aid Millicent in her decision.”
The writer thinks: I’ve seen other agencies’ submission guidelines that have asked for synopses at the querying stage. I’ve already gone to the trouble of writing one, so I might as well use it. As long as Millicent is perusing my query, she might as well consider it.

When Millicent receives the over-stuffed packet, she responds, “Wow, this querier did not read the submission guidelines — or did not understand them. Whether he didn’t do his homework on my agency or didn’t read carefully enough to get what we were asking, this client would be more work to represent than someone who does read instructions thoughtfully and implements them. Like, say, the next query in my reading queue. Next!”

That’s if she’s in a good mood. If she’s just burned her lip on a too-hot latte — or, even more likely, has just finished reading 14 queries from desire-anticipators, her response might well run more like this: “Hey, who does this writer think he is, to assumes that I will be willing to spend three times the time on his query than on everybody else’s?”

Yes, really. Couldn’t be much farther than your intentions, could it, element-adder? But now that you stop and think about it, wouldn’t reading your query require precisely the extra time and effort Millicent just mentioned? And is that fair?

Painful, I know, but worth contemplating, I think. It’s far, far better that we discuss the possible outcomes here than for any of you to risk automatic rejection on this kind of avoidable basis. Let’s move on.

The dogged attacher says, “Oh, this agency says it won’t open attachments. I’ll just attach a Word document, anyway.”
The writer thinks: I’ve done my homework about agents, and I’ve learned that improper formatting can be fatal to a manuscript submission. So because my e-mail program doesn’t preserve all of the bells and whistles of Word, I’m more likely to impress Millicent if I submit in a format I know is right: as it would appear on the manuscript page.

Upon receiving the query with the attachment, Millicent responds, “Oh, great — another one who didn’t bother to read our guidelines, which clearly state that we don’t read unsolicited attachments. I’m just going to reject this query unread.”

I’m afraid that you are going to hurt your neck, doing all of those double-takes. “You’ve got to be kidding me, Anne,” dogged attachers everywhere protest. “This is an instant-rejection offense? In heaven’s name, why? The agency’s guidelines asked for this material, and it would only take Millicent a couple of seconds to open it.”

Ah, but if she did, she would risk exposing her agency’s computer system to viruses — the primary reason that most agencies did not accept e-mailed queries at all until after the anthrax scare rendered opening thousands of pieces of mail considerably less desirable. In essence, by sending an unrequested attachment, a querier is expecting Millicent not only to devote those extra few seconds to opening it, but to violate her agency’s standing computer use policies.

That “Next!” sounds quite a bit more reasonable now, does it not?

The kitchen sink sender says, “Oh, the guidelines say they want just the first X pages, but my document is Y long. I’ll just send the whole thing.”
The writer thinks: it would be a whole lot of work to copy the requested pages, create a new Word document, copy the text into it, and make sure that the formatting is right. Millicent can just stop reading whenever she wants — and if she likes my writing, she may well want to read more. This is a win/win.

But Millicent, blinking in disbelief at the size of the file, snaps: “Either this querier can’t read directions — problematic, as I murmured above — or she’s expecting me to make an exception for her. For her and her alone, I will read not X pages, but however many she chooses to send me. That’s completely unfair to everyone else who queries, as well as an unwarranted imposition upon my time. Next!”

Does the gnashing of teeth and rending of garments I hear out there mean that this is the first time some of you have tried to see this exchange from Millie’s perspective? Does that mean you will never over-send again?

No? Okay, let’s move on to the next set of excuses.

The sneaky upgrader says, “Oh, they say they want X pages, but the first scene/chapter/a really good bit ends slightly farther into the manuscript. I’ll just go ahead and send enough pages to complete that section.”
The writer thinks: as my manuscript currently stands, stopping at page X does not provide a complete scene and/or cuts off before a bit I particularly like. In fact, the bottom of page X ends in mid-sentence. Since no sane person could possibly want to cease reading in mid-thought, obviously, what the agent really wants is for me to send the entire section/chapter.

And Millicent, cranky at spotting the 20th such over-long writing sample of the day, just shrugs and rejects it unread. “This querier must think we are awfully stupid, to assume that we would believe that any good book would automatically come to a natural stopping-point on the bottom of page X. Way to substitute your opinion for how to assess writing for ours, non-professional. Next!”

Harsh? You bet, considering that all the writer was trying to do here was provide a complete reading experience. But in Millie’s defense — and Aunt Mehitabel’s; contest entrants indulge in sneaky upgrading tactics all the time — this strategy betrays a complete misunderstanding of why some agencies ask for writing samples to be included in query packets. It’s not so they can get into your story; it’s so they can see if you can write.

Not only write well, but write well for readers in your chosen book category. (You’d be astonished at how many opening pages don’t sound remotely like works in their intended categories.) If Millicent decides that you do, then she can turn to the synopsis or request the manuscript/proposal in order to consider your book as a whole.

That was a big aha! moment for some of you, I’m sensing. But the rules lawyers amongst you still have questions: “Okay, Anne, I accept that requesting a writing sample at the querying stage is a pretty good way to spot the strong stylists right off the bat. I can even see that by accepting those pages up front, Millicent can save herself a great deal of time: instead of basing her assessment of whether to request the manuscript or book proposal upon the query alone, then having to wait until those requested materials arrive in order to reject them on page 1, she can skip a step.

“Given that practice, though, shouldn’t I be sending my best writing as a sample, rather than just the first few pages? My favorite part of the book is a 150 pages in. That scene also, conveniently enough, happens to be the precise number of pages the agency’s guidelines suggest. So I’d be smart to send them instead, right?”

It’s a clever notion, rules lawyers, but absolutely not: while you could get away with a mid-book writing sample in a pitching situation, if the agent in front of you asked to see a few pages, the assumption with any requested pages or writing sample in a query packet is that they will begin on page 1 of the book. Why? Well, it’s the way a reader in a bookstore would first encounter the text, for one thing; it’s the part of the story that requires the least set-up, by definition. And since neither agents nor editors simply open manuscripts in the middle and read random passages in order to assess their quality, the opening pages provide a better indication of how they would respond to the manuscript or proposal as a whole.

I know, I know: that places writers who take a while to warm up at a significant disadvantage. You wouldn’t believe how many manuscripts have fabulous openings buried somewhere on page 15. Since the overwhelming majority of manuscripts are rejected on page 1 — I am doling out the hard truths today with a lavish hand, amn’t I? — Millicent just doesn’t see that great prose.

The track record-ignorer says, “Oh, this agent doesn’t list any clients in my book category, and her blurb doesn’t mention that she’s looking for my kind of writing, but her name turned up in a database/in the index of one of the standard guides to literary agents as representing books like mine. I’ll just go ahead and query her anyway.”
The writer thinks: because the Literature Fairy constantly combs the Internet to assure that every single piece of information floating around out there about agents and agencies is not only true, but absolutely up to date, if I can find even one source that claims a given agent represents my kind of book, she must abide by that. So there’s really no reason for me to do any research beyond running by chosen book category through that database or looking in the index of an agents’ guide.”

This one makes Millicent positively choke on her latte, even after it has cooled down. “Why on earth,” she exclaims, “wouldn’t my boss be allowed to change her mind about what she represents? This is a market-driven business, after all: she can only afford to pick up clients whose work she believes she can sell in the current market. So while I might have given this well-written query serious consideration five years ago, back when she handled this category, now, I can simply reject it as soon as I ascertain that it’s pitching a book she doesn’t represent.”

I’ve said it before, and I’ll doubtless say it again: since there is no easier query to reject than one apparently addressed to the wrong agent — Millie seldom needs to read beyond the first paragraph in order to glean that much — it is a complete waste of an aspiring writer’s time to query an agent who does not currently represent books in his chosen book category. Save yourself some chagrin; take the time to check.

Starting to sense a pattern here? Like, say, that trying to save time by skipping the research step is often a false economy, resulting not only in more rejection, but often a longer querying process as well?

I shall leave you to ponder that one for the nonce. Let’s move on to the 600-pound gorilla of querying faux pas.

The one-size-fits-all querier says, “Oh, I don’t need to check whether this agency has posted specific guidelines for what it wants to see in a query packet; everyone wants the same thing.”
At this point in Queryfest, do I even need to reproduce this writer’s logic? Well, okay, for the sake of future would-be queriers who might stumble upon this post in isolation in the archives: anything called a query must by definition mean the same thing, right? So anything I have ever heard about querying, as well as any advice on the subject I might find on the Internet, must be referring to the same thing. That must be true, since the publishing industry — and, by extension, agencies — are set up first and foremost to identify new talent in raw form; for a good writer with a good book, this process should be easy. That being the case, all I need to do is find a template that someone says will work and follow it. Easy-peasy.”

Breathe into this bag, Millicent, until you stop hyperventilating. Then share your thoughts: “Criminy, another aspiring writer who can’t read. Or hasn’t bothered. My agency takes the time to publish guidelines for a reason: we know what we want to see. While this querier may well have a great manuscript on his hands, the letter does not give me the information and/or materials I need in order to say yes to it. So I am saying no.

“Wait — I’m not done yet. Since this querier is treating my agency as identical to every agency, and my boss as identical to every other agent currently milling around Manhattan, I shall return the favor: this query is identical to a good half of the others I see in any given month. Not in subject matter, but in attitude. Believe it or not, following the rules we set out is rare enough that following them makes a query stand out from the crowd. So fly back home to the person who wrote you, little query, and I hope that if he does genuinely have talent, this rejection will teach him to treat his future agent — and her staff — with more respect.”

Of course, it would be far, far easier for the writer in question to learn that particular lesson if the rejection letter actually said any of this — or if he received a formal rejection at all. Even twenty years ago, though, this type of generic, wallpaper-New-York-with-letters query almost always received not a personalized reply, but a form-letter rejection. Queriers who presented themselves better, but had missed the mark in small ways, were often given specific reasons the agency wasn’t asking to see pages. Now, not only would virtually every rejected query generate the same form letter at most agencies — many agencies simply don’t reply at all if the answer is no.

So how is that misguided querier to learn better? Good question. The basic theory underlying the querying and submission process — that since a manuscript or proposal not only needs to be well-written, book category-appropriate, and market-ready in order to catch a good agent’s eye, but also presented professionally at the query and submission stages, a gifted writer might have to take the same manuscript through many revisions and multiple query and submission rounds before finding the best home for it — is predicated upon the assumption that any serious writer will figure out both that it’s essential to her book’s success that she invest the time in learning the ropes, but that she is aware that there are ropes to learn. And that she will have the time, patience, and faith in her talent to keep pressing forward in spite of rejection until she has acquired the necessary skills and expertise to wow an agent.

That’s a whale of a presumption, one that could be quite easily undermined by, well, talking to even a small handful of the thousands upon thousands of exceptionally talented writers who spend years trying to crack the code. But I’ve already said enough today about the dangers of assuming that one knows what is in other people’s minds — or other people’s interests.

There’s another, more query-specific cost to this series of presumptions — but rather than tell you what it is, I have the great good fortune of being able to show you. At the beginning of Queryfest, I appealed to the Author! Author! community, calling upon queriers brave and true to volunteer their real queries for discussion here. These are actual queries from your actual fellow writers, campers: I’m sure I don’t need to remind you that while we welcome constructive criticism here at Author! Author!, we should all be grateful that these hardy souls have been generous enough to help further our discussion.

So on this day of examining common presumptions from both sides of the querying fence, I am delighted to bring you what from a writerly perspective might be considered an excellent query letter for a genuinely interesting-sounding book, courtesy of Author! Author! reader Kitty Hawk. As with all of our never-to-be-sufficiently-thanked Queryfest exemplars, Kitty’s name and contact information have been altered to protect her privacy. And as always, if you are having trouble seeing the particulars, try holding down the COMMAND key and pressing + repeatedly to enlarge the image.

Sounds like a heck of a good read, doesn’t it? It also, thank goodness and Kitty’s great good sense, steers clear of all of the problems we discussed above. She’s also, very much to her credit, caught the YA tone exceptionally well here: while the level of word repetition and relatively simple sentence structure would not be pluses for most adult fiction queries, a Millicent working for a YA-representing agent would certainly have no trouble appreciating Kitty’s familiarity with the conventions, vocabulary, and tone of her chosen book category. So far, very well done, Kitty!

Yet although virtually the entire letter is devoted to a description of the book, Millicent might well stop reading before she learns much about it — and for a reason that, like so many of our double-sided tactics above, was probably far from Kitty’s intent. Any guesses what it is?

Hint: the devil is in the details here. You’re going to need to take a very, very close look at the page.

That means, naturally, if your hand immediately shot skyward as you cried two paragraphs back, “This letter is in business format, not correspondence format,” you hit upon a reason Millicent might have taken this letter less seriously if it arrived via regular mail — even at this late date, business format is not considered particularly literate by people who deal with books for a living — but not typically an instant-rejection offense. Besides, since most e-mail programs more or less force unindented paragraphs, this oversight wouldn’t particularly matter in an e-mailed query. Since Kitty submitted this to Agent McAgentson via e-mail (via me), I vote for cutting her some slack on this one.

Ditto if you pointed out, and rightly, that Kitty has included only one means of contacting her — a no-no, even in an e-mailed query. She should have included the whole shebang: mailing address, phone number, e-mail address. Yes, Millicent could simply have hit REPLY to ask for pages, but as we discussed earlier in this series (but not as early, I believe, as the date Kitty sent today’s example to me), queries get forwarded around agencies all the time. So if an administrator or Millicent’s boss, the agent, had forwarded it to the screeners, or one screener had forwarded it to another (not at all implausible, considering how many Millicents are students working part-time as interns), that request for materials would head back to the sender, not Kitty.

Of course, that could still happen if Kitty includes her full contact info, but still, it’s always a good idea to make it as easy as possible for the agent of your dreams to contact you. Hawkeye might have a question best discussed by phone (unlikely at this stage, but not unheard-of), or the agency might print out successful queries. Or — sacre bleu! — Kitty’s eventual submission might get misplaced, and Millicent might have to go tearing through the files, frantically trying to track down a means of contacting her.

Anyway, Kitty does not have the usual justification for not wanting to devote several lines of the page to the way contact information is usually presented in correspondence format: this query is quite comfortably under a page. Especially as — and again, while Millicent might see this as a gaffe, most aspiring writers would not — the right and left margins are not the usual 1 inch, but 1.25. That allows plenty of room for adding necessary information.

What might this query look like with these small, purely technical errors corrected? Glad you asked. In order to help us spot the red flag that might prevent this (again, quite well-written) query from getting read at virtually any U.S. agency, as well as the pale pinkish flag that might cause some Millicents to delete it after paragraph 1 if it were sent via e-mail, let’s make the cosmetic corrections and see just how big a difference it might make on the page.

Quite a difference for less than a minute’s worth of revision, isn’t it? And now that you see the two letters side by side (or, more accurately, stacked), can you see why Millicent might well have had a visceral negative reaction to the first? The first version scans like a printed-out e-mail; the second looks like a letter.

Okay, now do you see the instant-rejection trigger? What about the reason she might have stopped reading a few paragraphs in, or the reason she might not have made it all the way through that quite nice description? No? Then how about the structural choice that might cause a time-strapped Millicent — aren’t they all? — to assume that this letter contains less professional information than it actually does?

Now that I’ve dropped that tonnage of hint for the last one, let’s concentrate on it first. To figure out what Millie might have expected to see earlier in the letter (oops, there I go again, bouncing those hints), why don’t we refresh our memories about the requisite vs. the merely helpful elements to include in a query letter, checking to see which, if any, Kitty has omitted?

What a fine idea, if I do say so myself. A query letter must contain:

1. The book’s title

2. The book’s category, expressed in existing category terms

3. A brief statement about why you are approaching this particular agent

4. A descriptive paragraph or two, giving a compelling foretaste of the premise, plot, and/or argument of the book, ideally in a voice similar to the narrative.

5. An EXTREMELY brief closing paragraph thanking the agent for considering the project.

6. The writer’s contact information and a SASE, if querying by mail

And it may be helpful to include:

7. A brief marketing paragraph explaining for whom you have written this book and why this book might appeal to that demographic in a way that no other book currently on the market does.

8. A platform paragraph giving your writing credentials and/or expertise that renders you the ideal person to have written this book.

Okay, how did this query do? It does contain the title and the category, as well as a nicely-written description of the book and a polite, if rather terse, sign-off. But that’s it. Millie would be left to guess why Kitty was approaching her boss, whether she had any previous publications, and to whom, out of the wide and varied array of YA readers, this book is likely to appeal and why.

I can’t even begin to estimate how often screeners receive queries like this, book descriptions shoehorned into letter format. Yes, it makes the story sound appealing, but if it weren’t addressed to an agency, a reader might even have a hard time figuring out that it is a query intended to solicit an invitation to submit a manuscript, rather than a sales pitch for an already-published book..

“That last paragraph, while I do indeed that information, doesn’t make much sense if it isn’t a query,” Millicent muses, “so I suppose it must be. But honestly, does Kitty assume that an agency receives no correspondence other than queries?”

Yet, again, from a writer’s perspective, there’s absolutely nothing wrong with this query as it now stands, other than a few typos. (We’ll be getting to those later.) It’s polite; it contains what many first-time queriers would assume was the totality of the information necessary in a query letter; it’s genre-appropriate and presumably addressed to an agent who represents books like this.

All of this is good — but by not including all of the elements Millicent would expect a writer familiar with the querying process (and thus a homework-doer) to display, it inevitably comes across as slightly less professional than it could. The big tip-off that Kitty is new (or newish) to querying: placing the book’s title and category at the bottom of the missive.

Why is that a sign of relative inexperience? Because screeners scan queries really, really fast — on average, a mailed query will receive less than 30 seconds of her attention, and that’s counting stuffing the form-letter rejection into the SASE. For e-queries, it’s often even less.

So I ask you: is it really a good idea to make Millie scroll down to learn what kind of book this is? Or to presume that she will read a paper query all the way to the closing thank-yous before deciding whether this manuscript belongs in a book category her boss currently represents?

Don’t believe it would make much of a difference? Okay, here’s that query again, with nothing changed except the title and category’s being moved to the top. Oh, and I’m going to add a date, to decrease the (possibly accurate) impression that Kitty might be mailing precisely the same query to every agent in the country that represents YA paranormal romance.

I see your brows knitting: you’re thinking it looks a trifle funny now, don’t you? Millicent can tell right away whether it’s a book in a category her boss represents, but the presentation is awkward. Also, why include the word count, unless Picky and Pickier’s guidelines specifically ask for it? THE GROTTO is not long enough that mentioning this detail is going to be a deal-breaker — as it often is, if the count is over 100,000 words — but wouldn’t it be more to Kitty’s advantage to use that space for something else? Like, say, some mention of why, out of all the agents currently working in the U.S, she is approaching Hawkeye, or who might want to read this book?

And I’m sure it didn’t escape your sharp eye that in order to fit in the date, I had to skimp on the number of lines between the Sincerely and the contact info. Millicent would have noticed that, too.

So how are we going to free up the requisite space to personalize this query for Agent McAgentson? Well, for starters we can tighten that description: since Millicent is expecting a description only 1-2 paragraphs long, that’s to Kitty’s advantage, anyway. That will enable us to lessen the word repetition and move a nicely unusual detail closer to the top.

Absolutely no doubt that it’s a query now, is there? It’s also clear from the get-go that it’s a book that Hawkeye represents — it must be, since Kitty’s mentioned a similar book. Heck, she even has room now to add a paragraph about her writing credentials, educational background, and/or relevant life experience.

I’m sensing some disgruntlement out there, though. “But Anne,” lovers of completeness point out, “we get less of the story this way. True, it is less word-repetitious, and that nice YA tone still comes across loud and clear, but shouldn’t Kitty want to cram as much of the plot into her query as humanly possible?”

Not necessarily, completeness advocates: all she needs to do is establish her protagonist as an interesting person in an interesting situation, setting up the central conflict — or, in this case, three — and giving Millicent some sense of what’s at stake. Check, check, and check. This version also enjoys the advantage of getting to the paranormal elements faster.

Oh, hadn’t you noticed that a screener would have to make it halfway down the page in the original version before encountering any paranormal element at all? If Hawkeye represents only paranormals, rather than straight-up YA romances, Kitty’s legitimately paranormal story might easily have gotten dismissed as not right for the agent’s list.

The two reasons that many Millicents would have stopped reading before the end of the original version are quite a bit more apparent now, though. Did you catch either?

If you murmured, “Well, I did notice that the tense kept changing,” give yourself a nice, warm pat on the head. For fiction, a book description should be entirely in the present tense. And remember, tense consistency is considered a sign of professionalism.

If you also called out, “Hey, there are quite a few typos here,” feel free to rub your tummy as well. Like college application screeners, most Millicents are specifically trained to stop reading after just a few typos.

Both are easily fixed, however, at least by hands not feverishly occupied in patting a head and rubbing a tummy at the same time. Personally, I would add the characters’ ages — a standard professional touch — but again, that’s the work of a moment. So is punching up the language a little to make Leah seem a bit more active, always a plus in a protagonist, and excising that minor cliché about having nowhere to turn. And If I knew more about the story, I would like to add a clearer sense of what her destiny entails, but for now, I’m going to have to leave that to the person best equipped to fill in the details, the writer.

Which leaves us with only the seemingly unimportant oversight that might well have prevented Millicent from reading the body of this letter at all. Ready, set — discern!

Please tell me you spotted it this time. Hint: to Millicent’s eye, it’s a pretty clear indicator that Kitty has been reusing the same query over and over again, merely changing the agent’s address and salutation this time.

That’s right, campers: Kitty addressed the query to Dear Mcagentson, rather than Dear Ms. McAgentson. While the missing honorific might have been the result of a simple slip of the mousing hand while cutting and pacing, mispunctuating the agent’s name — and thus effectively misspelling it — implies hasty retyping. Believe it or not, both are common enough agents’ pet peeves that much of the time, either will get a query rejected unread.

Isn’t it amazing how changing just a few elements, matters that might well strike a writer as trivial, can make such a monumental difference in how Millicent would receive a query? And isn’t it nice to see Kitty’s good story presented professionally, to maximize its chances of getting picked up?

The answer on both counts, should you be wondering, is yes. Let’s take one last look at her query, all polished up.

Ah, that’s nice. Please join me in thanking Kitty profusely for allowing us to deconstruct her query — and in wishing her the very best of luck in finding the right agent for what sounds like a wonderful book.

More real-life query examples follow in the days to come. Watch those assumptions, everybody, and keep up the good work!