Formatpalooza, part XVII: not all that glitters is…well, you know the rest

sequined hat

I had hoped to wrap up Formatpalooza by the end of the year, but frankly, I think it’s going to be a trifle on the tight side, unless I post a couple of times tomorrow. Even by my standards of vim, that might be overkill.

My vehemence is kindly-motivated, I assure you: contrary to popular opinion amongst aspiring writers, how a submission is presented can make a very great difference in how it’s received. Yes, yes, I hear you, those of you who have been running around to writers’ conferences in recent years: you can hardly throw a piece of bread at an agent or editor’s forum without hitting a pro saying, “It all depends upon the writing.”

They tend to spout this aphorism for a very good reason — it is in fact true. But as we discussed both earlier in this series and in earlier ‘Paloozas, that doesn’t mean that the quality of the writing is the only criterion agents, editors, contest judges, or any of the rest of us who read manuscripts for a living use when deciding whether to read beyond the first page of a submission. Professional presentation plays a role, as does marketability, a story’s probability of appealing to its target audience (not exactly the same thing), what happens to be the surprise bestseller of the moment — and yes, that whole slew of intangibles that make up personal taste.

There is, in short, no such thing as a foolproof formula for producing the perfect manuscript for submission. Sorry to be the one to break that to you.

As I’ve been arguing throughout this ‘Palooza, however, agents, editors, contest judges, screeners, and other professional readers develop an almost visceral sense of when a manuscript is properly formatted. So rather than screening submissions with a list of don’t by their sides, they more or less automatically discount pages that are cosmetically incorrect.

This is most emphatically not the same thing, though, as rejecting such pages on the spot because, say, an aspiring writer underlined a foreign-language word on page 1 instead of italicizing it. (I know, I know: sacre bleu!) Much as a reader with impeccable grammar will not necessarily throw down a book that misuses semicolons, most professional readers will not instantly reject an improperly-formatted submission without some further provocation.

But as we discussed last time, the writer in both cases is going to have to work a whole lot harder to impress the pro as literate. Unfortunately, the prevailing standards for printed books — which, as we have seen, differ in many significant respects from manuscripts — often lead innocent writers astray.

Leading them to, say, include a table of contents in a manuscript submission.

That seems as if it would be a helpful page to tuck in there, doesn’t it? One can make an argument for it, certainly: in fiction, including it would enable an agent to go back and re-read the submission easily; in nonfiction, it would permit an editor to skip ahead to a chapter of particular interest. And heck, if the manuscript fell upon the floor in the kind of you got chocolate in my peanut butter!/you got peanut butter in my chocolate! we witnessed with horror earlier in this series, a well-organized table of contents might render it a trifle easier to reassemble, right?

Wrong. Including a table of contents in a manuscript submission is a classic rookie mistake, the kind of stunt that makes Millicent the agency screener roll her eyes.

Why is it such a serious strategic error? Well, in a published book, a table of contents, like an index, is a courtesy to browsers trying to get a feel for the contents and buyers who do not necessarily want to read the entire book. In order to serve this function well, however, the pages listed would have to match up with the beginnings of the relevant sections, right?

This is difficult in a manuscript, for several reasons. First, Millicent doesn’t expect to see a table of contents, particularly in a novel submission; it just won’t look right to her. Second, since a published book is typically about 2/3rds the length of its original manuscript (documents shrink in the transition to the printed page), the pages listed on a manuscript table of contents would ultimately be inaccurate, anyway.

Third — and perhaps most relevant at the submission stage — including a table of contents implies that the writer does not expect the agent of her dreams to read the manuscript in its entirety, but merely to flip to the pages that interest him most. From the publishing industry’s point of view, that’s a pretty jaw-dropping assumption: why, they wonder, would an agent or editor be interested in acquiring a book if he doesn’t like it well enough to read it in full?

So really, including a table of contents in a manuscript is just wasting a page. It does not belong in a manuscript, any more than an index or those boxes around text that magazines are so fond of printing. To professional eyes, it looks unprofessional, especially in a novel submission.

