Routine / A PRACTICAL WRITING GUIDE

How to Track Writing Progress

Choose a few measures that tell you what changed and what to do next. A rising word count is only one kind of evidence.

Try the exerciseRead the guide
THE PRACTICAL ANSWER

Track the change your current phase needs. During drafting, that may be new scenes or clearly defined new words; during research or revision, it may be resolved claims or sections with a working purpose. Keep a short record of the intended task, actual result, and next action. Review several sessions before adjusting the plan, and treat any completion forecast as arithmetic based on assumptions you can revise.

Useful when word totals or streaks hide structural progress, repeated work, or a schedule that needs adjusting.

The spreadsheet says you wrote 2,400 words this week. The manuscript says you have three versions of the same opening and no clearer plan for chapter four. In another week, you delete 1,000 words and solve a structural problem, yet the chart makes the week look like a failure. Both results show how easily a measure can lose contact with the work.

A useful progress record supports decisions about the manuscript. This guide follows Theo, an invented writer developing a practical book about drawing everyday objects. His project moves through drafting, testing examples, and revision. The numbers are illustrations of a tracking method, not productivity benchmarks or predictions about how quickly anyone should finish.

Decide which question the tracker needs to answer

Before adding columns, ask what you are trying to learn. You might need to know whether you are making time to draft, which chapters are blocked, whether a revision pass is complete, or how much work remains before a review. These are different questions. A single number is unlikely to answer all of them.

Theo wants to know whether the book’s practice chapters are becoming draftable and then complete. A total word count can show manuscript growth, but it cannot reveal whether each drawing example has an explanation or whether a chapter ends with a usable exercise. His tracker therefore needs a view of chapter status alongside a modest session record.

Write the tracker’s purpose at the top: “Help me identify the next useful manuscript task and review the current phase.” If a proposed field does not support that purpose, leave it out for now. You can add information when a real decision requires it. Collecting more data is not automatically the same as understanding your process better.

Match the measure to the current phase

During drafting, useful measures may include new words, scenes drafted, or sections brought from notes into prose. During research, a better unit may be a question resolved with traceable evidence. During structural revision, you might track chapters assessed and specific problems repaired. During proofreading, a defined pass through a stable version can make more sense than counting words changed.

Theo initially tracks rough explanatory sections drafted. Later, he switches to whether each worked example demonstrates the distinction the chapter teaches. That second phase may involve deleting material and producing fewer new words. Keeping the first phase’s target would encourage him to expand when he needs to clarify.

Name a completion condition for the unit. “Chapter reviewed” is ambiguous. “Chapter reviewed for sequence, with each section’s job summarized and structural changes recorded” is inspectable. Keep the condition appropriate to the phase. A first-draft section does not need to satisfy the same standard as a manuscript prepared for publication.

THE IDEA, MADE VISIBLERecord the work, not only the word count.A WORKING RECORD
Change

Remove a repeated introduction.

Evidence

Four chapters now have a practice task.

Next action

Draft the missing explanation in chapter 5.

A structural pass can reduce the manuscript and still leave a clearer route through the work. Original illustrative example.

Distinguish activity from manuscript change

Activity measures tell you what you did: spent thirty minutes drafting, read a source, or attended a writing session. Manuscript-change measures tell you what resulted: completed a scene, replaced an unsupported claim, or resolved the order of two sections. Both can be useful, but they should not be treated as interchangeable.

Theo spends forty minutes attempting an explanation of contour drawing and produces only a rough paragraph. His activity record shows that the session happened. His result note says he discovered the example needs a simpler object. The next action is to test a cup rather than a tangled set of keys. That note makes the limited output useful.

Avoid treating time spent as proof that a task is complete, or treating a small output as proof that the time was wasted. Review the relationship. If repeated long sessions produce no new understanding or material, investigate the task design. If a short session resolves a major uncertainty, let the record show the significance without inventing a numerical equivalent.

Manuscript pages and chapter material spread across a planning desk
THE WORK, MADE VISIBLEMake the change visible.

For a structural pass, record what each chapter now does differently as well as how many units you reviewed.

Original editorial illustration

Use word counts with clear definitions

If you count words, decide whether you mean words newly drafted, net change in the active manuscript, or the current total. Gross new words can show drafting activity. Net change includes deletions and replacements. The total gives a rough picture of manuscript size. These numbers describe different things, and mixing them makes comparisons unreliable.

