GenerateRandomSearch

Writing Sprint Challenge Generator

The hard part of a writing sprint is not the timer — everybody has a phone. It is knowing what a realistic target looks like, because a number picked out of the air is either so low it does nothing or so high it guarantees failure. Twenty words a minute is roughly the pace of talking, written down.

What this generator does

Turns a length and a pace into a word target you can actually hit, and pairs it with a short constraint brief to write against. It deliberately contains no timer: a countdown on a web page is one tab-switch away from being wrong, and the thing that is genuinely hard to work out in your head is what a realistic target looks like for the time you have.

How to use this tool

  1. Set how many minutes you have and pick a pace.
  2. Press Set the sprint for a word target and a brief.
  3. Start your own timer and write.
  4. Draw again for the next sprint, keeping the constraints you liked.

Understanding the controls

Minutes
How long the sprint runs. Fifteen to twenty-five is the range most people sustain; beyond forty the pace drops and the target stops being realistic.
Pace
Gentle leaves room to think between sentences. Steady is roughly the pace of talking. Fast means no editing at all, which is uncomfortable on purpose — it is the setting for getting a draft down rather than getting it right.
Constraints
An optional brief to write against. Sprints with a constraint tend to produce more usable material than open ones, because there is no time to decide what to write about.

Worked examples

A standard sprint
20 minutes, steady — 400 words.
A short hard one
10 minutes, fast — 300 words, and no editing.
A gentle session
30 minutes, gentle — 360 words, with room to think.
With a brief
15 minutes, steady, 300 words · first person · no dialogue.

Common use cases

  • Daily writing practice with a target that is actually achievable
  • Group sprints where everybody works the same length and brief
  • Drafting sessions during a novel-writing month
  • Breaking a long session into stretches with a break between
  • Finding out what your real writing pace is

How this generator works

The target is minutes multiplied by a words-per-minute figure for the chosen pace: twelve for gentle, twenty for steady, thirty for fast. Those are deliberately modest — published sprint advice often quotes figures that only apply to people already drafting fluently, and a target nobody hits teaches the wrong lesson on the first attempt. The constraint brief is drawn from the same slot mechanism as the constraint generator, so a sprint can carry a narrator and a rule as well as a number.

Randomness and fairness

The word target is arithmetic and not random at all — the same minutes and pace always give the same number. Only the constraint brief is drawn, using the browser's cryptographic random number generator.

For how randomness is produced across the whole site, see how Generate Random works.

Assumptions this tool makes

  • You are drafting rather than editing. Editing rates are far lower and these targets would be absurd for it.
  • The sprint is continuous. Targets assume writing throughout rather than in bursts.

Limitations and good to know

  • There is no timer. That is deliberate — use a phone or a kitchen timer, both of which keep running when a browser tab is backgrounded.
  • Word targets are estimates from a pace, not measurements of you. Your own rate is worth learning and will differ.
  • It counts nothing. Whether you hit the target is between you and your word processor.
  • Nothing here writes or edits. The constraints are rules for a person to work within.

Common mistakes

Setting a target from somebody else's rate
Published sprint figures usually come from people already drafting fluently. Start at gentle or steady, find your own rate over a few sessions, and set targets from that.
Editing during a sprint
The targets assume drafting. Editing runs at a fraction of the rate, and a sprint spent editing will miss any target and feel like a failure that it is not.
Sprinting for an hour
Pace falls away well before that. Two twenty-minute sprints with a break produce more than one forty-minute one, and the second one starts faster.

Practical tips

  • Record what you actually wrote for a week. Your real pace is more useful than any of these figures and takes five sessions to find.
  • Draw the constraints before starting the timer. Deciding what to write about inside the sprint is what eats the first five minutes.
  • For a group, use the same length and brief and compare afterwards. The variety from identical constraints is the interesting part.

Troubleshooting

I never hit the target
Drop to a gentler pace. The targets are meant to be reachable; a target you consistently miss is measuring the wrong thing about you.
The sprint has no timer
By design. A browser tab that is backgrounded can have its timers throttled, so a countdown here would sometimes be wrong. Use a phone.

Privacy and your data

Nothing is entered beyond a length and a pace, and nothing is stored. Sprints are generated in your browser, never uploaded and never written into the page address. Analytics records only that the tool ran.

Frequently asked questions

How many words should I write in twenty minutes?
At a steady pace, around 400 — roughly twenty words a minute, which is about the speed of talking written down. Gentle is nearer 240 and fast nearer 600. Those are starting points; your own rate after a few sessions is a much better guide.
Why is there no timer?
Because a browser timer is unreliable in exactly the situation you would use it: a backgrounded tab can have its timers throttled, so a countdown can quietly run slow. A phone timer does not have that problem, and everybody has one.
Do the constraints help or get in the way?
They help, in a specific way: a sprint with no brief usually spends its first minutes deciding what to write about. A constraint removes that decision, which is worth more in a twenty-minute sprint than the freedom it costs.