IntermediateLesson 16 of 305 min read

Long Writing Projects

Learn to plan long documents with a brief, outline, word budgets and a facts sheet, write section by section, and check the whole for length and contradictions with a real program.

In this lesson you will

  • Plan with a brief, outline and word budgets
  • Use a facts sheet
  • Write section by section
  • Check length and contradictions across sections

About 22 minutes

A report that contradicts itself

Meera is writing the library’s festival report, forty paragraphs over several sittings, with help from Claude. By the end, the introduction says the festival is on Saturday 17 June. A later section says Saturday 24 June. Nobody noticed, because each section was written on a different day and each looked fine on its own. Long writing is where consistency quietly breaks. This lesson shows how to plan and build long documents with Claude, one piece at a time, and how to check the whole.

Plan first, then write in pieces

A long document asked for in one go tends to be generic and uneven. A better method is to build it like a house: plan, frame, then fill each room. In practice:

  1. Brief. Say what the document is, who reads it, what it must achieve and how long it is.
  2. Outline. Ask for a section-by-section outline and approve or change it. Give each section a word budget.
  3. Facts sheet. Write down the facts that must stay the same: names, dates, numbers, places. Paste it into each section’s request.
  4. Write section by section. One conversation turn per section, with the facts sheet and the outline.
  5. Review the whole. Look for repetition, gaps and contradictions.
  6. Edit in your voice. Read it aloud, cut, and fix.
We are writing a report on the village festival for the committee. Here is the facts sheet: festival date Saturday 17 June; place the village hall; budget 400 pounds. Write only the section "The plan" in about 150 words, following this outline: [outline]. Use only the facts on the sheet.

The facts sheet is the most valuable trick in the lesson. Without it, Claude reconstructs the facts from the conversation, and may invent, or mix, a date or a figure. With it, every section starts from the same truth. If the conversation grows very long, start a new one for the next section and paste in the facts sheet and a short summary of what came before, as lesson 2 suggested.

Checking the whole

A person can check a long draft for contradictions, but it is slow, and the eye slides over repeated phrases. The program below does a simple version of the job. It compares each section’s length with the budget from the outline, flagging any that are more than a fifth over, or less than 60 per cent of the budget. And it hunts for the festival date in every section, so that any disagreement shows. It also estimates reading time at 200 words a minute. The draft is made-up sample text.

import re

outline = {"Introduction": 80, "The plan": 150, "The budget": 100, "Next steps": 60}
draft = {
    "Introduction": "The library festival will take place on Saturday 17 June at the village hall. " * 4,
    "The plan": ("Doors open at 10am on Saturday 17 June. Volunteers run three tables. "
                 "Tea is served by the front desk. ") * 6,
    "The budget": "The budget is 400 pounds. The festival is on Saturday 24 June. " * 5,
    "Next steps": "Posters go up on Monday. Ask Anil about the banner. " * 3,
}
print("section: words of budget")
for name, budget in outline.items():
    n = len(draft[name].split())
    flag = "OVER" if n > budget * 1.2 else ("short" if n < budget * 0.6 else "ok")
    print(f"{name}: {n} of {budget} {flag}")

dates = {}
for name, text in draft.items():
    for d in re.findall(r"Saturday \d+ June", text):
        dates.setdefault(d, set()).add(name)
print()
print("different dates used:", len(dates))
for d, where in sorted(dates.items()):
    print(f"  {d}: in {', '.join(sorted(where))}")
total = sum(len(t.split()) for t in draft.values())
print(f"total: {total} words, about {total / 200:.1f} min to read")
section: words of budget
Introduction: 56 of 80 ok
The plan: 114 of 150 ok
The budget: 60 of 100 ok
Next steps: 30 of 60 short

different dates used: 2
  Saturday 17 June: in Introduction, The plan
  Saturday 24 June: in The budget
total: 260 words, about 1.3 min to read

Three of the four sections are within budget. Next steps is flagged as short: it has 30 words against a budget of 60, which tells you it needs more, or that the outline was too ambitious. The more serious finding is the dates. The program found 2 different dates: Saturday 17 June in Introduction, The plan, and Saturday 24 June in The budget. That is exactly Meera’s problem, found in a second. The total is 260 words, about 1.3 minutes to read. The program cannot say which date is correct, only that the document disagrees with itself, so you go to the facts sheet and fix the odd one out. A real check would also look for names, figures and places.

Keeping a voice across a long piece

  • Give Claude a paragraph of your own writing and ask it to match that voice in every section.
  • Keep a style note: sentence length, words you like and words you avoid.
  • Read the opening of every section together, because tone drifts there first.
  • Write the introduction and conclusion yourself, or at least rewrite them heavily.
  • Ask for a list of the claims in the draft that need a source, and check each.
Common mistake: all in one go

Asking for the whole document in one request and trusting the result. Long outputs repeat themselves, drift in tone and contradict their own facts. Build in sections, and check the whole at the end.

You sign it off

For documents that matter, such as grant bids, reports or legal text, a human must read every word. Claude is a drafting and editing partner, not the author who signs it off.

Choose a document of about 600 words. Write a facts sheet and an outline with word budgets. Ask for each section separately. Then run a simple check of your own for dates and names across the sections.

Practice for this lesson

Check what you learned

Five quick questions. Pick an answer and you will see straight away whether it is right and why.

What is the purpose of a facts sheet?

  1. It makes sections longer
  2. It writes the conclusion
  3. It changes the style
  4. It keeps names, dates and numbers the same in every section

A shared facts sheet stops sections from inventing or mixing facts.

Why build a long document in sections?

  1. Long single outputs drift and contradict themselves
  2. It is always shorter
  3. Claude cannot write more
  4. It avoids reading

Sections with a plan stay consistent and are easier to check.

What did the checker find in the draft?

  1. No problems
  2. A missing title
  3. Two different festival dates
  4. A broken link

Saturday 17 June and Saturday 24 June both appeared, so the draft contradicted itself.

What can the checker NOT tell you?

  1. That the dates differ
  2. Section lengths
  3. Reading time
  4. Which date is correct

It only shows disagreement, and you decide the truth from your facts sheet.

What should you write yourself in an important document?

  1. Nothing
  2. The introduction and conclusion, at least heavily rewritten
  3. Only the title
  4. Only the footnotes

The opening and closing carry your voice and your responsibility.

Summary

  • Plan first, then write in sections, with a facts sheet in every request.
  • Check length against the plan and facts across the whole.
  • Keep your own voice and write the opening and closing yourself.
  • You sign off anything that matters.

Next lesson

Lesson 17 looks at images and screenshots as input.

Questions

Can Claude write a whole book?

It can help draft and edit chapters, but long works need your plan, your facts and your review. Quality depends far more on the planning than on the length.

How do I keep a long chat from drifting?

Start fresh for each big section, paste the facts sheet and a short summary, and keep each request to one task.

What if sections repeat each other?

Ask Claude to list the main point of each section, then remove or merge repeats yourself.

Progress is saved in this browser.