What to Do Between Your First Draft and Hiring an Editor

You typed "The End." Maybe you even did a little fist pump. (I would. No shame.)

And now you're staring at a manuscript that you KNOW isn't ready for a professional editor... but you're not sure what to do with it first. You've heard you should let it sit in a drawer. You've heard you should get beta readers. You've heard you should do a revision pass. Probably all three, in some order nobody agrees on.

The real problem is simpler than any of that. There's a gap between finishing your draft and paying someone $3,000 to $5,000 to tell you what's wrong with it. And most writers either ignore the gap entirely or fill it with busywork that doesn't actually move the manuscript forward.

So let's talk about the workflow that does.

Step one: cool down (but not forever)

Yeah, the drawer advice is real. Put the manuscript down for a couple of weeks. Maybe three. You need distance from the thing before you can see it clearly. Every writer who's ever tried to revise the day after finishing knows how that goes... you can't read what's actually on the page because your brain keeps filling in what you MEANT to write.

But here's where a lot of writers go wrong. They let the cool-down period stretch. Two weeks becomes six weeks becomes three months. The momentum dies. The draft starts feeling like somebody else wrote it (and not in the useful way). You lose the thread of what you were trying to do.

Two to three weeks. That's the sweet spot. Enough distance to read with fresh eyes, not so much that you've emotionally detached from the project.

Step two: the read-through you're probably skipping

Before you touch a single sentence, read the whole thing. Start to finish. No editing. No fixing. No margin notes that say "FIX THIS LATER" (we all do it, and then we never do it).

Just read. Like a reader would.

This is harder than it sounds. Your fingers will itch. You'll spot a clunky sentence on page four and want to rewrite it immediately. Don't. The goal here isn't line-level polish. The goal is to feel the shape of the book. Where does your attention wander? Where do you feel the pace drag? Where does a scene feel like it exists because you needed a bridge between two other scenes, not because it earns its place?

Take notes AFTER each reading session, not during. What you remember bothering you when you close the laptop is more diagnostic than what you flag in the moment.

Step three: structural triage

OK, now you've got your notes from the read-through. And I'd bet real money that most of them cluster around a few recurring issues. Pacing in the middle. A character who shows up strong in act one and then sort of... fades. Scenes that don't turn. Maybe a subplot that you're not sure actually connects to anything.

This is the structural layer. The bones.

And this is exactly the layer that most writers skip past on their way to line editing. Because line editing feels productive. You can sit down for two hours and "fix" forty sentences and feel like you accomplished something. But if the scene those sentences live in doesn't turn, if it doesn't change the value state for your character from one pole to another, then those forty polished sentences are still sitting inside a scene that isn't working.

Structural triage means ranking your problems by severity. A pacing issue that spans five chapters matters more than a dialogue scene that runs a little long. A POV inconsistency that confuses the reader matters more than a paragraph of tell-not-show on page 212.

You don't have to fix everything at once. You have to know what to fix FIRST.

Step four: get an alpha read

Most writers know what a beta reader is. Fewer know about alpha readers. The difference matters here.

A beta reader tells you what a reader experiences. "I got bored in the middle." "I didn't connect with the love interest." "The ending felt rushed." That's useful feedback... but it's REACTION, not diagnosis. Your beta reader isn't going to tell you that chapter fourteen doesn't turn because the protagonist's goal doesn't shift. They're going to tell you it felt slow. And then you're left figuring out WHY it felt slow, on your own, with no craft framework to guide the analysis.

An alpha reader operates at the craft level. An alpha read evaluates your manuscript against established principles of fiction craft... pacing, scene structure, POV discipline, dialogue mechanics, narrative distance, show vs. tell... and tells you not just WHAT isn't working but why, with every finding traced to a named craft principle.

This is the step that goes between your self-revision and your beta readers. You fix the structural craft issues first. Then your betas are reacting to a manuscript that already has its bones set. Their feedback gets sharper because they're not tripping over problems you could've caught earlier.

And when you eventually hire a developmental editor (if you hire one), you're not paying $4,000 for someone to catch issues an alpha read would've surfaced for a fraction of that.

Step five: revise from the bones out

Once you've got your alpha read back, resist the urge to start at page one and work forward. That's the linear trap. Instead, go where the biggest structural problems are.

If your alpha read flagged a pacing collapse in act two, start there. If it caught a POV drift that runs across six chapters, fix that before you touch anything else. Work from the biggest problems down to the smallest. Structure first, then scene-level issues, then line-level polish last.

I know this feels backwards. Every instinct says "start at the beginning." But starting at the beginning means you'll spend your best revision energy on chapters that might be fine while the real problems sit untouched in the middle and back half of the book.

This is also where a lot of writers discover that one structural fix cascades into others. Fix the pacing in act two and suddenly that character who was fading makes sense again, because the scenes that were dragging were the ones where she had nothing to do. You didn't have a character problem. You had a pacing problem that looked like a character problem.

Step six: THEN send to betas

Now your manuscript has been through a cool-down, a full read-through, structural triage, an alpha read, and a targeted revision pass. THIS is the manuscript your beta readers should see. Not the raw first draft. Not the "I fixed some typos and tightened a few sentences" version.

Your betas will give you better feedback because they're reading a structurally sound manuscript. They'll catch things that matter at the reader-experience level... emotional beats that don't land, a twist that's too telegraphed, a section that still drags despite the structural work... instead of stumbling over problems that you already knew about but hadn't fixed yet.

Where FirstReader fits

I built FirstReader to fill the alpha reader slot in this workflow. It runs your manuscript against established craft principles of developmental editing. Every finding traces to a named principle. It's rules-based, not vibes.

You upload your manuscript. You get back a structured craft report with chapter-level and book-level analysis. The report tells you what to fix, where to fix it, and which craft principle explains why it's a problem.

It won't replace your developmental editor. But it'll make sure you're not paying an editor to catch things a rules-based analysis could've surfaced first. And it goes in at step four... after your read-through, before your betas.

You can try it free on a single chapter and see what it catches.

The honest caveat

Not every manuscript needs all six steps. If you're on your fifth novel and you've internalized the structural stuff, maybe you skip the formal triage and go straight to an alpha read. If you're writing in a genre with tight conventions (romance, thriller) and you know the expected beats cold, your structural instincts might already be solid.

But if you're staring at a finished draft and feeling that familiar uncertainty... "something's off but I don't know what"... this workflow gives you a path through the gap. The gap that sits between typing "The End" and spending real money on professional feedback.

Fill it with structural work. Not hope. Not busywork. Not premature line editing on scenes you might end up cutting anyway.

Fix the bones first. Then let other people read it.