How to Improve Vocabulary | Frequency and Habit — Use Always, Usually, Often, Sometimes, Occasionally, Rarely and Seldom Precisely

This specialist guide continues the How to Improve Vocabulary series by isolating frequency and habit as a word-choice problem. The purpose is not to collect impressive expressions. It is to make small differences in function visible enough that a learner can choose deliberately, explain the choice, and transfer the distinction into new reading, speaking and writing situations.

Frequency words compress repeated events into a pattern, but most are deliberately vague. Precision comes from matching the word to evidence and context, not pretending each adverb has a universal percentage. The wider complete vocabulary system explains how words are learned and retained. This page is narrower: it owns the precision decisions named in the title and treats neighbouring systems only when they change those decisions.

The same discipline appears throughout the precision strand. Cause and Effect separates reasons from results; Causal Strength separates causal commitment from association; Purpose and Result separates intention from outcome; Comparison and Degree exposes scales and thresholds. Here the learner applies that style of reasoning to frequency and habit.

Strong vocabulary is quiet when it works. The reader does not stop to admire the connector or modifier; the reader simply receives the right relation. That means an ordinary word can be the expert choice. A formal word can be the wrong choice. The test is whether the expression preserves meaning, grammar, register and the writer’s actual evidence.

Quick Read: Frequency Words Are Ordered, Not Fixed Percentages

Always normally makes a universal claim over the relevant set of occasions and therefore creates a heavy evidence burden.

Usually presents something as the normal pattern while allowing exceptions.

Often indicates relatively frequent occurrence but has no fixed universal percentage.

Sometimes marks intermittent occurrence without specifying a stable rate.

Occasionally generally suggests lower frequency than often, but the boundary depends on context.

Rarely and seldom both mark low frequency; register and collocation differ, and neither should be converted into an invented percentage without data.

Scope Boundary

This owner covers qualitative frequency and habitual patterns expressed by always, usually, often, sometimes, occasionally, rarely and seldom. The earlier How to Improve Vocabulary | Frequency page owns a different question: how repeated exposure to a word affects vocabulary learning. Exact proportions and numerical rates belong to Proportion and Ratio; quantifier scope belongs to Scope and Quantifiers. This page therefore owns frequency-as-meaning in sentences, not frequency-of-exposure in learning.

Use the Word-Choice Decision System whenever the difficulty is broader than this topic. Use Scope and Quantifiers for how large a claim becomes, Modality and Certainty for commitment to possibility or necessity, and Contrast and Concession when the main relation is opposition or resistant truth.

1. Core Principles

1. Define the opportunity set

Frequency depends on what counts as an occasion for the event to happen.

2. Always is strong

One genuine counterexample can defeat a universal claim unless the context defines a narrower set.

3. Usually allows exceptions

The normal pattern can coexist with atypical cases.

4. Often is contextual

Twice a day can be often for one event and rare for another.

5. Sometimes is not a number

It should not be assigned a fixed percentage across contexts.

6. Occasionally suggests infrequency

But it is still qualitative unless the writer supplies a count or rate.

7. Rarely and seldom are low-frequency terms

Their naturalness varies by construction and register.

8. Habit and frequency differ

A repeated behaviour can be habitual even if opportunity itself is limited.

9. Reported frequency can be biased

Memory and self-report are not identical to measured counts.

10. Time window matters

Often this week and often over ten years can describe different patterns.

11. Population matters

A group-level frequency statement does not describe every individual.

12. Use numbers when stakes require them

Qualitative adverbs are not substitutes for measured rates when exactness matters.

2. Core Forms

1. always

always has a specific job here. It presents the event or state as holding on every relevant occasion within the understood scope. The nearest trap is usually, which permits exceptions. Test it with this question: What is the relevant set of occasions, and can I defend a universal claim over it?

Model: In this procedure, the safety cover must always be closed before the machine starts. Near miss: The bus is always late because it was late twice this week. Repair: The bus has often been late this week. Universal language should not grow from a tiny sample.

2. usually

usually has a specific job here. It presents a pattern as normal or typical while allowing exceptions. The nearest trap is always, which removes those exceptions. Test it with this question: Is this the dominant pattern rather than an absolute rule?

Model: The library is usually quiet after lunch, although group activities sometimes change that. Near miss: The library is always quiet after lunch, although it is noisy on Fridays. Repair: The library is usually quiet after lunch. An admitted exception often points toward usually.

3. often

often has a specific job here. It describes relatively frequent occurrence without fixing a universal numerical threshold. The nearest trap is sometimes, which is generally less frequent but also context-dependent. Test it with this question: Does the context make the recurrence reasonably high relative to expectations?

Model: During the wet season, afternoon storms often develop quickly. Near miss: The comet often appears once every seventy-five years. Repair: The comet returns on a cycle of roughly seventy-five years. Domain expectations shape what counts as often.

4. sometimes

sometimes has a specific job here. It marks occurrence on some occasions but not others without specifying a stable rate. The nearest trap is occasionally, which often suggests lower frequency. Test it with this question: Do I only need to establish intermittent occurrence?

Model: The sensor sometimes gives a false reading when condensation forms. Near miss: The sensor sometimes fails in exactly 37 percent of trials. Repair: The sensor failed in 37 percent of trials. Use the measured number when exact data are available.

5. occasionally

occasionally has a specific job here. It presents an event as happening from time to time and generally with relatively low frequency. The nearest trap is rarely, which tends to place the event nearer the low end of the frequency scale. Test it with this question: Is the event infrequent but still recurring enough to expect again?

Model: The printer occasionally jams when thick card is loaded. Near miss: The printer occasionally works, when successful printing is the normal pattern. Repair: The printer usually works but occasionally jams. The baseline pattern matters.

6. rarely

rarely has a specific job here. It marks an event as uncommon within the relevant set of opportunities. The nearest trap is never, which makes the stronger claim that the event does not occur. Test it with this question: Are there genuine occurrences, but few relative to the opportunity set?

Model: This species is rarely seen near the city centre. Near miss: This species is never seen near the city centre; three sightings were recorded last year. Repair: This species is rarely seen near the city centre. Evidence of exceptions rules out never.

7. seldom

seldom has a specific job here. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. The nearest trap is rarely, which is often more common and flexible. Test it with this question: Does the register make seldom natural without pretending it has a different fixed rate?

