When I am fortunate enough to have a paper get accepted for publication, I often dread the final round of proofreading before I submit the LaTeX source files. Often, I read the paper start to finish multiple times and make incremental/superficial changes, but always have a difficult time calling it properly "proofread". In addition, I find this approach (multiple full proofreads) seems less useful for checking technical aspects of a paper (e.g., mathematical derivations or involved pseuedo-code) which is arguably more important.

I am wondering what types of routines people have developed for this situation. I would prefer to be much more systematic, as my current approach is both inefficient (time-wise) and doesn't seem very effective. Specifically, what do you do in order to call the paper "proofread" and feel comfortable sending it off to never be edited again?

  • Lots of existing Q&A here at academia.stackexchange.com/questions/tagged/proofreading including academia.stackexchange.com/questions/86533/… academia.stackexchange.com/… also may give you additional hits that haven't had the tag added.
    – Bryan Krause
    Commented Jul 20, 2022 at 22:10
  • Thanks! These are very useful. The last question (see recent edit) is really what I am most interested in, and past Q&A didn't seem to cover this.
    – WazyMaze
    Commented Jul 20, 2022 at 22:12
  • As a minor... or maybe not soooo minor ... point: the last few percentages of perfection are stunningly more expensive than any other part. Not to mention statistical futility of removing all errors. Even with "theorem provers/assistants", while they give certain assurances, we are left to wonder about their own correctness, etc. "It's turtles all the way down." :) Commented Jul 20, 2022 at 22:13
  • @WazyMaze I'm not sure I follow how that really changes/adds anything, besides perhaps some measure of "aww $&@% it" that's going to vary by person to person (along the lines of paul's comment) and be "opinion-based" regarding "feel comfortable".
    – Bryan Krause
    Commented Jul 20, 2022 at 22:17

2 Answers 2


It is very difficult to proofread your own work. You brain knows what you want to say and too often, in my experience, you "see" what isn't written because your mind produces the correct statement. And, my experience is that the harder I try the worse I do. Fatigue? Reinforcement?

My best advice is to make a deal with a colleague in your (sub) field and collaborate by proofing each other's work. Their mind doesn't have preconceptions about what is (should be) on the page, so they are much more likely to catch those things, especially those at the margins, that your mind refuses to see.

I no longer have the opportunity for that (retired) and I often find truly bone-headed errors in my technical writing. I've swapped symbols for "and" and "or" for example creating true nonsense.

A text editor at a book publisher can help with this, but they aren't often used for papers, and they often lack the required technical expertise.

I often find my own errors if I lay the work aside for a while and come back to it, but that doesn't work very well for papers. A week's pause is probably untenable.

Get fresh eyes if possible. Even a graduate student might be able to do it for a bit of cash.

  • 1
    @EthanBolker, precisely. Unintentional, but it proves my case. Fixing...
    – Buffy
    Commented Jul 20, 2022 at 23:43

Two things that our group follows for every submission:

(1) Atleast two people read it together (our submissions are always multi-author, so this isn't hard to arrange). This is typically the lead writer and a co-author. It helps because the chance of two persons simultaneously missing an error is low.

(2) Reading it out aloud. Vocalising somewhat takes your brain off the driver's seat, and you're less likely to gloss over things that are incorrect but obviously understood by you. I imagine this would be difficult if there are a large number of equations, but otherwise it is surprisingly effective, and fast.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .