CELPIP Writing word count: what's optimal (150-200 isn't a law)
You've finished a practice email, glanced at the word count, and seen 142. Your stomach drops. Does 142 fail? Do you add a paragraph? Then the next practice you write 260 words and feel productive — but your score doesn't move. If word count is a live anxiety for you, this post settles it: where the 150–200 recommendation comes from, why it's guidance rather than a rule, and what the rater is actually counting when they read your response.
To see whether your natural length is working for or against you, take a free mock test and check the writing score → celpipuni.com/free-mock-test.
TL;DR
CELPIP recommends 150–200 words per writing task, but it's guidance, not a hard rule — there's no automatic penalty at 142 or 210. What's scored is development density: every sentence should add content — a reason, an explanation, an example, a request. 170 well-developed words beat 260 padded ones. Under about 130 words rarely develops enough to score well. Count development, not words.
What the word count actually measures
Both CELPIP Writing tasks — the Task 1 email (~27 minutes) and the Task 2 survey response (~26 minutes) — carry a recommended length of 150–200 words. Notice the language: recommended. It's guidance for the band levels, not a fence with penalties on either side. The rater doesn't start by counting words — they start by asking: does this do the job the task set, and does every sentence pull weight?
The recommendation exists for a practical reason. Below roughly 150 words, most writers can't fit the required content — the situation, request, reason, and consequence in Task 1; two developed reasons plus a concession in Task 2. Above roughly 200, most writers drift: repetition, ceremony ("thank you in advance for your kind consideration"), a third reason nobody asked for. The range isn't about the number — it's a proxy for "enough development, not much padding."
So the honest framing: a 142-word email that covers every bullet with two specific details scores above a 210-word email that circles its request for three paragraphs. Fix the density and the word count lands in range on its own.
How to think about length in practice
Here's the process I teach, in the order you'll actually use it on test day.
Plan first, and the length decides itself. Your 3–4 minutes of planning should end with a skeleton: for Task 1, reader + situation + request + consequence; for Task 2, choice + two reasons + one example each + concession. Write the skeleton and the response lands between 160 and 190 words. People who aim for "at least 180" write padded responses. People who aim for the skeleton write right ones.
The long-answer trap: more words, more error surface. Every extra sentence is another chance for a missing article, a wrong tense, a comma splice. At band 7–8 level, a 260-word response typically contains 60% more errors than a 170-word one covering the same content — same accuracy rate, larger surface. And under time pressure, sentence 15 is written more carelessly than sentence 5. Cutting words is the cheapest grammar fix there is.
The short-answer trap: under 130 rarely develops. Below about 130 words, Task 2 answers usually contain one reason plus a dangling "secondly." Task 1 emails state a situation and make a vague request ("please look into this") without a consequence. The response might be flawless — flawless and thin scores as thin.
Diagnose your own tendency in one writing session. Write three timed responses. Count words. Consistently under 150? Your planning step is probably skipping examples — add "one concrete example per reason" to your plan. Over 220? You're probably writing ceremony: circle every sentence that could be deleted without losing information. Most people find 3–5.
The numbers: what's developed and what's filler
The word-count guidance, and the time math that produces it:
| Task | Time | Recommended | Planning | Writing | Editing |
|---|---|---|---|---|---|
| Task 1 (email) | ~27 min | 150–200 words | 3–4 min | 18–20 min | 3–4 min |
| Task 2 (survey) | ~26 min | 150–200 words | 3–4 min | 16–18 min | 3–4 min |
At a natural typing pace, 18 minutes of writing produces 170–200 words with time to fix what you know you get wrong. That's where the recommendation comes from — it's the time budget expressed in words.
And the sentence-level test — what counts as developed versus filler:
| Developed (counts) | Filler (costs you) |
|---|---|
| "The technician was a no-show on the 3rd, so I hot-spotted off my phone all week." | "As you may or may not be aware, there was an issue with the installation." |
| "A park is used from dog-walkers at 7 am to soccer at 8 pm — the same land works harder." | "Parks are very important for the community and its wellbeing." |
| "Could you send someone by Thursday? I work from home, so before 5 works." | "I would like to request your kind assistance in resolving this matter." |
| Reason + explanation + example, in any order | The same reason rephrased as a second reason |
Read a practice response of yours and sort every sentence into those columns. That's development density, and it's what the rater is actually measuring. (Word-count guidance and timings get revised periodically — confirm current numbers on the official CELPIP site.)
The mistakes people make with length
Panic-padding to cross 150. A student of ours — call him Ahmed — wrote a clean 138-word email, then added "I hope this email finds you well" and a closing paragraph thanking the reader for "their time and understanding in this matter." He crossed 150 and dropped his score: the added sentences were pure ceremony, and they diluted two specific details he'd already written. His natural length was right; his obedience to the number was wrong.
Counting words while you write. Do it once, after drafting. Live word-count anxiety mid-writing pushes you into shorter, choppier sentences to "stay safe" — you protect the number and sacrifice the development the rubric actually scores. And don't cut good content to get under 200: if you're at 215 with two developed reasons, cut a filler sentence instead. There's almost always one.
What good looks like at any length
Here's a Task 1 request at 158 words that covers everything — and the density is visible:
Hi Dana,
My washing machine (unit 214) stopped draining on Tuesday, and by Wednesday the floor around it was holding about a centimetre of water. I've mopped and put towels down, but every cycle adds more, and I can't run laundry at all now — with two kids, that's about five loads a week I'm hauling to the laundromat.
Could you send a technician this week? Any weekday works — I'm home after 3. If the machine's not repairable, I'd like to know what the replacement process is under the lease, since the unit came with the apartment.
Thanks, Reza, unit 214
No sentence is decoration. The situation has a measurement (a centimetre of water), the impact has a number (five loads), the request has a time window and a follow-up question. It's 158 words, it's in range, and — this is the point — it would score the same at 168 or 148, because nothing in it is padding.
Your word-count checklist
- Plan to a skeleton, never to a word count
- Aim for 150–200 as a byproduct of full development, not a target
- Under 150? Check for a missing example or consequence before adding words
- Over 220? Circle deletable sentences — you'll find 3–5
- One concrete detail (number, date, measurement) per paragraph
- Count words once, after drafting, then edit for 3–4 minutes
- Practice typed, timed, at the end of a Reading session — fatigue changes length
Want a grader to tell you whether your writing is developed or padded? Get a detailed evaluation with band-level feedback → celpipuni.com/evaluation.
The nuance nobody mentions
My honest position after years of grading: word count is the most over-checked number in CELPIP prep, and the test knows it. The counter sits on the screen, ticks up with every sentence, and turns a development problem into an arithmetic problem — "I need 12 more words" instead of "my second reason has no example." The candidates who move bands stop looking at the counter mid-writing and start asking of every sentence: if I delete this, do I lose content? If yes, keep it. If no, it was padding at any word count. The counter is a terrible steering wheel. Use it as a mirror.
Tools and resources
- The official CELPIP site — the current writing tasks and recommended word counts, straight from the source. (Guidance gets revised — confirm there.)
- Free mock test — see your writing score before and after you change your length strategy: celpipuni.com/free-mock-test
- Human evaluation — the fastest answer to "is mine developed or padded," with band-level feedback: celpipuni.com/evaluation
- Task deep-dives — what full development looks like in each task: Task 1 samples, Task 2 formula
Frequently asked questions
How many words should I write in CELPIP Writing?
Aim for 150–200 per task — the official recommendation. But it's guidance, not a rule: raters score development density, not length. 170 well-developed words beat 260 padded ones, and 142 words that cover everything outscore 210 that don't.
Is there a minimum or maximum word limit in CELPIP Writing?
No hard cutoff that auto-fails you. Very short responses (under about 130 words) score poorly because they can't develop enough content; very long ones accumulate errors and padding. The 150–200 band is where the content fits naturally.
Do raters count words?
No — they score what they read against the rubric: content, vocabulary, readability, task fulfillment. Length matters only through what it does to those four. A padded response reads as padded; a thin one reads as thin.
Will I lose points for writing 210 words?
Not for the number itself. The risk at 210+ is what the extra words usually contain — repetition, ceremony, rushed final sentences. If everything earns its place, 210 is fine.
How long is each CELPIP Writing task?
Task 1 runs about 27 minutes, Task 2 about 26. Budget 3–4 minutes planning, 16–20 writing, 3–4 editing. Timings get revised — confirm current ones on the official CELPIP site.
Is CELPIP Writing longer or shorter than IELTS Writing?
Shorter. IELTS Task 2 alone asks for 250 words; CELPIP's two tasks recommend 150–200 each, and both are everyday writing rather than academic essays. More in CELPIP vs IELTS Writing.
What to do next
- Today: write one timed response. Count the words at the end — that's your baseline number.
- Sort every sentence into developed or filler. Circle the deletable ones.
- Rewrite it tomorrow at the length the skeleton produces — no aiming at a number.
- This week: get one evaluation to confirm your density reads at the level you're targeting.
Related reading
- CELPIP Writing: The Complete Guide to a 9+ (2026)
- CELPIP Writing Task 2: The Survey Response Formula
- 12 CELPIP Writing Mistakes That Cap You at 7
- CELPIP vs IELTS Writing: What Each Test Actually Asks For
The bottom line
The 150–200 recommendation is a time budget expressed in words, not a rule with penalties. Write to a skeleton, make every sentence add content, and your length lands where it should. If you're under, you're missing development, not words. If you're well over, you're carrying filler that costs you errors and points. Count development, not words — that's the whole secret.
See whether your writing is developed or padded — get a detailed evaluation with band-level feedback → Check your writing level.