Model: The old path is seldom used during the hottest part of the day. Near miss: The path is seldom used exactly five percent of the time. Repair: The path was used on 5 percent of observed visits. Do not assign invented percentages to qualitative adverbs.

3. Pairwise Decisions

1. always versus usually

always and usually can occupy neighbouring territory, but they are not safe automatic replacements. It presents the event or state as holding on every relevant occasion within the understood scope. It presents a pattern as normal or typical while allowing exceptions. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

2. always versus often

always and often can occupy neighbouring territory, but they are not safe automatic replacements. It presents the event or state as holding on every relevant occasion within the understood scope. It describes relatively frequent occurrence without fixing a universal numerical threshold. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

3. always versus sometimes

always and sometimes can occupy neighbouring territory, but they are not safe automatic replacements. It presents the event or state as holding on every relevant occasion within the understood scope. It marks occurrence on some occasions but not others without specifying a stable rate. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

4. always versus occasionally

always and occasionally can occupy neighbouring territory, but they are not safe automatic replacements. It presents the event or state as holding on every relevant occasion within the understood scope. It presents an event as happening from time to time and generally with relatively low frequency. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

5. always versus rarely

always and rarely can occupy neighbouring territory, but they are not safe automatic replacements. It presents the event or state as holding on every relevant occasion within the understood scope. It marks an event as uncommon within the relevant set of opportunities. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

6. always versus seldom

always and seldom can occupy neighbouring territory, but they are not safe automatic replacements. It presents the event or state as holding on every relevant occasion within the understood scope. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

7. usually versus often

usually and often can occupy neighbouring territory, but they are not safe automatic replacements. It presents a pattern as normal or typical while allowing exceptions. It describes relatively frequent occurrence without fixing a universal numerical threshold. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

8. usually versus sometimes

usually and sometimes can occupy neighbouring territory, but they are not safe automatic replacements. It presents a pattern as normal or typical while allowing exceptions. It marks occurrence on some occasions but not others without specifying a stable rate. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

9. usually versus occasionally

usually and occasionally can occupy neighbouring territory, but they are not safe automatic replacements. It presents a pattern as normal or typical while allowing exceptions. It presents an event as happening from time to time and generally with relatively low frequency. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

10. usually versus rarely

usually and rarely can occupy neighbouring territory, but they are not safe automatic replacements. It presents a pattern as normal or typical while allowing exceptions. It marks an event as uncommon within the relevant set of opportunities. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

11. usually versus seldom

usually and seldom can occupy neighbouring territory, but they are not safe automatic replacements. It presents a pattern as normal or typical while allowing exceptions. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

12. often versus sometimes

often and sometimes can occupy neighbouring territory, but they are not safe automatic replacements. It describes relatively frequent occurrence without fixing a universal numerical threshold. It marks occurrence on some occasions but not others without specifying a stable rate. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

13. often versus occasionally

often and occasionally can occupy neighbouring territory, but they are not safe automatic replacements. It describes relatively frequent occurrence without fixing a universal numerical threshold. It presents an event as happening from time to time and generally with relatively low frequency. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

14. often versus rarely

often and rarely can occupy neighbouring territory, but they are not safe automatic replacements. It describes relatively frequent occurrence without fixing a universal numerical threshold. It marks an event as uncommon within the relevant set of opportunities. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

15. often versus seldom

often and seldom can occupy neighbouring territory, but they are not safe automatic replacements. It describes relatively frequent occurrence without fixing a universal numerical threshold. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

16. sometimes versus occasionally

sometimes and occasionally can occupy neighbouring territory, but they are not safe automatic replacements. It marks occurrence on some occasions but not others without specifying a stable rate. It presents an event as happening from time to time and generally with relatively low frequency. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

17. sometimes versus rarely

sometimes and rarely can occupy neighbouring territory, but they are not safe automatic replacements. It marks occurrence on some occasions but not others without specifying a stable rate. It marks an event as uncommon within the relevant set of opportunities. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

18. sometimes versus seldom

sometimes and seldom can occupy neighbouring territory, but they are not safe automatic replacements. It marks occurrence on some occasions but not others without specifying a stable rate. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

19. occasionally versus rarely

occasionally and rarely can occupy neighbouring territory, but they are not safe automatic replacements. It presents an event as happening from time to time and generally with relatively low frequency. It marks an event as uncommon within the relevant set of opportunities. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

20. occasionally versus seldom

occasionally and seldom can occupy neighbouring territory, but they are not safe automatic replacements. It presents an event as happening from time to time and generally with relatively low frequency. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

21. rarely versus seldom

rarely and seldom can occupy neighbouring territory, but they are not safe automatic replacements. It marks an event as uncommon within the relevant set of opportunities. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. To choose, identify the writer’s intended relation, the grammar that follows, the strength of the claim and the likely reader inference. Substitution is useful as a test precisely because a good substitution exposes what the original expression was doing.

4. Precision Laboratory: Ninety Decisions

1. always: a data commentary

In a data commentary, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check logical direction before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

2. usually: a comprehension answer

In a comprehension answer, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check reference set before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

3. often: a formal email

In a formal email, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check scope before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

4. sometimes: a research summary

In a research summary, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check logical direction before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

5. occasionally: a literature response

In a literature response, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check reference set before elegance. Explain the difference in reference set. Do not accept “it sounds better” as the final answer; name the meaning relation.

6. rarely: a comparison review

In a comparison review, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check scope before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

7. seldom: an argumentative paragraph

In an argumentative paragraph, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check logical direction before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

8. always: a reflective journal

In a reflective journal, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check reference set before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

9. usually: a history essay

In a history essay, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check scope before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

10. often: a speech

In a speech, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check logical direction before elegance. Explain the difference in logical direction. Do not accept “it sounds better” as the final answer; name the meaning relation.

11. sometimes: a public notice

In a public notice, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check reference set before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

12. occasionally: a parent-teacher note

In a parent-teacher note, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check scope before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

13. rarely: a problem-solution paragraph

In a problem-solution paragraph, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check logical direction before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

14. seldom: a school report

In a school report, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check reference set before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

15. always: a narrative scene

In a narrative scene, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check scope before elegance. Explain the difference in scope. Do not accept “it sounds better” as the final answer; name the meaning relation.

16. usually: a geography response

In a geography response, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check logical direction before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

17. often: a project evaluation

In a project evaluation, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check reference set before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

18. sometimes: a set of instructions

In a set of instructions, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check scope before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

19. occasionally: an oral answer

