How to Prepare a Novel for a Developmental Edit

A developmental edit is most useful when the manuscript is complete enough to reveal its real structure and open enough to change. Send too early, and the editor diagnoses gaps you already planned to fill. Polish too long, and you may spend months perfecting scenes that a structural revision removes.

Preparation is not making the novel flawless. It is making the version coherent, stable, readable, and accompanied by enough context for an editor to evaluate the pages rather than reconstruct your file system.

Rowan has finished a coastal family saga about three siblings contesting ownership of a fishing business. The opening is polished through six drafts. The final third contains bracketed transitions and two versions of a confrontation. Rowan knows the inheritance motive has changed but has not updated early chapters. Sending this draft would produce expensive feedback on instability rather than the story’s deeper choices.

The right preparation pass closes known structural blanks, documents uncertainties, and preserves the editor’s ability to respond independently.

Decide whether the draft is ready for this kind of edit

A developmental edit examines structure, character arcs, stakes, pacing, viewpoint, logic, genre expectations, and thematic coherence. The draft does not need line polish, but it should contain the whole intended story.

You are probably ready when:

• the manuscript has a beginning, middle, and ending;
• placeholders do not conceal major scenes or outcomes;
• you have completed at least one author-led structural pass;
• the current file represents one set of choices, not competing versions;
• you can describe what kind of feedback you need;
• you are prepared to consider substantial change.

If you already know the ending is missing or the protagonist changes halfway through, finish that work first unless you are specifically hiring for an outline or partial-manuscript consultation.

Clarify the service and deliverables

Editors use terms differently. Ask what the edit includes: editorial letter, in-manuscript comments, sample line notes, call, follow-up questions, style sheet, or second read. Confirm word-count basis, schedule, payment, file format, and whether the editor works in your genre and draft stage.

Request a sample edit or consultation when available, especially for a long engagement. Evaluate whether the editor identifies underlying problems, explains reasoning, respects the book’s aims, and distinguishes observation from prescription.

Compatibility does not mean agreement. A useful editor may challenge the manuscript. You need confidence that the challenge is specific, intelligible, and directed toward the novel you are trying to write.

Do not assume a developmental edit includes copyediting, fact checking, sensitivity reading, or formatting unless the agreement says so.

Stabilize the manuscript version

Choose a cut-off date. Resolve duplicate chapters, tracked alternatives, and notes such as “maybe kill him here.” Fill transitions enough that cause and effect can be read. Update names, viewpoint labels, and major facts changed during drafting.

You may leave small verification markers, but explain them in the brief. An editor can read [CHECK TIDE]; they cannot assess a climax represented by [ADD RESCUE].

Save the submission as a new immutable version. Use a clear filename such as RowanNovel_DevEdit_2026-08-09.docx. Keep your working draft separate. Do not continue changing the editor’s copy while they read, or later comments will refer to a manuscript that no longer exists.

Back up the exact submission.

Complete one author-level diagnostic pass

Before submission, read for problems you can identify without external judgment:

• missing or repeated scenes;
• chronology and naming contradictions;
• viewpoint labels or chapter order errors;
• unresolved placeholders;
• abrupt changes left from earlier versions;
• unreadable formatting;
• accidental omissions after file conversion.

Do not solve every subtle issue. The purpose is to remove noise that would consume editorial attention.

For Rowan, the inheritance motive must be consistent enough for the editor to assess its emotional and structural effect. Fixing every sentence in the opening is less important than choosing which motive the book currently contains.

Write a short editorial brief

Provide title, genre, audience, word count, one-paragraph premise, draft history, and the kind of edit requested. Then list a few genuine concerns or questions.

Good questions are open and diagnostic: Does Mara’s decision to sell the boat feel prepared? Does the middle sibling remain active after the funeral? Where does the inheritance conflict lose urgency? They tell the editor where you feel uncertainty without dictating an answer.

Avoid a ten-page defence of every choice. Do not explain what scenes are supposed to accomplish. The gap between intention and page is valuable evidence.

Mention non-negotiable boundaries honestly. If the novel must remain single viewpoint or avoid a reconciliation ending, say so. Distinguish artistic commitment from fear of revision.

Include context the manuscript cannot supply

Tell the editor if the book is part of a series, uses material not included in the submission, has contractual length constraints, or has received prior professional notes you already acted on. Explain whether this is a first novel, a translation, or a revision after major life or market changes only when relevant to the service.

For a series, provide a concise previous-book summary and fixed canon, not an encyclopedia. For historical or technical work, flag places where the plot depends on uncertain research.

Disclose content that may affect the editor’s ability or willingness to work. Professional alignment is easier before the project begins.

