English Can-Do Descriptors — B1 Level (CEFR)

Concept Explanation

At B1 level, you should be able to follow the main thread of a conversation on familiar topics — even if you don't catch every word or detail:

• Familiar topics: travel, work, family, hobbies — conversations about these subjects use vocabulary and structures you already know, even when speakers talk at a natural pace.
• Following main points despite missing details: the goal isn't perfect comprehension — it's understanding "what's being discussed" and "what people think/feel about it," even if specific names, numbers, or minor details slip by.
• Inferring meaning from context: when you hear an unfamiliar word, use the surrounding words, tone, and topic to guess its meaning — for example, if someone says "The flight was delayed, so we had to wait for ages at the gate," you can guess "ages" means "a long time" even without knowing the word.

This is a shift from earlier levels: instead of needing to understand 100% of short, simple exchanges, you're now training yourself to extract the overall meaning from longer, more natural conversations.

---

Why It Matters

This skill is the foundation for real-world listening — natural conversations are rarely simple or slow:

• Social integration: following group conversations, even when multiple people talk and topics shift naturally.
• Confidence building: realizing you understood "enough" — even with gaps — reduces the anxiety of "not understanding everything."
• Vocabulary growth: inferring meaning from context is one of the most efficient ways to learn new words naturally, without needing a dictionary every time.

Without this skill, learners often get "stuck" on individual unknown words and lose the thread of the whole conversation — this topic trains you to keep going.

---

Additional Examples

1. "We were thinking of going to Portugal this summer, but flights are so expensive right now." — Following the main idea (travel plans + a problem) even if "flights are so expensive" includes unfamiliar phrasing.
2. "He's been really stressed at work lately — they're understaffed and he's covering two roles." — Inferring "understaffed" means "not enough staff" from context.
3. "My sister just got a new puppy — it's adorable but it's chewing everything!" — Guessing "chewing" from context (puppies + "everything" + a slightly exasperated tone).
4. "I'm into hiking these days — I go most weekends if the weather's good." — Understanding "I'm into" means "I like/I'm interested in" from context.
5. "Honestly, I just need a proper break — I haven't had a holiday in over a year." — Following the speaker's feeling (needing rest) even with the phrase "a proper break".
6. "The traffic was terrible, so I ended up being late for the meeting again." — Following cause and effect (traffic → late) as the main thread.

---

Common Mistakes

1. Stopping to "translate" every unfamiliar word mentally This breaks the flow and causes you to miss what comes next. Instead, make a quick guess based on context and keep listening — you can often confirm or correct your guess later.

2. Assuming you must understand 100% to participate You can often respond appropriately to the main idea even with gaps: "That sounds frustrating" is a valid response even if you missed exactly why something was frustrating.

3. Ignoring tone and intonation as clues Tone often carries as much meaning as words — a frustrated tone, a laugh, or a pause can tell you how to interpret a sentence even when specific words are unclear.

4. Giving up too early on a conversation If you lose the thread, it's fine to ask "Sorry, what were you saying?" or simply listen for the next natural topic shift — conversations often "reset" with a new sentence or question.

Concept Explanation

Following a simple podcast or video involves recognizing both content and structure:

• Types of content at this level: summarized news and simple interviews — resources like "BBC Learning English," "6 Minute English," or travel vlogs are designed to be clear and well-paced for learners.
• Recognizing the structure of spoken discourse: most short podcasts/videos follow a predictable shape — introduction (what the topic is) → key points (the main information, often 2-4 points) → conclusion (a summary or final thought). Within key points, you'll often hear an example followed by an explanation, or vice versa.

Recognizing this structure helps you predict what's coming next — if you hear "For example..." you know a specific illustration is coming; if you hear "So, to sum up..." you know a conclusion is starting.

---

Why It Matters

Podcasts and videos are one of the most accessible and abundant sources of natural English input — and recognizing structure makes them much easier to follow:

• Independent learning: being able to follow podcasts/videos opens up a huge amount of free, engaging listening practice.
• Predicting content: recognizing signal phrases ("first," "for example," "in conclusion") helps you anticipate what type of information is coming.
• Note-taking and summarizing: understanding structure (intro/key points/conclusion) makes it easier to take notes or summarize what you heard — a useful skill for studies or work.

This topic also bridges listening comprehension with awareness of how spoken English is organized, which will help with more complex listening at higher levels.

---

Additional Examples

1. "Today we're talking about..." — A typical introduction phrase signaling the topic.
2. "There are three main reasons for this. First..." — Signaling that key points are about to follow, in a numbered structure.
3. "For example, last year the city introduced..." — Signaling a specific example to illustrate a point.
4. "This is interesting because..." — Signaling an explanation of why something matters.
5. "So, to sum up..." / "In conclusion..." — Signaling that the speaker is moving to a conclusion.
6. "Thanks for listening — see you next time!" — A typical closing phrase for a podcast episode.

---

Common Mistakes

1. Treating every podcast/video the same regardless of level Choose content designed for learners (like "6 Minute English") before moving to native-level podcasts — the pacing and vocabulary are calibrated to be more accessible.

2. Listening only once and expecting full understanding Listening to the same short episode 2-3 times — first for the general idea, then for more detail — is a very effective strategy, and is normal practice even for advanced learners.

3. Ignoring visual/written support Many learner podcasts provide transcripts or show notes — using these alongside listening (not instead of it) reinforces both reading and listening skills together.

4. Not using structure words as listening "anchors" Missing words like "first," "however," "for example," and "finally" means missing the roadmap of the talk — these words are worth specifically training your ear to catch.

Concept Explanation

Reading simple newspaper articles introduces two specific challenges:

• Human interest and local news topics: stories about people, local events, and travel experiences tend to use everyday vocabulary and a narrative style — easier to follow than political or technical articles.
• Headline vocabulary: newspaper headlines use a special, condensed style that often omits words (especially "to be" and articles) and uses short, punchy verbs. For example: "PM to meet EU leaders" actually means "The Prime Minister is going to meet EU leaders" — the headline drops "The," "is," and "going."

Headlines also often use present tense for past events ("Storm hits coast" = a storm hit the coast recently) and infinitives for future events ("PM to meet..." = the PM will/is going to meet...).

---

Why It Matters

Newspapers (and news websites) are everywhere, and being able to read at least the headlines and simple articles opens up a huge amount of real-world reading material:

• Staying informed: reading news in English exposes you to current vocabulary and topics in a natural way.
• Headline literacy: once you understand the "code" of headlines (dropped words, infinitives for future, present tense for past), they become much less confusing.
• Building reading stamina: human interest articles are usually shorter and more narrative than hard news — a good stepping stone toward longer texts.

---

Additional Examples

1. "PM to meet EU leaders" = "The Prime Minister is going to meet EU leaders." — Infinitive "to meet" = future.
2. "Storm hits coast, thousands without power" = "A storm hit the coast, and thousands of people are without power." — Present tense "hits" describing a past event.
3. "Local hero saves family from fire" — Human interest headline; "saves" = past event reported in present tense.
4. "New park to open next month" = "A new park is going to open next month." — Infinitive "to open" = future plan.
5. "Tourists flock to city for festival" — "Flock" (informal/journalistic for "go in large numbers") describing a current trend.
6. "Council plans new bus routes" — "Plans" (present tense) describing an ongoing/recent decision.

---

Common Mistakes

1. Reading headlines literally, word-for-word "PM to meet EU leaders" read literally seems to be missing a verb — remembering that headlines drop "is/are/will" before infinitives ("to meet" = "is going to meet" or "will meet") resolves this.

2. Confusing present tense headlines with the present tense in normal sentences "Storm hits coast" doesn't mean the storm is hitting the coast right now (necessarily) — in headlines, present tense often reports something that already happened, for immediacy/impact.

3. Getting stuck on unfamiliar names/places in human interest stories Names of people and places aren't usually essential to understanding the main story — focus on what happened, to whom (in general terms), and why it's newsworthy.

4. Avoiding news articles because they "seem too hard" Human interest and local stories are often written in a more accessible, narrative style than political/economic news — they're a good entry point, not just for advanced readers.

Concept Explanation

Understanding instructions and basic manuals involves recognizing imperative structures and sequencing:

• Recipes: typically list ingredients first, then steps using imperative verbs (commands without a subject) — "Mix the flour and eggs. Add milk gradually. Bake for 20 minutes." Each sentence is a direct instruction.
• App/software instructions: often use a specific format showing navigation paths — "Click Settings → Account → Change Password." The arrow (→) indicates a sequence of clicks/steps, each one leading to the next screen or menu.

Both types of instructions rely heavily on imperative verbs (mix, add, click, select, press, open) — these don't need a subject ("you" is implied) and are the standard way to give instructions in English.

---

Why It Matters

Instructions and manuals are everywhere in daily life — cooking, using technology, assembling furniture, following safety guidelines:

• Cooking: following a recipe in English opens up a huge range of content (cooking videos, blogs, recipe books).
• Technology: most apps, websites, and devices have instructions or help sections in English — understanding these is often necessary for troubleshooting.
• Independence: being able to follow instructions without needing a translation makes you more self-sufficient in many everyday tasks.

The imperative structure is simple grammatically (no subject, no tense changes) — once you recognize it, these texts become much more approachable than they might first appear.

---

Additional Examples

1. "Mix the flour and eggs. Add milk gradually until you get a smooth batter." — Recipe steps with imperatives + a result clause.
2. "Preheat the oven to 180°C. Bake for 25 minutes." — Two-step instruction with a temperature and a time.
3. "Click Settings → Account → Change Password." — Navigation path using imperatives and arrows.
4. "Insert tab A into slot B, then fold along the dotted line." — Furniture/assembly instructions with sequencing ("then").
5. "Do not use this appliance near water." — Negative imperative for a safety warning.
6. "To reset your password, go to the login page and click 'Forgot password?'" — Instruction with "to + verb" (purpose) + imperative steps.

---

Common Mistakes

1. Looking for a subject in imperative sentences "Mix the flour" doesn't need "you" before it — imperatives in instructions are a complete, correct sentence on their own ("(You) mix the flour").

2. Misreading navigation arrows (→) as something else "Click Settings → Account" means: first click "Settings," then within that, click "Account" — it shows a sequence of menu levels, not a single combined action.

3. Missing negative imperatives "Do not" / "Don't" + verb is just as important as positive instructions — "Do not open" and "Open" are opposite instructions that look similar at a glance; read carefully.

4. Ignoring sequencing words "First," "then," "after that," "finally," "until" — these words establish the order of steps. Skipping or misreading them can mean doing steps in the wrong order (e.g., adding an ingredient too early).

Concept Explanation

Talking about personal experiences combines the present perfect (for life experiences, without a specific time) with the simple past (for specific details) and superlatives (for emphasis):

• Present perfect for life experiences: "I've been to Japan." / "I've never tried sushi." / "Have you ever been abroad?" — this structure (have/has + past participle) is used when the specific time isn't mentioned or important — the focus is on the experience itself, "at some point in your life."
• Past simple for additional details: once you mention a specific time, switch to past simple — "I went there in 2019 and stayed for two weeks." (specific year + duration = past simple, not present perfect).
• Superlatives for emphasis: "It was the most incredible thing I've ever done." — combining a superlative ("the most incredible") with present perfect ("I've ever done") is a common way to emphasize how significant an experience was.