It’s also an inconvenience — and yes, Virginia, to someone who has to skim as quickly as Millicent to get through the day’s reading, having to turn over an extra page is an actual inconvenience.

Don’t believe me? Okay, think about our time-strapped friend’s expectations when opening a submission envelope: when she turns over the title page, she is looking forward to finding the first page of text there waiting for her, all ready to be judged in a flash. If instead she finds a table of contents, something she would only find helpful if she were to read the entire manuscript, she may well be a trifle miffed. Given that she tends to reject most submissions somewhere between paragraph 1 and page 5, the information that Chapter 8 begins on page 112 will most likely strike her as at best gratuitous — and at worst presumptuous.

“What gives?” she’ll say, taking an extra sip of her too-hot latte as she impatiently gets the table of contents out of her way. “Doesn’t this writer know the difference between a manuscript and a book?”

‘Nuff said, I think.

Or maybe not — do I hear some aspiring nonfiction writers clamoring for my attention? “But Anne,” these excellent souls point out, “a book proposal is supposed to include a table of contents for the planned book, isn’t it? I read it in an article on how to write a book proposal.”

Ah, I’m glad that you brought this up, nonfictionists, because first-time proposers often conflate the table of contents one might find in a published book with the annotated table of contents required in a book proposal. They are in fact quite different things.

Again, mixing up terms is a classic rookie mistake. Over and over again, I see aspiring writers new to the game simply assuming that because a term means something in one context, it must necessarily mean exactly the same thing in another context.

As a general rule of thumb, that’s not always true. In this case, it most definitely is not.

When hyper-literal proposers hear the term table of contents, they assume, wrongly, that an agent or editor is simply asking to see what the writer thinks the table of contents in the published book will look like, presumably as an exercise in guessing how many pages each of the proposed chapters will contain. (It’s hard to imagine it serving any other purpose.)

As a result, first-time proposals tend to include a section that looks a little something like this:

Leaving aside for the moment the fact that Millicent simply would not expect to see this page in a book proposal at all , do you see any problems with this as a marketing document intended to convince an editor to pay the writer to write the proposed book?

Actually, I’m sure that some of your hands shot into the air even before I showed this example, in your eagerness to take issue with the notion that a submission should resemble a published book in the first place — and thus that the kind of table of contents one might expect to see in a nonfiction book would clearly be out of place in a submission.

Well caught, eager wavers. Spot any other problems?

If you said, “Well, for starters, the example above doesn’t include information that could possibly be either accurate or useful to an editor,” give yourself a gold star for the day. Obviously, it would be impossible for a proposer to state with certainty where the chapter breaks would fall in the proposed book when published; all the information s/he could reasonably offer in this sort of table of contents would be educated guesses about how long each chapter might be. Or perhaps a list of where those breaks fall in the draft manuscript.

But that’s not the information nonfiction agents and editors want to see in the book proposal; they’re perfectly aware that since the book in question has not yet been written (or needn’t be), any length estimates must be just that, estimates, not fact. The information they do want to see in the annotated table of contents section of a book proposal is a brief description of the CONTENTS of each chapter.

The word annotated should have been a clue, I guess.

Typically, each proposed chapter is summarized in one or two paragraphs. Well, typically is a bit of an exaggeration; what’s actually typical in a first time proposer’s book proposal is either the information-light version we saw in today’s first example or an entire page devoted to each chapter.

Neither is what is expected, however. The typical form I am talking about here is what professional nonfiction authors use.

And like so many other differences between professional formatting and, well, everything else they see in submissions, it’s really, really obvious at first glance to someone who has seen a book proposal before whether the submitter du jour has followed the rules. Compare what the first page of a correctly put-together annotated table of contents looks like with the truncated version above:

See the difference? Millicent will. From ten paces away.

Hey, while we’re on the subject, why don’t we take a quick gander at all of the constituent parts of a book proposal, so all of you nonfiction writers out there may be sure that Millicent will like the look of yours? To make the overview even more useful, let’s run through the sections in the order they would appear in the proposal.

First, let’s take a peek at the title page. See if you notice anything distinctive about it:

