Speaking

CELPIP Speaking Task 2: Tell a Focused Personal Story

Sep 13, 2026

CELPIP Speaking Task 2 asks you to describe a personal experience clearly enough for a listener to follow what happened and why it mattered. Choose one manageable event, establish the situation briefly, explain the important actions, and finish with a result or reflection. You need a coherent story, not an extraordinary life experience.

The supplied official Listening and Speaking Study Guide gives Task 2 thirty seconds of preparation and sixty seconds of recording time. Follow the actual on-screen instructions. The official test format identifies this task as Talking about a Personal Experience. The original prompts and responses in this article are teaching examples, not authentic test questions or officially scored answers.

Many learners lose time searching for a perfect memory. Others begin with so much background that the main event arrives just before recording ends. The solution is to make story selection and story structure separate skills. Learn how to recognize a usable event quickly, then practise shaping that event for a short spoken response.

Choose an event that contains a change

A useful story has a beginning situation and something that changes. You expected one thing and experienced another. You faced a small problem and responded. Someone did something that affected you. This change gives the listener a reason to follow the events and makes the ending easier to explain.

Suppose the prompt asks about a time you learned a useful skill. “I learned to cook because cooking is important” describes a topic. “I had to prepare dinner when my roommate was away, and my first attempt went wrong” creates an event. The second version contains a situation, a challenge, and room for a result.

The event does not need to be dramatic. Learning to repair a bicycle tyre, helping a neighbour complete a form, or finding an unfamiliar classroom can produce a clear response. Everyday events are often easier to tell because the objects, actions, and consequences are familiar. You can spend your attention on communication instead of technical vocabulary.

Choose a story with a limited cast. If the listener must remember six names and several family relationships, your short answer becomes difficult to follow. One or two other people are usually enough for practice. Identify each person by a useful role, such as “my supervisor” or “a classmate,” unless a name makes the narrative easier.

The official study guide allows a realistic imagined experience when remembering a real one is difficult. That is permission to construct a coherent answer, not a reason to invent elaborate adventures. Keep the details ordinary and consistent so that you can maintain the story while speaking. The skill being demonstrated is understandable narration.

Read the whole prompt before selecting the memory

A personal-experience prompt may include more than a topic. It might ask who was involved, what you did, why the event was memorable, or how you felt afterward. A story can fit the general theme while missing a specific requested element. Check those obligations before committing to an event.

For example, “Talk about a time someone helped you solve a problem” is different from “Talk about a time you helped someone solve a problem.” The same workplace setting could support both, but the roles change. A response that focuses on your own clever solution may fail to answer the first version properly.

Use a brief mental check: event, role, required ending. If the prompt concerns receiving advice, decide what the advice was and how it affected your action. If it concerns a surprising experience, identify the surprise. If it concerns a decision, make the alternatives and the final choice audible.

Do not try to incorporate every memory associated with the subject. A prompt about a journey does not require your travel history. Select one journey and one significant moment within it. Narrowing the scale allows enough space for explanation and prevents an answer from becoming a list of places you have visited.

When two stories seem equally suitable, choose the one you can explain with the language you already control. An ordinary event told clearly is more useful than an impressive event that requires constant searching for words. During preparation, communicative manageability is a reasonable selection criterion.

Build a four-part narrative path

A practical structure is setting, turning point, response, and outcome. The setting identifies when and where the event happened. The turning point introduces the problem, surprise, or decision. Your response explains what you or another person did. The outcome shows what changed and, when relevant, why the experience stayed with you.

This is a planning aid rather than a required test formula. Some stories involve several small actions rather than one obvious problem. You can still use the same questions: Where was I? What made the event worth describing? What happened next? What was the result? These questions encourage movement instead of background accumulation.

For a story about learning to cook, the notes might be “last winter / roommate away / soup too salty / added vegetables / confidence.” Each note cues a piece of the narrative. You do not need to write the sentences you will say. In fact, writing the whole opening may leave too little preparation time for the ending.

Aim to establish the setting in one or two sentences. “Last winter, I decided to cook dinner for my roommate after she had worked a long shift” gives time, purpose, and a relationship. The listener does not also need the exact date, the apartment's location, or a detailed account of how you first met.

The outcome deserves deliberate planning. Without it, a story may stop after the last action and feel unfinished. “The meal was simple, but it was the first dinner I had made without following every instruction on a screen” explains significance. A conclusion need not contain a moral; it can simply clarify the result.

Original worked story: a presentation problem

Practice prompt: describe a time when you had to change a plan unexpectedly. Explain what happened and how you handled it. The following original response illustrates a compact narrative. Its word count is not an official speaking target; record it at a comfortable pace and use your own details when practising.

A few months ago, I was preparing to give a short presentation at work. I had made a set of slides showing how our team could organize incoming requests, and I expected to use the meeting-room screen.

Just before we started, the screen stopped working. At first, I was worried because most of my examples were in the slides. Then I remembered that the main idea was actually quite simple.