In an oral answer, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check logical direction before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

20. rarely: a science explanation

In a science explanation, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check reference set before elegance. Explain the difference in reference set. Do not accept “it sounds better” as the final answer; name the meaning relation.

21. seldom: a data commentary

In a data commentary, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check scope before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

22. always: a comprehension answer

In a comprehension answer, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check logical direction before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

23. usually: a formal email

In a formal email, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check reference set before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

24. often: a research summary

In a research summary, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check scope before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

25. sometimes: a literature response

In a literature response, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check logical direction before elegance. Explain the difference in logical direction. Do not accept “it sounds better” as the final answer; name the meaning relation.

26. occasionally: a comparison review

In a comparison review, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check reference set before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

27. rarely: an argumentative paragraph

In an argumentative paragraph, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check scope before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

28. seldom: a reflective journal

In a reflective journal, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check logical direction before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

29. always: a history essay

In a history essay, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check reference set before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

30. usually: a speech

In a speech, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check scope before elegance. Explain the difference in scope. Do not accept “it sounds better” as the final answer; name the meaning relation.

31. often: a public notice

In a public notice, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check logical direction before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

32. sometimes: a parent-teacher note

In a parent-teacher note, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check reference set before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

33. occasionally: a problem-solution paragraph

In a problem-solution paragraph, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check scope before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

34. rarely: a school report

In a school report, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check logical direction before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

35. seldom: a narrative scene

In a narrative scene, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check reference set before elegance. Explain the difference in reference set. Do not accept “it sounds better” as the final answer; name the meaning relation.

36. always: a geography response

In a geography response, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check scope before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

37. usually: a project evaluation

In a project evaluation, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check logical direction before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

38. often: a set of instructions

In a set of instructions, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check reference set before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

39. sometimes: an oral answer

In an oral answer, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check scope before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

40. occasionally: a science explanation

In a science explanation, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check logical direction before elegance. Explain the difference in logical direction. Do not accept “it sounds better” as the final answer; name the meaning relation.

41. rarely: a data commentary

In a data commentary, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check reference set before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

42. seldom: a comprehension answer

In a comprehension answer, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check scope before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

43. always: a formal email

In a formal email, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check logical direction before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

44. usually: a research summary

In a research summary, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check reference set before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

45. often: a literature response

In a literature response, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check scope before elegance. Explain the difference in scope. Do not accept “it sounds better” as the final answer; name the meaning relation.

46. sometimes: a comparison review

In a comparison review, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check logical direction before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

47. occasionally: an argumentative paragraph

In an argumentative paragraph, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check reference set before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

48. rarely: a reflective journal

In a reflective journal, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check scope before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

49. seldom: a history essay

In a history essay, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check logical direction before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

50. always: a speech

In a speech, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check reference set before elegance. Explain the difference in reference set. Do not accept “it sounds better” as the final answer; name the meaning relation.

51. usually: a public notice

In a public notice, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check scope before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

52. often: a parent-teacher note

In a parent-teacher note, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check logical direction before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

53. sometimes: a problem-solution paragraph

In a problem-solution paragraph, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check reference set before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

54. occasionally: a school report

In a school report, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check scope before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

55. rarely: a narrative scene

In a narrative scene, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check logical direction before elegance. Explain the difference in logical direction. Do not accept “it sounds better” as the final answer; name the meaning relation.

56. seldom: a geography response

In a geography response, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check reference set before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

57. always: a project evaluation

In a project evaluation, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check scope before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

58. usually: a set of instructions

In a set of instructions, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check logical direction before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

59. often: an oral answer

In an oral answer, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check reference set before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

60. sometimes: a science explanation

In a science explanation, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check scope before elegance. Explain the difference in scope. Do not accept “it sounds better” as the final answer; name the meaning relation.

61. occasionally: a data commentary

In a data commentary, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check logical direction before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

62. rarely: a comprehension answer

In a comprehension answer, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check reference set before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

63. seldom: a formal email

In a formal email, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check scope before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

64. always: a research summary

In a research summary, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check logical direction before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

65. usually: a literature response

In a literature response, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check reference set before elegance. Explain the difference in reference set. Do not accept “it sounds better” as the final answer; name the meaning relation.

66. often: a comparison review

In a comparison review, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check scope before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

67. sometimes: an argumentative paragraph

In an argumentative paragraph, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check logical direction before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

68. occasionally: a reflective journal

In a reflective journal, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check reference set before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

69. rarely: a history essay

In a history essay, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check scope before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

70. seldom: a speech

In a speech, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check logical direction before elegance. Explain the difference in logical direction. Do not accept “it sounds better” as the final answer; name the meaning relation.

71. always: a public notice

In a public notice, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check reference set before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

72. usually: a parent-teacher note

In a parent-teacher note, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check scope before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

73. often: a problem-solution paragraph

In a problem-solution paragraph, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check logical direction before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

74. sometimes: a school report

In a school report, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check reference set before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

75. occasionally: a narrative scene

In a narrative scene, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check scope before elegance. Explain the difference in scope. Do not accept “it sounds better” as the final answer; name the meaning relation.

76. rarely: a geography response

In a geography response, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check logical direction before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

77. seldom: a project evaluation

In a project evaluation, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check reference set before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

78. always: a set of instructions

In a set of instructions, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check scope before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

79. usually: an oral answer

In an oral answer, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check logical direction before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

80. often: a science explanation

In a science explanation, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check reference set before elegance. Explain the difference in reference set. Do not accept “it sounds better” as the final answer; name the meaning relation.

81. sometimes: a data commentary

In a data commentary, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check scope before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

82. occasionally: a comprehension answer

In a comprehension answer, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check logical direction before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

83. rarely: a formal email

In a formal email, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check reference set before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

84. seldom: a research summary

In a research summary, decide whether seldom is licensed by the intended meaning. Start from the model “The old path is seldom used during the hottest part of the day.” and compare it with “The path is seldom used exactly five percent of the time.” and “The path was used on 5 percent of observed visits.”. Check scope before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

85. always: a literature response

In a literature response, decide whether always is licensed by the intended meaning. Start from the model “In this procedure, the safety cover must always be closed before the machine starts.” and compare it with “The bus is always late because it was late twice this week.” and “The bus has often been late this week.”. Check logical direction before elegance. Explain the difference in logical direction. Do not accept “it sounds better” as the final answer; name the meaning relation.

86. usually: a comparison review