The key pattern: present perfect to introduce an experience ("I've been to..."/"I've never...") → past simple to give details (when, where, how long) once the time becomes specific.

---

Why It Matters

Talking about life experiences — travel, food, activities you have or haven't done — is one of the richest conversation topics, and this present perfect/past simple combination is essential for telling these stories naturally:

• Travel conversations: "Have you ever been to...?" is one of the most common ways to start a conversation about travel experiences.
• Sharing stories naturally: moving from "I've been to Japan" (general experience) to "I went there in 2019" (specific details) mirrors how native speakers naturally tell stories.
• Expressing strong reactions: superlatives + present perfect ("the best meal I've ever had," "the most beautiful place I've ever seen") are a natural way to express enthusiasm.

Mastering the present perfect/past simple switch is one of the clearest markers of B1-level fluency — many learners either overuse one or avoid the present perfect altogether.

---

Additional Examples

1. "I've been to Japan. I went there in 2019 and stayed for two weeks." — Present perfect (experience) → past simple (details).
2. "Have you ever tried Thai food?" → "Yes, I have — I had it for the first time last year." — Present perfect question → past simple detail.
3. "I've never been skiing, but I'd love to try it." — Present perfect (negative experience) + future wish.
4. "It was the most incredible trip I've ever taken." — Superlative + present perfect for emphasis.
5. "She's lived in three different countries — she moved to Canada in 2015." — Present perfect (life summary) → past simple (specific event).
6. "Have you ever met someone famous?" → "Actually, yes — I met a famous actor at the airport last year!" — Present perfect question → past simple story.

---

Common Mistakes

1. Using present perfect with a specific past time "I've been to Japan in 2019." → "I went to Japan in 2019." / "I've been to Japan." (without the date) Once a specific time is mentioned ("in 2019," "last year," "when I was a child"), the present perfect becomes incorrect — switch to simple past.

2. Using simple past for general life experience questions "Did you ever go to Japan?" (less natural for general experience) → "Have you ever been to Japan?" For general life experience (no specific time in mind), present perfect with "ever" is more natural.

