Reasons I Didn’t Accept Your Review Request

photo-1424115087662-5845efc6b366Awhile back I wrote an article entitled “Four Reasons I Didn’t Finish Your Book”; it was a basic rundown of reasons why I usually DNF books. The article is one of my most liked articles, and thinking back on it, I decided to take the same idea in another direction.

Here’s the thing: I get a lot of review requests. I’m three years into my Author Unpublished blog and I now get sometimes upwards of 10-40 e-mails each week from authors who are interested in having me review their books. It’s awesome—it really is—but as much as I’d love to, I can’t accept every review request sent my way. It’s just not possible to read that many books each year. I mean, that’s like 520-2,080 review requests in a year. Even if I read a book a day, there’s no way I could get that done. It’s inevitable that I will turn some requests down… but I also understand that being on the other end of things, authors may not always realize why they aren’t getting responses, or why their requests are denied. So, I thought I’d sit down today and shed some light on the complicated process of whittling down a year’s worth of review requests to something a bit more manageable.

First of all, understand that I only read 50-112 books a year on average, and that’s my ideal number barring illness, vacations, computer issues, or whatever else that may pop up to prevent me from reading and posting reviews. So the number one reason your book may get denied is that I simply already have too many books on my list that I’ve agreed to review. This is made worse by the fact that if I do end up agreeing to a review and then not getting it done… that book review request is then rolled forward into the next year. So already, that 50-112 books a year is starting to look more like 30-92.

book-1171564_1920The second hurdle is whether or not you’ve read my Review Policy & FAQs. I can tell when you haven’t. To be fair, I’m a pretty good sport about it. If you haven’t read my FAQs, I may give you some leeway, because I understand that you, as an author, have probably sent review requests to any number of reviewers, and as long as my FAQs page is, you probably didn’t bother to read it. I get it. At the same time, however, the FAQs is important because all the steps I wrote into it for you to follow… yah… it makes the process of deciding if I want to read your book easier. So if you didn’t follow my FAQs, well, sometimes I just can’t be bothered. A lot of what I’m going to be including on this list from this point forward is directly related to my Review Policy & FAQs, so seriously… read it.

Super nice, personable authors are more likely to have their books reviewed. I’m all for the professional, impersonal review request, but the less human you seem, the less likely I am to feel bad about turning your review request down. Sometimes I accept review requests because authors are super nice and friendly, and I want to do a favor for them. I know, it’s ridiculous, but it works. By the same token, if you’re demanding, sound arrogant, or you’re just a good old fashioned jerk… I’ll probably toss out your review request without reading any of it.

pen-1329258I also throw out review requests from authors if I’ve read their work before and didn’t like it because they’re wasting my time. Chances are if I didn’t give your previous book at least a 3-star review, I’m not going to like any books you write after that… so don’t bother. Really. It’s nothing personal, I just don’t want to write you another negative review. I know it hurts your feelings, and I feel bad about it. Don’t make me.

Another reason I might toss out a review request is if the cover is terrible. I feel like I need a caveat here. Your book cover has to be really terrible for me to toss out your review request—like you’ve put in almost no effort at all. If your cover is just sort of “meh” then I’ll still go on to investigate further. Don’t freak out.

If your back-cover blurb isn’t interesting, or contains a topic that I’m not a fan of, you’ll probably get tossed… because let me be honest, I don’t want to read a boring book, and if you can’t hook me with a blurb, there’s no way you’re going to hook me with the actual book. That doesn’t mean your book is bad, every reader has a genre they just aren’t a fan of, and if you fall into that category, I’m not going to waste my time or your stars.

book-15584_1920So here’s where things become less of a checklist and more of a process. When I receive a review request, the first thing I do is read the genre, any personal note you’ve included, and then the back-cover blurb. If you haven’t included any of those things, your book is in the trash. (Okay, that’s not true. I have an actual folder dedicated to rejected review requests. Yes, I keep track of them.) If I don’t immediately throw out your request because it sounds sort of interesting in any way shape or form, I’ll do further investigation. Step one of that process is to see if you’ve bothered to send me the book file. If I’m only sort of interested in your request and you don’t send a file, it’s trashed. I don’t want to waste time e-mailing you to get ahold of a file if I’m not really into the book in the first place. As an author, this is an easily passable step. Just follow my FAQs and include the file. It’s as simple as that.

If I’m still interested (and by interested I mean I’m anywhere from “OMG this sounds so good! Gimme!” to “Meh. Maybe it’s okay?”) I’ll go look up your book on Amazon and Goodreads. What am I looking for? Your previous reviews. Let me state it now: If you copy and pasted your previous positive reviews or quotes about your book into your review request… I don’t care. I guarantee you that I won’t read them, because obviously you’re only going to include the most glowing of reviews—and usually those sound fake. No, what I’m looking for are your worst reviews. The one, two, and three-star reviews. If you don’t have any and I was on the fence about your review request, it’s immediately in the trash. The only time this doesn’t apply is if you have zero reviews. I like to give new authors a chance, so if you don’t have any reviews, period, you might still make it through my process.