In a comparison review, decide whether usually is licensed by the intended meaning. Start from the model “The library is usually quiet after lunch, although group activities sometimes change that.” and compare it with “The library is always quiet after lunch, although it is noisy on Fridays.” and “The library is usually quiet after lunch.”. Check reference set before elegance. Paraphrase the relation without the target expression, then put the expression back only if it earns its place.

87. often: an argumentative paragraph

In an argumentative paragraph, decide whether often is licensed by the intended meaning. Start from the model “During the wet season, afternoon storms often develop quickly.” and compare it with “The comet often appears once every seventy-five years.” and “The comet returns on a cycle of roughly seventy-five years.”. Check scope before elegance. Write a second example on an unrelated topic. Transfer, not repetition, is the stronger test of control.

88. sometimes: a reflective journal

In a reflective journal, decide whether sometimes is licensed by the intended meaning. Start from the model “The sensor sometimes gives a false reading when condensation forms.” and compare it with “The sensor sometimes fails in exactly 37 percent of trials.” and “The sensor failed in 37 percent of trials.”. Check logical direction before elegance. Ask what a careful reader would infer. If that inference is stronger than the evidence, revise.

89. occasionally: a history essay

In a history essay, decide whether occasionally is licensed by the intended meaning. Start from the model “The printer occasionally jams when thick card is loaded.” and compare it with “The printer occasionally works, when successful printing is the normal pattern.” and “The printer usually works but occasionally jams.”. Check reference set before elegance. Compare with the simplest possible wording. Keep the specialist form only when it preserves a useful distinction.

90. rarely: a speech

In a speech, decide whether rarely is licensed by the intended meaning. Start from the model “This species is rarely seen near the city centre.” and compare it with “This species is never seen near the city centre; three sightings were recorded last year.” and “This species is rarely seen near the city centre.”. Check scope before elegance. Explain the difference in scope. Do not accept “it sounds better” as the final answer; name the meaning relation.

5. Genre Transfer

1. academic essay

In a academic essay, the choice of always should be driven by the relation the sentence needs. It presents the event or state as holding on every relevant occasion within the understood scope. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

2. science report

In a science report, the choice of usually should be driven by the relation the sentence needs. It presents a pattern as normal or typical while allowing exceptions. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

3. history essay

In a history essay, the choice of often should be driven by the relation the sentence needs. It describes relatively frequent occurrence without fixing a universal numerical threshold. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

4. geography response

In a geography response, the choice of sometimes should be driven by the relation the sentence needs. It marks occurrence on some occasions but not others without specifying a stable rate. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

5. literature analysis

In a literature analysis, the choice of occasionally should be driven by the relation the sentence needs. It presents an event as happening from time to time and generally with relatively low frequency. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

6. comprehension answer

In a comprehension answer, the choice of rarely should be driven by the relation the sentence needs. It marks an event as uncommon within the relevant set of opportunities. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

7. creative writing

In a creative writing, the choice of seldom should be driven by the relation the sentence needs. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

8. reflective writing

In a reflective writing, the choice of always should be driven by the relation the sentence needs. It presents the event or state as holding on every relevant occasion within the understood scope. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

9. formal email

In a formal email, the choice of usually should be driven by the relation the sentence needs. It presents a pattern as normal or typical while allowing exceptions. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

10. speech

In a speech, the choice of often should be driven by the relation the sentence needs. It describes relatively frequent occurrence without fixing a universal numerical threshold. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

11. data commentary

In a data commentary, the choice of sometimes should be driven by the relation the sentence needs. It marks occurrence on some occasions but not others without specifying a stable rate. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

12. project evaluation

In a project evaluation, the choice of occasionally should be driven by the relation the sentence needs. It presents an event as happening from time to time and generally with relatively low frequency. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

13. research summary

In a research summary, the choice of rarely should be driven by the relation the sentence needs. It marks an event as uncommon within the relevant set of opportunities. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

14. instructions

In a instructions, the choice of seldom should be driven by the relation the sentence needs. It also marks low frequency and is often slightly more formal or literary than rarely in contemporary usage. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

15. public notice

In a public notice, the choice of always should be driven by the relation the sentence needs. It presents the event or state as holding on every relevant occasion within the understood scope. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

16. oral presentation

In a oral presentation, the choice of usually should be driven by the relation the sentence needs. It presents a pattern as normal or typical while allowing exceptions. Write one accurate version, one deliberate near miss and one plain-English paraphrase. The three versions force the learner to separate the underlying function from the surface vocabulary.

6. Error Clinic

1. Diagnose the intended relation first

When often looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test register, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

2. Diagnose the intended relation first

When occasionally looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test punctuation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

3. Diagnose the intended relation first

When seldom looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test claim strength, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

4. Diagnose the intended relation first

When usually looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test reader expectation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

5. Diagnose the intended relation first

When sometimes looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test logical direction, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

6. Diagnose the intended relation first

When rarely looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test ambiguity, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

7. Diagnose the intended relation first

When always looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test evidence, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

8. Diagnose the intended relation first

When often looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test sentence rhythm, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

9. Diagnose the intended relation first

When occasionally looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test cohesion, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

10. Diagnose the intended relation first

When seldom looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test reference set, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

11. Diagnose the intended relation first

When usually looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test threshold, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

12. Diagnose the intended relation first

When sometimes looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test frequency interpretation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

13. Diagnose the intended relation first

When rarely looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test precision, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

14. Diagnose the intended relation first

When always looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test tone, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

15. Diagnose the intended relation first

When often looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test scope, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

16. Diagnose the intended relation first

When occasionally looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test register, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

17. Diagnose the intended relation first

When seldom looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test punctuation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

18. Diagnose the intended relation first

When usually looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test claim strength, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

19. Diagnose the intended relation first

When sometimes looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test reader expectation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

20. Diagnose the intended relation first

When rarely looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test logical direction, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

21. Diagnose the intended relation first

When always looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test ambiguity, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

22. Diagnose the intended relation first

When often looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test evidence, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

23. Diagnose the intended relation first

When occasionally looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test sentence rhythm, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

24. Diagnose the intended relation first

When seldom looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test cohesion, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

25. Diagnose the intended relation first

When usually looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test reference set, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

26. Diagnose the intended relation first

When sometimes looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test threshold, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

27. Diagnose the intended relation first

When rarely looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test frequency interpretation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

