A copyeditor’s query asked me to confirm my own heading hierarchy. I did not just say yes — and I did not dig in. There is a third thing every author is allowed to do when a query arrives: ask why.
Yesterday I wrote that my copyedit was late, and that waiting well was the work. This morning, it arrived — every page carrying someone else's careful marks, every query waiting for my answer, and a new deadline to plan around. After years of being the editor who sends the tracked changes, here's what it's like to receive them — and why a copyedit is a gift, not a verdict.
August was a month of endings — a dissertation delivered early, an article submitted early, and my own book's page proofs and index sent back to Routledge one day before the deadline. It was also the month I ended two editing engagements because the manuscripts were not ready yet, which turns out to be part of the job.
On Sunday I sent the corrected proofs and the index back to my publisher, and that was the last thing I will ever do to this book. What the proof stage actually asks of an academic author — and why the index I spent thirty hours building turned out not to be an index at all.
On Friday 08/21/26, my book came back from Routledge, the publisher, looking like a book — page proofs, typeset into designed pages, along with the job of building the index myself. It is my only review of the full proofs before print, and it changes how you have to read. What the proof stage actually asks of an author: the errors that surface, an index that had to be cut rather than built, and why the last stretch asks for a different muscle than the writing did.
My copyeditor asked for up to ten catchwords — the nouns that decide whether anyone ever finds the book. It was the smallest query in the file and the only one with a marketing consequence. Here is my real list, how I chose it, and why the same task is waiting at the end of your dissertation.