I drew three columns on a whiteboard and asked my colleagues to suggest real requests we had received that week. We placed each example in the appropriate column and discussed who should handle it.

The meeting became more interactive than I had planned. Afterward, my supervisor asked me to keep the whiteboard activity in future sessions. That experience taught me to prepare a simple backup and focus on the message rather than the equipment.

The first paragraph establishes the intended plan. The broken screen creates the change. The whiteboard activity provides a concrete response, and the supervisor's request demonstrates the result. The reflection is connected to the actual event rather than a generic statement about never giving up.

Notice that the answer does not explain every slide or name every colleague. Those details are unnecessary for this prompt. It includes enough context to make the response understandable, then spends most of its space on the change and the action. That distribution is a useful model for your own recordings.

Keep the timeline easy to follow

Past simple is a useful foundation for completed narrative events: “I arrived,” “the screen stopped,” and “we discussed the problem.” Use past continuous when a background action was in progress: “I was setting up the room when the screen stopped working.” This distinction helps the listener understand what was already happening and what interrupted it.

Past perfect can clarify an earlier event when the order might otherwise be confusing. “I had saved a copy on my laptop, so I could still check my notes” places the saving before the equipment problem. You do not need past perfect in every sentence. Once the sequence is clear, repeated use can sound unnecessarily heavy.

Be careful when moving from the story to a present reflection. “I learned that preparation matters” is natural: the learning occurred in the past, and the general principle remains current. A present-tense ending is not automatically an error. The question is whether the tense change communicates a meaningful shift in time.

An unclear version might say: “Yesterday I go to the office, and my manager is asking me to help, so I helped him and we finish the report.” Repair the main event sequence first: “Yesterday I went to the office, and my manager asked me to help. We worked together and finished the report.” You can add more complexity after the timeline is stable.

Time expressions can do useful work without appearing in every sentence. “At first,” “a few minutes later,” and “by the end of the afternoon” mark changes the listener needs. Avoid mechanically starting every sentence with “then.” A clear causal relationship often makes the order obvious without an additional time marker.

Explain causes instead of merely listing events

A sequence is not yet a satisfying story if the listener cannot understand why the actions occurred. “I called my neighbour. We went downstairs. I bought a tool. We fixed it” gives events but hides their connections. The response becomes more coherent when the reasons are explicit.

You might say: “I called my neighbour because he repairs bicycles in his spare time. He checked the wheel and realized I needed a new inner tube, so we walked to the nearby shop. After replacing it, he showed me how to check the tyre for sharp objects.” The event sequence now communicates learning and cooperation.

Cause-and-effect language also helps you reduce unnecessary detail. Instead of describing a long conversation, summarize its effect: “Her explanation helped me realize that I had misunderstood the deadline.” This sentence moves the story forward while preserving the important information. The listener usually needs the consequence more than a transcript of every exchange.

When including a feeling, link it to a reason or change. “I was nervous” is understandable but broad. “I was nervous because I had never spoken to that many colleagues before” clarifies the initial pressure. Later, “Once they began asking questions, I felt more comfortable” shows how the emotion developed.

Do not add feelings solely to make the story sound dramatic. A quiet response such as relief, satisfaction, or mild embarrassment can fit an everyday event. The emotion should help the listener interpret the experience rather than compete with the main action for attention.

Select details with a purpose

Specific details make a story memorable when they contribute to understanding. A wet notebook can explain why you lost your directions. A handwritten thank-you note can show why a routine act of help mattered. A precise detail often communicates more than several adjectives such as wonderful, amazing, and unforgettable.

Suppose you describe a neighbour helping you move a heavy table. “He was very nice and helpful” evaluates the neighbour. “He arrived with a small trolley and stayed until we had moved the table safely upstairs” shows the behaviour behind that evaluation. The listener can understand your appreciation without repeated praise.

Use a detail test during revision. Ask whether the detail explains the setting, action, obstacle, result, or significance. If it does none of those jobs, consider removing it. The colour of a jacket may be irrelevant in a story about missing a deadline but essential in a story about recognizing someone in a crowd.

Avoid exact dates and numbers unless they matter. “Last summer” usually works as well as a full calendar date. “About twenty people” may be easier to say than an oddly precise attendance figure. Unnecessary precision can consume planning attention and make an imagined story harder to keep consistent.

Details should also agree with one another. If you say the event happened during your first week at a job, do not later refer to a system you had been managing there for years. Consistency matters because contradictions force the listener to stop and reinterpret the story.

Repair stories that run out of time

A common unfinished story spends most of its time explaining life before the event. The speaker describes moving to a city, searching for work, meeting colleagues, and learning office routines before reaching the memorable meeting. The repair is not necessarily faster speech. It is choosing the true starting point.

Begin near the important change: “During my first team meeting at a new job, I misunderstood a question.” That sentence provides enough background to proceed. You can add a missing detail later if the listener needs it. Starting close to the action protects time for the response and outcome.