28. Diagnose the intended relation first

When always looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test precision, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

29. Diagnose the intended relation first

When often looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test tone, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

30. Diagnose the intended relation first

When occasionally looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test scope, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

31. Diagnose the intended relation first

When seldom looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test register, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

32. Diagnose the intended relation first

When usually looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test punctuation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

33. Diagnose the intended relation first

When sometimes looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test claim strength, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

34. Diagnose the intended relation first

When rarely looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test reader expectation, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

35. Diagnose the intended relation first

When always looks wrong, do not begin by swapping vocabulary. State what the writer means, identify the grammatical structure, test logical direction, compare the nearest alternative and then revise. A locally fluent replacement can still damage the paragraph if it changes the logic. Correction should restore the intended relation, not merely produce a sentence that sounds more formal.

7. Retrieval Workbook

1. Build, replace, explain

Write a sentence in a speech that genuinely needs sometimes. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

2. Build, replace, explain

Write a sentence in a project evaluation that genuinely needs occasionally. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

3. Build, replace, explain

Write a sentence in a research summary that genuinely needs rarely. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

4. Build, replace, explain

Write a sentence in a public notice that genuinely needs seldom. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

5. Build, replace, explain

Write a sentence in a set of instructions that genuinely needs always. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

6. Build, replace, explain

Write a sentence in a literature response that genuinely needs usually. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

7. Build, replace, explain

Write a sentence in a parent-teacher note that genuinely needs often. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

8. Build, replace, explain

Write a sentence in an oral answer that genuinely needs sometimes. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

9. Build, replace, explain

Write a sentence in a comparison review that genuinely needs occasionally. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

10. Build, replace, explain

Write a sentence in a problem-solution paragraph that genuinely needs rarely. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

11. Build, replace, explain

Write a sentence in a science explanation that genuinely needs seldom. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

12. Build, replace, explain

Write a sentence in an argumentative paragraph that genuinely needs always. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

13. Build, replace, explain

Write a sentence in a school report that genuinely needs usually. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

14. Build, replace, explain

Write a sentence in a data commentary that genuinely needs often. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

15. Build, replace, explain

Write a sentence in a reflective journal that genuinely needs sometimes. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

16. Build, replace, explain

Write a sentence in a narrative scene that genuinely needs occasionally. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

17. Build, replace, explain

Write a sentence in a comprehension answer that genuinely needs rarely. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

18. Build, replace, explain

Write a sentence in a history essay that genuinely needs seldom. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

19. Build, replace, explain

Write a sentence in a geography response that genuinely needs always. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

20. Build, replace, explain

Write a sentence in a formal email that genuinely needs usually. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

21. Build, replace, explain

Write a sentence in a speech that genuinely needs often. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

22. Build, replace, explain

Write a sentence in a project evaluation that genuinely needs sometimes. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

23. Build, replace, explain

Write a sentence in a research summary that genuinely needs occasionally. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

24. Build, replace, explain

Write a sentence in a public notice that genuinely needs rarely. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

25. Build, replace, explain

Write a sentence in a set of instructions that genuinely needs seldom. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

26. Build, replace, explain

Write a sentence in a literature response that genuinely needs always. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

27. Build, replace, explain

Write a sentence in a parent-teacher note that genuinely needs usually. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

28. Build, replace, explain

Write a sentence in an oral answer that genuinely needs often. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

29. Build, replace, explain

Write a sentence in a comparison review that genuinely needs sometimes. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

30. Build, replace, explain

Write a sentence in a problem-solution paragraph that genuinely needs occasionally. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

31. Build, replace, explain

Write a sentence in a science explanation that genuinely needs rarely. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

32. Build, replace, explain

Write a sentence in an argumentative paragraph that genuinely needs seldom. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

33. Build, replace, explain

Write a sentence in a school report that genuinely needs always. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

34. Build, replace, explain

Write a sentence in a data commentary that genuinely needs usually. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

35. Build, replace, explain

Write a sentence in a reflective journal that genuinely needs often. Replace it with the nearest alternative. Under the two sentences, write four short labels: intended relation, grammar, reader inference and register. Finish with a third example on a different subject. The exercise is complete only when the explanation predicts why the alternatives behave differently.

8. Teaching and Independent Practice

For independent study, collect real sentences rather than isolated words. Mark the decision point, predict the function, check the surrounding clause or phrase, and record one contrastive example. Revisit it later by rebuilding rather than rereading. The point is to retrieve the distinction, not merely recognise the page.

For teaching, ask replacement questions: “What changes if we use the other form?” “Does the sentence become stronger, weaker, broader, narrower or simply different?” “What grammar has to change?” These questions expose partial knowledge quickly and make feedback more useful than a correct/incorrect mark alone.

9. Further Study

For general reference, see the British Council English grammar reference and Cambridge Dictionary grammar reference. Qualitative frequency should hand off to Proportion and Ratio when exact rates or percentages are available, to Approximation and Precision when only an estimate or bound is justified, and to Scope and Quantifiers when the problem is how many cases the claim covers. The older Frequency page remains the owner for frequency of vocabulary exposure in learning.

10. Final Checklist

1. What relation am I expressing?

Final check: 1. What relation am I expressing? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

2. What does the form grammatically attach to?

Final check: 2. What does the form grammatically attach to? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

3. What scope does it have?

Final check: 3. What scope does it have? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

4. What would the nearest alternative change?

Final check: 4. What would the nearest alternative change? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

5. Is the register appropriate?

Final check: 5. Is the register appropriate? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

6. Does the evidence justify the wording?

Final check: 6. Does the evidence justify the wording? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

7. Could the reader infer more than I intend?

Final check: 7. Could the reader infer more than I intend? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

8. Can I paraphrase the relation plainly?

Final check: 8. Can I paraphrase the relation plainly? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

9. Can I use the same function in a new context?

Final check: 9. Can I use the same function in a new context? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

10. Is the simplest accurate form already enough?

Final check: 10. Is the simplest accurate form already enough? State the intended relationship, identify the nearest competing expression, and explain one concrete reason the chosen wording is more accurate. If the answer depends only on “it sounds better”, revise again.

Advanced Application: Transfer Problems

Application 1: always — a science explanation

In a science explanation, write one sentence that genuinely needs always. Then replace it with the closest alternative and explain what changes in opportunity set. Move the same distinction into a comprehension answer without copying the original wording. Finish by naming one context in which always would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 2: usually — an oral response