stamp-114438_1920So, I read the negative reviews—and I mean, really read them. I look to see if there’s a running theme for why people didn’t like your book – or if they’re just being jerks. If the reasons your books got negative reviews aren’t horrendous, you’re probably still in the running. So what qualifies as horrendous? 1. Anything that is my personal pet peeve. 2. Characters that have little to no depth and make decisions that make no logical sense. 3. Rumors of stolen property. 4. Egregious typos. (anywhere under 20 typos is fine… but if you can’t even complete a grammatical sentence, I’m not going to bother.)

If I’m still not sure if I want to read your book, I’ll then go look at the sample on Amazon. I read the first page. If it’s not terrible, your book is in. I’ve accepted it. If it’s boring or ill-written—and believe me, after three years or reviewing, I know if your book is terrible after the first page—I’ll throw it out.

The process I have for accepting and rejecting book reviews isn’t as simple as it first appears. I genuinely don’t arbitrarily reject books very often (and if I do, it’s probably because it was a novella, about poetry, or it had something to do with the military because I can’t be bothered with my least favorite topics). I investigate. I read and re-read requests… and if your book sounds even remotely interesting, I’ll probably read it. I will go out of my way to give your book a fair shot at being read—but again, I can’t read everything. I do reject a lot of books.

Finally, here’s a list of things that won’t get your book arbitrarily rejected—because sometimes I don’t care. If it sounds interesting, I’m going to read it.

  • You followed my Review Policy & FAQs and your book sounds even remotely interesting.approval-15914_1280
  • Your book sounds interesting despite not following my FAQs.
  • Your cover isn’t great, but it doesn’t look like it was painted by a 6-year-old in MS paint.
  • Your book falls into a genre or category that I don’t usually read… but It’s not a novella or poetry.
  • You’ve never had a review.
  • You are an indie author.
  • You’re a brand new author who’s never written a book before.
  • Your book has some typos.
  • Your book/plot sounds weird.
  • Your book’s plot or topic is considered taboo.
  • Your book is x-rated.
  • I’ve reached my quota of review requests for the year. Honestly, I never even look at my quota. You may have to wait awhile, but I won’t dismiss your request because I have too many books on my TBR list.

I try to give authors a shot. So, even though I do reject book review requests quite often, I also don’t arbitrarily dismiss a request for flippant reasons. There are lots of times when I make exceptions. Even though I hate novellas, sometimes I read them. A book’s genre isn’t necessarily going to make me throw it out. I don’t care if your editing is perfect (though I’ll mention it), and I don’t care if you’re an indie author. In fact, 90% of the books I read are from indie authors, not publishers.

So don’t be intimidated in sending me a review request. Yes, I turn a lot of them down, but that shouldn’t keep you from sending them because I honestly try to give a fair shot to every request I get. It’s a complicated process. Just follow the rules and cross your fingers.

Writer’s Tip: Outlining—The Ups and Downs of Figuring Stuff Out

Khet6

What It Means To Be A Pantster

I used to be a pantster; someone who wrote books by the seat of their pants so-to-speak. Writing from the top of your head can be a freeing experience, and one that I’d suggest all writers try out at one point or another. I went through a phase where I was cranking out 6-10k words a day—practically blazing through the first draft of a novel.

Don’t get me wrong, being a panster is great; the creativity flows non-stop and you get a lot of writing done in a short period of time. It makes you feel like you can do anything, and it helps train your brain to write without significant pauses… that is, until you hit the brick wall of not knowing what comes next.

The Inherent Problems With Being A Pantster

Every pantster eventually comes to a point where they pause and say “okay, what’s next?” Because they didn’t take the time to plot out their novel ahead of time, they reach a point where they aren’t sure where to go with the plot. Sometimes the plot gets so entangled that they can’t see an easy way out. Sometimes the on-the-fly novel lacks the appropriate amount of character development or conflict. Some writers get past it; they roll up their sleeves, fix a few things, and keep pushing—but not everyone can. Sometimes things go so awry that you have to start all over. I know, because I’ve done it.

Khet

Once upon a time, not so long ago, I began a novel writing project I hesitantly named Khet. It was originally the story of a girl named Khet, and was set in pre-historic times. It was a fantasy/paranormal/historical/romance mishmash that explored the idea of what would happen if a stubborn little girl stood up to an ancient god. That was about as much as I knew about the story when I began writing, and at about nine chapters in, I got stuck. I didn’t know what kind of story I was writing. I didn’t know the characters. I got to the point where I sat back and took a good look at my story and said “I have to fix this.”