Another time problem is repeating a point in slightly different words. “I was really nervous, and I felt worried, and I didn't feel confident” communicates one emotional state three times. Keep the clearest version and use the saved time to describe what you did despite that feeling.

If you realize while speaking that the story is becoming too long, summarize the middle. “After a few unsuccessful attempts, we finally found a solution” can compress minor actions, provided you explain the solution itself. You do not have to narrate every attempt in equal detail. The prompt determines which moments deserve attention.

Practise a short ending that can close the story from several points: result plus significance. For example, “We completed the task that afternoon, and I became much more comfortable asking for help.” This is more useful than an unrelated closing phrase because it resolves the specific event you have described.

Build a memory bank without memorizing scripts

A memory bank is a small collection of events you understand well. It can reduce the pressure of recalling a story, but it should not become a set of fixed answers forced onto unrelated prompts. Record each event as a few notes: situation, people, change, action, and result.

Useful categories include learning something, receiving help, solving a problem, making a decision, attending an event, and experiencing a surprise. One event may fit more than one category, but the emphasis must change. A volunteering experience could illustrate teamwork or an unexpected challenge depending on which part you describe.

For example, a community garden event could become a story about meeting someone helpful. In that version, focus on the conversation and assistance. If the prompt asks about adapting to a problem, focus on the missing supplies and your group's response. Reusing the setting is reasonable; delivering the same story regardless of the question is not.

Write the notes in language you would actually say. A bank filled with literary phrases may be difficult to retrieve naturally. You need accessible verbs such as noticed, offered, checked, arranged, and realized. These words allow you to narrate many everyday situations precisely without learning an artificial performance voice.

Refresh the bank with ordinary recent experiences. At the end of a day, identify one small event that had a beginning, change, and result. Describe it aloud in a minute. This connects practice to real observation and prevents preparation from depending entirely on a handful of rehearsed memories.

Use recording review to find the actual weakness

The official Speaking dimensions are Content/Coherence, Vocabulary, Listenability, and Task Fulfillment, as explained in the official results information. For a narrative, review those dimensions through practical questions. Could someone reconstruct the event? Were actions described precisely? Was the speech easy to follow? Did the story answer the exact prompt?

Listen first without reading a transcript. Note the moment when you understand what the story is about. If that moment arrives late, the opening likely needs revision. Then write a one-sentence summary of what happened. If you cannot summarize it easily, the response may contain too many competing events.

Next, transcribe a short section where the timeline becomes confusing. Mark the verbs and time expressions. Correct only the tense choices needed to make the sequence clear, then say the section again. This targeted repair is more manageable than trying to perfect every sentence in one session.

The official speaking podcast recommends recording and reviewing practice. Use a second recording to test a specific change, such as a shorter setting or a clearer outcome. Compare the two versions on that feature rather than deciding vaguely that one sounds better.

If another person listens, ask them to identify the turning point and result. Their answer provides useful evidence. They do not need to estimate a CELPIP level. A listener who misses your main action can help you locate a communication problem that you overlooked because you already knew the story.

Original practice prompts and transfer exercises

Try describing a time when someone explained a difficult process clearly. Choose the process, identify what confused you, and explain what the other person did differently. Your outcome should show the change in understanding rather than simply state that the person was helpful.

Next, describe a time when you misplaced something important. Keep the search brief and focus on the decision or action that resolved the situation. If the item was never found, that can still support a coherent ending: explain the consequence and what you changed afterward.

For a third prompt, describe a small event that made you feel welcome in a new place. The event might involve a colleague including you in a conversation or a neighbour explaining a local routine. Show the welcoming action concretely. Avoid turning the answer into a general description of an entire city.

After completing one prompt, change the requested emphasis. Ask why the experience surprised you, what you learned, or how another person contributed. Retell the event with a different selection of details. This exercise develops adaptability and reveals whether you understand the story's structure beyond a memorized sequence of sentences.

Frequently asked questions

Does the experience have to be true?

The supplied official guide permits a realistic imagined experience when needed. Choose something plausible that you can describe consistently. A simple invented event is easier to manage than a complicated story with many people, locations, and technical details. Do not spend your preparation time trying to create an impressive adventure.

Should I use only past tense?

Most completed story events will use past forms, but meaningful shifts are possible. You may describe a present habit or a general lesson at the end. The goal is a clear timeline, not an absolute ban on present tense. Check whether each shift reflects a real change in time or meaning.

What if I cannot remember the right word?

Describe the object or action using words you know, then continue the narrative. “The small cart we used to move the boxes” can replace a forgotten equipment name. A clear explanation protects the story's flow. Avoid abandoning the entire sentence while searching for one exact term.

Do I need a dramatic ending?

No. The listener needs to understand the result and the experience's relevance. A modest outcome, such as becoming more confident with a task or appreciating a colleague's help, can complete the narrative. Match the scale of the ending to the event and the wording of the prompt.

Sources and further reading