• strict warning: Declaration of FeedsImporter::copy() should be compatible with FeedsConfigurable::copy(FeedsConfigurable $configurable) in /home/writezil/public_html/sites/all/modules/feeds/includes/FeedsImporter.inc on line 94.
  • strict warning: Declaration of FeedsNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsFeedNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsFeedNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsUserProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsUserProcessor.inc on line 195.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • You must include at least one positive keyword with 3 characters or more.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_plugin_display::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display.inc on line 1877.
  • strict warning: Declaration of views_plugin_display_block::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display_block.inc on line 193.
  • strict warning: Declaration of views_handler_field_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_field.inc on line 641.
  • strict warning: Declaration of views_handler_sort_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_sort.inc on line 82.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 609.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 128.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of content_handler_field::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/cck/includes/views/handlers/content_handler_field.inc on line 208.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_argument_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 770.

How to Find the Right Developmental Editor for Your Book

https://i1.wp.com/writerunboxed.com/wp-content/uploads/2017/02/The-Indie... 300w, https://i1.wp.com/writerunboxed.com/wp-content/uploads/2017/02/The-Indie... 525w" sizes="(max-width: 600px) 100vw, 600px" data-recalc-dims="1" />
Books elicit different responses from different people, so it’s no wonder that the feedback we receive from critique groups and beta readers can be varied and even contradictory. As an indie author, it can be hard to discern good advice from bad or know whose feedback to trust—especially when that feedback is yanking your story in different directions. You can make change after change, only to find that your critique partners are never quite satisfied. If you’ve reached this stage with your work in progress, it might be time to seek the advice of a developmental editor.
Unlike a line editor (who focuses on the granular details of your story, like grammar, sentence structure, spelling, punctuation, tense, fact checking, and voice) or a proofreader (who is usually the final set of eyes and is on the lookout for any mistakes that were overlooked during previous rounds of editing), a developmental editor focuses on big-picture items, like plot and characterization.
I hired a developmental editor before publishing my novel, Empty Arms, and the experience was transformational. With the help of my critique partners, I’d taken my manuscript as far as I could on my own, but something wasn’t quite right and none of us could put our finger on it. After my editor read my manuscript and compiled her notes, we met at a café in upstate New York to discuss her feedback. She showed me structural elements that weren’t working and distracting subplots that could be cut out entirely. She questioned my characters’ motivations and authenticity and helped me identify the true heart of the story.
When I left that meeting, my head was spinning and I faced a serious revision. Rather than wishing me luck and sending me on my way, she encouraged me to revise my outline and send it to her. It took some time, but I did. Again, she showed me what was working, what wasn’t, and why. She offered thoughtful suggestions for improvement, and I revised it again. We spent a few weeks going back and forth until the outline was tight, which made tackling the revisions more manageable.
Since publishing Empty Arms, readers have come up to me, grabbed my arm, and said things like, “I LOVED that book” and “I didn’t see that ending coming.” While compliments like that fill my heart with joy, I know they wouldn’t have been possible without the help of my developmental editor and the massive rewrite she inspired.
While hiring a developmental editor isn’t cheap, their expertise can be invaluable. But it’s critical that you find the right person for your project. Today, I’m going to share my process for doing just that.
Step 1: Do your homework
Compile a list of editors who specialize in projects like yours and have the qualifications to back them up. Research what titles they’ve worked on, how long they’ve been in the business, what type of training and credentials they have, and whether they have any client testimonials on their website. Here are some resources to get you started:

Once your list is complete, send each candidate an e-mail detailing your project (include word count, genre, log line, etc.) and request a time to speak on the phone so you can get a feel for his or her process and pricing. While most editors will be willing to speak with you, a few may be too busy to take on new projects, have a long wait list, or only work with referrals.

Step 2: Interview prospective candidates (and shortlist the good ones)
Treat these phone calls like job interviews in which you are the employer. Don’t be shy about broaching topics like past experience, pricing, and references. A qualified editor will be happy to provide you with this information.
Here are some examples of the kinds of questions you should ask:

  1. Can you tell me about your editing process? What will you expect from me? What can I expect from you?
  2. What is your experience in the industry?
  3. Tell me about a recent client success.
  4. How does your pricing structure work? What would you charge me for my specific project?
  5. What are your payment terms? (50% upfront and 50% upon completion? Payment in thirds?)
  6. Is there a waiting list for your services? If so, when is the next available opening?
  7. If we end up working together, can you provide a letter of agreement that will outline the terms of our relationship? If not, are you willing to sign one that I create so we are both clear on the terms of our agreement?
  8. Can you provide three references that I can contact to discuss your work?