Build a three-sentence mini-example in an oral response: first establish the context, then use usually, then write a correction that would be needed if time window changed. Rework the example for a geography explanation. This tests whether usually is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 3: often — a public notice

Imagine a careful editor questions often in a public notice. Defend it by identifying the intended relation and the evidence that supports universal versus typical claim. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a classroom discussion. A strong answer makes the boundary of use visible as well as the successful use.

Application 4: sometimes — a reflective paragraph

Write two versions of the same idea in a reflective paragraph: one with sometimes, one without it. Compare the reader’s likely interpretation, paying particular attention to low-frequency wording. Then change the audience and rewrite the idea for a report conclusion. The goal is not to preserve the word; it is to preserve the meaning. Keep sometimes only when it earns its place.

Application 5: occasionally — a short speech

Create a deliberate near miss with occasionally in a short speech, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention habit versus measured frequency. Then create a fresh correct example in a history paragraph. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 6: rarely — a data commentary

In a data commentary, write one sentence that genuinely needs rarely. Then replace it with the closest alternative and explain what changes in qualitative versus numerical frequency. Move the same distinction into a project evaluation without copying the original wording. Finish by naming one context in which rarely would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 7: seldom — a narrative scene

Build a three-sentence mini-example in a narrative scene: first establish the context, then use seldom, then write a correction that would be needed if exceptions to the pattern changed. Rework the example for a research summary. This tests whether seldom is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 8: always — a literature response

Imagine a careful editor questions always in a literature response. Defend it by identifying the intended relation and the evidence that supports opportunity set. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a technical note. A strong answer makes the boundary of use visible as well as the successful use.

Application 9: usually — a comparison review

Write two versions of the same idea in a comparison review: one with usually, one without it. Compare the reader’s likely interpretation, paying particular attention to time window. Then change the audience and rewrite the idea for a problem-solution paragraph. The goal is not to preserve the word; it is to preserve the meaning. Keep usually only when it earns its place.

Application 10: often — a revision note

Create a deliberate near miss with often in a revision note, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention universal versus typical claim. Then create a fresh correct example in a policy note. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 11: sometimes — a formal email

In a formal email, write one sentence that genuinely needs sometimes. Then replace it with the closest alternative and explain what changes in low-frequency wording. Move the same distinction into a parent update without copying the original wording. Finish by naming one context in which sometimes would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 12: occasionally — a comprehension answer

Build a three-sentence mini-example in a comprehension answer: first establish the context, then use occasionally, then write a correction that would be needed if habit versus measured frequency changed. Rework the example for a set of instructions. This tests whether occasionally is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 13: rarely — a geography explanation

Imagine a careful editor questions rarely in a geography explanation. Defend it by identifying the intended relation and the evidence that supports qualitative versus numerical frequency. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in an exam response. A strong answer makes the boundary of use visible as well as the successful use.

Application 14: seldom — a classroom discussion

Write two versions of the same idea in a classroom discussion: one with seldom, one without it. Compare the reader’s likely interpretation, paying particular attention to exceptions to the pattern. Then change the audience and rewrite the idea for a science explanation. The goal is not to preserve the word; it is to preserve the meaning. Keep seldom only when it earns its place.

Application 15: always — a report conclusion

Create a deliberate near miss with always in a report conclusion, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention opportunity set. Then create a fresh correct example in an oral response. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 16: usually — a history paragraph

In a history paragraph, write one sentence that genuinely needs usually. Then replace it with the closest alternative and explain what changes in time window. Move the same distinction into a public notice without copying the original wording. Finish by naming one context in which usually would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 17: often — a project evaluation

Build a three-sentence mini-example in a project evaluation: first establish the context, then use often, then write a correction that would be needed if universal versus typical claim changed. Rework the example for a reflective paragraph. This tests whether often is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 18: sometimes — a research summary

Imagine a careful editor questions sometimes in a research summary. Defend it by identifying the intended relation and the evidence that supports low-frequency wording. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a short speech. A strong answer makes the boundary of use visible as well as the successful use.

Application 19: occasionally — a technical note

Write two versions of the same idea in a technical note: one with occasionally, one without it. Compare the reader’s likely interpretation, paying particular attention to habit versus measured frequency. Then change the audience and rewrite the idea for a data commentary. The goal is not to preserve the word; it is to preserve the meaning. Keep occasionally only when it earns its place.

Application 20: rarely — a problem-solution paragraph

Create a deliberate near miss with rarely in a problem-solution paragraph, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention qualitative versus numerical frequency. Then create a fresh correct example in a narrative scene. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 21: seldom — a policy note

In a policy note, write one sentence that genuinely needs seldom. Then replace it with the closest alternative and explain what changes in exceptions to the pattern. Move the same distinction into a literature response without copying the original wording. Finish by naming one context in which seldom would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 22: always — a parent update

Build a three-sentence mini-example in a parent update: first establish the context, then use always, then write a correction that would be needed if opportunity set changed. Rework the example for a comparison review. This tests whether always is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 23: usually — a set of instructions

Imagine a careful editor questions usually in a set of instructions. Defend it by identifying the intended relation and the evidence that supports time window. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a revision note. A strong answer makes the boundary of use visible as well as the successful use.

Application 24: often — an exam response

Write two versions of the same idea in an exam response: one with often, one without it. Compare the reader’s likely interpretation, paying particular attention to universal versus typical claim. Then change the audience and rewrite the idea for a formal email. The goal is not to preserve the word; it is to preserve the meaning. Keep often only when it earns its place.

Application 25: sometimes — a science explanation

Create a deliberate near miss with sometimes in a science explanation, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention low-frequency wording. Then create a fresh correct example in a comprehension answer. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 26: occasionally — an oral response

In an oral response, write one sentence that genuinely needs occasionally. Then replace it with the closest alternative and explain what changes in habit versus measured frequency. Move the same distinction into a geography explanation without copying the original wording. Finish by naming one context in which occasionally would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 27: rarely — a public notice

Build a three-sentence mini-example in a public notice: first establish the context, then use rarely, then write a correction that would be needed if qualitative versus numerical frequency changed. Rework the example for a classroom discussion. This tests whether rarely is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 28: seldom — a reflective paragraph

Imagine a careful editor questions seldom in a reflective paragraph. Defend it by identifying the intended relation and the evidence that supports exceptions to the pattern. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a report conclusion. A strong answer makes the boundary of use visible as well as the successful use.

