CELPIP Writing Task 1 Samples with Answers

Four original email prompts with complete answers: a complaint, a request, an apology and a suggestion. Each one shows how the email covers the three points in the prompt. These are teaching samples, not official or scored answers.

How to write your own Task 1 email

CELPIP Writing Task 1 becomes easier when you treat the email as a practical communication problem. Identify who will read it, what that person needs to understand, and what you want to happen next. Then build a short message that covers every instruction, explains relevant details, and uses an appropriate tone. A useful response does more than announce a topic: it helps the recipient act.

The task is part of the CELPIP Writing component, alongside a survey response. The official format page lists 53 minutes for Writing. The supplied seventh-edition Reading and Writing Study Guide allocates 27 minutes to the email and asks for approximately 150–200 words. Always follow the instructions and timer shown in your test. The length of this preparation guide is not the length you should write in the exam. Official CELPIP format

• Start with the communication problem
• Convert each instruction into a job for a paragraph
• Use an opening that gets to the point
• Develop the problem through cause and consequence
• Make the request specific enough to answer
• Match the tone to the relationship and purpose
• Organize for a reader who has limited time
• Use the word range as a content budget
• Edit in an order that protects the message
• Three common drafts and how to repair them
• Practise a full cycle, not just another first draft
• A short revision workshop
• Frequently asked questions
• Sources and further reading

Start with the communication problem

Before choosing vocabulary, describe the task in one plain sentence. For example: “I need to tell the community centre why a booking change creates a problem and ask for a workable alternative.” That sentence gives the response a destination. Without it, candidates often spend half the email explaining background and reach the actual request only in the final line.

Next identify the relationship. A message to a friend can assume shared knowledge and use conversational language. A message to a manager should explain unfamiliar details and make the requested action easy to locate. Formality is not a competition to use the longest expressions. “Could you confirm the revised start time?” is both polite and precise. “I humbly solicit your esteemed clarification” distracts from the same request.

Finally, identify the practical constraint. Perhaps the replacement class conflicts with work, the delivery arrived after an event, or a volunteer assignment requires equipment you cannot provide. A constraint connects the facts to the purpose. It explains why the recipient should care about a detail and why your proposed solution is reasonable.

Convert each instruction into a job for a paragraph

Read the prompt twice, once for the overall situation and once for the required content. Write a short planning label beside each requirement. If the prompt asks you to describe an event, explain a problem, and suggest a solution, your labels might be “booking,” “schedule conflict,” and “alternative.” These are content obligations, not phrases that must appear verbatim in your answer.

One paragraph does not always have to correspond to one bullet. Two closely connected requirements can share a paragraph if the relationship remains clear. However, mapping requirements to paragraphs is useful during practice because it reveals omissions quickly. An elegant paragraph about your disappointment cannot replace an instruction asking you to explain what happened.

Do not interpret a broad prompt as permission to include every imaginable fact. Choose details that make the requested communication believable. For a booking problem, the relevant information could be the type of class, the original evening, the revised evening, and your availability. A long description of your hobbies would consume words without helping the centre resolve the issue.

After planning, point to where each requirement will be answered. If one has no place, repair the outline before drafting. This takes less effort than adding an unrelated sentence to the end of an already crowded response.

Use an opening that gets to the point

A productive opening usually combines context and purpose. “I registered for the Thursday pottery course, and I am writing because the new Saturday schedule conflicts with my work.” The reader learns what the email concerns and why it exists. There is no need for a long statement about the importance of pottery or the reputation of the organization.

When writing to someone you know, the context can be lighter. “Thanks for offering to organize the neighbourhood cleanup. I would like to help, but I need to change the assignment we discussed.” This opening acknowledges the relationship while still moving toward the task. The friendly first sentence supports the communication rather than delaying it.

Avoid openings that fit almost any prompt. “I am writing this email to bring an important matter to your attention” is grammatically possible, but the reader still does not know the matter. Replace general importance with specific information. When you revise, test whether the opening could belong to twenty unrelated emails. If it could, make it more informative.

Develop the problem through cause and consequence

Useful detail follows a chain: what happened, why it matters, and what would address it. Suppose a study room reservation was moved from a quiet room to an open lobby. Merely saying that the change is inconvenient leaves the recipient guessing. Explain that the session includes recorded interviews and that background conversations would interfere with the recording. Now the requested quiet room has an obvious purpose.

Keep the consequence proportional to the situation. You can describe disappointment or disruption without claiming that a minor scheduling error has destroyed your future. Exaggeration may make the message less credible and can push the tone away from practical problem solving. The strongest detail is often ordinary: a missed connection, an unavailable team member, or additional travel that the original plan avoided.