What Is An Outline?

Of course, the easiest way to “fix” Khet, was to start over and begin an outline. Think of an outline as a roadmap: it tells you all the stopping points along the journey to the story… who you’re going to meet, where you’re going to meet them, and what your plans with them are. Some outlines are simple—just a few important points to keep the story on track, like when to introduce a particular character or an outside conflict scenario—and sometimes outlines are remarkably thorough, detailing each step in how a scene plays out, conversations that need to be had between characters, and how tiny details from previous chapters play into the current scene. There’s no wrong way to write an outline, but I’d like to share with you one method of setting up an outline that I’ve personally found useful. I like to refer to it as the branch method.

Branching Out

The idea behind the branch method of outlining is that you start with big, vague concepts and begin to define and detail each concept until you’ve whittled things down to the tiny details. The best way to show this is probably by throwing myself under the bus (yet again) and give you an example from Khet’s outlining process.

When I started re-writing Khet, I started with the big, vague concepts of what the story was about. I chose the themes of my story first:

  • Romance
  • Fantasy

This helped me define what the story was going to be about, and helped me pick the setting. I decided that Khet was going to be about a girl (Khet) that is caught in a war between two species. Her love interest, Leander, is of the dominant species (Felnatherin), and she is a half-breed of Human and Felnatherin decent. This introduced conflict for Khet to overcome.

The next step, was to figure out the conflict points of the story… the bits of drama that spur the story on. So I decided that:

  • There would be a war raging between Humans and Felantherin, and Khet/Leander would have to be on opposite sides of that war.
  • There would have to be an outside conflict to drive the couple together and pose more problems for them. In this case, because of Leander’s love for Khet, he breaks the laws of the Felnatherin to keep her alive. This pits Leander against his own kind, and forces Leander and Khet to get along.

Of course, these aren’t the only points of conflict in the story, but these were the major points. Then I took a step deeper and thought to myself “If Leander hates Humans (as do all Felnatherin), what would make him fall in love with Khet? What keeps him from following the law of his people?” Light bulb! Khet looks just like the sister (Arielle) that Leander was forced to kill in the past (because she sided with the humans and broke Felnatherin law herself. He is a peacekeeper for his people). Because Khet looks identical to Arielle, Leander has to step back and take a moment to think before he executes her. He didn’t enjoy doling out punishment to his sister the first time around, and he couldn’t bring himself to do it a second time. Not only that, he was also curious to see WHY this girl had suddenly appeared that looked so much like his dead sister.

This brought up all sorts of conflict. Suddenly I had the beginnings of a real story. From there, I branched out yet again, taking time to decide why certain characters made the choices they did and what the consequences of those choices could be. I introduced new characters and started to plot out how those characters were involved with the overarching plot and how they worked to help or hinder the story of Leander and Khet. I spent time creating the rules of my universe: how bloodlines of Felnatherin transferred from generation to generation, the laws of the Felnatherin Court, the history between the two races that created the war.

Before I knew it, I had an entire notebook detailing the overall plot of my story and a list of characters. From there, I went one step deeper. I went back over my notes, throwing in sticky notes and comments in the margins—dividing my story into scenes, POV’s, and listing important conversations or incidents that needed to happen for the story to work. This gave me time to go back and fix continuity errors, add and remove characters, introduce new sub-plots, love interests, and details, and change things around that didn’t work on a second look (or replace them with better ideas!).

The next step was to organize it all. I started to write out a detailed outline detailing each scene, the location it took place, the time of day, weather, the characters involved, and a run through of how the chapters would play out from the first line to the last. It wasn’t super-thorough… I didn’t write out dialogue or actions, just general ideas, feelings, and context such as:

Chapter 8: The River Valley Village, Mid-Morning, Summer, Hot & Humid. Characters: Khet, Harith (brother), Safiya (sister), Hala (mother). POV: Khet.

Khet enters town, blinded, but she can get around easily enough. The village is alive with the sound of drumbeats and the smell of roasting meat. People move past Khet with purpose, barely paying her any mind. Everyone is focused on the upcoming ceremonies. By now, most people are used to the crippled girl getting around on her own and maybe, are even a bit wary of the fact that despite her blindness, she navigates with certainty and ease. They may believe there is some supernatural aspect to it.

The drumbeats at the village center reach a crescendo and then stop abruptly—signaling the arrival of the Felnatherin presiding over the maturing ceremony. The sudden silence sends a chill up Khet’s spine and she stops in her steps for a moment, turning towards the center of town—though blinded or not, she would not have been close enough to see.

A hand grabs her arm and a familiar voice guides her away from the center of the village, towards her home. She recognizes the voice immediately as that of her elder brother, Harith, and she is glad that he’s come to greet her. She needs to watch her actions and be careful not to draw attention to herself while the Felnatherin is in town, and without being able to take off her blind, it was difficult for her to tell who was around, even in so familiar a place.