Application 29: always — a short speech

Write two versions of the same idea in a short speech: one with always, one without it. Compare the reader’s likely interpretation, paying particular attention to opportunity set. Then change the audience and rewrite the idea for a history paragraph. The goal is not to preserve the word; it is to preserve the meaning. Keep always only when it earns its place.

Application 30: usually — a data commentary

Create a deliberate near miss with usually in a data commentary, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention time window. Then create a fresh correct example in a project evaluation. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 31: often — a narrative scene

In a narrative scene, write one sentence that genuinely needs often. Then replace it with the closest alternative and explain what changes in universal versus typical claim. Move the same distinction into a research summary without copying the original wording. Finish by naming one context in which often would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 32: sometimes — a literature response

Build a three-sentence mini-example in a literature response: first establish the context, then use sometimes, then write a correction that would be needed if low-frequency wording changed. Rework the example for a technical note. This tests whether sometimes is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 33: occasionally — a comparison review

Imagine a careful editor questions occasionally in a comparison review. Defend it by identifying the intended relation and the evidence that supports habit versus measured frequency. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a problem-solution paragraph. A strong answer makes the boundary of use visible as well as the successful use.

Application 34: rarely — a revision note

Write two versions of the same idea in a revision note: one with rarely, one without it. Compare the reader’s likely interpretation, paying particular attention to qualitative versus numerical frequency. Then change the audience and rewrite the idea for a policy note. The goal is not to preserve the word; it is to preserve the meaning. Keep rarely only when it earns its place.

Application 35: seldom — a formal email

Create a deliberate near miss with seldom in a formal email, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention exceptions to the pattern. Then create a fresh correct example in a parent update. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 36: always — a comprehension answer

In a comprehension answer, write one sentence that genuinely needs always. Then replace it with the closest alternative and explain what changes in opportunity set. Move the same distinction into a set of instructions without copying the original wording. Finish by naming one context in which always would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 37: usually — a geography explanation

Build a three-sentence mini-example in a geography explanation: first establish the context, then use usually, then write a correction that would be needed if time window changed. Rework the example for an exam response. This tests whether usually is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 38: often — a classroom discussion

Imagine a careful editor questions often in a classroom discussion. Defend it by identifying the intended relation and the evidence that supports universal versus typical claim. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a science explanation. A strong answer makes the boundary of use visible as well as the successful use.

Application 39: sometimes — a report conclusion

Write two versions of the same idea in a report conclusion: one with sometimes, one without it. Compare the reader’s likely interpretation, paying particular attention to low-frequency wording. Then change the audience and rewrite the idea for an oral response. The goal is not to preserve the word; it is to preserve the meaning. Keep sometimes only when it earns its place.

Application 40: occasionally — a history paragraph

Create a deliberate near miss with occasionally in a history paragraph, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention habit versus measured frequency. Then create a fresh correct example in a public notice. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 41: rarely — a project evaluation

In a project evaluation, write one sentence that genuinely needs rarely. Then replace it with the closest alternative and explain what changes in qualitative versus numerical frequency. Move the same distinction into a reflective paragraph without copying the original wording. Finish by naming one context in which rarely would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 42: seldom — a research summary

Build a three-sentence mini-example in a research summary: first establish the context, then use seldom, then write a correction that would be needed if exceptions to the pattern changed. Rework the example for a short speech. This tests whether seldom is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 43: always — a technical note

Imagine a careful editor questions always in a technical note. Defend it by identifying the intended relation and the evidence that supports opportunity set. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a data commentary. A strong answer makes the boundary of use visible as well as the successful use.

Application 44: usually — a problem-solution paragraph

Write two versions of the same idea in a problem-solution paragraph: one with usually, one without it. Compare the reader’s likely interpretation, paying particular attention to time window. Then change the audience and rewrite the idea for a narrative scene. The goal is not to preserve the word; it is to preserve the meaning. Keep usually only when it earns its place.

Application 45: often — a policy note

Create a deliberate near miss with often in a policy note, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention universal versus typical claim. Then create a fresh correct example in a literature response. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 46: sometimes — a parent update

In a parent update, write one sentence that genuinely needs sometimes. Then replace it with the closest alternative and explain what changes in low-frequency wording. Move the same distinction into a comparison review without copying the original wording. Finish by naming one context in which sometimes would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 47: occasionally — a set of instructions

Build a three-sentence mini-example in a set of instructions: first establish the context, then use occasionally, then write a correction that would be needed if habit versus measured frequency changed. Rework the example for a revision note. This tests whether occasionally is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 48: rarely — an exam response

Imagine a careful editor questions rarely in an exam response. Defend it by identifying the intended relation and the evidence that supports qualitative versus numerical frequency. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a formal email. A strong answer makes the boundary of use visible as well as the successful use.

Application 49: seldom — a science explanation

Write two versions of the same idea in a science explanation: one with seldom, one without it. Compare the reader’s likely interpretation, paying particular attention to exceptions to the pattern. Then change the audience and rewrite the idea for a comprehension answer. The goal is not to preserve the word; it is to preserve the meaning. Keep seldom only when it earns its place.

Application 50: always — an oral response

Create a deliberate near miss with always in an oral response, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention opportunity set. Then create a fresh correct example in a geography explanation. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 51: usually — a public notice

In a public notice, write one sentence that genuinely needs usually. Then replace it with the closest alternative and explain what changes in time window. Move the same distinction into a classroom discussion without copying the original wording. Finish by naming one context in which usually would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 52: often — a reflective paragraph

Build a three-sentence mini-example in a reflective paragraph: first establish the context, then use often, then write a correction that would be needed if universal versus typical claim changed. Rework the example for a report conclusion. This tests whether often is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 53: sometimes — a short speech

Imagine a careful editor questions sometimes in a short speech. Defend it by identifying the intended relation and the evidence that supports low-frequency wording. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a history paragraph. A strong answer makes the boundary of use visible as well as the successful use.

Application 54: occasionally — a data commentary

Write two versions of the same idea in a data commentary: one with occasionally, one without it. Compare the reader’s likely interpretation, paying particular attention to habit versus measured frequency. Then change the audience and rewrite the idea for a project evaluation. The goal is not to preserve the word; it is to preserve the meaning. Keep occasionally only when it earns its place.

Application 55: rarely — a narrative scene