Format for sustained reading

Follow the editor’s requested format. In the absence of instructions, use a standard readable font, consistent headings, page breaks between chapters, paragraph indents, and generous line spacing. Include page numbers and title or surname in the header if requested.

Remove layout designed for print unless book design is part of the service. Decorative fonts, justified text, manual line breaks, and complex headers make commenting harder.

Check conversion. Open the final file on another device if possible. Verify first page, last page, chapter sequence, italics, scene breaks, footnotes if any, and total word count.

Accessibility matters. Ask whether the editor needs another format and provide it when practical.

Protect an independent first read

Authors sometimes send summaries that reveal every intended interpretation, a list of feared criticisms, and explanations for passages that confused beta readers. This can bias the editor toward your map of the book.

Give necessary context, then let the pages work. If the editor misunderstands a relationship the manuscript expects readers to understand, that misunderstanding is useful data.

Do not include leading questions such as “Did you love the twist where Mara nobly sacrifices her share?” Ask when they recognized the plan, what they believed, and how the choice landed.

Set up a note-receiving system before notes arrive

Create a clean copy of the submission, a feedback log, and a place for questions. Decide that you will read the full editorial letter before editing. Give yourself time between receipt and response.

The log can include note, location, underlying issue, related notes, initial reaction, decision, and revision status. This preparation prevents comments from becoming dozens of isolated tasks.

Do not promise yourself that every note will be accepted. Promise that every note will be understood. The next guide on turning editorial feedback into a revision plan covers that interpretation work.

Plan for communication and boundaries

Confirm how questions should be sent, response windows, and whether a call is included. Gather questions after reading rather than sending reactions one by one. Professional clarity protects both schedules.

If a note feels dismissive, biased, or outside the agreed scope, document the concern and raise it directly. An editor’s authority does not override your boundaries or ownership. At the same time, discomfort with a structural note is not proof the note is wrong. Return to page evidence.

Keep personal history private unless it helps the editor understand a boundary or the material’s stakes. You do not need to justify why a story matters to receive serious craft attention.

Budget for implementation, not only the edit

The fee and delivery date are only part of the project. Reserve time after feedback for reading, clarification, planning, and a substantial revision. A developmental edit can recommend changes that take months, and an immediate publishing deadline may make useful advice impossible to apply.

Decide what happens if the notes reveal a larger rewrite than expected. You might revise in phases, request a follow-up assessment, seek targeted readers, or postpone submission. Do not promise an editor or yourself that the next draft will be ready in two weeks before seeing the work.

Keep the editor’s role distinct from your decision-making. Paying for expertise does not obligate you to implement every suggestion, and declining a suggestion does not recover the value of the diagnosis. Budget emotional attention for understanding why a reader had the experience.

If this is a contracted project, clarify which changes are possible within length, schedule, and publisher expectations before the edit. If it is an independent project, protect funds for later copyediting or proofreading rather than assuming structural work produces a clean final file.

Preparation includes creating realistic space for the revision the service is meant to provoke.

Assemble a compact supporting packet

Most novels need only the manuscript and brief. Add supporting material when it reduces genuine ambiguity: a one-page cast list for a very large ensemble, a series-canon summary, a map used for travel logic, or a glossary essential to reading.

Keep each item current and short. Do not ask the editor to reconcile a forty-page story bible with the novel unless that review is in scope. The manuscript remains the primary evidence.

Label whether a supporting fact is established on-page or private intent. If the family tree says Rowan is Mara’s uncle but the novel never communicates it, the editor should be able to identify that gap rather than silently supplying knowledge from the packet.

Know what not to do during the edit

Do not send rolling updates unless agreed. Do not rewrite the manuscript while waiting and expect comments to transfer automatically. Do not recruit many readers to evaluate the same unstable draft, creating incompatible streams before you process the first.

Use the waiting period for rest, another project, or organizing research. Preserve distance.

If you discover a severe missing-file or wrong-version problem, contact the editor promptly. A small typo does not warrant replacing the manuscript.

Perform a final submission audit

Before sending, verify agreement, filename, file contents, word count, brief, deadline, payment step, contact method, and backup. Read the email once for attachments before pressing send.

Rowan’s final packet contains one complete 104,000-word manuscript and a two-page brief. The duplicate confrontation is resolved, the inheritance motive is consistent, and the questions focus on agency, escalation, and the ending. The prose still has rough sentences. That is appropriate for the stage.

Good preparation does not make an editor’s work smaller. It makes the work deeper. By removing avoidable instability and preserving an honest first read, you give structural feedback the best chance to address the novel you have actually written—and the one it might become.