CELPIP email samples for Task 1: the 5 scenarios that cover most prompts

You open the Task 1 prompt on test day and the scenario feels brand new — a dentist appointment to move, a coworker covering your shift, a gym complaint — and your prepared structure evaporates. Here's what we tell every student after their first mock: it isn't new. Task 1 pulls from a small set of everyday situations, and five scenario families cover nearly every prompt we've seen. Learn the five skeletons and the prompt stops mattering. This post gives you two full band-level samples, skeletons for the rest, and the register rules that carry across all of them.

If you want to see which family your writing is weakest in, a free mock test with instant writing scores will show you → celpipuni.com/free-mock-test.

TL;DR

Nearly every CELPIP Task 1 prompt is one of five scenarios: complaint about a service, request to a landlord/building manager, workplace request, cancellation or reschedule, and a thank-you with a follow-up ask. Same skeleton underneath all five: greeting → situation → request + reason → consequence or deadline → close. Register is polite-but-direct. The traps: over-apologizing, vague threats, and matching a friend's tone to a manager's inbox.

Why five scenarios are enough

Task 1 is everyday life, and everyday life repeats. The prompt asks you to email someone who can fix, grant, move, or hear about something: a manager, a company, a landlord, a coworker. Strip away the surface details — the noise complaint, the missed delivery, the double-booked shift — and the underlying jobs-to-be-done are five.

That matters because of how practice compounds. If every prompt looks new, you start every response from zero and hope. If every prompt maps to a family you've practiced ten times, Task 1 becomes an execution problem — the kind you solve with a checklist, not inspiration. The scenario decides the facts; the family decides the structure. The situations vary and formats get revised periodically (confirm current task examples on the official CELPIP site), but the families transfer: your noise-complaint skeleton works for the missed delivery and the gym complaint, because the reader's job is identical — hear a problem, act on it.

How to use the five skeletons

The base skeleton, once, because all five share it:

1. Greeting — the reader's name if the prompt gives one; a role if it doesn't.
2. Situation — 1–2 sentences with one checkable detail: a date, a room number, a measurement.
3. Request — small, specific, action-sized. "Could you [do X] by [time]?"
4. Consequence or deadline — a next step, not a threat. "If X, then I'll Y — I'd rather not."
5. Close — name plus whatever identifies you (unit, account, booking number).

The five families, and what each adds:

Same skeleton, five overlays. Practice one family per day for a week and you've covered the task.

Sample 1: workplace request to a manager

Prompt: your team uses a shared meeting room that's always booked. Write to your manager requesting a solution. Cover: the situation, its impact on your work, what you've tried, and what you suggest.

Hi Farah,

A quick one about Room 4 — the small meeting room our team shares with two others. It's booked solid most days: I checked last week and found 14 of 16 workday slots taken, mostly by people outside our team. When it's full, my one-on-ones end up as desk conversations in an open-plan area, which defeats the purpose of a one-on-one.

I asked Priya in Facilities about a second booking calendar, but the room list is fixed for the quarter.

Could we look at reserving two slots a week for the team — Tuesday and Thursday mornings, when our check-ins cluster? If a standing reservation isn't possible, I'd take a switch to Room 7 on those days.

Thanks — happy to put the request in writing if that helps.

Ravi, Product team

Why this works at band 9: the situation has a number (14 of 16 slots) that proves the writer counted; "what I've tried" is one honest sentence, not a saga; the request offers a fallback (Room 7) so the manager can say yes to something. The consequence slot becomes flexibility instead of escalation — right for a workplace email.

Sample 2: thank-you plus follow-up ask

Prompt: a neighbour looked after your cat while you were away. Write an email thanking them and asking a favour. Cover: your thanks, something specific they did, and the request.

Hi Beatrice,

We got back last night, and I'm still not sure "thank you" covers it — nine days of feeding a cat who hates being fed is its own achievement. The note you left about her 3 am sprint under your bed made me laugh all through unpacking. The plants surviving too is beyond what I paid for.

I'd love to return the favor — dinner's on us whenever suits you.

And one more ask, since you've proven braver than our vet: we're away the last weekend of the month, the 28th to 30th. Any chance you could do two nights? I'll leave food, the good treats, and my number on the counter.

Thanks again — for the cat, the plants, and the note.

Sofia, unit 12

Why this works: the thanks arrive first and are specific — the 3 am sprint, the plants. A thank-you email that rushes to the ask reads as a bribe; this family's task fulfillment is all about the ratio. The ask is small (two nights), equipped (food, treats, number), and dated. And the register is warm because the reader is a neighbour — the same writer's "Hi Dana" heater email would be wrong here. Register follows reader.

Skeletons for the other three families

Complaint about a service. Situation: what you paid for vs. what happened, one date and one number. Request: the remedy, named. Consequence: escalation to a complaints process, framed reluctantly. Keep it factual; the checkable detail does the anger's work.

Landlord/building request. Situation: what's broken or missing, since when, with one measurement. Request: the action and a time window ("this week"). Consequence: a lease-relevant step — a repair deadline in writing, a formal complaint. Firm beats furious; you'll need this relationship after test day too.

Cancellation or reschedule. Situation: the booking, the reference, what changed. Request: the cancellation or the move, plus two concrete alternative slots ("Tuesday after 4 or Friday morning") so the reader resolves it in one reply. Consequence usually unnecessary — the one family where you can skip it and stay natural.