Create a deliberate near miss with rarely in a narrative scene, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention qualitative versus numerical frequency. Then create a fresh correct example in a research summary. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 56: seldom — a literature response

In a literature response, write one sentence that genuinely needs seldom. Then replace it with the closest alternative and explain what changes in exceptions to the pattern. Move the same distinction into a technical note without copying the original wording. Finish by naming one context in which seldom would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 57: always — a comparison review

Build a three-sentence mini-example in a comparison review: first establish the context, then use always, then write a correction that would be needed if opportunity set changed. Rework the example for a problem-solution paragraph. This tests whether always is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 58: usually — a revision note

Imagine a careful editor questions usually in a revision note. Defend it by identifying the intended relation and the evidence that supports time window. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a policy note. A strong answer makes the boundary of use visible as well as the successful use.

Application 59: often — a formal email

Write two versions of the same idea in a formal email: one with often, one without it. Compare the reader’s likely interpretation, paying particular attention to universal versus typical claim. Then change the audience and rewrite the idea for a parent update. The goal is not to preserve the word; it is to preserve the meaning. Keep often only when it earns its place.

Application 60: sometimes — a comprehension answer

Create a deliberate near miss with sometimes in a comprehension answer, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention low-frequency wording. Then create a fresh correct example in a set of instructions. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 61: occasionally — a geography explanation

In a geography explanation, write one sentence that genuinely needs occasionally. Then replace it with the closest alternative and explain what changes in habit versus measured frequency. Move the same distinction into an exam response without copying the original wording. Finish by naming one context in which occasionally would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 62: rarely — a classroom discussion

Build a three-sentence mini-example in a classroom discussion: first establish the context, then use rarely, then write a correction that would be needed if qualitative versus numerical frequency changed. Rework the example for a science explanation. This tests whether rarely is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 63: seldom — a report conclusion

Imagine a careful editor questions seldom in a report conclusion. Defend it by identifying the intended relation and the evidence that supports exceptions to the pattern. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in an oral response. A strong answer makes the boundary of use visible as well as the successful use.

Application 64: always — a history paragraph

Write two versions of the same idea in a history paragraph: one with always, one without it. Compare the reader’s likely interpretation, paying particular attention to opportunity set. Then change the audience and rewrite the idea for a public notice. The goal is not to preserve the word; it is to preserve the meaning. Keep always only when it earns its place.

Application 65: usually — a project evaluation

Create a deliberate near miss with usually in a project evaluation, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention time window. Then create a fresh correct example in a reflective paragraph. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 66: often — a research summary

In a research summary, write one sentence that genuinely needs often. Then replace it with the closest alternative and explain what changes in universal versus typical claim. Move the same distinction into a short speech without copying the original wording. Finish by naming one context in which often would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 67: sometimes — a technical note

Build a three-sentence mini-example in a technical note: first establish the context, then use sometimes, then write a correction that would be needed if low-frequency wording changed. Rework the example for a data commentary. This tests whether sometimes is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 68: occasionally — a problem-solution paragraph

Imagine a careful editor questions occasionally in a problem-solution paragraph. Defend it by identifying the intended relation and the evidence that supports habit versus measured frequency. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a narrative scene. A strong answer makes the boundary of use visible as well as the successful use.

Application 69: rarely — a policy note

Write two versions of the same idea in a policy note: one with rarely, one without it. Compare the reader’s likely interpretation, paying particular attention to qualitative versus numerical frequency. Then change the audience and rewrite the idea for a literature response. The goal is not to preserve the word; it is to preserve the meaning. Keep rarely only when it earns its place.

Application 70: seldom — a parent update

Create a deliberate near miss with seldom in a parent update, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention exceptions to the pattern. Then create a fresh correct example in a comparison review. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 71: always — a set of instructions

In a set of instructions, write one sentence that genuinely needs always. Then replace it with the closest alternative and explain what changes in opportunity set. Move the same distinction into a revision note without copying the original wording. Finish by naming one context in which always would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 72: usually — an exam response

Build a three-sentence mini-example in an exam response: first establish the context, then use usually, then write a correction that would be needed if time window changed. Rework the example for a formal email. This tests whether usually is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 73: often — a science explanation

Imagine a careful editor questions often in a science explanation. Defend it by identifying the intended relation and the evidence that supports universal versus typical claim. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a comprehension answer. A strong answer makes the boundary of use visible as well as the successful use.

Application 74: sometimes — an oral response

Write two versions of the same idea in an oral response: one with sometimes, one without it. Compare the reader’s likely interpretation, paying particular attention to low-frequency wording. Then change the audience and rewrite the idea for a geography explanation. The goal is not to preserve the word; it is to preserve the meaning. Keep sometimes only when it earns its place.

Application 75: occasionally — a public notice

Create a deliberate near miss with occasionally in a public notice, diagnose exactly why it fails, and repair it with the smallest possible change. Your diagnosis must mention habit versus measured frequency. Then create a fresh correct example in a classroom discussion. This repair-first method turns frequency and habit into an editing skill rather than a recognition exercise.

Application 76: rarely — a reflective paragraph

In a reflective paragraph, write one sentence that genuinely needs rarely. Then replace it with the closest alternative and explain what changes in qualitative versus numerical frequency. Move the same distinction into a report conclusion without copying the original wording. Finish by naming one context in which rarely would mislead the reader. The task is successful only if the explanation states the semantic difference rather than appealing to style.

Application 77: seldom — a short speech

Build a three-sentence mini-example in a short speech: first establish the context, then use seldom, then write a correction that would be needed if exceptions to the pattern changed. Rework the example for a history paragraph. This tests whether seldom is tied to a memorised sentence or to a transferable decision about frequency and habit.

Application 78: always — a data commentary

Imagine a careful editor questions always in a data commentary. Defend it by identifying the intended relation and the evidence that supports opportunity set. Next, concede a case where the editor would be right and supply a better alternative. Repeat the decision in a project evaluation. A strong answer makes the boundary of use visible as well as the successful use.

Application 79: usually — a narrative scene

Write two versions of the same idea in a narrative scene: one with usually, one without it. Compare the reader’s likely interpretation, paying particular attention to time window. Then change the audience and rewrite the idea for a research summary. The goal is not to preserve the word; it is to preserve the meaning. Keep usually only when it earns its place.

Closing Principle

Frequency vocabulary is precise when the opportunity set, time window and evidence support the pattern. Treat the adverbs as contextual categories, not universal percentage labels.