CELPIP Writing Task 1 is not really a vocabulary contest. It is an email task where you need to sound organized, complete, and appropriately polite in about 150 to 200 words.
That is why a good template helps. Not a memorized paragraph. A usable structure.
#What the examiner wants from Task 1
Task 1 usually gives you an everyday email situation and about three things you must do. The scoring pressure is not hidden:
- answer all the required points
- keep your tone appropriate for the person you are writing to
- organize the response into readable paragraphs
- stay near the expected word count
If one bullet point is weak or missing, the whole email feels incomplete even if the grammar is decent.
#The simplest Task 1 writing system
The easiest reliable approach is:
- Identify who you are writing to.
- Decide the tone.
- Answer each required bullet in order.
- Add one concrete detail to each body paragraph.
- Finish with a polite action-focused close.
-
Read for role and purpose firstBefore writing, identify the recipient, your relationship to them, and the main reason for the email. This tells you whether the tone should feel formal, neutral-professional, or friendly.
-
Mark the required bulletsMost Task 1 prompts are easier once you see them as three mini-jobs. If the prompt asks you to explain, request, and suggest, your email body should visibly do those three things.
-
Write one paragraph per taskThis keeps the response readable and protects you from forgetting one part. It also makes the email feel more natural than one large block of text.
-
Use one real detail per paragraphAdd a date, time, location, effect, example, or practical consequence. Concrete details make the email more believable and improve coherence.
-
Close with a clear next stepDo not just stop after explaining the situation. Ask for confirmation, action, information, or a reply.
#Choose the email shape before you write
Not every Task 1 email has the same purpose. The underlying email usually falls into one of a few families:
- complaint or problem report
- request or inquiry
- apology or explanation
- arrangement or rescheduling
- proposal or suggestion
- appreciation with a follow-up request
That matters because the tone and paragraph goals change slightly.
For example:
- a complaint email should stay polite and solution-oriented
- a request email should sound specific and clear
- an apology email should take responsibility and propose repair
- a proposal email should explain benefits, not just preference
#A master CELPIP Writing Task 1 template
This is the core structure that works across most Task 1 prompts.
Dear [Name or Sir/Madam],
I am writing regarding [situation]. Specifically, I would like to [main purpose].
To begin with, [answer required point one clearly]. [Add one concrete detail].
In addition, [answer required point two clearly]. [Add one supporting detail or consequence].
Finally, [answer required point three clearly]. [State the request, suggestion, or next step].
Thank you for your time and consideration. I look forward to your response.
Sincerely,
[Your Name]
#What changes depending on the prompt
The skeleton stays stable, but the language changes based on the purpose.
#If the email is a complaint
Focus on:
- what happened
- how it affected you
- what you want done
Useful language:
- I am writing to express my concern about...
- Unfortunately, this caused...
- I would appreciate it if you could...
#If the email is a request or inquiry
Focus on:
- what information or help you need
- why you need it
- when you need a reply
Useful language:
- Could you please confirm...
- I would also like to know...
- It would help if I could receive this information by...
#If the email is an apology or explanation
Focus on:
- taking responsibility
- briefly explaining the issue
- offering a solution or prevention step
Useful language:
- Please accept my sincere apologies for...
- The mistake happened because...
- To prevent this from happening again, I will...
Do not sound too casual or too dramatic
Task 1 usually needs a practical, respectful tone. Avoid slang, texting language, exaggerated emotion, or rude phrasing even when the situation is frustrating.
#A worked example
Below is the kind of prompt where this structure works well: a complaint email that also needs explanation and a request.
Opening: State the purpose immediately. Example: “I’m writing regarding my recent delivery and would like to request a refund for damaged items.”
Body paragraph 1: Describe the problem with detail. Mention what was damaged and when you noticed it.
Body paragraph 2: Explain the impact. Say how the problem affected your plans, time, or costs.
Body paragraph 3: Ask for action. Request the refund, clarification, or another concrete next step.
Close: End politely and invite a reply.
#Timing plan for Task 1
Many test-takers lose control of the email because they start drafting too early. A better pattern is:
- 2 minutes to read and mark the prompt
- 4 minutes to plan the purpose and the three body paragraphs
- 18 minutes to draft
- 3 minutes to proofread
That short planning stage usually saves more time than it costs.
#Final checklist before you submit
- Did I make the purpose clear near the beginning?
- Did I answer all the required bullet points in order?
- Did each body paragraph include at least one concrete detail?
- Is the tone respectful and appropriate for the recipient?
- Did I end with a clear request, suggestion, or next step?
- Is the response roughly within the expected word range?
#Frequently asked questions
Can I memorize this whole email template?
Do I need a subject line in Task 1?
How formal should the email sound?
What if I cannot think of strong ideas?
#Final takeaway
For Task 1, the safest high-scoring habit is not fancy language. It is visible structure.
If you remember one thing, remember this:
purpose first, one paragraph per task, polite action at the end.