Imagine Theo drafts 700 words, removes 400 from an older explanation, and moves 300 into a separate notes file. His active manuscript grows by a different amount from his new drafting output. He records the new words only if that number answers his drafting question, and keeps the current total separately. The movement of old text is not new writing.

Choose a counting convention and use it consistently. You do not need forensic precision for a personal tracker, but you do need enough clarity to interpret trends. If counting itself becomes cumbersome, simplify. A rough result note and chapter-status update may support better decisions than a detailed numerical system you dislike maintaining.

A SECOND CASE / PUT THE METHOD TO WORK

Measure revision by a change you can inspect.

A word counter can make a productive structural week look empty. For a revision pass, choose evidence connected to the editorial problem before deciding what to count.

WORKING STUDYBOOKDRAFTLAB / 01

A weekly revision record

  1. Intention

    Remove repeated explanations of the museum closure.

  2. Evidence

    Chapters 2 and 4 now do different jobs.

  3. Next check

    Can the reader understand chapter 4 without the removed explanation?

Original invented teaching example. Adapt the decisions to your own book.
WHY THIS CHOICE HELPS

“Two chapters revised” records activity but conceals whether the problem changed. Keep a brief before-and-after note as well as the unit count. If revision exposes missing material, record that discovery instead of disguising it as failure to meet the original target. At review time, use the evidence to choose the next task and estimate capacity; avoid adding several unrelated measures into a single score that suggests more precision than you have.

What if I need a word target as well?

Track new drafting separately from revision and research. Compare like sessions when estimating pace, and keep the target provisional. A week of fact-checking cannot fairly be evaluated by the number of new paragraphs it produces.

Build milestones that represent useful states

A milestone describes a meaningful state of the manuscript. “Reach 20,000 words” is measurable but may have little editorial meaning. “Draft all six practice chapters, with an example and a provisional exercise in each” tells you what will exist. You can still record the total length as context, while using the manuscript state to guide the work.

Theo creates statuses for each chapter: outlined, rough draft present, examples checked for clarity, structural revision complete, and ready for a later polish. The statuses do not claim the book is objectively excellent. They record whether he has performed particular work under a defined standard. A chapter can move backward if a later discovery reopens an earlier question.

Keep milestones small enough to review. A single status called “finished” hides the remaining work, while twenty tiny statuses can make the tracker harder to understand than the manuscript. Choose the few transitions that matter for your project. If a chapter needs a special check, add a note rather than redesigning the whole system around one exception.

Write session notes that preserve decisions

A short session log can contain the date, task, result, and next action. Add duration or words only if useful. The result should describe what changed or what you learned. The next action should be specific enough that you can begin without rereading the entire project. This makes the log useful when several days pass between sessions.

Theo writes: “Chapter 3: replaced the keyring example with a cup. The comparison now shows one visible edge at a time. Next: explain why the reader should pause before adding interior detail.” That is more helpful than “Good session, 450 words.” He can keep the positive impression, but the task and decision are what help him return.

Do not turn the log into a second manuscript. A few lines should be enough for most sessions. If you find yourself writing a long account of why the work was difficult, decide whether the note contains a project decision worth extracting. Preserve that decision and keep the rest only if the reflection serves a purpose for you.

Review patterns without inventing causes

At a weekly or otherwise suitable interval, look across several sessions. Which tasks repeatedly stall? Which chapter status has not changed? Which conditions seem to support useful work? Treat patterns as prompts for experiments, rather than as immediate explanations. Three difficult evening sessions do not prove that you can only write in the morning.

Theo notices that he drafts explanations easily but postpones exercises. The log shows that “write exercise” usually appears without a specific reader task. He tests a clearer brief: “Ask the reader to draw the same cup twice, changing only how they observe its edge.” The next review can assess whether the clearer task helped. This is a local adjustment, not a universal theory of his productivity.

Review manuscript quality separately from output. A completed chapter status means a defined task was performed; it does not prove every explanation works for readers. When appropriate, use feedback or a fresh reading to test the work itself. Let the tracker help you find what needs attention without asking it to judge everything a book requires.

A hand making a pencil note on a paper manuscript beside a previous draft
THE WORK BETWEEN THE PAGESRead with one question in mind.

Observe the difficulty, choose the scale of the repair and keep an original against which to test the result.

Original illustrative photograph, created for BookDraftLab.

Forecast cautiously and keep scope visible

If you want a rough completion estimate, use recent experience from comparable tasks and state the assumptions. Drafting five similar sections gives more relevant information than averaging a research day with a proofreading day. Use a range and expect it to change. A forecast is a planning tool, not a commitment extracted from your past output.

