CELPIP Writing Task 1 Email Template for CLB 9: A Real Structure That Works

If you're aiming for CLB 9 on CELPIP Writing, you've probably already noticed something annoying: most templates floating around online give you a skeleton (Dear [Name], I am writing to inform you that [problem]...) but never explain why that skeleton earns 9s instead of 7s. That gap matters more than people think, because CELPIP raters aren't grading you on whether you filled in a template — they're grading four specific things: Content/Coherence, Vocabulary, Readability, and Task Fulfillment. A template only helps if you understand what each part of it is doing for those four scores.

This matters even more if you're going through Express Entry. The jump from CLB 8 to CLB 9 is the steepest gap in the whole CRS conversion chart — going from an 8 to a 9 across all four abilities can be worth a meaningful chunk of CRS points, sometimes enough to shift you from "watching the draws anxiously" to "comfortably above the cutoff." Writing Task 1, the email, is usually the more coachable of the two writing tasks, because unlike the survey response (Task 2), an email has a predictable shape. That predictability is exactly what you can exploit.

What the Task Actually Asks You to Do

CELPIP Writing Task 1 gives you a scenario — a problem at your apartment, a request to a manager, a complaint about a product, an invitation you need to decline, a recommendation you need to write for a friend — and three bullet points you must address. You get 27 minutes and are expected to produce somewhere in the 150-200 word range. The email can be formal (to a landlord, a company, an employer) or informal (to a friend, a relative, a former colleague), and the tone you're asked to strike changes what "correct" looks like. A CLB 9 response to a formal complaint email and a CLB 9 response to an informal email asking a friend for advice look nothing alike in tone — but the underlying skeleton of how you organize ideas is nearly identical.

Here's the mistake that costs people the most points, and it's not a grammar mistake: skipping or under-developing one of the three bullet points. Task Fulfillment is graded on whether you addressed everything the prompt asked, with enough development that the reader could act on what you wrote. A grammatically flawless email that glosses over the third bullet point in one throwaway sentence will not score a 9, no matter how elegant the vocabulary is. Raters are explicitly checking for this, and it is the single most common reason strong writers plateau at CLB 7 or 8 instead of breaking into 9.

The Template Structure (and Why Each Piece Earns Points)

Here's the framework I'd actually use, broken down by what it's doing for your score rather than just what to type.

1. Subject line. This is a small thing that a lot of guides skip entirely, but it's a fast, visible signal of vocabulary and content control. Compare:

• Weak (CLB 7 range): "Problem"
• Strong (CLB 9 range): "Urgent: Water Leak in Unit 204 — Request for Immediate Repair"

The second one does three things in six words: names the issue, signals urgency appropriately, and states what you want. That's Content/Coherence and Vocabulary working together before the rater has even read your first sentence. Don't overthink this — just make sure your subject line names the specific issue and, where relevant, what action you want.

2. Greeting matched to register. "Dear Mr. Alvarez," or "Dear Property Manager," for formal; "Hi Priya," for informal. This sounds trivial, but mismatched register (an overly casual greeting in a formal complaint, or a stiff greeting in a note to a friend) is exactly the kind of thing that pulls your Readability and Content scores down even when your grammar is fine.

3. Opening line that states purpose immediately. CLB 9 emails don't warm up slowly. First or second sentence should tell the reader why you're writing. Something like: "I am writing to report a persistent water leak in the bathroom ceiling of my unit, which began three days ago and has worsened since." Notice this sentence already does double duty — it states the problem (bullet point 1, probably) and gives a timeframe, which shows control of detail without needing a separate sentence for it.

4. Body paragraph(s) that map directly onto the three bullet points. This is where task fulfillment lives or dies. I'd suggest, quite literally, one paragraph per bullet point if the prompt gives you three distinct things to cover, or one combined paragraph with clear sentence-level separation if two of the bullets are closely related (e.g., "describe the problem" and "explain how it's affecting you" often blend naturally). The key discipline: after you finish drafting, go back to the prompt and check off each bullet point against your draft. If you can't point to a specific sentence that addresses a bullet, it's not there — vague implication doesn't count.