If you immediately cried, “Why, unlike a title page for a novel, the proposal’s title page does not include a word count,” give yourself another gold star. (You’re racking them up today, aren’t you?) The length of a nonfiction book is a contractual matter; since what a proposal is offering is not the finished book, but a book concept and an author to write it to the specifications desired by the publisher, it does not make sense for the writer to guesstimate the length up front.

Award yourself yet another if you also mentioned that the contact information listed here is Scaredy’s agent’s, not Scaredy’s. Naturally, if Napolèon does not yet have an agent, naturally, he would list his own contact info in the bottom-right corner.

Any guesses why his address would be replaced by his agent’s down the line?

The reason is pretty straightforward: no agent in his right mind would allow his clients to circulate their proposals (or manuscripts, for that matter) without his contact info on them. After all, if an editor falls in love with the proposal, it’s the agent she’s supposed to be contacting, not the writer.

What follows next in a book proposal is the overview, a brief description of what the book is about and why the writer proposing it is the best person on earth to write it. Never, ever forget that this is both a marketing document and a job application, proposers: you’re trying to get the publisher to hire you to write this book, right?)

Most first-time proposers just include the bare bones here, leaping right into the description, but I like to open with a little sample of the type of writing the editor may expect to see in the completed book. To this end, I always advise starting a proposal with a vividly-told illustrative anecdote.

The first page of the proposal, then, would look like this:

overview1

As you may see, like everything else in the book proposal, the overview should be in standard format: double-spaced, indented paragraphs, 12-point Times, Times New Roman, or Courier. Unlike the opening of a chapter, however, each new section is simply titled, a line skipped, and the text begun. Since this is a nonfiction document, whether to place OVERVIEW in boldface is up to you; my agency happens to like it, as well as the all-caps titling.

Notice, please, that because this is a proposal for a memoir, the anecdote is written in the first person singular. The rest of the proposal should be as well. Many memoirists mistakenly believe that writing about their books in the third person is more professional, but that’s simply not the case.

Back to formatting. Just as a simple section break is sufficient to separate scenes in a novel or memoir, all that’s required in a proposal to differentiate the opening anecdote from the description of the proposed book is a skipped line:

overview2

Since the overview typically covers a broad range of topics, I like to break it down into several smaller sections, to make it easier for an agent or editor to find the answers to the pertinent questions any good book proposal must answer. Every proposal is slightly different, of course, but typically, apart from the opening anecdote and the book’s description, I advise including subsections on why the proposed book will appeal to readers (this is a great place to bring up any demographic information you may have collected on your readership), why the book is needed now (as opposed to any other time in publishing history; this provides an excellent opportunity to bring up any relevant trends), and how to convince the target readership that this is the book for them (not a specific marketing plan, mind you — that comes later in the proposal — but a brief explanation of who the target reader is and why that reader might pick it up).

Nit-picky? Sure. But that’s the nature of a book proposal.

How does one mark each of these subsections? You already know how to do this one, actually: as is permissible in a nonfiction manuscript, to differentiate between topics within sections — to alert the reader to the start of the subsection on why you’re the best person currently gracing the crust of the earth to tell this particular story, for instance, or to usher onstage your explanation of precisely why the literate world needs this story right now — you may insert a subheading. To reuse the example from the last time we discussed subheadings:

Wharton subheading example

When moving between major sections of a book proposal, convention dictates inserting a page break between sections. Why? Because unlike a novel manuscript, proposals are often broken apart, with one section going to a publisher’s marketing department another going to legal, a third staying with the editor interested in acquiring it, and so forth.

It’s also customary to begin a new major section with a centered title. For example, when moving from the overview to the competitive market analysis (i.e., the section of the proposal where the writer lists similar books currently on the market, then explains why his proposed book is different and better), the latter section would begin like this:

comp market analysis

I’ve written at some length about how to construct a competitive market analysis — contrary to popular opinion, it’s not just a list of similar books currently on the market — so I shan’t go into the ins and out of creating this narrative here. But if you’d like to hear more, please check out the posts collected under the aptly-named HOW TO WRITE A BOOK PROPOSAL category on the archive list at right.

