CELPIP Writing Task 1 Template — Polite Request Email

CELPIP Writing Task 1 gives you one email to write in 150–200 words in about 27 minutes, addressing three bullet points. One of the most common versions is the polite request email: you need someone to do something — grant time off, extend a deadline, send information, issue a refund, or simply do you a favour. This guide keeps the generic method short and focuses on what actually makes a request email score: the right level of politeness, a clear justification, a specific ask, and a courteous close.

A request email is different from a complaint or an apology. You are asking the reader to give up something — their time, money, or a decision in your favour — so the tone has to do real work. Get the politeness wrong and even a well-organised email reads as demanding or, at the other extreme, so vague the reader cannot say yes.

What the examiner is looking for

Writing is scored on four criteria. Here is how each one applies to a request email.

• Content & Coherence — You cover all three bullets and connect them logically: why you are writing, why your request is reasonable, and exactly what you want. A request that skips the justification feels entitled; one that skips the specific ask leaves the reader guessing. Hit it by following the request structure below and linking ideas with transitions.
• Vocabulary — You use precise, situation-appropriate words and, crucially, softening language (I was wondering whether, would it be possible). Hit it by varying your request phrasings instead of repeating "Can you" three times.
• Readability — Your email flows in clear paragraphs with controlled grammar, punctuation, and a consistent register. Hit it by using a greeting, two to three short body paragraphs, and a sign-off — and by not mixing "Dear Sir" with "Hey, thanks heaps!".
• Task Fulfilment — You write to the right reader, in the right tone, at the right length, and you make a request that could realistically be granted. Hit it by reading the prompt for who you are writing to (a manager is formal; a friend is friendly) and matching your politeness to that relationship.

Plan in 3 minutes: who, why, what

Before writing, spend two to three minutes answering three questions. This is the request-email version of the "Rule of 3".

1. Who am I writing to, and how polite must I be? (Boss/landlord/company = formal; colleague = semi-formal; friend = friendly.)
2. Why is my request reasonable — what is my justification?
3. What exactly do I want, and by when?

Those three answers become your three body moves. Now build the email.

Step 1 — Open with purpose, not demands

State why you are writing in the first line, politely. In a formal email you might write, "I am writing to request a short extension on the Henderson report." This signals the topic immediately (good for Coherence) and sets a respectful tone. Avoid opening with the bare demand ("I need more time") — lead with the framing verb request or a softened I was hoping to ask.

Step 2 — Justify before you ask

Give a brief, credible reason before the request itself. Readers say yes more readily when they understand the why. For example: "My team has taken on two urgent client deliverables this week, which has pushed back my schedule." Keep it to one or two sentences — enough to be reasonable, not a sob story. This is the single move most weak request emails skip, and it is exactly what lifts Content & Coherence.

Step 3 — Make the ask specific and easy to grant

Now state precisely what you want, with any concrete detail (dates, amounts, format). "Would it be possible to submit the report on Friday the 23rd instead of Wednesday the 21st?" A specific ask lets the reader simply approve it. Vague asks ("Can I have a bit longer?") force a follow-up and cost you Task Fulfilment marks.

Step 4 — Anticipate a yes and close courteously

Show good faith — offer reassurance, flexibility, or thanks: "I will ensure the quality is not affected, and I am happy to share a draft in the meantime." Then thank the reader and sign off in a register that matches the greeting. The close is where politeness lands; never end a formal request with "Thanks, bye."

The fill-in template

Dear [Name / Mr. / Ms. Surname],

I am writing to request [the specific thing, stated politely].

[Justification: one or two sentences explaining why the request is
reasonable — your situation, the reason for the favour.]

[The specific ask, softened: "Would it be possible to..." / "I was
wondering whether you could..." + concrete detail such as a date,
amount, or format.]

[Anticipate a yes: offer reassurance, flexibility, or what you will do
in return. "I would be very grateful" / "Please let me know if..."]

Thank you very much for considering my request.

Kind regards,
[Your Name]

Phrase bank by tone

Match the column to your reader. Pick one phrase per row and you have a full email in the correct register.

Softening and politeness: direct vs. polite

The quickest way to raise your register is to replace blunt requests with softened ones. The right-hand column is what scores well in a formal or semi-formal Task 1.

Notice the patterns: past-tense framing (I was wondering, I was hoping), modal verbs (would, could, might), and hedges (a little, if possible, when you have a moment). These are the building blocks of polite English requests, and using two or three of them is enough to lift the whole email.

Model answer

Scenario: Your apartment's heating has stopped working and you are writing to your building manager to request a repair. The three bullets ask you to explain the problem, say how it is affecting you, and request a specific action.

Why this answer scores high

• Opening (purpose): The first sentence names the request (urgent repair) and the unit number, so the reader knows the topic instantly — strong Coherence and Task Fulfilment.
• Bullet 1 (the problem): Concrete detail — since Sunday evening, radiators completely cold, thermostat has no effect — shows precise vocabulary and proves the issue is real.
• Bullet 2 (the impact): The justification (uncomfortable overnight, two young children) makes the request reasonable without being dramatic. This is the move that earns sympathy and the "yes".
• Bullet 3 (the ask): "Would it be possible to send a technician this week, ideally before the weekend?" is softened and specific, and the offer of access times makes it easy to grant.
• Close: Reassurance (happy to provide further details) plus a courteous, register-matched sign-off. Politeness is consistent from greeting to signature.
• Range: Modal softeners (would it be possible, I would be grateful), varied sentence length, and accurate punctuation cover Vocabulary and Readability. At roughly 180 words, it sits comfortably in range.

What CLB 7, 9 and 11 look like

• CLB 7: All three bullets are covered and the request is clear, but the politeness is uneven — perhaps one blunt line ("Fix it soon") slips in, softeners are repetitive (can you… can you…), and there are a few grammar or article errors that do not block meaning.
• CLB 9: Consistently polite and well-organised, with varied softening phrases, accurate modals, and clear paragraphing. The justification and ask are both specific. Minor slips may remain but the register never wobbles.
• CLB 11: Effortless, natural courtesy with precise word choice and smooth flow. The writer controls tone with subtlety (hedging, reassurance, anticipation of the reader's concerns), uses varied sentence structures accurately, and reads like a competent native professional with virtually no errors.

Common mistakes to avoid

• Skipping the justification. Jumping straight to the ask reads as entitled. Always give a brief, credible reason first.
• A vague request. "Can I have some time off?" forces a follow-up. State the exact dates, amount, or action so the reader can simply approve.
• Mismatched register. Opening with "Dear Sir" and closing with "Cheers!", or writing to a friend as if drafting a legal letter. Keep one tone throughout.
• Over-apologising or grovelling. Three sentences of "so sorry to bother you" weakens the email. One polite softener is enough.
• Being too blunt with modals. "You must", "I need you to", and bare imperatives sound like orders. Use would, could, and I was wondering.
• Wrong length. Under 150 words usually means a missing bullet or no justification; over 200 risks rambling. Aim for 170–190 and check the count.