5. A clear, specific request or action item. CLB 9 emails don't end vaguely. "Please let me know how you plan to address this" is fine but generic. "Could you arrange for a plumber to inspect the unit by Friday, and confirm the appointment time by email?" is specific, reasonable, and shows command of polite-but-firm register — which raters are explicitly told to look for in complaint-style prompts. A common point-loser here is failing to balance firmness with formality: being too blunt reads as rude, being too soft reads as if you don't actually need anything done.

6. Closing that matches tone. "I look forward to your prompt response" for formal; "Let me know what you think!" for informal. Then sign off appropriately — "Sincerely, [Your Name]" versus "Talk soon, [Your Name]."

A Worked Example, Annotated

Let's say the prompt is: You recently stayed at a hotel and had a disappointing experience. Write an email to the hotel manager. In your email: describe what happened during your stay, explain how it affected your trip, and say what you would like the manager to do.

Here's a CLB 9-range response, with notes on what each part is doing:

Subject: Complaint Regarding Room Conditions — Stay of March 3–5, Room 412

Dear Ms. Chen,

I am writing to bring to your attention several issues I experienced during my recent stay at the Lakeside Inn from March 3rd to 5th, which I had booked for a family celebration.

Upon check-in, I discovered that the heating in my room was not functioning, and despite two calls to the front desk, the issue was not resolved until the following afternoon. In addition, the room had not been properly cleaned; there were visible stains on the carpet and the bathroom lacked basic toiletries that had been listed as included in my reservation.

These problems significantly disrupted what was meant to be a relaxing weekend with my family. My elderly mother, who was travelling with me, found the cold particularly uncomfortable, and we ended up spending much of the first evening trying to resolve the situation rather than enjoying our celebration as planned.

Given these circumstances, I would appreciate a partial refund for the first night, as well as written confirmation of what steps your hotel is taking to prevent similar issues for future guests. I have stayed at your property twice before without incident, and I would like to continue choosing the Lakeside Inn if this matter can be resolved satisfactorily.

I look forward to hearing from you soon.

Sincerely, Aiden Park

Why this lands in the CLB 9 range: the subject line is specific and dated. The opening sentence states purpose and gives context (occasion, dates) in one breath — that's efficient use of the word count. All three bullet points are covered distinctly and in enough depth that a reader could act on them: what happened (heating, cleanliness), how it affected the trip (family celebration disrupted, mother's discomfort), and what's wanted (partial refund, written confirmation). The tone stays firm without tipping into rudeness — "I would appreciate," "I would like to continue choosing," softens the complaint while still being clear about the ask. And the closing detail about having stayed there twice before is a small, human touch that shows range beyond mechanical complaint-writing — it signals genuine investment in the relationship, which is the kind of nuance that separates 8s from 9s.

Compare that to a CLB 7-range version of the same email, which might say: "I am writing because my stay at your hotel was bad. The room was cold and dirty. This ruined my trip. Please fix this and give me a refund. Thank you." That version technically touches all three bullets, but with so little development that Content/Coherence and Vocabulary both take a hit — there's no specific detail, no register control, and nothing beyond the bare minimum.

What About Informal Emails? The Template Shifts, Not the Discipline

A common "but what if" question: what changes when the prompt asks for an informal email to a friend rather than a formal complaint?

The three-bullet-point discipline stays identical — you still need to hit every bullet with real development. What changes is vocabulary register and sentence rhythm. Formal emails favor full sentences, hedged requests ("I would appreciate," "would it be possible to"), and no contractions. Informal emails to friends or family should actually use contractions naturally ("I can't make it," "it'd be great if"), shorter sentences, and warmer, more direct language ("Hey, quick favor to ask"). Raters notice when someone writes an informal email in stiff, formal register — it reads as unnatural and actually hurts your Vocabulary and Readability scores, because part of what's being tested is whether you can adapt tone to audience, not just whether you can write grammatically correct sentences.