There are a couple of formatting curiosities I would like to point out, however. First, the competitive market analysis should be written in a narrative style, not as a list. Second, it does not include all of the bibliographic information for the book. Just the author and title — in italics, as is appropriate for a book title in standard format — with the publisher and year of publication following in parentheses, will generally suffice. (Although if the agent of your dreams asks for something more, like the ISBN, for heaven’s sake, give it to her.)

Is that all there is to a book proposal, you ask hopefully? Heavens, no: there are several more vital sections. As usual, I have a great deal to say about each, so I am going to sign off for today and pick it up next time. Keep up the good work!

6 Replies to “Formatpalooza, part XVII: not all that glitters is…well, you know the rest”

  1. Anne,
    I’m curious about the layout of the memoir title page as shown in this post. Is the fact that the title and author’s name in the center of the page are spaced quite a ways apart something that applies to all non-fiction? Or is it a peculiararity of memoir alone?
    Dave
    P. S. Happy New Year!

    1. Happy New Year, Dave! No, it’s more a combination of what my agency prefers and my not having re-checked that particular example. (I had a health setback just before Christmas, so I’ve been a bit low-energy.) I’ll go back and change it.

  2. Hallo again! How do we format back matter for memoirs? I’d like to include a few appendices and an index with mine, but I have no idea how to go about it.

    1. That’s a good question, Ruth, but before I answer it, may I double-check that you mean formatting it in the manuscript, rather than in the book proposal? In a book proposal, the appendices would appear in the Annotated Table of Contents in the same way chapters would. But you are asking about how to present appendices in the manuscript, right?

      I can answer the part about the index right now, though: you should not include an index in a manuscript; manuscripts do not include them, ever, so it’s not as though Millicent is going to glance at your submission and say, “Hmm, I am looking for something specific. I wish this book had an index.” Why? Well, manuscripts shrink about two-thirds in the transition to published books, so any page reference would be a matter of guesswork, anyway.

      Unless you are formatting a manuscript for self-publication? If so, it still would not make sense to index the book until the print files have been finalized.

      1. Of course, you’re right. Yes, appendices in manuscripts is what I mean. (And indexes, too. I’m guessing then the publisher takes care of indexing? Or would they notify me at the proper time so I could handle it?)

        Would appendices be formatted like a chapter, and then noted in the Annotated Table of Contents? Would one also mention an index would be going there as well?

        Thank you ever so much for clearing this up for me. Your blog has been an awesome help!

        1. Oh, that’s very helpful, Ruth. I think the problem here is that you may be thinking of the manuscript as more similar to the published book than it actually is. Manuscripts do not contain many of the bells and whistles of books: they do not contain tables of contents, for instance, or dedications. There’s a good reason for that — the publisher makes all of the design decisions for the book. The manuscript is the raw material from which the finished book is designed.

          The index is one of those design elements; they’re seldom in a book because the author considers it necessary. Since an index adds pages (and thus expense) to the publishing process, it’s imperative that the publisher retains the ability to decide whether it should be in the book or not. That means, in practice, that the publisher would not expect an author to index a book for herself; it’s not part of the writer’s job. It’s also a highly technical professional skill; there’s more to it than figuring out what is on which page. (But on the million-to-one chance that you ever find yourself in that position, drop me a line — I know a tremendous freelance indexer that I would be delighted to recommend.)

          So you don’t need to think about the index at all, at this juncture, and you definitely should not mention it in the Annotated Table of Contents, because it’s not a chapter. Which is a helpful way to think of it: the ATOC does not contain a description of every element of the book; it merely describes different chunks of text that a nonfiction writer is suggesting the publishing house pay her to write.

          An appendix definitely falls into that category, so if you liked, you could mention it in the Annotated Table of Contents, but it’s not completely necessary. It’s not unheard-of to hold back an appendix, to suggest at a later point. If you see it as one of the selling points of the book, however (and it sounds as though you do), by all means, bring it up.

          And yes, an appendix should be formatted like a chapter. It merely requires a two-line chapter title: the top line would read APPENDIX I (it need not be in caps), and the second would contain the appendix’s title.

          I hope this helps!

Leave a Reply

Your email address will not be published. Required fields are marked *