The most commonly cited proofreading benchmark is roughly one minute per page for a light pass, and about two minutes per page for a thorough one. In practice, these numbers are starting points, not targets. Document type, complexity, reviewer expertise, and review purpose can all shift the realistic time per page considerably — sometimes by a factor of five or more.
What drives proofreading time up
Dense text with technical terminology or complex sentence structures takes longer per page than plain business prose. Documents with tables, figures, or data that need checking take longer than text-only pages. Inconsistent formatting that requires correction as you go slows everything down. And any document where the proofreader is not fully familiar with the subject matter requires more careful passes to catch errors without misreading them as intentional.
Realistic proofreading benchmarks by document type
Light copyediting of standard business correspondence: 1–2 minutes per page. Marketing collateral or creative copy: 2–3 minutes per page. Technical reports, specifications, or white papers: 3–6 minutes per page. Legal contracts or compliance documents: 5–10 minutes per page. Academic or scientific papers: 5–8 minutes per page. These are realistic estimates for a competent reviewer — not worst-case figures.
How to use proofreading time estimates in project planning
If you are scheduling a document review cycle, use your per-page estimate to calculate the total review time, then build in additional time for note-writing, consolidation, and a second pass. For a 30-page technical document at 5 minutes per page, that is 150 minutes of review time minimum — plus consolidation. Scheduling a 24-hour review window for a document of that complexity is often unrealistic. A document review time calculator helps you arrive at a defensible estimate you can share with stakeholders.
Getting better results from your review cycle
Beyond the time question, the quality of a document review depends on how it is structured. Reviewers who are asked to check everything tend to check nothing carefully. Assigning specific review focus areas — one reviewer for technical accuracy, one for formatting compliance, one for regulatory language — produces more thorough results in comparable time. PDF proofing software that supports structured annotation makes this kind of targeted review much easier to coordinate.
“The 'two minutes per page' benchmark assumes a single reviewer, familiar with the subject matter, working on a clean draft. Most real document reviews do not meet even one of those conditions.”
Proofreading time benchmarks by document type
- Business correspondence and memos: 1–2 minutes per page
- Marketing copy and creative briefs: 2–3 minutes per page
- Technical reports and white papers: 3–6 minutes per page
- Legal contracts and compliance documents: 5–10 minutes per page
- Financial statements and data-heavy documents: 4–8 minutes per page
- Academic or scientific papers: 5–8 minutes per page
Frequently asked questions
How many pages can a proofreader review per hour?
For standard business documents, an experienced proofreader typically reviews 20–40 pages per hour on a light pass. For a thorough review of technical or legal documents, 6–12 pages per hour is more realistic. The range is wide because document complexity matters more than page count alone.
Is proofreading faster on screen or on paper?
Most research suggests errors are caught more reliably on paper, but the difference is smaller than it used to be. Screen-based review with a PDF annotation tool that allows precise comment pinning can match paper for accuracy while being significantly faster to process and share.
How do I build proofreading time into a client project timeline?
Use a per-page benchmark appropriate to the document type, multiply by page count, and add 30–50% for note consolidation and a second pass. Then communicate the resulting window to the client as a required turnaround time — not a suggestion. Clients who understand why the window exists tend to respect it.
Should I charge for document proofreading time separately?
If proofreading is part of your standard deliverable scope, include it in your project fee with the time accounted for. If a client asks for proofreading on a document type or volume that is outside your original scope, quote it separately using your realistic time estimates and hourly rate.
Related resources
FileFeedback
Struggling with client feedback on your projects?
FileFeedback lets clients leave frame-accurate, timestamped comments directly on your videos and images — no more email chains, no more confusion about which version they mean.
Try FileFeedback free