The writing pace calculator above converts a word-count target and a deadline into the only number that matters day to day: how many words you have to write on each remaining writing day. It then does the part most planning tools skip, which is comparing that required pace against the pace you have actually achieved so far and projecting a finish date from the real one rather than the hopeful one.
Arb Digital publishes this page because the arithmetic of a long writing project is trivial and the psychology is not, and people routinely get the trivial part wrong in a direction that flatters them. Dividing a 50,000-word novel by thirty days gives 1,667 words a day, which sounds manageable. Dividing the 42,000 words you still have left by the twenty days you still have, on the five days a week you actually write, gives 2,940 — a completely different project. This tool always divides what remains by what remains.
What This Writing Pace Calculator Does
It takes a goal, your progress, a start date, a deadline, how many days a week you write and your realistic drafting speed, and returns five things: the words per writing day still required, the total words remaining, the number of writing days left, the hours per writing day that implies at your stated speed, and a projected finish date computed from the pace you have demonstrated since the start date.
The two progress bars answer a question a single percentage cannot. One shows how much of the word count is done; the other shows how much of the calendar is gone. When they sit level you are on schedule. When the calendar bar runs ahead, you are behind, and by exactly the gap you can see.
This is a scheduling tool, not a counting tool. If you need to count the words in a piece of text, use our word counter. If you need to know how many pages a word count fills at a given font and spacing, that is our words per page calculator. If you want to know how long a finished piece takes somebody else to read, use the reading time calculator. This page is only about the schedule between now and the deadline.
How to Use It
- Enter your total word goal — the manuscript, dissertation, report or challenge target you are working towards.
- Enter the words you have already written and intend to keep. Be strict: notes, outlines and abandoned chapters flatter the number and distort the pace.
- Set the start date and deadline. The fields default to a project already ten days old with twenty days left so you can see a realistic result immediately; change both to your own dates.
- Set your writing days per week. Seven is a genuine choice for a short sprint and a poor one for a long project. Five leaves room for the weeks that go wrong.
- Enter your drafting speed in words per hour to convert the daily quota into hours you have to find in the day, which is the constraint that actually binds.
The Formula and How It Is Calculated
The core calculation is deliberately simple:
Words remaining = goal − words written
Calendar days left = deadline − today
Writing days left = calendar days left × (writing days per week ÷ 7)
Required pace = words remaining ÷ writing days left
Hours per writing day = required pace ÷ words per hour
The writing-days conversion is proportional rather than a true calendar count, because which specific weekdays you write on changes the answer by at most a day either way over a project of any length, and pretending otherwise implies a precision the estimate does not have. Days are counted from today, not from the start date, so the number always reflects the position you are in now.
The projected finish date uses your demonstrated pace instead of your intended one. Achieved pace is words written divided by days elapsed since the start date, and the projection adds words remaining divided by that pace, adjusted back to calendar days by the same writing-days-per-week factor. If fewer than one day has elapsed there is no pace to measure and the tool says so rather than inventing one.
Worked check with the defaults: a 50,000-word goal with 8,000 written, twenty calendar days left and seven writing days a week leaves 42,000 words over twenty writing days, which is 2,100 words per writing day, or 4.2 hours a day at 500 words an hour. Set writing days per week to five and the same 42,000 words fall across 14.3 writing days, giving 2,940 a day and 5.9 hours — the same project, two entirely different lives.
Drafting Speed Is Not Typing Speed
The single most common error in writing schedules is using typing speed as though it were writing speed. A competent typist manages 60 words a minute, which is 3,600 words an hour, and a schedule built on that number implies a 50,000-word draft is fourteen hours of work. Nobody has ever written a book in fourteen hours.
Drafting speed includes the thinking, the rereading, the sentence you write four times, the paragraph you delete, and the twenty minutes spent looking up one fact. For most people producing first-draft prose it lands somewhere between 300 and 1,000 words an hour, and it varies more by material than by person: dialogue and personal narrative run fast, technical exposition and anything requiring citation runs slowly.
The right way to set this field is to measure it. Write for one timed hour, count what you kept, and use that. Our typing speed test measures raw keyboard throughput, which is a genuinely different quantity and a poor proxy for this one — it tells you what your hands can do, not what your sentences cost.
Why the Required Pace Keeps Rising
A schedule set once at the start is a schedule that lies to you from day two onwards. Miss a single day at 1,667 words and the quota for every remaining day goes up. Miss a week and the remaining quota can easily double. This is not a motivational point, it is arithmetic: the numerator stays fixed while the denominator shrinks.
The practical consequence is that the cheapest day to catch up is always today, and the cost of a missed day rises as the deadline approaches. A day lost in week one of a six-week project spreads across thirty-five remaining days. The same day lost in the final week spreads across six. Recalculating after every session, rather than every week, keeps this visible while it is still cheap to fix.
It also argues for building slack into the plan from the start. Setting writing days per week to five when you could in principle write seven creates two absorbing days each week. Those days are not laziness; they are the difference between a plan that survives a bad cold and one that does not.
Sprint Targets and the 1,667 Problem
The famous 50,000-words-in-30-days challenge produces a daily target of 1,667 words, and that number has become a default far outside the month it was designed for. It is worth understanding what it assumes: writing every single day including weekends and holidays, starting from zero on day one, and accepting a genuinely rough draft. Those are reasonable conditions for a deliberate month-long sprint and unreasonable ones for a dissertation, a technical report or a book with research behind it.
Sprints work because they suspend editing. The pace is achievable only if you stop revising, and the output is a draft that needs substantial rewriting. If your goal is a finished piece rather than a complete draft, budget the revision separately — many writers find revision takes as long as drafting and it does not add words, so it never appears in a word-count schedule at all. A schedule that ends on the day the draft is complete has quietly hidden half the project.
Setting a Realistic Goal in the First Place
If the required pace this tool returns is well beyond anything you have ever achieved, the honest response is to change the goal or the deadline rather than to promise yourself a new personality. The University of North Carolina’s writing centre makes this point well in its guide to procrastination and unrealistic scheduling: the plans that fail most reliably are the ones that assumed perfect conditions and no interruptions.
Where the deadline is genuinely fixed, the variables you can move are the scope and the writing days. Cutting a planned 90,000-word manuscript to 70,000 is a real decision with real consequences, and it is a better one than discovering in the final week that the schedule was never survivable. Purdue University’s guide to the writing process covers the planning and revision stages this calculator deliberately does not model.
One more variable is worth naming: reading. Research-heavy writing needs reading time that produces no words, and slotting it inside a word-count schedule guarantees the schedule fails. Plan it separately — our reading goal calculator handles that side — and treat the writing days in this tool as days when you are only writing.
Arb Digital plans, writes and publishes content on a calendar that survives contact with a real business week. If your editorial pipeline keeps stalling, we can take the writing off your desk.
Content Marketing Services Copywriting ServicesCommon Mistakes to Avoid
- Dividing the whole goal by the whole period. Once you are past day one, the only useful sum is words remaining divided by days remaining.
- Using typing speed as drafting speed. It overstates output by a factor of four or more and produces a schedule that was never possible.
- Counting notes and outlines towards the goal. It inflates progress and hides the fact that the pace is slipping.
- Assuming seven writing days a week. A plan with no absorbing days fails on the first bad week and never recovers.
- Leaving revision out of the timeline entirely. Revision produces no new words, so it never shows up in a word-count schedule unless you add it deliberately.
Related Free Tools From Arb Digital
Count what you have written with the word counter or check repetition with the word frequency counter, convert the total into pages with the words per page calculator, estimate how long readers will spend on it with the reading time calculator, measure keyboard throughput with the typing speed test, and plan the research side with the reading goal calculator. Everything else is in the free online tools hub.
Frequently Asked Questions
There is no universal figure. Divide the words you still have left by the writing days you still have left, which is what this calculator does. That number changes every day, and the version computed at the start of a project stops being true the first time you miss a session.
For most people producing first-draft prose it falls between 300 and 1,000 words per hour, depending far more on the material than on the writer. Technical or heavily cited writing sits at the low end. Measure your own with one timed hour rather than guessing.
Because the words remaining are divided by fewer days. Every missed session raises the quota for every session after it, and the increase gets steeper as the deadline gets closer.
Count only draft words you currently intend to keep. Counting material you expect to cut makes progress look better than it is and produces a projected finish date that will not happen.
No. This is a drafting schedule measured in words, and revision produces no new words. Budget revision as a separate block after the draft is complete, and be aware that for many writers it takes comparable time.
It measures the pace you have actually achieved since your start date, then extends that pace across the words you have left. If less than a day has elapsed there is no measurable pace, and the tool says so instead of guessing one.
The calculator does not take a view. What it does show is that a five-day week needs a higher daily quota for the same deadline, in exchange for two days each week that can absorb an interruption without moving the finish date.
This tool produces a scheduling estimate from the figures you enter. It makes no claim about how quickly any individual can or should write, and it is not a substitute for the guidance of a supervisor, editor or institution where a deadline is formally set.
