There is one moment in book production that authors often underestimate.
It is the moment they tell the designer:
“Yes. The manuscript is ready. Go ahead.”
That sentence does more than give permission to start the layout.
It marks the end of the creative stage.
Before that moment, rewrite Chapter 6. Move Chapter 10. Delete a paragraph. Bring it back from the dead. Change your mind seventeen times. Decide the hero should have been called Bernard all along.
That is your manuscript. This is the time to do it.
But once you give the designer the green light, the rules change.
Creative rewriting is no longer particularly welcome.
And once the book is fully laid out, creativity should not merely be discouraged.
It should have packed its bags and left the building.
“Ready” means ready. Not “I ran out of ideas for today.”
One of the stranger things I have learned from working with authors is that the word ready does not always mean what I thought it meant.
Sometimes “ready” apparently means:
“I have no more ideas right now.”
Or:
“I pressed Save in Word.”
Or:
“I am tired of looking at this manuscript and would like somebody else to deal with it for a while.”
None of those mean ready.
Ready means ready.
It means you have actually finished saying what you wanted to say.
The chapters are there.
Their order is decided.
The text has been edited.
You have checked spelling, punctuation, grammar, language, tone and consistency.
You have collected the illustrations — or, at the very least, you know exactly which illustration belongs where.
Old comments are gone.
Track Changes has been resolved.
Mysterious highlighting has disappeared.
Notes to yourself have been dealt with.
And preferably no forgotten AI instruction is still hiding between paragraphs like an archaeological artefact.
The Save button is not a publishing milestone.
Ready is a production state, not a mood.
Think of it like the word all.
When someone says “all,” we normally assume they mean all.
Not:
“All except for the three things I will remember tomorrow morning.”
The same rule applies here.
When you tell a designer:
“The manuscript is ready. You can start.”
you are not saying:
“I currently have no further ideas.”
You are saying:
“The creative and editorial work is finished. You can now build the book from this material.”
That distinction matters.
A lot.
Once layout starts, your manuscript becomes part of a system
Before layout, your manuscript is flexible.
You can add a paragraph and very little happens.
Delete three pages? Fine.
Move a chapter? Word will survive.
Once the manuscript enters book layout, however, it becomes part of an interconnected system.
Text affects pages.
Pages affect chapter openings.
Chapter openings affect pagination.
Pagination affects the table of contents.
Images affect text flow.
Captions affect spacing.
A seemingly innocent extra paragraph can push text onto the next page, which may move an image, which may create a nearly empty page, which may move the next chapter, which may change several page references.
This is why a change that looks tiny in Word may not be tiny in the finished book.
The manuscript is no longer just text.
It is now architecture.
And architecture is generally less enthusiastic about someone arriving halfway through construction and saying:
“Actually, could we move the staircase?”
Rule number one: do not send a newly edited manuscript as your corrections
The designer sends you a PDF proof.
You find a typo on page 37.
A sentence on page 52 feels slightly awkward.
Then inspiration strikes.
You open the original Word manuscript.
You make 36 edits.
Rewrite half of Chapter 6.
Move Chapter 10.
Add two paragraphs.
Save the file as:
FINAL_MANUSCRIPT_REALLY_FINAL_CORRECTED_v7.docx
…and send it back to the designer.
Somewhere, a book designer feels a disturbance in the Force.
Once your book has been laid out, the old Word manuscript is no longer the working layout file.
The designed book is.
Of course, you can update your manuscript for your own records.
You can fix every comma in it. Polish it. Admire it. Give it a spa day.
But sending a revised manuscript to your designer as “corrections” creates one important question:
What exactly is the designer supposed to do with it?
Those changes are not automatically connected to the layout.
They do not politely walk into InDesign, locate their paragraphs, introduce themselves and sit down in the correct places.
The designer has to compare the new manuscript with the previous one.
Find every change.
Locate the matching passage in the layout.
Work out what has been added, removed or rewritten.
Then make those changes manually.
At some point, this stops being proof correction.
It becomes re-layout.
If you have substantially rewritten your manuscript, that may be perfectly legitimate.
Perhaps you are preparing a second edition.
But then we are talking about a new production stage.
Not corrections to an existing layout.
Rule number two: proofing is not the time for structural surgery
Large changes after layout are especially dangerous.
By “large changes,” I mean things such as:
- moving chapters;
- deleting chapters;
- adding new chapters;
- replacing large sections of text;
- inserting several new pages;
- adding many new images;
- removing major sections;
- significantly changing the structure of the book.
And then there is the classic:
“Could Chapter 10 become Chapter 1, Chapter 1 become Chapter 3, Chapter 3 disappear completely, and instead of Chapter 6 we’ll write a new Chapter 10?”
Of course.
Would you also like us to rotate the building twelve degrees while we move the kitchen upstairs?
Large changes affect much more than the text being changed.
They may alter:
- pagination;
- chapter openings;
- page breaks;
- running headers;
- image placement;
- captions;
- the table of contents;
- cross-references;
- blank pages;
- the visual rhythm of the entire book.
Then the revised layout has to be checked again.
Possibly proofread again.
And possibly corrected again.
That means more work.
More time.
More opportunities for new errors.
And a later publication date.
This does not mean you can never make an important change.
Sometimes an important mistake is discovered late.
Sometimes a paragraph genuinely has to be replaced.
Sometimes something must change.
Fine.
But before making a major post-layout change, ask yourself:
Is this really a correction — or am I rewriting the book?
Those are two different jobs.
So what should be changed after layout?
Think:
tweezers, not chainsaw.
The proof stage is the right time for things such as:
- spelling mistakes;
- punctuation errors;
- grammatical or syntactical corrections;
- a missing word;
- an incorrect name, number or date;
- a wrong heading or caption;
- replacing a few words with a few better words;
- adding a very small amount of text — ideally no more than a line or two;
- replacing an existing image with a better version of roughly the same dimensions.
These are normal book proof corrections.
They improve the existing book.
They do not ask the existing book to wake up tomorrow as a completely different book with a new personality and three additional chapters.
Images deserve particular caution.
Replacing an existing image with a higher-quality version of the same image is usually straightforward.
Adding five new photographs in the middle of a carefully balanced chapter?
That sentence began with “adding” and ended with “new layout.”
How to send book proof corrections to your designer
There are two wonderfully boring ways to send corrections.
Boring is good.
Boring means nobody spends forty minutes trying to understand what:
“I changed that thing somewhere near the middle”
is supposed to mean.
Option 1: Send a clear correction list
Create a Word document or another simple text file.
List each correction separately.
For example:
PDF page 37 — line 8 from the top
Current: “The children was waiting outside.”
Change to: “The children were waiting outside.”
PDF page 52 — line 4 from the bottom
Delete the comma after “however.”
PDF page 81 — paragraph 2
Replace “large red house” with “small brick house.”
You can count lines from the top.
You can count them from the bottom.
The universe will survive either system.
The important thing is that the location is unambiguous.
And please give the designer the actual correction, not a treasure map.
“Something is wrong in this paragraph” is not a correction.
“Replace form with from” is.
Option 2: Mark the corrections directly in the PDF
This is often even better.
Open the PDF proof in Adobe Acrobat or another proper PDF annotation tool.
Use comments, sticky notes, highlighting, replacement-text tools or similar annotations.
Place the comment exactly where the correction belongs.
Then write clearly what should change.
For example:
Replace: “2025”
With: “2026”
Or:
Delete this sentence.
Or:
Insert after this sentence: “The following examples apply to both print and ebook editions.”
Now the designer can see the correction in its actual location.
No archaeology required.
No guessing.
No opening six different files named FINAL.
One more small favour: put the corrections in one place
Try not to send:
- eleven corrections in the PDF;
- four by email;
- two in WhatsApp;
- one in a screenshot;
- another in a voice message;
- and the final one three days later beginning with: “Sorry, one tiny thing…”
At that point, we are no longer proofing a book.
We are running a distributed database without version control.
Whenever possible, review the entire proof first.
Collect the corrections.
Then send one organised batch.
Your designer will love you.
Possibly not enough to include you in the will, but definitely enough to open your next email without trembling.
Before making a big change, ask three questions
If you are considering something substantial after layout, ask yourself:
1. Am I correcting an error, or rewriting the book?
Different jobs.
2. Could this change affect the structure, length, pagination, images or chapter flow?
If yes, speak to the designer first.
3. Is this change important enough to justify the additional time, cost and another round of checking?
Sometimes the answer will absolutely be yes.
That is fine.
The point is not:
“Never change anything.”
The point is:
Understand what the change means before making it.
Respect is part of the production workflow
And this brings us to something more important than page numbers, Word files or sticky notes.
Respect.
A good book is a collaboration.
When an author sends me a manuscript that has been proofread, cleaned and genuinely prepared for layout, I notice.
When old comments have been removed, Track Changes has been resolved, random highlighting has disappeared, unexplained fonts are gone, and the document does not look like a crime scene after six months of editing — I notice that too.
To me, that preparation says:
“I respect your work enough not to make you clean up things I could have cleaned up myself.”
That matters.
And it changes the tone of the entire project.
When I receive a carefully prepared manuscript, I know the author has thought not only about the book, but about the person who will have to work with it.
That deserves the same level of care in return.
Because respect works both ways.
The designer has responsibilities too
The designer should not treat the author’s book as an opportunity to demonstrate how many typography rules they know.
The designer needs to listen.
How does the author imagine the book?
What atmosphere should it have?
What matters emotionally?
Which details are important to the author?
What is the book supposed to feel like?
Sometimes an author’s vision matters more than a designer’s favourite convention.
Typography matters.
Colour theory matters.
Grids matter.
Proportions matter.
Publishing standards matter.
But they are tools.
The author’s book is the reason those tools are there.
A designer has to be sensitive enough to understand when a rule should guide the work — and when the author’s intention is more important than showing everyone how correctly the rulebook was followed.
The author made the book. The designer helps it arrive.
I sometimes think a book designer is a little like a midwife.
The author created this thing.
They carried it around for months or years.
They worried about it.
Changed it.
Loved it.
Hated it.
Rewrote page 126 at three in the morning.
And eventually decided it was ready to meet the world.
The designer did not create that child.
But the designer can help it arrive healthy, coherent, readable — and preferably wearing something more interesting than default Times New Roman.
For that relationship to work, there has to be trust in both directions.
The author needs to respect the designer’s time, process and expertise.
The designer needs to respect the author’s ownership, intentions and emotional connection to the work.
When both people are working toward the same result, you can feel it in the finished book.
When one is rowing north, the other is rowing south, and someone has started drilling a hole in the boat because they “had a new idea,” you can feel that too.
The best final correction is a small one
By the time a book reaches proof stage, the main question should no longer be:
“How can I rewrite this book?”
It should be:
“How can we make this version clean, accurate and ready to publish?”
Do the creative work before layout.
Make the major editorial decisions before layout.
When you tell the designer the manuscript is ready, mean ready.
When you give the green light, understand what that green light means.
Then, when you receive the designed PDF, read it carefully.
Collect small, precise corrections.
Mark them clearly by PDF page and location, or annotate the PDF directly.
Speak to the designer before requesting structural changes.
And above all, remember that there is another human being on the other side of the file.
A good author and a good designer are not opponents negotiating a hostage release.
They are two people trying to make the same book better.
A little mutual respect can save hours of work, prevent mistakes, shorten the production process — and produce a book both of you are genuinely proud to put your names behind.