Publishing a Book: A to Z of Being a Project Editor
Most of what I know about being a project editor came from moments when I was afraid. Afraid to tell a senior colleague that a schedule would not hold. Afraid to send an author a difficult piece of feedback. Afraid to ask a question that might expose what I had not yet understood. Each time, I took the step anyway, and each time it paid off, not at once but in time: the trust deepened, the problem shrank, and the book was better for it. I have come to believe that fear is not a sign you are doing something wrong. It is often a sign you are about to do something that matters.
Drawing from my experience, here is an A to Z of what a project editor has to oversee, and the moments along the way where acting early pays off.
A project editor is the person who takes a manuscript, or the idea of one, and carries it to a finished book on schedule, on budget and to standard. The job title varies across publishing houses, but the responsibility is the same: you are the single point of accountability for the project. This is the arc, stage by stage.
A. Acquisition and the Brief
A project starts with a brief, whether it comes from acquisitions, a curriculum plan or a commissioning decision. Ask early: who is the reader, what is the book for, what format and length, what is the budget, and what is the publication date? An unclear brief is the most expensive problem in publishing, because everything downstream inherits it.
B. Building the Plan
Convert the brief into a working schedule with named owners and dates: manuscript delivery, editing, design, proofs, files to press, finished copies. Build in slack for the stages that always slip (author delivery and review cycles) and make dependencies visible. As a rule of thumb, keep a contingency week before files go to press; if you never need it, you can hand it back. A schedule nobody can read is not a schedule.
C. Contracts and Permissions
Make sure the author or contributor agreement is signed before substantive work begins. Identify what needs permission, such as third-party images, extracts, data and quotations, and start clearing early. Permissions have a way of arriving last and costing the most.
D. Delivery and Manuscript Assessment
When the manuscript arrives, assess it before editing it. Is it complete? Does it match the brief? Is the structure sound? A manuscript that is seventy per cent complete usually should go back to the author, not into the edit. Raising fundamental problems now costs a conversation. Raising them at proof stage costs money and the date.
E. Editing, in Layers
Edit in sequence, not all at once.
Developmental/structural: argument, organisation, gaps, balance.
Line and substantive: clarity, flow, tone, consistency.
Copyediting: grammar, usage, style, fact-flagging.
Fact-checking: names, dates, figures, quotations and references, plus any AI-assisted content and citations.
Proofreading: the final check against the typeset pages.
Each layer assumes the one before is done. Mixing them wastes effort, because you will polish sentences that later get cut.
F. Style and Consistency
Agree on a style sheet at the start: spellings, capitalisation, number style, referencing system, terminology. Keep it live and share it with everyone who touches the text. Inconsistency is the most visible sign of an unmanaged project.
G. Briefing Design
Give the designer and typesetter a clear brief, covering the audience, the tone, the page budget and the elements the text includes (boxes, tables, activities, figures). Good design briefs prevent expensive rework. Raise structural questions about the text's elements before layout, not after.
H. Handling the Author
Authors are partners, and they are also people with their own deadlines and anxieties. Set expectations at the start about timelines and the number of review rounds. Give feedback that is specific and respectful. When an author is late, find out why early, because late delivery is rarely a surprise to the author.
I. Illustrations and Assets
Commission or source illustrations, photographs and data visuals on a timeline that runs parallel to editing. Track every asset's source, licence and credit line in a single register.
J. Judgement Calls
You will constantly decide between speed, cost and quality. Know which of the three is fixed on each project and which can flex, and tell your stakeholders when a trade-off is being made. Judgement improves when you can articulate the reasoning, and when you record it.
K. Keeping the Schedule Honest
Review progress regularly against the plan. When a date will slip, say so immediately and propose options, rather than hoping to recover. A project editor who flags a delay early is trusted. One who flags it late is not.
L. Legal and Compliance Review
Check for defamation, copyright infringement, privacy issues and anything the legal or compliance team needs to see. In educational publishing, this includes curriculum alignment and accuracy checks. Do it before design lock, not after.
M. Managing the Budget
Know your cost lines (editing, design, illustration, permissions, typesetting, printing) and track actuals against estimates. Flag overruns early and distinguish between those caused by scope change and those caused by poor planning.
N. Negotiating Internally
Marketing, sales, production and finance all have views on your book. You are the person who holds the project's coherence while taking their input. Learn what each team needs from you and when.
O. Organising the Files
Version control is not optional. Use clear file naming, one master version, and a changelog. "Final_v3_revised_FINAL" is how a wrong file goes to press.
P. Proofs
Plan proof rounds, the number of readers and who has authority to approve. This is the proofreading layer from E, managed as a process. Proof corrections should be limited to errors, because late changes of mind are what break schedules and budgets.
Q. Quality Checks
Before files go to press, run a final checklist: front matter, page numbers, running heads, contents against page references, cross-references, image captions, barcode and ISBN, copyright page. A checklist outperforms memory every time.
R. Rights and Metadata
Make sure the book's metadata (title, subtitle, description, edition, author information, subject categories) is accurate and ready for distributors and retailers. Poor metadata means poor discoverability.
S. Sign-Off to Press
Obtain formal approval from everyone with authority. Get the author’s sign-off in writing on final text changes, so that nothing is disputed after files go to press. Keep the record. Confirm specifications with the printer: paper, binding, quantity, delivery date.
T. Tracking Production
Stay engaged through printing. Check printer proofs or machine proofs where possible, and plan for transit and warehousing.
U. Unforeseen Problems
Something will go wrong on every project: a missing image, a corrupted file, an author who disappears for three weeks. Keep a short list of contingency options. Calm, practical responses build teams' confidence.
V. Verifying the Finished Book
Examine finished copies against the approved files. Log any errors for the next reprint and correct them in the master files while the details are fresh.
W. Working with Marketing and Sales
Supply the people selling the book with accurate summaries, author information and key selling points as early as possible. You know the book better than anyone, so make that knowledge usable.
X. The X Factor: Care
The difference between a competent project and an outstanding one is usually attention: reading the text one more time, or asking one more question. Care is not a process, but it is the thing processes exist to protect.
Y. Your Post-Mortem
When the book is out, hold a short review: what ran to plan, what didn't, what you would change. Write it down. Over several projects, these notes become your own method.
Z. Zero Surprises
If one principle runs through all of the above, it is this: your job is to make sure that nobody is surprised late. Information, risk, and delay should travel to the right people quickly. The best project editors are rarely the loudest in the room. They are the ones whose books arrive when and as they were promised.