The register toolkit: polite-direct lines that work anywhere

Phrases to keep in rotation across all five families — polite, direct, zero ceremony:

• Opening: "Quick one about…" · "I'm writing about…" · "I wanted to flag…"
• Requesting: "Could you [do X] by [day]?" · "I'd like [the remedy], please." · "Any chance you could [small ask]?"
• The reason: "That matters because…"
• The consequence: "If it's not possible by then, I'll [escalate] — I'd rather not."
• Closing: "Thanks — [name], [identifying detail]." · "Let me know what works."

And the lines to retire: "I hope this email finds you well." "Thank you in advance for your prompt attention to this matter." "Please do the needful." Each is padding a rater reads a dozen times an hour.

The scenario traps

Over-apologizing. The reschedule family brings this out: "I'm so terribly sorry to trouble you, I sincerely apologize for the inconvenience…" One "sorry for the short notice" is human. Six apologies turn a reasonable request into a burden — and bury the request itself.

Threats instead of consequences. "If this is not resolved immediately I will make sure everyone knows how this company treats customers" — that drops your register through the floor. The consequence is a process step you'd rather skip: a formal complaint, a cancellation, an escalation. Stated once, reluctantly.

Wrong formality for the reader. The prompt names your reader, and the reader sets the register. A manager gets "Hi Farah" and full sentences; a neighbour gets "Hi Beatrice" and warmth. The classic cap: "Dear Sir or Madam" to a prompt that names the reader — the email equivalent of calling your next-door neighbour "Mr. Hall" at a barbecue.

Your five-family practice checklist

• Write one email per family this week, timed, 27 minutes each, typed
• Check each against the base skeleton — request by sentence 3, always
• One checkable detail per email: a date, a number, a room, a measurement
• Register matched to the named reader — friend warm, manager brisk, company role-based
• Zero ceremony lines ("hope this finds you well" and friends, deleted)
• Complaint and landlord emails end with a reluctant next step, not a threat
• Reschedules include two alternative slots

Want a grader to check your five skeletons against the band you need? Get a detailed evaluation with band-level feedback on all four criteria → celpipuni.com/evaluation.

The nuance nobody mentions

My honest position: the five families matter less as prompts and more as register training. The real skill Task 1 tests is calibration — writing to Beatrice differently than to Farah differently than to "Hello Customer Service," sometimes within the same week of your life. Test-takers who practice one fixed "email style" score like that style: fixed, flat, band 7. Test-takers who practice the same skeleton at three formality levels walk in with a skill that adapts to whatever prompt appears. On test day you don't choose the scenario. You do choose the register. Practice like it.

Tools and resources

• The official CELPIP site — free sample Task 1 prompts and current task guidance. Check your family-mapping against real prompt wording. (Format gets revised — confirm there.)
• Free mock test — instant section scores to find your weakest family: celpipuni.com/free-mock-test
• Human evaluation — find out whether your emails read at your target band across all five families: celpipuni.com/evaluation
• Annotated Task 1 samples — the companion deep-dive with every structural move labeled: Task 1 samples annotated

Frequently asked questions

What topics does CELPIP Task 1 usually give?

Everyday situations: complaints, requests to landlords or building managers, workplace requests, reschedules, and thank-you-with-a-follow-up emails. Nearly all map to the five families.

Can I prepare Task 1 emails in advance?

Prepare skeletons, not sentences. On test day you swap in the prompt's facts. Sentences memorized in advance read as memorized, and that costs you.

How long is the Task 1 email?

~27 minutes, recommended 150–200 words. Budget 3–4 minutes planning, 18–20 writing, 3–4 editing. Timings get revised — confirm current ones on the official CELPIP site.

What if I don't know the reader's name?

Use the role: "Hello Customer Service," "To the Building Manager." The prompt usually identifies who you're writing to — match that, not "Dear Sir or Madam."

Should I apologize in a complaint email?

No. State facts, name the remedy, move on. A checkable detail ("the 3rd, order 88412") reads stronger than emotional language. Over-apologizing belongs to the reschedule family — one "sorry for the short notice" there, maximum.

Do these five families cover Task 2 as well?

No — Task 2 is a survey response where you pick one of two options and justify it. Different structure, different practice. Start with the Task 2 formula.

What to do next

1. Today: pick the family that scares you most and write it, timed, against the base skeleton.
2. Tomorrow: a different family. Note which moves felt automatic.
3. Days 3–5: the remaining three, one per day.
4. Day 6: rewrite your weakest one, fixing one thing only.
5. Day 7: get an evaluation on two of them.

Related reading

• CELPIP Writing: The Complete Guide to a 9+ (2026)
• CELPIP Writing Task 1 Samples: Emails That Score 9
• CELPIP Writing Task 2: The Survey Response Formula
• 12 CELPIP Writing Mistakes That Cap You at 7

The bottom line

Task 1 isn't five hundred possible prompts — it's five skeletons wearing different clothes, and every skeleton is the same five moves with a request at its heart. Practice each family once this week, match the register to the reader the prompt names, and test day stops being a surprise party.

Ready to check your five skeletons against a trained grader's eye? Get a detailed evaluation with band-level feedback → Get your emails evaluated.