He scolds her in a not-unfriendly way, telling her she is late and their mother is agitated beyond belief. Khet apologizes, but they both know her mind is on other things. If her ceremony ends up in marriage, these will be the last few hours where Khet has any freedom without her blind. It’s a daunting prospect. He compliments her on her new necklace (given by Adala in the previous scene).

Harith guides Khet home and then leaves (he has duties to attend?). Khet enters their meager family hut, which is bustling with activity.

Transition Setting: Khet’s family hut inside the river valley village, mid-morning, summer, hot and humid—but cooler indoors, and dark. Characters: Khet, Safiya, Hala. POV: Khet.

Khet removes her blind. Her elder sister (Safiya) is diligently finishing the last few bits of adornment on her ceremony outfit. When Khet enters, her sister scolds her for being late and threatens Khet to be sure that she pretends they aren’t related. She doesn’t want her association with the blind girl to ruin her last chance at marriage (Having failed to secure a husband at her first ceremony the year before).

Their mother scolds Safiya for being cruel to her sister, but asks Khet to understand… Safiya is nervous that she may miss out again this year. Khet shakes her head and says that Safiya is right. She has no intention of ruining her day, and she certainly hopes she doesn’t find a groom for herself. Her mother chastises her for wishing something so odd, but Khet explains her worst fears: that she will have to hide her secret for the rest of her life. She can’t explain to a husband that she’s been pretending to be blind her entire life, and she can’t explain why their children would be born with green eyes—the eyes of the Felnatherin. The voiced fear puts a stop to her family’s activities. She shrugs and says that she’d rather live the rest of her life alone than live with that fear.

Safiya tells Khet not to sulk, and ready, leaves to join the ceremony. Khet’s mother tells her not to worry and helps her to quickly get read.

Notes: Make Safiya’s dislike of her sister clear. Show that although she puts on a brave front, Khet is frightened by what her future might entail, and though she says she hopes to never get married or have children, she secretly wants both… just not at the expense of her freedom. Khet at some point should ask about Ruwa (Khet’s eldest sister)—where she is, what she’s doing. (Side note: Ruwa is also unmarried)—she is helping their grandmother set up the ceremony. (Side note: The Grandmother is one of the village elders).

As you can see, there’s enough detail to give a complete run-through of what will happen in the chapter and any important points that need to be made, but not so much detail that it’s a chapter in-and-of itself. I didn’t add in their conversations word-for-word or the little movements they make (like ducking under the entrance to the hut, or removing Khet’s blind and tucking it in her waistband), but I have a pretty good  idea of where the chapter will go, what will happen, and what conversations need to take place. The next step would be the First Draft.

There are a lot of ways to outline. Some people make point-by-point lists. Some organize scenes onto notecards. Some outlines are incredibly detailed, and some are vague. This isn’t the only way to create an outline, and it won’t work for everyone. I like it because it allows me to study the bigger picture of my story first, and then slowly whittle it down to the details. By the time I get to this final version that’s scene-for-scene, I don’t have any major points that need to be moved around or fixed. If I get ideas along the way for new characters or new conflict, it’s easy to write them on a sticky note and slide them into the outline. I can go back chapters ahead of where I am and add in side-notes of things that need to be addressed that have an impact on later chapters. This kind of outline feels natural to me because as the outline progresses, so does the fleshing out of the story. It’s easy to fix, and in the end, I pretty much know what’s going to happen in my story, all that’s left to do is to get to the fun part: writing it.

As I’ve said before: there’s nothing wrong with being a pantster—I encourage everyone to try it—but personally, I like being a prepared pantster. I can sit down and write my heart out after I know where the story is going rather than trying to figure it out on the fly. Ultimately, I know it’s going to lead me to having a better book because I’ve had time to really stop and think about things like bloodlines, historical events, the reasoning behind character’s actions, and the possibilities that their dialogues spur on. By the time I’ve gotten to the first draft, I know I’ve made sure I have enough conflict and that the characters actions will make sense… and the most pressing problem I’ll have is my sentence structure and punctuation.

Outlining isn’t an easy process. It takes time—lots of time. Sometimes it takes me a day or two to figure out how to solve a problem Khet and Leander face. Sometimes I create more problems for myself by changing a scene that other scenes relied on later in the story, and I have to then go back and figure out how that change butterfly-effected it’s way on down through the rest of the plot. There were times I got to chapter thirty-something and realized that I had a much better idea for how a scenario would play out and I had to go back to chapter one and remove a character that no longer needed to be in the book. Outlining is like trying to piece together a puzzle that is constantly changing it’s picture…. but it’s a lot of fun, and it’s so worth it in the end when you sit back and say “I know where my story is going.” and then sit down and write it.