3. Confusing "been" and "gone" in the present perfect "He's gone to Japan" (he is currently there, hasn't returned) vs. "He's been to Japan" (he visited at some point and is back). These have different meanings — "been" implies the trip is finished.

4. Forgetting "ever" in questions about experience "Have you been to Thailand?" is fine, but "Have you ever been to Thailand?" is more natural when asking generally about life experience — "ever" emphasizes "at any point in your life".

Concept Explanation

Giving and defending a simple opinion involves three building blocks:

• Expressing an opinion: "I think...," "In my opinion...," "I believe...," "It seems to me that..." — these phrases introduce your viewpoint and signal that what follows is a personal opinion, not a fact.
• Showing agreement and disagreement: "I agree." (full agreement) / "I'm not sure about that." (polite doubt/disagreement) / "I see your point, but..." (acknowledging the other view before disagreeing — a softer, more diplomatic way to disagree).
• Adding a reason: "...because it's more practical." / "...since it helps people." — opinions are much stronger and more convincing when supported by a reason, introduced with "because" or "since".

The phrase "I see your point, but..." is a particularly useful diplomatic structure — it acknowledges the other person's view (showing you listened) before introducing your own, different opinion.

---

Why It Matters

Giving and discussing opinions — politely and with reasons — is central to real conversations, debates, and discussions:

• Everyday discussions: "What do you think about...?" comes up constantly, whether about a movie, a news story, or a decision at work.
• Polite disagreement: "I see your point, but..." allows you to disagree without being rude — an important social skill in English-speaking cultures, where direct "You're wrong" can sound harsh.
• Persuasion: adding "because/since + reason" makes your opinions more convincing and shows you've thought about the issue.

This topic moves beyond simple factual statements into the realm of discussion and debate — a key step toward more sophisticated conversation.

---

Additional Examples

1. "I think we should walk — it's not far, and it's a nice day." — Opinion + reason.
2. "In my opinion, this is the best option, because it's cheaper and faster." — Formal opinion phrase + two reasons.
3. "I agree with you — that makes a lot of sense." — Agreement + supporting comment.
4. "I'm not sure about that. I think there might be a better way." — Polite disagreement + alternative opinion.
5. "I see your point, but I still think we should consider other options." — Acknowledging + disagreeing.
6. "It seems to me that the new system is more efficient, since it saves time for everyone." — Opinion phrase + reason with "since".

---

Common Mistakes

1. Stating opinions as if they were facts "This is the best restaurant in town." (sounds like an objective fact) → "I think this is the best restaurant in town." / "In my opinion, this is the best restaurant in town." Adding an opinion phrase signals that you're aware this is your personal view, not a universal truth — important for polite discussion.

2. Disagreeing too directly "You're wrong." / "No, that's not true." (can sound confrontational) → "I see your point, but I think..." / "I'm not sure about that — what about...?" Softer disagreement phrases maintain a friendly tone while still expressing a different view.

3. Forgetting to give a reason "I think we should do X." (opinion alone, less convincing) → "I think we should do X, because..." A reason ("because/since...") makes your opinion stronger and shows critical thinking.

4. Confusing "because" and "because of" "I like it because of it's cheap." → "I like it because it's cheap." (because + clause with subject+verb) / "I like it because of the price." (because of + noun phrase) "Because" is followed by a clause (subject + verb); "because of" is followed by a noun.

Concept Explanation

Narrating a story or past event combines the past continuous (for setting the scene) with the simple past (for the main events), connected by narrative connectors:

• Setting the context with past continuous: "It was a sunny day and I was walking home when..." — the past continuous (was/were + -ing) describes an action in progress that forms the background/setting of the story.
• Narrating events with simple past: "Suddenly, I saw a dog. It ran towards me and..." — the simple past describes the main, completed actions that move the story forward — often interrupting the "background" action.
• Narrative connectors: "first," "then," "after that," "suddenly," "finally," "in the end" — these words organize the sequence of events and add drama/pacing to a story.

A classic pattern: past continuous (background) + simple past (interrupting event) — "I was walking home when I saw a dog" — the walking was already happening (continuous/background) when the seeing happened (a single completed event that interrupts).

---

Why It Matters

Telling stories about past events — what happened to you, an interesting experience, even retelling a movie plot — is a core part of natural conversation:

• Sharing experiences: "You won't believe what happened to me yesterday..." is a natural story opener that requires this combination of tenses.
• Engaging listeners: using "suddenly" and other connectors makes stories more vivid and interesting, rather than a flat list of events.
• Structuring narratives: this past continuous + simple past + connectors pattern is the backbone of storytelling in English, used in conversation, writing, and even jokes.

---

Additional Examples

1. "It was a sunny day and I was walking home when I saw a dog. It ran towards me and started barking." — Background (past continuous) + interrupting events (simple past).
2. "First, we checked into the hotel. Then, we went for a walk along the beach." — Sequencing with "first" and "then".
3. "I was watching TV when the phone rang." — Classic past continuous + simple past pattern.
4. "After that, we had dinner at a small restaurant near the hotel." — "After that" connecting to the previous sentence.
5. "Suddenly, the lights went out and everyone started laughing." — "Suddenly" introducing an unexpected event.
6. "In the end, we missed the train, but we found a later one and still made it home." — "In the end" introducing the resolution of the story.

---

Common Mistakes

1. Using simple past for the "background" action "I walked home when I saw a dog." (sounds like two separate, sequential events, losing the "background" effect) → "I was walking home when I saw a dog." (the walking was already in progress)

2. Using past continuous for the main, completed events "I was seeing a dog and it was running towards me." → "I saw a dog and it ran towards me." The main story events (what happened, in sequence) should be in simple past — past continuous is for background/ongoing actions only.

3. Overusing "and then... and then... and then..." Varying connectors ("first," "after that," "suddenly," "finally," "in the end") makes a story far more engaging than repeating "and then" for every event.

4. Forgetting "when" or "while" to connect background and event "I was walking home. I saw a dog." (two separate sentences, less connected) → "I was walking home when I saw a dog." (one connected sentence showing the relationship between the two actions).

Concept Explanation

Making plans and negotiating schedules involves three conversational moves:

• Proposing a plan: "How about Tuesday?" / "What if we meet at 6?" — these are common, informal ways to suggest a time or idea, often phrased as questions to invite the other person's input.
• Accepting or rejecting: "That works for me!" (acceptance, enthusiastic) / "I'm afraid I can't make it then." (polite rejection — "I'm afraid" softens the negative response).
• Suggesting an alternative: "Could we do Thursday instead?" / "What about the morning?" — after rejecting a suggestion, it's polite to offer an alternative rather than just saying no.

Notice how "How about...?" and "What about...?" are used both to propose something new and to suggest an alternative — these are very flexible, widely-used phrases for negotiation.

---

Why It Matters

Negotiating schedules — for meetings, social plans, appointments — is an extremely common real-life task that requires a mix of clarity and politeness:

• Work and social coordination: arranging meetings, calls, or get-togethers almost always involves some back-and-forth about timing.
• Politeness in refusal: "I'm afraid I can't make it" is much softer than a blunt "No" — important for maintaining good relationships.
• Collaborative problem-solving: suggesting alternatives ("Could we do Thursday instead?") shows willingness to find a solution, rather than just rejecting an idea.

This topic combines question forms, modal verbs ("could"), and softening language ("I'm afraid," "instead") into a natural, practical conversation flow.

---

Additional Examples

1. "How about Tuesday?" → "That works for me!" — Proposal + acceptance.
2. "What if we meet at 6?" → "I'm afraid I can't make it then — I have a class until 7." — Proposal + polite rejection with reason.
3. "Could we do Thursday instead?" → "Sure, Thursday is fine." — Alternative + acceptance.
4. "What about the morning instead of the afternoon?" → "Good idea, let's say 10 am." — Alternative + agreement on a specific time.
5. "Does Friday work for you?" → "Actually, I'm busy on Friday. How about Saturday?" — Proposal, rejection, counter-proposal.
6. "I'm free anytime after 3 — does that help?" — Offering flexibility to help find a time.

---

Common Mistakes

1. Rejecting a plan without an alternative "I can't make it." (can sound final/unhelpful) → "I'm afraid I can't make it then. Could we do Thursday instead?" Pairing a rejection with an alternative keeps the conversation moving toward a solution.

2. Using overly direct language for rejection "No, Tuesday is bad for me." → "I'm afraid Tuesday doesn't work for me." "I'm afraid..." and "doesn't work for me" are softer, more diplomatic alternatives to a direct "no".

3. Confusing "How about" with a yes/no question "How about Tuesday?" doesn't need "do" — it's already a complete question. Adding "do" ("How about do Tuesday?") is incorrect — "How about" is followed directly by a noun, time, or "-ing" verb: "How about Tuesday?" / "How about going for a coffee?"

4. Not confirming the final agreement After negotiating, it's good practice to confirm clearly: "So, Thursday at 10, right?" — avoiding this step can lead to misunderstandings about what was actually agreed.

Concept Explanation

Dealing with unexpected travel situations requires specific vocabulary and the present perfect to describe a recent event with a current consequence:

• Lost items: "I've lost my passport." / "My bag has been stolen." — present perfect (have/has + past participle) connects a past action to its present effect: the passport is still lost right now.
• Health problems: "I need to see a doctor." / "I have a high fever." — direct, simple statements describing a current need or symptom, used to get help quickly.
• Accommodation/transport problems: "My flight has been cancelled." / "There's a problem with my room." — present perfect passive ("has been cancelled") for an event that affects your current plans.

Notice the passive forms "has been stolen" and "has been cancelled" — these emphasize that something happened to your belongings or plans, without needing to say who did it.

---

Why It Matters

Travel emergencies are stressful, and having ready-made phrases can make a real difference:

• Speed and clarity: in an emergency, you need to communicate the problem quickly and clearly — these set phrases do exactly that.
• Getting help efficiently: "I've lost my passport" immediately tells airport staff or police what kind of help you need (a police report, embassy contact, etc.).
• Confidence under pressure: knowing these phrases in advance reduces panic — you don't have to construct sentences from scratch when stressed.

This is one of the most practical, real-world applications of the present perfect — connecting a past problem to its ongoing impact on your trip.

---

Additional Examples

1. "I've lost my passport — where's the nearest police station?" — Lost item + asking for help.
2. "My bag has been stolen. It had my wallet and phone inside." — Theft + additional detail (past simple for what was inside).
3. "I need to see a doctor — I think I have food poisoning." — Health problem + possible cause.
4. "I have a high fever and I've been feeling dizzy since this morning." — Combining symptoms with present perfect ("since this morning").
5. "My flight has been cancelled due to bad weather. Is there another one today?" — Travel disruption + follow-up question.
6. "There's a problem with my room — the air conditioning isn't working." — Accommodation issue + specific detail.

---

Common Mistakes

1. Using simple past instead of present perfect for "still relevant" problems "I lost my passport." (sounds like it might be resolved now) → "I've lost my passport." (it's still missing right now) Present perfect signals the problem is ongoing — important information for whoever is helping you.

2. Forgetting passive structures for things done "to" you "Someone stole my bag." (focuses on the unknown thief) → "My bag has been stolen." (focuses on the bag/your situation, more natural when you don't know who did it)

3. Being too vague about the problem "There's a problem with my room." is fine as an opener, but follow up with specifics: "...the heating doesn't work" / "...the room hasn't been cleaned." Vague complaints are harder for staff to resolve quickly.

4. Overusing "I have a problem" without details "I have a problem with my flight." → "My flight has been cancelled — can you help me find an alternative?" Being specific from the start saves time and gets you to a solution faster.

Concept Explanation

Phone conversations follow predictable patterns for three common situations:

• Answering and introducing yourself: "Hello, this is Ana speaking." (when you answer and identify yourself) / "Hi, can I speak to Dr. García?" (when you call and ask for someone). Note: "this is [name] speaking" is the standard way to identify yourself on the phone — not "I am [name]".
• Making a reservation: "I'd like to book a table for two for Saturday evening." — the structure "I'd like to book/reserve [what] for [number of people] for [date/time]" works for restaurants, hotels, and other services.
• Leaving a message: "Could you tell him I called?" / "I'll call back later." — polite requests when the person you want isn't available.

Phone English often differs slightly from face-to-face English — for example, "speaking" after "this is [name]" is specific to phone calls and isn't used in other contexts.

---

Why It Matters

Phone calls remove visual cues (gestures, facial expressions, lip-reading) — making clear, predictable language patterns especially important:

• Reduced anxiety: phone calls in a foreign language can feel intimidating; knowing the standard openings and closings removes much of the uncertainty.
• Practical necessity: booking restaurants, calling services, or speaking to receptionists by phone remains common, especially for older or more formal services.
• Professional contexts: "This is [name] speaking" and message-taking phrases are used constantly in workplace phone etiquette.

---

Additional Examples

1. "Hello, this is Ana speaking. How can I help you?" — Answering professionally.
2. "Hi, could I speak to Mr. Brown, please?" — Asking for someone politely.
3. "I'd like to book a table for four for Friday at 8 pm." — Making a reservation with all key details.
4. "I'm calling to confirm my appointment for tomorrow." — Stating the purpose of the call.
5. "He's not available right now. Could you tell him I called?" — Receiving + leaving a message.
6. "Sorry, could you repeat that? The line isn't very clear." — Asking for repetition (very useful on the phone).

---

Common Mistakes

1. Saying "I am [name]" instead of "This is [name] speaking" "I am Ana." (sounds unusual on the phone) → "This is Ana speaking." / "Ana speaking." This is a fixed phone-specific phrase in English.

2. Forgetting "please" or softeners when asking for someone "Give me Mr. Brown." (too direct) → "Could I speak to Mr. Brown, please?" Phone requests benefit from extra politeness since tone of voice is the only social cue available.

3. Using "reserve" and "book" incorrectly with prepositions "I'd like to reserve a table to two people." → "I'd like to book/reserve a table for two." "For" + number of people, "for" + date/time — both use "for," not "to".

4. Not confirming details at the end of a call Ending a booking call without confirming ("So that's a table for two, Saturday at 8, under the name Smith?") can lead to errors — confirming key details is standard, polite practice.

Concept Explanation

A simple formal email follows a three-part structure:

• Formal opening: "Dear Mr. Smith," (when you know the name) / "Dear Sir/Madam," or "To Whom It May Concern," (when you don't know who will read it). Note the comma after the greeting, and capital letters in "Dear".
• Clear purpose in the first sentence: "I am writing to enquire about..." (asking for information) / "I am writing in response to your advertisement." (replying to something). Starting with your purpose immediately tells the reader why you're writing — essential in formal/professional communication.
• Formal closing: "I look forward to hearing from you." (a polite way to end, suggesting you expect a reply) followed by "Yours sincerely," (if you used the person's name) or "Yours faithfully," (if you used "Dear Sir/Madam").

The sincerely/faithfully distinction is a classic British English convention: name known → "sincerely"; name unknown → "faithfully".

---

Why It Matters

Formal emails are used for job applications, customer service inquiries, complaints, and official requests — situations where tone and structure matter:

• First impressions: a well-structured formal email signals professionalism and attention to detail.
• Efficiency: stating your purpose immediately helps busy readers understand and respond faster.
• Cultural expectations: English-speaking formal communication has specific conventions (greetings, closings) that differ from informal emails — using them correctly avoids seeming too casual.

---

Additional Examples

1. "Dear Mr. Smith, I am writing to enquire about the availability of your services." — Known recipient + clear purpose.
2. "Dear Sir/Madam, I am writing in response to your advertisement for a part-time tutor." — Unknown recipient + purpose.
3. "To Whom It May Concern, I would like to request information regarding..." — Very formal opening for unknown recipients.
4. "I look forward to hearing from you. Yours sincerely, Ana López" — Closing when the name was known.
5. "Thank you for your time and consideration. Yours faithfully, [Name]" — Closing when "Dear Sir/Madam" was used.
6. "I am writing to ask for further details about the course schedule." — Clear purpose using "ask for" as an alternative to "enquire about".

---

Common Mistakes

1. Mismatching greeting and closing "Dear Sir/Madam, ... Yours sincerely," → "Dear Sir/Madam, ... Yours faithfully," Remember: name unknown → "faithfully"; name known → "sincerely". This is a classic formal email rule.

2. Starting with "I want" instead of "I am writing to" "I want to ask about..." (too direct/informal for a first line) → "I am writing to ask about..." / "I am writing to enquire about..." "I am writing to..." is the standard, professional way to state your purpose.

3. Forgetting the comma after the greeting "Dear Mr. Smith I am writing..." → "Dear Mr. Smith, I am writing..." A comma after the greeting (and a capital letter in "Dear") is a small but noticeable formatting detail.

4. Using contractions in formal emails "I'm writing to enquire..." → "I am writing to enquire..." Formal writing generally avoids contractions ("I'm," "don't," "can't") — write full forms instead.

Concept Explanation

A descriptive text (about a place, person, or event) follows a clear structure and relies on varied vocabulary:

• Basic structure: introduction (general overview) → body (specific details) → conclusion (impression/feeling). For example: Intro: "Barcelona is a vibrant city on the Mediterranean coast." → Body: specific details about neighborhoods, food, atmosphere → Outro: "What struck me most was how friendly the people were."
• Varied descriptive adjectives: instead of repeating "nice" or "good," use specific adjectives — "crowded," "peaceful," "vibrant," "cozy," "breathtaking," "memorable" — each creates a different, more vivid image.
• Organizing connectors: "In the center..." / "Nearby..." / "What struck me most was..." — these phrases help organize spatial details (where things are) and personal reactions (how you felt).

The phrase "What struck me most was..." is particularly useful for conclusions — it introduces your strongest personal impression in a natural, reflective way.

---

Why It Matters

Descriptive writing is one of the most common writing tasks — describing a holiday destination, a memorable person, or a special event:

• Vivid communication: specific adjectives ("breathtaking" vs. "nice") help readers actually picture what you're describing.
• Structured writing: the intro/body/conclusion structure works for almost any descriptive topic and helps organize your ideas before writing.
• Personal voice: phrases like "what struck me most" let you add a personal, reflective dimension — important for more engaging writing at B1 level and beyond.

---

Additional Examples

1. "The old town is a maze of narrow streets, full of small cafés and colorful buildings." — Body: specific visual details.
2. "In the center of the square stands a beautiful fountain, surrounded by trees." — "In the center" as a spatial connector.
3. "Nearby, you'll find a small market selling fresh fruit and local crafts." — "Nearby" as a spatial connector.
4. "My grandmother is a calm, patient woman with a wonderful sense of humor." — Descriptive adjectives for a person.
5. "The view from the top of the mountain was absolutely breathtaking." — Strong descriptive adjective for emphasis.
6. "What struck me most was how peaceful the village felt, especially in the early morning." — Conclusion using the reflective connector.

---

Common Mistakes

1. Overusing basic adjectives like "nice" and "good" "The place was nice and the food was good." → "The place was charming and the food was delicious." Varied, specific adjectives make descriptions far more vivid and interesting.

2. Writing without a clear structure Jumping between unrelated details without an intro or conclusion makes a description feel disorganized → plan: general overview first, then specific details, then a final impression.

3. Listing facts without personal reaction "The museum has 20 rooms and is 100 years old." (purely factual) → adding "What struck me most was the incredible collection of ancient artifacts" gives the description a personal voice.

4. Misusing spatial connectors "In the center, there is a market. In the center, there is also a fountain." (repetitive) → "In the center, there is a market. Nearby, you'll also find a fountain." Vary connectors to avoid repetition and show different spatial relationships.

Concept Explanation

A short review (of a film, book, restaurant, product, etc.) typically has three parts:

• Overall assessment: "Overall, I would highly recommend this." / "I found it disappointing." — a clear, general opinion stated early, so the reader immediately knows your verdict.
• Supporting with concrete reasons: "The acting was brilliant, especially..." / "The plot was predictable because..." — specific examples and reasons that justify your overall assessment. Reviews are more credible and useful when opinions are backed by evidence.
• Final recommendation: "Perfect for fans of..." / "Not suitable for young children." — a closing statement that helps the reader decide whether this is right for them, often based on their interests or circumstances.

This structure (overall opinion → reasons → recommendation for a specific audience) is the basic template for almost any review, regardless of what's being reviewed.

---

Why It Matters

Reviews are everywhere — for films, restaurants, products, books, apps — and writing one well requires combining opinion, evidence, and audience awareness:

• Real-world application: writing reviews online (for restaurants, products, services) is a common real-life writing task.
• Persuasive writing skills: supporting opinions with reasons is a transferable skill for essays, emails, and other persuasive texts.
• Audience awareness: "Perfect for fans of..." / "Not suitable for..." shows you're thinking about who would benefit from this information — a more sophisticated writing skill.

---

Additional Examples

1. "Overall, I would highly recommend this restaurant — the food was excellent and the service was friendly." — Overall assessment + brief reasons.
2. "I found the ending disappointing because it left too many questions unanswered." — Negative assessment + reason with "because".
3. "The acting was brilliant, especially the lead actress, who brought real depth to her character." — Specific praise with detail.
4. "The plot was predictable because you could guess the ending after the first 20 minutes." — Criticism + specific reason.
5. "Perfect for fans of action movies who don't mind a simple storyline." — Recommendation for a specific audience.
6. "Not suitable for young children, as some scenes are quite frightening." — Warning/recommendation with reason.

---

Common Mistakes

1. Giving an opinion without any supporting reason "It was bad." → "It was disappointing because the story didn't go anywhere." A reason transforms a simple opinion into a useful, credible review.

2. Being too vague in the recommendation "I recommend it." → "Perfect for fans of mystery novels" / "Great for a family day out." Specific recommendations help readers decide if the item matches their interests.

3. Mixing up "boring" and "bored" "I was boring during the film." → "I was bored during the film." / "The film was boring." "-ed" adjectives describe how someone feels; "-ing" adjectives describe the thing causing that feeling.

4. Overusing "good" and "bad" throughout the review "It was good. The acting was good. The music was good too." → vary vocabulary: "impressive," "outstanding," "enjoyable," "underwhelming," "forgettable" — repetition weakens the impact of a review.

Concept Explanation

Connectors (linking words) help organize ideas and improve the flow of writing — they're grouped by function:

• Beginning and developing ideas: "First of all,..." / "To begin with,..." (introducing the first point) and "However,..." / "On the other hand,..." (introducing a contrast or different perspective).
• Concluding: "In conclusion,..." / "To sum up,..." / "All in all,..." — these phrases signal that you're moving toward a final summary or overall judgment, usually in the last paragraph.

Connectors act as signposts for the reader — they indicate the logical relationship between ideas (addition, contrast, cause, conclusion) without the reader having to guess.

---

Why It Matters

Cohesion — how well ideas connect to each other — is one of the main things that distinguishes basic writing from more fluent, B1-level writing:

• Clarity: connectors make the structure of an argument or description explicit, helping readers follow your reasoning.
• Formal/academic writing: essays, reports, and reviews rely heavily on connectors to organize paragraphs logically.
• Avoiding repetition: instead of starting every sentence with "And" or "But," connectors offer more precise, varied alternatives ("In addition," "Nevertheless," "Therefore").

Mastering these connectors is often one of the clearest ways to make writing sound more natural and organized.

---

Additional Examples

1. "First of all, let's look at the advantages of working from home." — Introducing the first point.
2. "To begin with, public transport is often cheaper than driving." — Alternative opening connector.
3. "However, this option isn't always practical for people with young children." — Introducing a contrast.
4. "On the other hand, some people prefer the flexibility of remote work." — Presenting an alternative viewpoint.
5. "In conclusion, both options have advantages and disadvantages depending on personal circumstances." — Concluding with a balanced summary.
6. "All in all, I believe the benefits outweigh the drawbacks." — Concluding with a personal final judgment.

---

Common Mistakes

1. Using "Firstly... Secondly..." inconsistently Starting with "First of all" but later switching to "Second" without matching style → choose one style ("First of all... Secondly... Finally...") and keep it consistent throughout the text.

2. Overusing "but" instead of varying contrast connectors "It was expensive but I bought it. But it broke quickly." → "It was expensive, but I bought it. However, it broke quickly soon after." Varying between "but," "however," and "on the other hand" makes writing more sophisticated.

3. Placing connectors incorrectly in the sentence "I think, however, that..." is correct mid-sentence, but starting a sentence requires a comma after the connector: "However, I think that..." — missing this comma is a common error.

4. Using "in conclusion" in short texts where it feels unnecessary For very short texts (a few sentences), "in conclusion" can feel overly formal — reserve strong concluding connectors for longer pieces (essays, reports) with multiple paragraphs.

Concept Explanation

The present perfect (HAVE/HAS + past participle) connects the past to the present in three main uses:

• Basic structure: "I've finished." / "She's never been abroad." / "We've just arrived." — formed with "have/has" + the past participle (regular: -ed; irregular: special forms like "been," "gone," "done").
• With EVER, NEVER, ALREADY, YET, JUST: these adverbs add nuance — "ever" (at any time, in questions: "Have you ever tried it?"), "never" (at no time: "I haven't done it yet" — wait, "never" not "yet" — actually "never" means at no point), "already" (sooner than expected, in positive sentences: "She's just called"), "yet" (up to now, in negatives/questions: "I haven't done it yet"), "just" (very recently: "She's just called").
• With FOR and SINCE: for duration up to the present — "for" + a length of time ("for 5 years"), "since" + a starting point ("since Monday"). "I've lived here for 5 years." (duration) vs. "She's been sick since Monday." (starting point, still true now).

The key idea across all these uses: the present perfect always connects to now — an experience you have (or don't have) up to now, something that just happened, or a situation that started in the past and continues.

---

Why It Matters

The present perfect is one of the most frequently used — and most often misused by Spanish speakers — tenses in English, because Spanish doesn't use an equivalent structure in the same way:

• Talking about experiences: "Have you ever...?" is essential for describing life experiences without specifying when.
• Giving updates: "I've just finished" / "She's already left" — common in everyday conversations about recent events.
• Describing ongoing situations: "I've lived here for 5 years" describes a situation that started in the past and is still true — extremely common in introductions and personal descriptions.

---

Additional Examples

1. "I've finished my homework, so I can go out now." — Result relevant to the present.
2. "She's never been abroad, but she'd love to travel one day." — "Never" + life experience.
3. "Have you ever tried Indian food?" — "Ever" in a question about experience.
4. "I haven't seen that movie yet, but I'm planning to watch it this weekend." — "Yet" in a negative sentence.
5. "We've just arrived — give us a minute to settle in!" — "Just" for something very recent.
6. "I've lived in this city for five years, and my sister has lived here since 2015." — "For" (duration) vs. "since" (starting point).

---

Common Mistakes

1. Using present perfect with a specific finished time "I've seen that film yesterday." → "I saw that film yesterday." / "I've seen that film." (without "yesterday") A specific past time word ("yesterday," "last week," "in 2020") requires simple past, not present perfect.

2. Confusing "for" and "since" "I've lived here since five years." → "I've lived here for five years." / "I've lived here since 2019." "For" + duration (a length of time); "since" + a point in time (a date, year, day).

3. Misplacing "ever," "never," "just," "already," "yet" "I have ever been there." (incorrect in a positive statement) → "I have been there." / "Have you ever been there?" ("ever" is mainly for questions and negatives, not positive statements) Also: "yet" goes at the end of negatives/questions ("I haven't finished yet"), while "already" and "just" go before the past participle ("I've already finished," "I've just finished").

4. Using the wrong past participle form "I have went there." → "I have gone there." / "I have been there." Irregular past participles (gone, been, done, seen, written) must be memorized separately from simple past forms (went, was, did, saw, wrote).

Concept Explanation

The choice between present perfect and simple past depends on whether a specific time is mentioned or relevant:

• Present perfect — no specific time / relevant now: "I've seen that film." — this describes an experience without saying when; what matters is that you have this experience, not the specific moment it happened.
• Simple past — specific time mentioned: "I saw it last Friday." — once a specific time ("last Friday," "in 2018," "yesterday") is given, English requires simple past, not present perfect.
• The "test" for the difference: "Have you been to Paris?" (general question, no time) → "Yes, I went there in 2018." (the answer specifies a time, so it switches to simple past). This question-answer pattern is the clearest illustration of how the two tenses work together.

A useful way to think about it: present perfect = "at some point up to now" (the when doesn't matter); simple past = "at this specific point in the past" (the when is the focus).

---

Why It Matters

This is one of the most important grammar distinctions for B1 learners, because Spanish typically uses one past tense (pretérito perfecto/indefinido) where English requires choosing between two:

• Natural-sounding English: native speakers immediately notice when present perfect is used with a specific time ("I have seen it yesterday" sounds clearly wrong) — getting this right is a strong marker of fluency.
• Conversational flow: the "general question → specific time in the answer" pattern (present perfect → simple past) appears constantly in everyday conversation about experiences.
• Avoiding ambiguity: choosing the right tense makes it clear whether you're talking about a general experience or a specific event.

---

Additional Examples

1. "I've seen that film." / "I saw it last Friday." — General experience vs. specific time.
2. "Have you been to Paris?" → "Yes, I went there in 2018." — Classic question-answer pattern.
3. "She's tried sushi before." / "She tried it for the first time at a restaurant in Tokyo." — General experience vs. specific occasion.
4. "We haven't visited that museum." / "We didn't visit it when we were there last month." — Negative forms following the same pattern.
5. "Has he ever played golf?" → "Yes, he played a few times when he was younger." — "Ever" (no time) vs. "when he was younger" (specific period).
6. "I've already eaten." / "I ate breakfast at 7 am." — Recent/relevant now vs. specific time.

---

Common Mistakes

1. Mixing tenses within the same idea "I have seen that film last Friday." → "I saw that film last Friday." / "I've seen that film." Once a specific time appears, the whole verb phrase must switch to simple past — don't combine "have" with a specific time expression.

2. Continuing to use present perfect when a time is later specified "Have you been to Paris? Yes, I have been there in 2018." → "Yes, I went there in 2018." The follow-up answer with a specific year requires simple past, even though the question used present perfect.

3. Avoiding present perfect altogether and only using simple past Some learners default to simple past for everything ("Did you ever go to Paris?" instead of "Have you ever been to Paris?") — for general life-experience questions without a specific time, present perfect with "ever" sounds more natural.

4. Forgetting that "been" (not "gone") is used for completed visits "I have gone to Paris twice." (suggests you might still be there or it's about a journey) → "I've been to Paris twice." (you visited and returned — the standard way to talk about completed visits).

Concept Explanation

The past continuous (was/were + -ing) describes actions in progress at a point in the past, often in relation to another action:

• Structure: "I was cooking when she called." — "was/were" + the "-ing" form of the verb describes an action that was already happening at a specific moment.
• Background action vs. specific event: "They were watching TV when the lights went out." — the past continuous ("were watching") sets the scene/background, while the simple past ("went out") describes the specific event that interrupted it.
• Two simultaneous actions: "While she was reading, he was cooking dinner." — when two actions were happening at the same time in the past, both can be in past continuous, often connected with "while".

A simple way to remember it: past continuous = "in the middle of doing something" at a past moment; simple past = "a complete action" at that same moment.

---

Why It Matters

The past continuous is essential for telling stories and describing scenes — it adds context and detail that simple past alone can't provide:

• Storytelling: setting the scene ("It was raining and people were walking quickly") makes narratives more vivid and realistic.
• Explaining interruptions: "I was sleeping when the alarm went off" is a very natural way to explain what was happening when something else occurred.
• Describing parallel activities: "while" + past continuous is useful for describing what different people were doing at the same time.

---

Additional Examples

1. "I was cooking dinner when the phone rang." — Background action interrupted by a specific event.
2. "They were watching a movie when the power went out." — Same pattern with "when".
3. "While she was studying, her brother was playing video games." — Two simultaneous actions with "while".
4. "What were you doing at 8 pm last night?" — Asking about an action in progress at a specific time.
5. "It was snowing heavily when we left the house." — Setting a scene with weather.
6. "I wasn't paying attention when the teacher explained the homework." — Negative form for a missed action.

---

Common Mistakes

1. Using simple past for both actions when one is "background" "I cooked dinner when she called." (sounds like two separate, sequential actions) → "I was cooking dinner when she called." (cooking was already happening; the call interrupted it)

2. Using past continuous for short, completed actions "I was dropping my phone." → "I dropped my phone." Quick, completed actions (drop, break, arrive, finish) are usually simple past, not past continuous — past continuous is for actions with duration.

3. Forgetting "while" with two simultaneous past continuous actions "She was reading, he was cooking dinner." (two unconnected sentences) → "While she was reading, he was cooking dinner." ("while" connects the two parallel actions)

4. Using past continuous with stative verbs "I was knowing the answer." → "I knew the answer." Stative verbs (know, like, want, believe, need) are not normally used in continuous forms, in past or present.

Concept Explanation

The first conditional describes real, possible future situations and their likely results:

• Structure: "If + present simple, ... will + base verb." — "If it rains, I'll stay home." The "if" clause describes a possible future condition (using present simple, not "will"); the main clause describes the likely result (using "will").
• Real possibility: "If you study hard, you'll pass the exam." — this isn't hypothetical or imaginary; it's a realistic prediction based on a real possible condition.
• Variants with CAN / SHOULD / MIGHT: instead of "will," other modal verbs can express different nuances — "If you're tired, you should rest." (advice) / "If she calls, I might go." (less certain result).

The order of clauses can be reversed: "I'll stay home if it rains." (no comma needed when "if" comes second).

---

Why It Matters

The first conditional is one of the most commonly used grammar structures for talking about real plans, warnings, promises, and predictions:

• Making plans: "If the weather's good, we'll go to the beach" — discussing real future possibilities.
• Giving warnings/advice: "If you don't leave now, you'll miss the bus" — a very common, practical use.
• Negotiating and promising: "If you help me with this, I'll help you with that" — common in everyday agreements.

A common error among Spanish speakers is using "will" in the "if" clause itself ("If it will rain...") — getting this structure right is a clear marker of grammatical accuracy at B1.

---

Additional Examples

1. "If it rains tomorrow, we'll cancel the picnic." — Classic if + present, will + base verb.
2. "If you study hard, you'll pass the exam." — Real possibility with a positive result.
3. "If you're tired, you should rest for a while." — Variant with "should" for advice.
4. "If she calls, I might go to the meeting after all." — Variant with "might" for uncertainty.
5. "You'll feel better if you drink more water." — Reversed clause order (no comma needed).
6. "If we leave now, we can catch the earlier train." — Variant with "can" for ability/possibility.

---

Common Mistakes

1. Using "will" in the "if" clause "If it will rain, I'll stay home." → "If it rains, I'll stay home." The "if" clause uses present simple, even though it refers to the future — "will" only goes in the main clause.

2. Forgetting the comma when "if" comes first "If it rains I'll stay home." (missing comma, less clear) → "If it rains, I'll stay home." When the "if" clause comes first, a comma separates it from the main clause. No comma is needed if the order is reversed.

3. Confusing first and second conditional "If I will have time, I would help you." (mixes both conditionals) → "If I have time, I'll help you." (first conditional, real possibility) or "If I had time, I would help you." (second conditional, less likely/hypothetical).

4. Using present continuous instead of present simple in the "if" clause "If it's raining tomorrow..." → "If it rains tomorrow..." For first conditional predictions about the future, present simple (not continuous) is used in the "if" clause.

Concept Explanation

The second conditional describes hypothetical or unlikely situations and their imagined results:

• Structure: "If + past simple, ... would + base verb." — "If I had more money, I would travel." The "if" clause uses past simple (but doesn't refer to the past — it refers to an imaginary present/future), and the main clause uses "would".
• Imaginary or unlikely situations: "If I were you, I wouldn't do that." — this is advice framed as an imaginary scenario ("imagine you were me/in this situation").
• WERE for all persons: "If she were taller..." / "If I were president..." — in formal/traditional English, "were" (not "was") is used with all subjects (I, he, she, it) in second conditional sentences — this is sometimes called the "subjunctive" form.

The key difference from the first conditional: second conditional situations are imaginary, unlikely, or contrary to current reality — not realistic future possibilities.

---

Why It Matters

The second conditional is essential for expressing wishes, hypothetical advice, and imaginary situations — a very common feature of natural conversation:

• Giving advice diplomatically: "If I were you, I wouldn't worry about it" is a softer, more natural way to give advice than a direct command.
• Talking about dreams and wishes: "If I won the lottery, I would buy a house" — expressing things that are unlikely or purely imaginary.
• Hypothetical discussions: "What would you do if you lost your job?" — common in interviews, discussions, and getting-to-know-you conversations.

---

Additional Examples

1. "If I had more money, I would travel around the world." — Classic hypothetical wish.
2. "If I were you, I wouldn't accept that offer." — Advice framed hypothetically.
3. "If she were taller, she could be a basketball player." — "Were" with "she" (formal/traditional usage).
4. "What would you do if you won the lottery?" — Hypothetical question, very common in conversation.
5. "If we lived closer to the city, we would walk to work." — Hypothetical situation contrary to current reality.
6. "If I knew the answer, I would tell you." — Hypothetical (implying "I don't know the answer").

---

Common Mistakes

1. Using "would" in the "if" clause "If I would have more money, I would travel." → "If I had more money, I would travel." The "if" clause uses past simple, not "would" — "would" only goes in the main clause.

2. Confusing first and second conditional based on likelihood "If I will win the lottery, I will buy a house." (sounds too certain/realistic) → "If I won the lottery, I would buy a house." (expressing something unlikely/hypothetical) Choose second conditional when the situation is imaginary or improbable, not a realistic plan.

3. Using "was" instead of "were" in formal contexts "If I was you..." is common in informal speech, but "If I were you..." is the traditional, more "correct" form often taught and expected in writing — both are widely understood, but "were" is safer in formal contexts.

4. Using second conditional for real future plans "If I would go to the party, I would see John." (sounds hypothetical/unlikely, but maybe you ARE going) → "If I go to the party, I'll see John." (first conditional, since it's a real possibility) Use second conditional only for unlikely or imaginary situations — not real plans.

Concept Explanation

Modal verbs can express different degrees of probability about present or future situations:

• MIGHT / MAY (around 50% certainty): "It might rain later." / "She may be at home." — these express genuine uncertainty; the speaker doesn't know and is making a guess. "May" is slightly more formal than "might," but both express similar probability.
• COULD (more remote possibility): "It could be a mistake." / "He could be wrong." — "could" often suggests a possibility that's worth considering, sometimes slightly less likely or more speculative than "might/may".
• MUST (strong logical deduction): "She's not answering — she must be busy." — "must" here doesn't mean obligation; it expresses a strong conclusion based on evidence. The speaker is reasoning: "the only logical explanation is that she's busy".

These modals + base verb (or "be" + adjective/-ing for ongoing situations) form a "scale" of certainty: must (very confident) > will (confident) > should (fairly confident) > might/may/could (uncertain).

---

Why It Matters

Expressing degrees of certainty is a natural part of everyday reasoning and conversation — we rarely state things as 100% certain or 100% impossible:

• Making guesses politely: "She might be in a meeting" sounds more natural and less presumptuous than "She is in a meeting" when you're not sure.
• Drawing conclusions from evidence: "He must be tired — he's been working all day" is a common way to reason about situations based on what you observe.
• Speculating about plans: "It could rain this weekend, so we might need a backup plan" — combining different levels of certainty in a single conversation.

---

Additional Examples

1. "It might rain later, so bring an umbrella just in case." — "Might" for genuine uncertainty + practical advice.
2. "She may be at home, but she's usually at work at this time." — "May" for uncertainty, with additional context.
3. "It could be a misunderstanding — let's not jump to conclusions." — "Could" for a more tentative possibility.
4. "He could be right, but I'd like to check the facts first." — "Could" expressing openness to a possibility.
5. "She's not answering her phone — she must be in class." — "Must" for strong deduction based on evidence.
6. "They must be on holiday — their house lights have been off all week." — "Must" + evidence-based reasoning.

---

Common Mistakes

1. Using "must" to mean "probably" when evidence is weak "She must be tired." (said with no real evidence) → "She might be tired." / "She's probably tired." "Must" should be reserved for situations where there's strong evidence supporting only one logical conclusion.

2. Confusing "must" (deduction) with "must" (obligation) "She must be busy" (deduction: "I conclude she is busy") vs. "She must finish this today" (obligation: "it's necessary that she finishes"). Context determines the meaning — but be aware these are different uses of the same word.

3. Adding "to" after modal verbs "It might to rain." → "It might rain." Modal verbs (might, may, could, must, should) are followed directly by the base verb, with no "to".

4. Using "can" instead of "could/might/may" for present possibility "It can rain later." (sounds like a general fact about weather, not a specific guess about today) → "It might rain later." / "It could rain later." "Can" is used for general possibilities/abilities; "might/may/could" are used for specific guesses about a particular situation.

Concept Explanation

Reported speech (indirect speech) is used to report what someone else said, with specific changes:

• Tense changes (backshift): when reporting what someone said, tenses usually shift "one step back" — present becomes past: "I'm tired" → He said he was tired. (present simple "am" → past simple "was")
• TELL vs. SAY: "She told me she was leaving." vs. "She said she was leaving." — "tell" is followed directly by a person ("told me"), while "say" is not normally followed directly by a person (you'd need "said to me"). Both can be followed by "that + clause" (the "that" is often omitted).
• Reported commands: "Stop!" → She told me to stop. — commands and requests are reported using "tell/ask + person + to + base verb" — a completely different structure from statements.

The general pattern: direct speech "[present tense]" → reported speech "[past tense]"; direct command "[imperative]" → reported "[told/asked + person + to + verb]".

---

Why It Matters

Reported speech is essential for retelling conversations, relaying messages, and reporting news — extremely common in both spoken and written English:

• Relaying messages: "He said he'd call back later" — passing on information from a phone call or conversation.
• Retelling conversations: "She told me she was moving to another city" — sharing news you heard from someone else.
• Following instructions: "The teacher told us to finish the exercise" — reporting what someone asked you to do.

The tense backshift and the tell/say/ask distinction are common error areas for Spanish speakers, since Spanish reported speech works somewhat differently.

---

Additional Examples

1. "I'm tired" → He said he was tired. — Present simple → past simple.
2. "I'll call you tomorrow" → She said she would call me the next day. — "Will" → "would," and "tomorrow" → "the next day".
3. "She told me she was leaving early." — "Tell" + person + reported clause.
4. "He said (that) he had already eaten." — "Say" + (that) + reported clause, with "that" optional.
5. "Stop!" → She told me to stop." — Reported command with "tell + to".
6. "Can you help me?" → He asked me to help him." — Reported request with "ask + to".

---

Common Mistakes

1. Forgetting to backshift the tense "She said she is tired." → "She said she was tired." When the reporting verb ("said") is in the past, the reported tense usually shifts back one step (present → past, present perfect → past perfect, etc.).

2. Using "say" with a direct object (person) "She said me she was leaving." → "She told me she was leaving." / "She said (to me) she was leaving." "Say" doesn't take a direct person object without "to" — use "tell" when you want to mention who was told directly.

3. Reporting commands as statements "He said me to stop." → "He told me to stop." Commands/requests use "tell/ask + person + to + verb" — not "said" + a "that" clause.

4. Forgetting to change time/place expressions "He said he would do it tomorrow" (reported a week later, still saying "tomorrow") → "He said he would do it the next day." Words like "tomorrow," "today," "here," "this" often need to change to "the next day," "that day," "there," "that" when reporting at a different time/place.

Concept Explanation

The passive voice shifts focus from "who does the action" to "what happens to something":

• Present passive: "English is spoken worldwide." / "The report is written every month." — formed with "am/is/are" + past participle. The focus is on "English" or "the report," not on who speaks/writes them.
• Past passive: "The letter was written by her." / "The bridge was built in 1990." — formed with "was/were" + past participle. Note "by + agent" can be added if it's relevant ("by her"), but is often omitted.
• When to use it: when the agent (the "doer") is unknown, obvious, or irrelevant. "The bridge was built in 1990" — we don't need to know who built it; the focus is on the bridge and when it was completed.

The general transformation: active "[Subject] + verb + [object]" → passive "[Object] + be + past participle (+ by [subject])". The object of the active sentence becomes the subject of the passive sentence.

---

Why It Matters

The passive voice is common in formal, descriptive, and factual writing — news reports, instructions, descriptions of processes, and historical facts:

• Formal/objective tone: "Mistakes were made" sounds more neutral/formal than "We made mistakes" — useful in reports and formal writing.
• Focus on the result, not the doer: "The museum was built in 1850" focuses on the building and date, which is usually more relevant than who built it.
• Describing processes: "The product is tested before it is shipped" — common in describing how things work, regardless of who specifically does each step.

---

Additional Examples

1. "English is spoken in many countries around the world." — Present passive, general fact.
2. "This software is updated every month." — Present passive, routine process.
3. "The novel was written by a famous author in the 19th century." — Past passive with "by + agent".
4. "The bridge was built in 1990 and renovated in 2015." — Past passive, historical facts.
5. "My car was stolen last night." — Past passive, agent unknown (we don't know who stole it).
6. "The decision was made after a long discussion." — Past passive, agent irrelevant (the focus is on the decision).

---

Common Mistakes

1. Forgetting "be" in the passive structure "The letter written by her." → "The letter was written by her." The passive always needs a form of "be" (is/was/are/were) + past participle — the past participle alone is not a complete verb.

2. Using the wrong past participle "The bridge was build in 1990." → "The bridge was built in 1990." Make sure to use the correct past participle form (built, written, made, done), not the base form or simple past form.

3. Adding "by + agent" unnecessarily "My car was stolen by someone." (adds little information) → "My car was stolen." ("by someone" is usually unnecessary when the agent is unknown — that's often the whole point of using passive)

4. Overusing the passive voice Using passive for everything ("The ball was kicked by me") makes writing sound unnatural and indirect — passive should be used specifically when the agent is unknown, obvious, or unimportant; otherwise active voice is usually clearer and more natural.

Concept Explanation

These five time expressions are commonly used with the present perfect, each with a distinct function:

• FOR (duration) vs. SINCE (starting point): "I've been here for two hours." (a length of time — 2 hours) vs. "I've known her since 2015." (a specific starting point — the year 2015, and the relationship continues).
• ALREADY (sooner than expected, in affirmatives): "I've already eaten." — used in positive sentences to show something happened before now, often earlier than expected. Usually placed between "have" and the past participle.
• YET (expected but not yet happened, in negatives/questions): "Have you finished yet?" / "I haven't called yet." — "yet" goes at the end of negative sentences and questions, asking about/stating something that hasn't happened up to now but is expected to.
• JUST (very recently): "I've just arrived." / "She's just left." — "just" indicates something happened a very short time ago, placed between "have" and the past participle.

These five words are some of the most common "signal words" for the present perfect — recognizing them helps you choose the right tense automatically.

---

Why It Matters

These time expressions appear constantly in everyday English and are essential for giving precise updates about timing:

• Describing duration vs. starting points: "for"/"since" let you specify exactly how long something has been true, in two different but related ways.
• Managing expectations: "already" and "yet" are central to conversations about whether tasks are done — "Have you finished yet?" / "I've already finished" are extremely common exchanges.
• Giving fresh updates: "just" is the natural way to announce something that happened moments ago — "I've just heard the news!"

---

Additional Examples

1. "I've been waiting here for twenty minutes." — "For" + duration.
2. "She's worked at this company since 2018." — "Since" + starting point.
3. "I've already seen this film — let's choose another one." — "Already" in an affirmative sentence.
4. "Have you done your homework yet?" → "No, not yet." — "Yet" in a question and short negative answer.
5. "We've just got back from our holiday — it was amazing!" — "Just" for very recent news.
6. "I haven't finished the report yet, but I've already written the introduction." — "Yet" (negative) + "already" (affirmative) in the same context.

---

Common Mistakes

1. Confusing "for" and "since" with the wrong type of expression "I've lived here since five years." → "I've lived here for five years." / "I've lived here since 2019." "For" needs a duration (five years, two hours, a long time); "since" needs a point in time (2019, Monday, last week, I was a child).

2. Placing "yet" in the wrong position "I haven't yet finished." (less natural) → "I haven't finished yet." "Yet" typically goes at the very end of the sentence in negatives and questions.

3. Using "already" in negative sentences "I haven't already finished." → "I haven't finished yet." "Already" is for affirmative sentences; "yet" is for negatives and questions — they aren't interchangeable.

4. Using "just" to mean "only" "I have just two apples" (meaning "only two") is a different "just" from "I've just arrived" (meaning "very recently") — in the present perfect context, "just" almost always means "a very short time ago".

Concept Explanation

Talking about work, studies, and ambitions involves three related areas of vocabulary and structure:

• Describing your current job: "I work as a project manager at a tech firm. I'm in charge of..." — "work as a [job title]" describes your role; "I'm in charge of..." (+ noun/-ing) describes your responsibilities.
• Talking about studies and training: "I studied journalism. I'm currently doing a master's in..." — past simple for completed studies, present continuous ("I'm doing") for studies in progress.
• Expressing ambitions: "I'd like to become a... someday." / "My goal is to..." — "would like to + verb" (polite, common way to express a wish) and "My goal is to + verb" (more formal, structured way to state an ambition).

This combination — past (what you studied) + present (what you do/are doing) + future (what you want) — gives a complete picture of someone's professional/educational journey, a very common topic in introductions and interviews.

---

Why It Matters

This is one of the most common topics in real conversations, job interviews, and networking situations:

• Introductions: "What do you do?" is one of the most frequent questions when meeting new people, especially in professional contexts.
• Job interviews: describing your background (studies) and ambitions (goals) is central to interview questions like "Tell me about yourself" or "Where do you see yourself in five years?"
• Building connections: sharing ambitions ("I'd like to become...") often leads to more personal, engaging conversations than just stating facts.

---

Additional Examples

1. "I work as a graphic designer for a marketing agency. I'm in charge of creating visual content for clients." — Job + responsibility.
2. "I studied computer science at university, and now I work as a software developer." — Past studies → current job.
3. "I'm currently doing a master's in business administration part-time." — Present continuous for ongoing studies.
4. "I'd like to become a team leader someday — that's my main career goal." — Ambition with "would like to become".
5. "My goal is to start my own business within the next five years." — Ambition with "My goal is to".
6. "I've been working in customer service for two years, but I'm hoping to move into sales." — Present perfect (experience) + future hope.

---

Common Mistakes

1. Using "I am" instead of "I work as" for jobs "I am a project manager work in a tech firm." (grammatically broken) → "I work as a project manager at a tech firm." / "I am a project manager." Both "I am a [job title]" and "I work as a [job title]" are correct — but don't combine them incorrectly.

2. Confusing "study" (verb) and "studies" (noun) tenses "I am studying journalism" (ongoing, e.g., currently at university) vs. "I studied journalism" (completed, in the past) — choosing the wrong one can misrepresent whether you're still studying.

3. Using "I want" instead of softer ambition phrases in formal contexts "I want to become a manager." (direct, fine informally) → "I'd like to become a manager" / "My goal is to become a manager" (softer, more natural in formal contexts like interviews).

4. Forgetting prepositions with "in charge of" "I'm in charge to manage the team." → "I'm in charge of managing the team." / "I'm in charge of the team." "In charge of" is followed by a noun or "-ing" form, not "to + verb".

Concept Explanation

Talking about movies, music, and books involves three steps: describing, evaluating, and recommending:

• Describing genre and plot briefly: "It's a thriller about a detective who..." — start with the genre (thriller, comedy, romance, sci-fi) and a one-sentence summary using "about" + a relative clause ("who/which...").
• Giving your opinion: "I really enjoyed it because..." (positive + reason) / "I found it a bit slow." ("find" + adjective is a common way to give a personal impression — "I found it boring/confusing/predictable").
• Making recommendations: "You should watch/read... — I think you'd love it." — "should" for a suggestion, plus a personal reason ("I think you'd love it" uses second conditional "would" to imagine the other person's reaction).

This structure — genre/plot → opinion + reason → recommendation — works for films, books, music albums, TV series, and even restaurants or other media.

---

Why It Matters

Discussing entertainment is one of the most natural, frequent conversation topics — at parties, with friends, or as small talk:

• Building connections: shared opinions about movies, music, and books often spark longer conversations and reveal common interests.
• Practicing opinion language: this topic is a low-pressure way to practice giving opinions and reasons (covered in earlier topics) in a fun context.
• Recommendations as social currency: "You should watch..." is one of the most common ways people share and bond over media.

---

Additional Examples

1. "It's a comedy about a family who moves to a small town and has to adapt to a new lifestyle." — Genre + plot summary.
2. "I really enjoyed the book because the characters felt so real." — Opinion + reason.
3. "I found the movie a bit slow in the middle, but the ending was great." — Mixed opinion using "find".
4. "You should listen to their new album — I think you'd love the lyrics." — Recommendation + personal reason.
5. "It's a thriller about a journalist who uncovers a conspiracy." — Genre + plot with relative clause "who".
6. "I'm not really into horror movies, but this one was actually quite good." — Personal preference + opinion.

---

Common Mistakes

1. Confusing "boring" and "bored" "I was boring during the film." → "I was bored during the film." / "The film was boring." "-ed" describes how you feel; "-ing" describes the thing that causes the feeling.

2. Using "see" for books and "read" for movies "I read that movie last week." → "I watched/saw that movie last week." / "I read that book last week." "Watch/see" for visual media (movies, TV); "read" for books and articles.

3. Forgetting "about" when describing plot "It's a thriller a detective who..." → "It's a thriller about a detective who..." "About" introduces the topic/plot of the story.

4. Overusing "good" and "bad" for opinions "The film was good. The music was good." → "The film was impressive. The soundtrack was fantastic." Varying vocabulary (enjoyable, gripping, disappointing, predictable, moving) makes opinions more interesting and specific.

Concept Explanation

Talking about news and current events involves introducing information and reacting to it:

• Introducing a piece of news: "I read that..." (citing a source) / "Have you heard about...?" (checking if the listener already knows) / "Apparently..." (reporting something you're not 100% sure is true — "apparently" signals "I heard this, but I'm not the original source").
• Giving a basic reaction: "That's surprising." / "I didn't know that." / "That's worrying." — short adjective-based reactions that show you're engaged with the news.

"Apparently" is a particularly useful word — it lets you share information while signaling that you're not vouching for its accuracy, which is a natural and common way to discuss news in everyday conversation.

---

Why It Matters

News and current events are common conversation topics — whether discussing world news, local events, or something happening at work:

• Starting conversations: "Have you heard about...?" is a natural conversation opener.
• Sharing information appropriately: "Apparently" and "I read that" show appropriate caution when sharing secondhand information.
• Showing engagement: simple reactions ("That's surprising," "That's worrying") show you're actively listening and processing what's being said — important for natural conversation flow.

---

Additional Examples

1. "Have you heard about the new bridge they're building downtown?" — Introducing news with a question.
2. "I read that the company is planning to open a new office here." — Introducing news with a source.
3. "Apparently, the meeting has been moved to next week." — Reporting unconfirmed information.
4. "That's surprising — I thought it was supposed to happen sooner." — Reaction + follow-up comment.
5. "I didn't know that! When did it happen?" — Reaction + follow-up question.
6. "That's worrying. Do you think it will affect us?" — Reaction expressing concern + question.

---

Common Mistakes

1. Using "apparently" to mean "obviously" "Apparently, the sky is blue." (sounds odd — this is common knowledge, not secondhand information) → "Apparently" is for information you've heard but aren't 100% sure about, not obvious facts.

2. Forgetting "about" after "hear" "Have you heard the news about the strike?" is fine, but "Have you heard the strike?" (without "about" or a clear object) sounds incomplete when introducing a topic — "heard about" is the safer, more general structure.

3. Reacting only with "good" or "bad" "That's bad." → "That's worrying." / "That's a shame." / "That's concerning." More specific reaction adjectives make conversations feel more natural and engaged.

4. Confusing "say" and "read/hear" as sources "I say that the prices are going up." → "I read that prices are going up." / "I heard that prices are going up." "Say" is for what people say directly to you in conversation; "read/hear (about)" are for information from other sources (news, articles, rumors).

Concept Explanation

Describing problems and proposing solutions follows a clear two-step pattern:

• Identifying the problem: "The issue is that..." / "The main problem with... is..." — these phrases clearly frame what follows as a problem, helping the listener focus on the issue itself.
• Proposing solutions: "One solution could be..." / "What if we...?" / "I think we should..." — three different ways to suggest a solution, ranging from tentative ("could be," "what if") to more confident ("I think we should").

"What if we...?" is particularly useful for brainstorming — it proposes an idea as a question, inviting discussion rather than presenting it as a final decision.

---

Why It Matters

Identifying problems and suggesting solutions is central to workplace discussions, group decisions, and everyday problem-solving conversations:

• Constructive communication: framing issues as "the problem is..." (rather than blaming) keeps discussions focused and productive.
• Collaborative brainstorming: "What if we...?" and "One solution could be..." invite others to build on ideas, rather than shutting down discussion.
• Showing initiative: being able to both identify problems and propose solutions (rather than just complaining) is valued in both academic and professional settings.

---

Additional Examples

1. "The issue is that we don't have enough time to finish the project." — Identifying the problem clearly.
2. "The main problem with the current system is that it's too slow." — Specific problem identification.
3. "One solution could be to hire an extra person for a few weeks." — Tentative solution.
4. "What if we moved the deadline to next month?" — Brainstorming solution as a question.
5. "I think we should talk to the manager about this issue directly." — Confident solution proposal.
6. "The main problem with the app is that it crashes too often — one solution could be to update it more regularly." — Problem + solution in one statement.

---

Common Mistakes

1. Stating problems without proposing solutions "The system doesn't work." (just a complaint) → "The system doesn't work well — one solution could be to upgrade it." Adding a solution makes the comment constructive.

2. Using "problem" too vaguely "There's a problem." → "The main problem is that the deadlines are too short." Being specific helps others understand and respond to the actual issue.

3. Confusing "what if" with a real question about the past "What if we moved the deadline?" (a suggestion/proposal) vs. "What happened if we moved the deadline?" (asking about a past result) — "what if" + past simple is for hypothetical suggestions, not asking about real past events.

4. Overusing "I think we should" for every suggestion Repeating "I think we should..." for every idea can sound repetitive — vary with "What if we...?", "One option would be to...", "Maybe we could...".

Concept Explanation

Talking about health and symptoms involves describing how you feel, for how long, and communicating with a doctor:

• Describing symptoms: "I have a headache." / "My throat is sore." / "I've been feeling dizzy." — note the different structures: "have a [noun]" (headache, fever, cold), "[body part] is [adjective]" (throat is sore, leg is swollen), and present perfect continuous "I've been feeling..." for ongoing symptoms.
• Duration of the problem: "I've had a fever for two days." (present perfect + "for" — duration up to now) / "It started this morning." (simple past — when it began).
• At the doctor's office: "Where does it hurt?" (doctor asking for location) / "I'm going to prescribe you..." ("be going to" for an immediate decision/plan the doctor is making).

The combination of present perfect ("I've had...for two days") with simple past ("it started this morning") gives a doctor a clear picture: how long the symptom has lasted, and exactly when it began.

---

Why It Matters

Being able to describe symptoms clearly is essential for getting appropriate medical help, especially when traveling or living abroad:

• Medical emergencies: clear, accurate descriptions help doctors diagnose problems faster.
• Pharmacy visits: describing symptoms ("I have a sore throat and a cough") helps pharmacists recommend appropriate medication.
• Everyday conversations: "How are you feeling?" often leads to brief health updates among friends and family — "I've been feeling a bit under the weather" is common small talk.

---

Additional Examples

1. "I have a really bad headache and I feel a bit nauseous." — Combining symptoms.
2. "My throat has been sore since yesterday." — "Since" + present perfect for duration.
3. "I've been feeling dizzy all morning." — Present perfect continuous for an ongoing symptom.
4. "I've had this cough for about a week now." — "For" + duration of a symptom.
5. "It started suddenly last night, after dinner." — Simple past for the onset.
6. "The doctor asked, 'Where does it hurt?' and I pointed to my lower back." — Doctor's question + response.

---

Common Mistakes

1. Saying "I am pain" instead of "I have pain/I'm in pain" "I am pain in my leg." → "I have pain in my leg." / "My leg hurts." / "I'm in pain." "Pain" is a noun (have pain) or used in the fixed phrase "in pain" — not an adjective on its own.

2. Using simple past instead of present perfect for ongoing symptoms "I had a headache for two days." (suggests it's over) → "I've had a headache for two days." (it's still happening now) Present perfect + "for/since" shows the symptom continues into the present.

3. Confusing "sore," "hurt," and "ache" "My throat hurts" / "My throat is sore" (adjective) are correct, but "I have a stomach hurt" → "I have a stomachache." / "My stomach hurts." "-ache" attaches to certain body parts as a noun (headache, stomachache, toothache, backache); "sore" is an adjective (sore throat, sore muscles); "hurt" is a verb ("it hurts").

4. Misusing "prescribe" "The doctor gave me a prescribe." → "The doctor prescribed some medicine for me." / "The doctor gave me a prescription." "Prescribe" is a verb; "prescription" is the noun (the document/medicine itself).

Concept Explanation

Phrasal verbs (verb + particle, with a meaning often different from the individual words) are grouped here by theme:

• Movement and management: "give up" (to stop trying / quit), "find out" (to discover information), "look after" (to take care of), "carry on" (to continue) — these describe actions related to effort, information, care, and continuation.
• Relationships and communication: "get along with" (to have a good relationship with someone), "fall out with" (to argue and stop being friends with someone), "make up" (to reconcile after an argument), "bring up" (to introduce a topic in conversation).
• Objects and technology: "turn on/off" (to activate/deactivate a device), "plug in" (to connect to an electrical socket), "run out of" (to have no more of something), "set up" (to configure/establish), "back up" (to make a copy of data for safety).

Phrasal verbs are extremely common in spoken English — often more natural than their single-word equivalents (e.g., "find out" vs. "discover", "give up" vs. "quit/abandon").

---

Why It Matters

Phrasal verbs are everywhere in everyday spoken and written English — avoiding them makes language sound overly formal or unnatural:

• Natural conversation: native speakers use phrasal verbs constantly — "I found out yesterday" sounds far more natural than "I discovered yesterday".
• Understanding native speech: phrasal verbs are common in films, podcasts, and conversations — recognizing them is key to comprehension.
• Practical, everyday topics: relationships ("get along with," "fall out with"), technology ("turn on," "plug in," "back up"), and daily tasks ("look after," "run out of") are all areas where phrasal verbs dominate.

---

Additional Examples

1. "I'm trying to give up sugar, but it's really hard." — "Give up" = stop/quit.
2. "I found out that the meeting was cancelled." — "Find out" = discover.
3. "Can you look after my dog while I'm away?" — "Look after" = take care of.
4. "Despite the rain, we decided to carry on with the trip." — "Carry on" = continue.
5. "I get along with most of my colleagues, but I fell out with one of them last year." — Relationship phrasal verbs together.
6. "My phone's battery is almost dead — I need to plug it in and back up my photos before I run out of storage." — Three tech phrasal verbs in one sentence.

---

Common Mistakes

1. Translating phrasal verbs literally "Give up" doesn't mean "dar arriba" — its meaning (to quit/stop trying) is completely different from the individual words. Phrasal verbs must be learned as whole units, not translated word-by-word.

2. Separating inseparable phrasal verbs incorrectly "Look my dog after" → "Look after my dog." Some phrasal verbs (like "look after," "get along with") cannot be separated — the object always comes after the whole phrase.

3. Confusing similar phrasal verbs "Turn on" (activate) vs. "turn up" (increase volume/arrive unexpectedly) — these look similar but have very different meanings; context and the specific particle matter a lot.

4. Overusing single-word equivalents in casual speech While "discover" and "find out" can both be correct, in casual conversation "find out" is far more common — using only formal single-word verbs can make spoken English sound stiff or unnatural.

Concept Explanation

Travel and tourism vocabulary covers three practical areas:

• Documentation and airport: passport, visa, boarding pass, check-in, customs, departure/arrival — the key terms for navigating an airport from arrival to departure. "Check-in" can be a noun (the check-in desk) or part of a verb phrase ("to check in").
• Accommodation: reservation, check-in/check-out, single/double room, half board, full board — "half board" (breakfast + one other meal included) and "full board" (all meals included) are common hotel terms, especially for package holidays.
• Tourist activities: sightseeing, guided tour, local cuisine, souvenir, itinerary — vocabulary for planning and describing what you do on a trip. "Itinerary" specifically means the planned route/schedule of a trip.

Note that "check-in" appears in both airport and hotel contexts, but with related (not identical) meanings — both involve "registering your arrival" at the start of a service.

---

Why It Matters

This vocabulary is essential for anyone traveling internationally — at airports, hotels, and tourist destinations:

• Airport navigation: knowing terms like "boarding pass," "customs," and "departure" helps you follow signs and announcements confidently.
• Booking accommodation: understanding "half board" vs. "full board," and "single" vs. "double" room, helps you choose and book the right option.
• Planning and describing trips: "itinerary," "sightseeing," and "guided tour" are useful both for planning your own trip and for describing it to others afterward.

---

Additional Examples

1. "Don't forget your passport and boarding pass before going through security." — Airport documentation.
2. "We need to go through customs before we can leave the airport." — Airport process.
3. "I've booked a double room with half board for our stay." — Accommodation vocabulary.
4. "What time is check-out? We need to catch an early flight." — Hotel check-out.
5. "On the first day, we did some sightseeing and tried the local cuisine." — Tourist activities.
6. "Our itinerary includes a guided tour of the old town and a day trip to the coast." — Itinerary + activities.

---

Common Mistakes

1. Confusing "travel," "trip," and "journey" "I had a nice travel." → "I had a nice trip." / "I had a nice journey." "Travel" is usually a verb or uncountable noun (general activity); "trip" and "journey" are countable nouns for a specific instance of traveling.

2. Mixing up "half board" and "full board" "Half board" = breakfast + one more meal (usually dinner); "full board" = all three meals included. Confusing these can lead to unexpected costs for meals not included.

3. Using "souvenir" to mean "memory" "I have good souvenirs from my trip" (sounds like physical objects) vs. "I have good memories of my trip" (mental recollections). "Souvenir" specifically refers to a physical object you bring back, not a memory — a classic false friend for Spanish speakers ("recuerdo" can mean both).

4. Forgetting "go through" with customs/security "I passed customs." (less natural) → "I went through customs." / "I went through security." "Go through" is the standard collocation for passing through airport checkpoints.

Concept Explanation

Office and work vocabulary covers tasks/responsibilities and workplace relationships:

• Tasks and responsibilities: deadline (the date by which something must be finished), task (a piece of work to be done), project (a larger, organized piece of work), meeting, report, presentation, target (a goal to be achieved, often with numbers — "sales target").
• Work relationships: colleague (a person you work with, at a similar level), manager (someone who supervises you), team, HR (Human Resources — the department dealing with staff issues), interview, promotion (moving to a higher position), resign (to formally leave a job), hire (to employ someone new).

These words often combine into common collocations: "meet a deadline," "give a presentation," "set a target," "get a promotion," "hand in your resignation".

---

Why It Matters

This vocabulary is essential for anyone working or studying in an English-speaking environment, or discussing their job:

• Daily work conversations: "I have a deadline tomorrow" / "We have a team meeting at 10" — extremely common in any workplace.
• Career discussions: "promotion," "resign," "hire" are key vocabulary for talking about career changes and progress.
• Professional writing: "report," "presentation," "project," "target" appear constantly in emails and documents at work.

---

Additional Examples

1. "I have a deadline on Friday, so I need to finish this report today." — Deadline + report.
2. "Our team has a big project due next month." — Team + project + deadline-related language.
3. "I get along really well with my colleagues, but my manager can be quite demanding." — Colleague vs. manager.
4. "She got a promotion last year after working really hard." — Career progress.
5. "He decided to resign after fifteen years at the company." — Leaving a job.
6. "The company is planning to hire five new people for the marketing team." — Hiring.

---

Common Mistakes

1. Confusing "colleague" and "college" "My college helped me with the report." → "My colleague helped me with the report." "Colleague" (a co-worker) and "college" (an educational institution) sound similar but are completely different words.

2. Using "fire" and "resign" interchangeably "He fired from the company." → "He resigned from the company." (he chose to leave) / "He was fired from the company." (the company removed him) "Resign" = leave voluntarily; "fire/be fired" = the company ends your employment.

3. Saying "make a meeting" instead of "have a meeting" "We will make a meeting tomorrow." → "We will have a meeting tomorrow." / "We're having a meeting tomorrow." "Have a meeting" is the standard collocation, not "make".

4. Confusing "HR" usage "I am HR." → "I work in HR." / "I work for the HR department." "HR" refers to the department, not a job title for a person.

Concept Explanation

This topic provides a range of expressions for agreeing, disagreeing, and staying neutral in discussions:

• Agreement: "That's a good point." (acknowledging the value of someone's argument) / "I couldn't agree more." (strong agreement) / "Absolutely." / "Exactly." (short, emphatic agreement).
• Polite disagreement: "I'm not sure about that." (gentle doubt) / "I see it differently." (stating a different view without confrontation) / "I take your point, but..." (acknowledging before disagreeing — similar to "I see your point, but...").
• Neutral position: "It depends on..." (the answer varies based on a factor) / "There are pros and cons." (both positive and negative aspects exist) / "I can see both sides." (understanding both viewpoints without committing to one).

Having a neutral option ("it depends," "there are pros and cons") is useful when you genuinely don't have a strong opinion, or want to encourage further discussion before committing to a side.

---

Why It Matters

These expressions add nuance and politeness to discussions — moving beyond simple "yes/no" or "I agree/I disagree":

• Richer discussions: "I couldn't agree more" vs. "That's a good point, but I see it differently" show different degrees and types of agreement/disagreement.
• Diplomatic communication: "I take your point, but..." and "I see it differently" allow disagreement without conflict — important in both social and professional settings.
• Balanced thinking: "There are pros and cons" and "I can see both sides" demonstrate critical thinking — valuable in debates, discussions, and essays.

---

Additional Examples

1. "That's a good point — I hadn't thought about it that way." — Agreement + acknowledgment.
2. "I couldn't agree more. This is exactly what we need to do." — Strong agreement.
3. "I'm not sure about that. I think there might be other factors to consider." — Polite disagreement.
4. "I see it differently — I think the benefits outweigh the risks." — Disagreement with reasoning.
5. "It depends on the situation — sometimes it works, sometimes it doesn't." — Neutral position.
6. "There are pros and cons to both options, so it's a difficult decision." — Neutral, balanced view.

---

Common Mistakes

1. Using "I agree" for every level of agreement "I agree." can sound flat compared to "I couldn't agree more" (strong) or "That's a good point" (acknowledging without full commitment) — varying agreement expressions sounds more natural and engaged.

2. Disagreeing too bluntly "That's wrong." → "I'm not sure about that." / "I see it differently." Direct disagreement can sound confrontational — softer phrases maintain a positive tone.

3. Avoiding a position entirely when one is expected Overusing "it depends" / "there are pros and cons" without ever stating your own view can seem evasive — these neutral phrases work best as a starting point before adding your own opinion: "There are pros and cons, but personally, I'd lean towards..."

4. Confusing "I take your point" with full agreement "I take your point, but I still think..." acknowledges the other person's argument without agreeing with it — using it as if it meant full agreement can create confusion in a discussion.

Concept Explanation

Discourse connectors organize ideas by their logical relationship — here grouped into three categories:

• Contrast: "however" / "although" / "even though" / "despite" / "on the other hand" — these introduce a contrasting idea. Note the grammar difference: "although/even though" + clause (subject + verb) vs. "despite" + noun/-ing form ("despite the rain" / "despite raining").
• Cause and result: "because" / "since" / "as" (all introduce a reason/cause, followed by a clause) vs. "therefore" / "as a result" / "consequently" (introduce a result, usually starting a new sentence or clause after a semicolon).
• Addition and sequence: "furthermore" / "in addition" / "also" (adding more information) and "first of all" / "then" / "finally" / "to sum up" (organizing ideas in order, often used in essays and presentations).

A key grammatical distinction: "because/since/as" + clause vs. "because of/due to" + noun — and similarly "although" + clause vs. "despite/in spite of" + noun/-ing.

---

Why It Matters

These connectors are the building blocks of well-organized speech and writing — especially for essays, presentations, and structured arguments:

• Essay writing: "furthermore," "however," "as a result," "to sum up" are essential for organizing paragraphs logically.
• Spoken arguments: "although," "despite," "therefore" help structure more sophisticated spoken opinions and explanations.
• Avoiding repetition: having multiple options for contrast (however/although/despite) and cause-result (because/since/therefore) lets you vary your language and avoid sounding repetitive.

---

Additional Examples

1. "Although it was raining, we decided to go for a walk." — "Although" + clause (contrast).
2. "Despite the rain, we decided to go for a walk." — "Despite" + noun (same meaning, different grammar).
3. "He was tired; however, he continued working." — "However" introducing contrast after a semicolon.
4. "She missed the bus, so she was late. As a result, she missed the meeting." — Cause-result chain.
5. "The project was successful. Furthermore, it came in under budget." — "Furthermore" adding information.
6. "First of all, let's review the budget. Then, we'll discuss the timeline. Finally, we'll assign tasks." — Sequencing connectors organizing a discussion.

---

Common Mistakes

1. Using "despite" with a clause "Despite it was raining, we went out." → "Despite the fact that it was raining, we went out." / "Although it was raining, we went out." / "Despite the rain, we went out." "Despite/in spite of" need a noun or "-ing" form, not a full clause with subject + verb (unless followed by "the fact that").

2. Confusing "because" and "because of" "Because of it was late, we left." → "Because it was late, we left." / "Because of the time, we left." "Because" + clause (subject + verb); "because of" + noun phrase.

3. Using "however" like "but" mid-sentence without correct punctuation "He was tired, however he continued." → "He was tired. However, he continued." / "He was tired; however, he continued." "However" usually starts a new sentence (or follows a semicolon), with a comma after it — unlike "but," which connects two clauses directly.

4. Overloading a single sentence with too many connectors "However, although it was raining, despite the cold, we went out." → choose ONE connector per contrast idea: "Although it was raining and cold, we went out." Using multiple connectors for the same relationship is redundant and confusing.