You can invent reasonable supporting details when an original practice prompt leaves them open, but maintain internal consistency. If the group is available only on Tuesday, do not request a Wednesday replacement later. Keep a tiny fact list beside your outline during practice. This prevents the drafting process from changing the situation halfway through the email.

Make the request specific enough to answer

A weak request asks the reader to “do something” or “solve this problem as soon as possible.” The writer may know what a solution looks like, but the recipient does not. A stronger request names an action: confirm a new date, arrange a replacement, explain a charge, reserve a room, or provide the missing information.

When several outcomes would work, state a preference and an alternative. “I would prefer a replacement before Friday. If that is unavailable, please let me know whether I can collect the item from another branch.” This is easier to process than listing five possibilities of equal importance. The hierarchy helps the reader understand what to try first.

Be careful with deadlines. Give a reason when timing affects the situation: “Please reply by Tuesday so we can finalize the volunteer schedule.” This is more constructive than an unexplained demand for an immediate answer. A reasonable deadline creates a practical link between the recipient's reply and your next step.

Before finishing the paragraph, imagine receiving the email. Could you answer it with a clear confirmation, explanation, or choice? If you would need to ask what the sender actually wants, the request still needs work.

Match the tone to the relationship and purpose

Tone is created by the whole response, not just the greeting. “Dear Manager” cannot make threats sound polite, and “Hi Alex” cannot make an unnecessarily distant message feel friendly. Consider the relationship, the problem's seriousness, and the degree of cooperation required. Most practical emails benefit from a calm explanation followed by a clear request.

Compare “You changed everything without caring about us” with “The revised schedule conflicts with the availability we provided.” The second sentence focuses on a verifiable issue. It leaves room for the recipient to help without first defending their character. This is particularly useful for complaints, where the goal is usually a resolution.

For a friendly invitation, the same neutral business style might sound cold. “It would be great to see you at the picnic” fits a friend better than “Your attendance would be appreciated.” For a workplace request, “Could you review the attached schedule?” is clearer than an extremely casual “Can you check this thing?” Adapt the language to the actual reader.

If tone is your main difficulty, use the separate CELPIP email tone guide for detailed comparisons. Keep this task's central priority in view: the right tone must carry the required information.

Organize for a reader who has limited time

Paragraph breaks tell the reader how to process the message. An opening paragraph can establish the context. A middle paragraph can explain the issue and its effect. A final paragraph can state the solution or next action. This familiar movement is useful because the reader encounters information in the order needed to understand the request.

Avoid a single block that hides a change in purpose. If the email moves from describing a delivery problem to requesting a refund, a new paragraph may help. Equally, avoid breaking every sentence into a separate paragraph. That can make a short email feel disconnected and prevent related ideas from developing together.

Connections also matter within paragraphs. “The room is beside the entrance. It has blue chairs. We need a quiet environment” includes one irrelevant detail and leaves the main relationship implicit. “Because the room is beside the busy entrance, it would be difficult to record clear interviews” makes the relationship explicit. Paragraph organization begins with choosing related ideas, not merely adding transition words.

Use the word range as a content budget

The approximate response range encourages selection. You need enough words to fulfill the task, but each sentence should contribute. In practice, allocate space according to the prompt rather than forcing equal paragraph lengths. A simple context may need one sentence, while a problem with two consequences may deserve three. Reserve room for the requested action.

When your draft is too short, do not add a generic sentence about how important the issue is. Look for missing explanation. Have you said why the change causes difficulty? Have you given a concrete example? Have you stated what the recipient can do? Expanding those elements improves the email while adding words for a reason.

When the draft is too long, remove repeated ideas first. “This is inconvenient and creates a great deal of inconvenience for me” says the same thing twice. Next remove background the reader does not need. Finally, simplify unnecessarily long phrases: “at this point in time” usually becomes “now.” Preserve task coverage while cutting excess.

Edit in an order that protects the message

Start revision with task fulfillment. A perfectly spelled email can still omit the requested suggestion. Check the prompt against the response, one requirement at a time. Then check the internal facts: dates, locations, names, quantities, and availability. These details are easy to change accidentally when you revise under pressure.

Next read for meaning. Ask whether pronouns have clear references and whether cause and effect are understandable. “They said it was unavailable, which was inconvenient” may be clear in context, but it can also leave the reader unsure whether “it” means the room, the equipment, or the date. Repeat a specific noun when necessary.

Only then focus on sentence-level editing. Check verb forms, subject–verb agreement, singular and plural nouns, articles, and punctuation. Pay particular attention to long sentences containing several clauses. Splitting one overloaded sentence may solve more problems than replacing several individual words.