Suppose Theo has completed three comparable rough chapters over several weeks. He can use that experience to sketch a possible range for the remaining chapters, while noting that two require new examples. If the scope grows from six chapters to nine, the forecast must change. The tracker should not show unexplained failure because the definition of the book expanded.

Record scope decisions beside the plan: added a chapter, merged two exercises, postponed a specialist appendix. This preserves the reason the remaining work changed. Avoid pretending a percentage is precise when both the total task and its completion standard keep moving. “Four of six rough chapters exist” is clearer than an unsupported claim that the book is sixty-seven percent finished.

Keep the system useful and easy to abandon

Try a tracker for a limited period and ask whether it helped you make a decision or begin a session. If it mainly produces guilt, decoration, or maintenance, simplify it. You may need only a chapter checklist and return notes. Someone else may benefit from a spreadsheet because they want to examine changing workload or a complex research process.

Be careful with streaks. They can provide a pleasing record of contact, but one missed day should not erase what the manuscript contains. If a streak encourages trivial actions merely to preserve the mark, it has stopped describing the work you care about. Record a pause plainly and return to the next useful task.

Your personal tracker can stay local in a notebook or ordinary file. You do not need a new service to understand your progress. Revisit the system when the project changes phase, and remove fields you no longer use. The best evidence of a useful tracker is that you can look at it, understand the manuscript’s current state, and choose an appropriate next action.

A week with fewer words can still show progressAN INVENTED EXAMPLE / COMPARE THE CHOICE
THE FIRST VERSION

Week total: minus 600 words. Target missed. Start over next week.

A DIFFERENT CHOICE

Structural pass: removed a repeated introduction, combined two demonstrations, and identified one missing explanation. Four of six rough chapters now have a clear practice task. Next: draft the missing explanation in chapter 5 before adding new material.

What changed

The revised record names the work performed and its consequences. It preserves the next step without converting a decrease in manuscript length into a verdict about the writer.

STRUCTURAL PASS / SESSION RECORD

A tracker that preserves the reason to return.

A completed example
A FILLED WORKING RECORD
SESSION 1
Task: compare the two chapter openings.
Result: both explain the same distinction; chapter 4 has the different demonstration.

SESSION 2
Task: remove the repeated explanation from chapter 4.
Result: the demonstration reaches its practice question earlier. A transition is now missing.

SESSION 3
Task: draft that transition.
Result: the chapter names its new question before the example.

NEXT CHECK
Ask a reader what the demonstration helps them decide.
BOOKDRAFTLAB / ORIGINAL TEACHING MATERIAL

An original illustrative specimen. Adapt the method to your own material.

NOW MAKE IT YOUR OWN

Design a tracker with only four essential fields

  1. Choose the current phase and write the question you want your tracker to answer. Define one meaningful manuscript milestone and its completion condition.
  2. Create four fields: date, intended task, result, and next action. Add one numerical measure only if it helps answer your chosen question.
  3. Record three real sessions. Use result notes that identify manuscript changes or discoveries, and keep the entries short enough to maintain.
  4. Review the entries and change one upcoming task based on what you see. Remove any field that did not help you understand or decide something.
Your result

A three-session log, one defined manuscript milestone, and a specific planning change supported by the record.

BEFORE YOU MOVE ON

Do your last three entries show what changed in the manuscript and support one concrete adjustment, or are you collecting numbers that leave the next task unclear?

Make your own version here.

0 / 3,000 characters

These notes are temporary for this visit. Download a copy before leaving the page.

Common questions

What is the best app for tracking writing progress?

The best starting point is a tool you already understand and will maintain. A notebook, document, or local spreadsheet can record tasks and results. Choose additional features only when you have a clear question they answer, rather than expecting the tool itself to create a routine.

How do I count progress when revising?

Define the revision pass and track the units assessed under that standard. For example, record scenes reviewed for a clear change or chapters checked for evidence gaps. Note the resulting decisions. Word-count increases and decreases can provide context, but they rarely describe the whole revision.

Should I track days when I do not write?

If it helps you understand capacity or interruptions, record a brief neutral note. You do not need to document every day. The purpose is to support planning, so avoid creating a system in which missing an entry feels like another task you have failed to complete.

Sources and further reading

These sources support further investigation. Check requirements at the relevant publisher or platform before a submission.

Back to the topMore from this collection

A closer look