If you’re satisfied with the answers you receive AND the candidate is willing to provide you with references, move them to your shortlist. (One editor told me she could not provide me with any references because of “client confidentiality.” While that may have been true, it made me uncomfortable. So, I crossed her off my list and focused on the editors who were happy to provide references.)
Step 3: Do a reference check
Once you receive the editor’s references, take time to set up phone calls with each of them to get a truer sense of what it’s like to work with the person. My general rule of thumb is to e-mail each reference a brief introduction, tell them you’d like to learn about their experience with Editor X, and request a few minutes to speak on the phone. While it might be easier to ask your questions via e-mail, I like speaking with references on the phone because I can pick up on subtle cues that would be imperceptible in an e-mail—a deep sigh, a long pause. Plus, it allows me to ask clarifying questions and dig deeper into their answers.
Here are some questions to get the conversation started:

  1. What type of project did you hire Editor X for? What type of editing service(s) did Editor X provide (e.g., developmental editing, line editing, proofreading)?
  2. Why did you choose to work with Editor X over other editors?
  3. Do you feel Editor X’s feedback was worth the price you paid?
  4. What was the outcome of your project?
  5. What do you feel was the biggest benefit to working with Editor X?
  6. What could Editor X have done better?

Try to ask open-ended questions to give them a chance to talk about their experience in detail. And be sure to throw in a question like #6 to give the person an opportunity to air any dirty laundry.
Step 4: Make a final decision
Once your reference interviews are complete, you should have a better sense of which candidates might be a good fit for your project. Pay attention to red flags and that nagging little feeling that something isn’t right. The final decision will likely come down to price, timing, and/or gut instinct.
The editor I chose soared through my process with flying colors. She wasn’t the cheapest and she had a considerable waitlist, but I couldn’t ignore the fact that working with her just felt right. We had a great connection on the phone, my project was in her wheelhouse, and past clients raved about their experience with her. Now, every time a reader grabs my arm and compliments my book, it’s confirmation that she was the perfect choice.
Are you thinking about hiring a developmental editor? What questions do you have about the process? Or, if you’ve already worked with a developmental editor, what helpful tips or resources can you share?

About Erika LiodiceErika Liodice is an indie author and founder of Dreamspire Press, where she is dedicated to following her writing dream and inspiring other writers to follow theirs. She is the author of EMPTY ARMS: A NOVEL and the forthcoming children’s series THE HIGH FLYERS. She is also a contributor to AUTHOR IN PROGRESS, the Writer Unboxed team's first anthology. Visit her at erikaliodice.com.Web | Twitter | Facebook | LinkedIn | More Posts

"Write without pay until someone offers pay. If nobody offers within three years, the candidate may look upon this as a sign that sawing wood is what he was intended for"
Mark Twain

Random picks

  • Another great gift idea for the holidays: "Powell's Books has collaborated with Rogue Ales and Spirits to create a beverage for anyone who has a thirst for books and artisan craft beer — White Whale Ale, infused with the seafaring spirit of Moby-Dick. The concept behind the project was to go where beer has never gone before — by adding actual pages from a copy of Moby-Dick to the brew."
  • Dissertation is a very crucial assignment that assigned to students at undergraduate or post graduate level. Many students are only aware about basic knowledge that how to write adissertation but at this level you should produce extra ordinary for good grades.
  • photo by Josef Dunne If you’re new to Twitter, you’ve likely already seen retweeting come up. If you’re about to jump on the bandwagon, this is one of the first things you’ll need to learn. And even if you’re a seasoned tweep, the intricacies of the mysterious retweet can be confusing. Don’t you worry; I’m here to help. Let’s walk through the details step by step. What a Retweet Is A tweet is 140-character message. When someone else publishes a tweet that you like, you can share it with your own followers by “retweeting” it – which you’ll commonly see abbreviated as “RT.” There are several...
  • Poke the Box by Seth Godin My rating: 2 of 5 stars Poke the Box should have been titled Tribes: We Need You to Lead Us – The Remix as Godin brings nothing new to the table other than a relationship with Amazon and some promotional pricing gimmicks. It’s his usual mix of paper-thin insights and exhortations to be bold! to lead! to ship! — but with notably less energy or conviction than usual, as if he wrote it in between blog posts over a rare quiet weekend. I pre-ordered the Kindle version for $1 and read it in a total of about 2 hours, and would still rather pay full price...
  • Science fiction and Fantasy (SF/F) novels and stories often use religious themes as an integral part of the story. Some ideas of why that is so and how to use it to your writing advantage.

Recommended sites

Most recent titles

01
20 hours ago
02
20 hours ago
03
1 day ago
04
1 day ago

Fast fact about writing

Where, and by whom writing was first developed remains unknown, but scholars place the beginning of writing at 6,000