Finish with the recipient's perspective. Is the request clear? Is the tone suitable? Can the reader respond without reconstructing the story? CELPIP publishes Writing assessment dimensions covering Content/Coherence, Vocabulary, Readability, and Task Fulfillment; use those as broad review lenses rather than inventing a score from a checklist. Official performance standards

Three common drafts and how to repair them

The first common problem is a background-heavy email. The writer explains how they discovered the course, why they like the subject, and who encouraged them to register. The actual scheduling conflict appears near the end. Repair this by moving the conflict into the opening and keeping only background that affects the solution. The recipient needs the booking and problem, not the writer's entire history.

The second is a list of unsupported complaints. “The room is bad, the arrangement is poor, and the service is disappointing” expresses evaluation without evidence. Replace each broad judgment with a relevant fact. For example, “The lounge has no screen, so we cannot show the training presentation.” The revised sentence is stronger because it connects an observable condition to the requested use.

The third is a polite but incomplete request. The writer says “I would appreciate your assistance” but never specifies the assistance. Keep the courtesy, then add the action: “Could you reserve an enclosed room for the same evening?” Politeness and clarity are compatible. You do not need to choose between sounding respectful and telling the recipient what would help.

Practise a full cycle, not just another first draft

For your next practice session, select a new email situation and write a three-label plan. Draft once under a realistic timer, then save the original. Review task coverage before grammar, and make a revised version. Place the drafts side by side and explain three changes in terms of the reader's needs. This turns revision into a skill you can repeat.

On a later day, use a different situation with the same communication demand. If you practised requesting a booking change, write a request to change a volunteer assignment. Keep the planning method but replace the facts, reasons, and language. If the new answer simply reproduces the old sentences with different nouns, push further toward a response that fits the new recipient.

Finally, test transfer without your notes. The objective is not to memorize an excellent workshop email. It is to recognize a new problem, select relevant details, organize the explanation, and make a reasonable request independently. That is the practical ability Task 1 gives you an opportunity to demonstrate.

A short revision workshop

Consider this original draft excerpt: “I booked your room last week and it was very good, but now you changed it and this is not acceptable. We need it for our activity, which is important. Please help me soon.” The reader can identify dissatisfaction but cannot identify a useful remedy. The pronoun “it” shifts between the booking and the room, while “activity” provides too little information to explain the requirement.

Begin by replacing vague references: “I reserved the Cedar Room for a volunteer training session.” Next replace the broad negative judgment with the exact difficulty: “The replacement lounge is beside the entrance, where arriving visitors may interrupt the interviews.” Finally, name the action: “Could you offer another enclosed room for Thursday evening?” These revisions improve content, organization, and clarity at the same time.

Now test whether each added detail earns its place. The room name helps identify the reservation. The interviews explain the need for quiet. Thursday evening tells the coordinator when to search for space. None of those details exists simply to make the vocabulary look advanced. They are useful because the recipient can act on them.

For your own exercise, write a similarly vague three-sentence email about a late equipment delivery. Then revise it by adding the original delivery arrangement, the specific consequence of the delay, and one reasonable request. Keep both versions. Underline the words that changed the reader's understanding and circle any words that merely made the sentence longer.

This distinction matters when you are editing quickly. Replacing “help” with “assistance” may change the register slightly, but it will not fix a missing request. Adding the required delivery date may fix the communication immediately. Prioritize revisions that change what the recipient knows or can do, then polish the remaining language if time permits.

Frequently asked questions

Should I memorize a complete email?

Memorize useful functions rather than a complete response. Knowing how to make a polite request or explain a consequence can help you begin. A memorized email may fail when the recipient, purpose, or required details change. Practise generating the content from each prompt and use familiar language only when it fits.

Is formal language always better?

No. The appropriate level of formality depends on the reader and situation. A friend, colleague, coordinator, and customer service manager may require different wording. Clear, natural, respectful English is more useful than ceremonial expressions that obscure an ordinary request. Read the relationship cues before deciding how to sound.

How much detail should I invent?

Use only the supporting details needed to make your practice response complete and coherent, while respecting every fact supplied by the prompt. One date or concrete consequence can clarify a situation. A complicated invented backstory can introduce contradictions and consume the word budget. Keep the recipient's decision at the centre.

Can an example response guarantee a particular score?

No. Examples illustrate choices in organization and language. They are not official ratings, and copying them does not demonstrate that you can perform on a different prompt. Evaluate what a sample accomplishes, practise those skills independently, and consult official standards for the assessment framework.

Sources and further reading

• Supplied CELPIP Study Guide: Reading and Writing, seventh edition, Writing overview and Task 1 sections.
• CELPIP test format.
• CELPIP Writing practice guidance.
• CELPIP performance standards.
• Continue with writing idea development and the grammar editing checklist.