So if the prompt says "write to your friend Sam explaining why you can't attend their birthday party, and propose an alternative way to celebrate," a strong response leans casual throughout: "Hey Sam, I feel terrible about this, but I won't be able to make it to your party on Saturday — my flight back from a work trip got moved up and I land right in the middle of the evening. I know how much you were looking forward to celebrating with everyone, so I really don't want to just cancel on you. Would you be up for grabbing dinner the following weekend instead, just the two of us? I'd love to actually celebrate properly rather than just sending a card." That's warm, specific, hits the "why," the apology, and the alternative — all three implied bullets — without ever sounding like a business letter.

Time Management: Don't Let the Clock Beat Your Structure

You have 27 minutes for this task, and it's easy to either rush the ending or spend too long polishing the opening. A rough allocation that works for most people: 2-3 minutes reading the prompt and mentally checking off the three bullet points, 15-17 minutes writing, and the remaining 5-7 minutes reviewing. That review time is not optional — it's when you catch the small grammar slips (subject-verb agreement, article errors, tense consistency) that otherwise quietly cap your Grammar score, and it's your last chance to verify all three bullets are genuinely addressed, not just gestured at.

One habit worth building during practice: after you finish a draft, literally go back to the prompt and underline the three bullet points, then find and label the corresponding sentence(s) in your email. If a bullet point has no clearly matching sentence, that's a real gap, not a stylistic choice — fix it before you move on. Doing this repeatedly during prep trains you to build task fulfillment into your first draft instead of discovering the gap on test day when there's no time left to fix it.

Common Vocabulary Upgrades Worth Memorizing

You don't need an enormous vocabulary bank — you need a handful of flexible, natural-sounding phrases that shift your writing from serviceable to polished. A few worth having ready before test day:

• Instead of "I am writing because..." → "I am writing to bring to your attention..." / "I wanted to reach out regarding..."
• Instead of "This is a big problem" → "This has caused considerable inconvenience" / "This has significantly disrupted..."
• Instead of "Please fix this" → "I would appreciate it if you could arrange..." / "Could you please look into..."
• Instead of "Thank you" (as a closer) → "I look forward to your response" / "I would appreciate your prompt attention to this matter"

Memorizing five or six of these and practicing plugging them into different scenarios does more for your score than trying to learn fifty new vocabulary words you'll be too nervous to use correctly under time pressure.

A Note on What's Actually Changing (and What Isn't)

There's a fair amount of noise online right now about CELPIP supposedly overhauling its format — claims about AI-hybrid scoring systems, new "scenario-based" writing structures, or CELPIP becoming a non-Canada-specific test with some kind of universal average score. I'd treat all of that with real skepticism. As of the most recent official information from CELPIP itself, the test remains a computer-delivered exam completed in one sitting, covering Listening, Reading, Writing, and Speaking, with the same general format Writing Task 1 has used for years. Given how much is riding on your score for immigration purposes, always double-check anything time-sensitive — test format, fees, processing times for your CRS-linked applications — directly on the official CELPIP site or canada.ca rather than trusting secondhand blog claims, including this one, for anything that might have changed since this was written.

Practicing Toward CLB 9, Not Just Toward "Done"

The biggest shift in mindset that gets people from CLB 7-8 to CLB 9 isn't learning new grammar rules — most CLB 7 writers already have solid grammar. It's learning to self-audit against the four criteria every single time you practice, rather than just writing an email and moving on. Set a timer, write the email in 20 minutes, then spend 5 minutes rating your own draft against Content/Coherence, Vocabulary, Readability, and Task Fulfillment as if you were the rater. Over a few weeks of doing this consistently, you start building those checks into your first draft instinctively — which is exactly the skill that shows up as a 9 on test day.