Data Analytics and Business Intelligence English — COMPLETE AI PRACTICE PROMPTS

Every block is a finished prompt. Copy one entire block between START PROMPT and END PROMPT into a new chat in your preferred AI. No prompt-writing is required. Use fictional or anonymized details when the exercise asks for your own response.

Lesson 01 · Metric Definitions and Business Questions | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 01: Metric Definitions and Business Questions
Original fictional case: Analyst Mei and product lead Rafael compare September figures for the same 2,000 eligible users, using UTC calendar boundaries and excluding internal and test accounts. One report counts 1,200 distinct users with a successful login. Another counts 900 distinct users with a completed transaction. All 900 are within the login group. Both queries match their stated definitions. The business question is how many eligible users completed a transaction, not how many signed in. The team must choose an accurate label and rate.
Language workshop: Two active-user totals, two different events
Communication goal: Reconcile apparently conflicting metrics by stating the event, distinct entity, window, and denominator.
Language guidance: 900/2,000 is 45% of eligible users. 900/1,200 is 75% of users who logged in. Both calculations are valid for their stated bases, but only the first answers the supplied eligible-user question.
Useful expressions (preserve the supplied facts): "Are we measuring sign-in or completed transactions?" / "Each user is counted once." / "The qualifying event is a completed transaction." / "Use the September calendar month in UTC." / "Both measures exclude internal and test accounts." / "Both queries match their own definitions." / "The reports use different activity events." / "Nine hundred users answer the transaction question." / "The eligible population is 2,000 users." / "That is 45% of eligible users." / "Seventy-five percent uses logged-in users as its base." / "The transaction group is a subset of the login group." / "Call this transaction-active users." / "Keep the login measure under its own label." / "The metric owner should approve the shared definition." / "We need consistent meaning, not an artificial match between different events."
Vocabulary: metric: A defined quantitative measure. / business question: The decision-relevant question an analysis is meant to answer. / metric definition: Rules specifying exactly how a measure is calculated. / qualifying event: An action meeting the condition for inclusion. / distinct user: A unique user counted once under a defined identity rule. / event count: The number of recorded qualifying occurrences. / eligible population: The complete group allowed into the measure's base. / denominator: The total used as the base of a rate. / numerator: The counted outcome placed over the base of a rate. / reporting window: The time period included in a measure. / calendar month: A month bounded by the adopted calendar and time zone. / time zone: The time reference used to assign event dates. / exclusion rule: A condition removing records from the measure. / internal account: An account belonging to the organization's own personnel or systems. / test account: An account used for testing rather than genuine activity. / deduplication: Removing repeated representations of the same counted entity. / identity resolution: Connecting records that refer to the same entity. / active user: A user meeting a specified activity definition. / login-based activity: Activity defined by a qualifying sign-in. / transaction-based activity: Activity defined by a qualifying transaction. / subset: A group entirely contained within another group. / metric owner: The role accountable for a measure's definition and use. / semantic layer: Shared definitions connecting data to business meaning. / reconciliation: Explaining and resolving differences between reported figures.
Speaking task: Read turns 1-10. Stress qualifying event and denominator as separate choices. Switch roles for turns 11-20. Keep the subset relationship clear when rejecting addition. Check the transfer. Read 40% and 50% with their different population bases.
Partner: Mei: Data analyst / Rafael: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A month has 1,000 eligible users, 800 distinct login users, and 400 distinct transacting users, all within the login group. The question asks for transaction activity among all eligible users.
Model for comparison AFTER my attempt, not a response to give me first: Rafael: Who signs off if the transaction event changes next month? I do not want the same label to hide a new definition.
Mei: Assign a metric owner and record the approved version. That gives both teams a place to resolve changes before comparing totals that no longer mean the same thing.
Rafael: My summary will be nine hundred transaction-active users, forty-five percent of two thousand eligible users, September UTC. The login measure remains separately labeled.
Mei: That completes the reconciliation. We have preserved both correct calculations, selected the measure that answers the decision, and removed the ambiguity that created the apparent conflict.
END REFERENCE
END PROMPT

Lesson 01 · Metric Definitions and Business Questions | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 01: Metric Definitions and Business Questions
Original fictional case: Analyst Mei and product lead Rafael compare September figures for the same 2,000 eligible users, using UTC calendar boundaries and excluding internal and test accounts. One report counts 1,200 distinct users with a successful login. Another counts 900 distinct users with a completed transaction. All 900 are within the login group. Both queries match their stated definitions. The business question is how many eligible users completed a transaction, not how many signed in. The team must choose an accurate label and rate.
Language workshop: Two active-user totals, two different events
Communication goal: Reconcile apparently conflicting metrics by stating the event, distinct entity, window, and denominator.
Language guidance: 900/2,000 is 45% of eligible users. 900/1,200 is 75% of users who logged in. Both calculations are valid for their stated bases, but only the first answers the supplied eligible-user question.
Useful expressions (preserve the supplied facts): "Are we measuring sign-in or completed transactions?" / "Each user is counted once." / "The qualifying event is a completed transaction." / "Use the September calendar month in UTC." / "Both measures exclude internal and test accounts." / "Both queries match their own definitions." / "The reports use different activity events." / "Nine hundred users answer the transaction question." / "The eligible population is 2,000 users." / "That is 45% of eligible users." / "Seventy-five percent uses logged-in users as its base." / "The transaction group is a subset of the login group." / "Call this transaction-active users." / "Keep the login measure under its own label." / "The metric owner should approve the shared definition." / "We need consistent meaning, not an artificial match between different events."
Vocabulary: metric: A defined quantitative measure. / business question: The decision-relevant question an analysis is meant to answer. / metric definition: Rules specifying exactly how a measure is calculated. / qualifying event: An action meeting the condition for inclusion. / distinct user: A unique user counted once under a defined identity rule. / event count: The number of recorded qualifying occurrences. / eligible population: The complete group allowed into the measure's base. / denominator: The total used as the base of a rate. / numerator: The counted outcome placed over the base of a rate. / reporting window: The time period included in a measure. / calendar month: A month bounded by the adopted calendar and time zone. / time zone: The time reference used to assign event dates. / exclusion rule: A condition removing records from the measure. / internal account: An account belonging to the organization's own personnel or systems. / test account: An account used for testing rather than genuine activity. / deduplication: Removing repeated representations of the same counted entity. / identity resolution: Connecting records that refer to the same entity. / active user: A user meeting a specified activity definition. / login-based activity: Activity defined by a qualifying sign-in. / transaction-based activity: Activity defined by a qualifying transaction. / subset: A group entirely contained within another group. / metric owner: The role accountable for a measure's definition and use. / semantic layer: Shared definitions connecting data to business meaning. / reconciliation: Explaining and resolving differences between reported figures.
Speaking task: Read turns 1-10. Stress qualifying event and denominator as separate choices. Switch roles for turns 11-20. Keep the subset relationship clear when rejecting addition. Check the transfer. Read 40% and 50% with their different population bases.
Partner: Mei: Data analyst / Rafael: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A month has 1,000 eligible users, 800 distinct login users, and 400 distinct transacting users, all within the login group. The question asks for transaction activity among all eligible users.
Model for comparison AFTER my attempt, not a response to give me first: Rafael: Who signs off if the transaction event changes next month? I do not want the same label to hide a new definition.
Mei: Assign a metric owner and record the approved version. That gives both teams a place to resolve changes before comparing totals that no longer mean the same thing.
Rafael: My summary will be nine hundred transaction-active users, forty-five percent of two thousand eligible users, September UTC. The login measure remains separately labeled.
Mei: That completes the reconciliation. We have preserved both correct calculations, selected the measure that answers the decision, and removed the ambiguity that created the apparent conflict.
END REFERENCE
END PROMPT

Lesson 01 · Metric Definitions and Business Questions | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 01: Metric Definitions and Business Questions
Original fictional case: Analyst Mei and product lead Rafael compare September figures for the same 2,000 eligible users, using UTC calendar boundaries and excluding internal and test accounts. One report counts 1,200 distinct users with a successful login. Another counts 900 distinct users with a completed transaction. All 900 are within the login group. Both queries match their stated definitions. The business question is how many eligible users completed a transaction, not how many signed in. The team must choose an accurate label and rate.
Language workshop: Two active-user totals, two different events
Communication goal: Reconcile apparently conflicting metrics by stating the event, distinct entity, window, and denominator.
Language guidance: 900/2,000 is 45% of eligible users. 900/1,200 is 75% of users who logged in. Both calculations are valid for their stated bases, but only the first answers the supplied eligible-user question.
Useful expressions (preserve the supplied facts): "Are we measuring sign-in or completed transactions?" / "Each user is counted once." / "The qualifying event is a completed transaction." / "Use the September calendar month in UTC." / "Both measures exclude internal and test accounts." / "Both queries match their own definitions." / "The reports use different activity events." / "Nine hundred users answer the transaction question." / "The eligible population is 2,000 users." / "That is 45% of eligible users." / "Seventy-five percent uses logged-in users as its base." / "The transaction group is a subset of the login group." / "Call this transaction-active users." / "Keep the login measure under its own label." / "The metric owner should approve the shared definition." / "We need consistent meaning, not an artificial match between different events."
Vocabulary: metric: A defined quantitative measure. / business question: The decision-relevant question an analysis is meant to answer. / metric definition: Rules specifying exactly how a measure is calculated. / qualifying event: An action meeting the condition for inclusion. / distinct user: A unique user counted once under a defined identity rule. / event count: The number of recorded qualifying occurrences. / eligible population: The complete group allowed into the measure's base. / denominator: The total used as the base of a rate. / numerator: The counted outcome placed over the base of a rate. / reporting window: The time period included in a measure. / calendar month: A month bounded by the adopted calendar and time zone. / time zone: The time reference used to assign event dates. / exclusion rule: A condition removing records from the measure. / internal account: An account belonging to the organization's own personnel or systems. / test account: An account used for testing rather than genuine activity. / deduplication: Removing repeated representations of the same counted entity. / identity resolution: Connecting records that refer to the same entity. / active user: A user meeting a specified activity definition. / login-based activity: Activity defined by a qualifying sign-in. / transaction-based activity: Activity defined by a qualifying transaction. / subset: A group entirely contained within another group. / metric owner: The role accountable for a measure's definition and use. / semantic layer: Shared definitions connecting data to business meaning. / reconciliation: Explaining and resolving differences between reported figures.
Speaking task: Read turns 1-10. Stress qualifying event and denominator as separate choices. Switch roles for turns 11-20. Keep the subset relationship clear when rejecting addition. Check the transfer. Read 40% and 50% with their different population bases.
Partner: Mei: Data analyst / Rafael: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A month has 1,000 eligible users, 800 distinct login users, and 400 distinct transacting users, all within the login group. The question asks for transaction activity among all eligible users.
Model for comparison AFTER my attempt, not a response to give me first: Rafael: Who signs off if the transaction event changes next month? I do not want the same label to hide a new definition.
Mei: Assign a metric owner and record the approved version. That gives both teams a place to resolve changes before comparing totals that no longer mean the same thing.
Rafael: My summary will be nine hundred transaction-active users, forty-five percent of two thousand eligible users, September UTC. The login measure remains separately labeled.
Mei: That completes the reconciliation. We have preserved both correct calculations, selected the measure that answers the decision, and removed the ambiguity that created the apparent conflict.
END REFERENCE
END PROMPT

Lesson 01 · Metric Definitions and Business Questions | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 01: Metric Definitions and Business Questions
Original fictional case: Analyst Mei and product lead Rafael compare September figures for the same 2,000 eligible users, using UTC calendar boundaries and excluding internal and test accounts. One report counts 1,200 distinct users with a successful login. Another counts 900 distinct users with a completed transaction. All 900 are within the login group. Both queries match their stated definitions. The business question is how many eligible users completed a transaction, not how many signed in. The team must choose an accurate label and rate.
Language workshop: Two active-user totals, two different events
Communication goal: Reconcile apparently conflicting metrics by stating the event, distinct entity, window, and denominator.
Language guidance: 900/2,000 is 45% of eligible users. 900/1,200 is 75% of users who logged in. Both calculations are valid for their stated bases, but only the first answers the supplied eligible-user question.
Useful expressions (preserve the supplied facts): "Are we measuring sign-in or completed transactions?" / "Each user is counted once." / "The qualifying event is a completed transaction." / "Use the September calendar month in UTC." / "Both measures exclude internal and test accounts." / "Both queries match their own definitions." / "The reports use different activity events." / "Nine hundred users answer the transaction question." / "The eligible population is 2,000 users." / "That is 45% of eligible users." / "Seventy-five percent uses logged-in users as its base." / "The transaction group is a subset of the login group." / "Call this transaction-active users." / "Keep the login measure under its own label." / "The metric owner should approve the shared definition." / "We need consistent meaning, not an artificial match between different events."
Vocabulary: metric: A defined quantitative measure. / business question: The decision-relevant question an analysis is meant to answer. / metric definition: Rules specifying exactly how a measure is calculated. / qualifying event: An action meeting the condition for inclusion. / distinct user: A unique user counted once under a defined identity rule. / event count: The number of recorded qualifying occurrences. / eligible population: The complete group allowed into the measure's base. / denominator: The total used as the base of a rate. / numerator: The counted outcome placed over the base of a rate. / reporting window: The time period included in a measure. / calendar month: A month bounded by the adopted calendar and time zone. / time zone: The time reference used to assign event dates. / exclusion rule: A condition removing records from the measure. / internal account: An account belonging to the organization's own personnel or systems. / test account: An account used for testing rather than genuine activity. / deduplication: Removing repeated representations of the same counted entity. / identity resolution: Connecting records that refer to the same entity. / active user: A user meeting a specified activity definition. / login-based activity: Activity defined by a qualifying sign-in. / transaction-based activity: Activity defined by a qualifying transaction. / subset: A group entirely contained within another group. / metric owner: The role accountable for a measure's definition and use. / semantic layer: Shared definitions connecting data to business meaning. / reconciliation: Explaining and resolving differences between reported figures.
Speaking task: Read turns 1-10. Stress qualifying event and denominator as separate choices. Switch roles for turns 11-20. Keep the subset relationship clear when rejecting addition. Check the transfer. Read 40% and 50% with their different population bases.
Partner: Mei: Data analyst / Rafael: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A month has 1,000 eligible users, 800 distinct login users, and 400 distinct transacting users, all within the login group. The question asks for transaction activity among all eligible users.
Model for comparison AFTER my attempt, not a response to give me first: Rafael: Who signs off if the transaction event changes next month? I do not want the same label to hide a new definition.
Mei: Assign a metric owner and record the approved version. That gives both teams a place to resolve changes before comparing totals that no longer mean the same thing.
Rafael: My summary will be nine hundred transaction-active users, forty-five percent of two thousand eligible users, September UTC. The login measure remains separately labeled.
Mei: That completes the reconciliation. We have preserved both correct calculations, selected the measure that answers the decision, and removed the ambiguity that created the apparent conflict.
END REFERENCE
END PROMPT

Lesson 02 · Data Quality and Trust | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 02: Data Quality and Trust
Original fictional case: Reporting analyst Asha reviews a dashboard with operations manager Tomas on Wednesday at 09:00 UTC. The dashboard refresh completed, and the orders source is verified complete through Tuesday 23:59 UTC. The refunds source is verified complete only through Monday 23:59 UTC because its next delivery is delayed. A Monday-Tuesday net-order-value figure subtracts available refunds from orders, so the periods are misaligned. Asha can publish a verified Monday-only comparison; Tuesday refunds are unknown, not confirmed zero. No delivery time for the missing source is confirmed.
Language workshop: Refreshed today, complete only through Monday
Communication goal: Explain mixed source freshness and set an appropriate reporting boundary without mislabeling missing data as zero.
Language guidance: A refresh timestamp records when processing ran, not how current every input was. Even a latest event timestamp alone would not prove completeness. Here, the brief explicitly verifies different complete-through cutoffs for the two sources.
Useful expressions (preserve the supplied facts): "The dashboard refresh completed at 09:00 UTC." / "That does not mean every source is current through Tuesday." / "Refunds are complete only through Monday." / "Orders are verified through Tuesday 23:59 UTC." / "The two-day net figure mixes coverage periods." / "Tuesday refunds are unknown, not confirmed zero." / "We can publish the verified Monday-only comparison." / "Place the source-cutoff note beside the figure." / "The missing delivery time is not confirmed." / "Check source completeness, not only job completion." / "The calculation depends on both orders and refunds." / "Reconcile the backfill before republishing the two-day figure." / "Keep the affected view marked incomplete until validation passes." / "Load time and event time are different." / "This view is complete through Monday only." / "Publish the aligned period and report the remaining source delay."
Vocabulary: data quality: Fitness of data for its intended use. / freshness: How recent data is relative to the intended use. / timeliness: Availability of data within the required time. / completeness: Presence of the required records or values. / accuracy: Agreement between data and the facts it represents. / validity: Conformance to defined formats or rules. / consistency: Agreement across related representations or rules. / uniqueness: Absence of unintended duplicate records. / refresh timestamp: The time a report or model was last updated. / source cutoff: The boundary through which source data is available or complete. / event time: When the represented business event occurred. / load time: When data entered the relevant system. / upstream source: An earlier system supplying data to a pipeline. / pipeline: A sequence of data movement and transformation steps. / ingestion delay: A lag in receiving data from a source. / late-arriving data: Records received after the expected processing point. / backfill: Loading previously missing historical records. / watermark: A tracked boundary used to process or assess data progress. / coverage window: The period or population represented by available data. / reconciliation check: A comparison used to verify agreement between records or totals. / null value: A marker for missing or unknown information in a data field. / zero value: A recorded quantity of none, not automatically a missing value. / data-quality notice: A visible explanation of a known data limitation. / recovery estimate: A qualified expectation for restoration of a data flow.
Speaking task: Read turns 1-10. Contrast the refresh timestamp with each source cutoff. Switch roles for turns 11-20. Stress event time rather than the later load time. Check the transfer. Read the Wednesday-only option without turning Thursday unknowns into zeros.
Partner: Asha: Reporting analyst / Tomas: Operations manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A report refreshed Friday. Sales are verified complete through Thursday, but returns only through Wednesday. Thursday returns are unknown. Both sources are complete for Wednesday.
Model for comparison AFTER my attempt, not a response to give me first: Tomas: When the delivery arrives, who checks that it is complete? I do not want the warning removed just because the refresh turns green.
Asha: Validate the backfill and document the checks. A green refresh icon should not be our only evidence that the previously incomplete reporting period is now fit for use.
Tomas: I will take the Monday-only view to the meeting, explain the Tuesday refund gap, and avoid promising a two-day net result before it is verified.
Asha: That is the right timeliness message: a useful aligned result now, a specific limitation, and a clear validation step before the fuller figure is released.
END REFERENCE
END PROMPT

Lesson 02 · Data Quality and Trust | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 02: Data Quality and Trust
Original fictional case: Reporting analyst Asha reviews a dashboard with operations manager Tomas on Wednesday at 09:00 UTC. The dashboard refresh completed, and the orders source is verified complete through Tuesday 23:59 UTC. The refunds source is verified complete only through Monday 23:59 UTC because its next delivery is delayed. A Monday-Tuesday net-order-value figure subtracts available refunds from orders, so the periods are misaligned. Asha can publish a verified Monday-only comparison; Tuesday refunds are unknown, not confirmed zero. No delivery time for the missing source is confirmed.
Language workshop: Refreshed today, complete only through Monday
Communication goal: Explain mixed source freshness and set an appropriate reporting boundary without mislabeling missing data as zero.
Language guidance: A refresh timestamp records when processing ran, not how current every input was. Even a latest event timestamp alone would not prove completeness. Here, the brief explicitly verifies different complete-through cutoffs for the two sources.
Useful expressions (preserve the supplied facts): "The dashboard refresh completed at 09:00 UTC." / "That does not mean every source is current through Tuesday." / "Refunds are complete only through Monday." / "Orders are verified through Tuesday 23:59 UTC." / "The two-day net figure mixes coverage periods." / "Tuesday refunds are unknown, not confirmed zero." / "We can publish the verified Monday-only comparison." / "Place the source-cutoff note beside the figure." / "The missing delivery time is not confirmed." / "Check source completeness, not only job completion." / "The calculation depends on both orders and refunds." / "Reconcile the backfill before republishing the two-day figure." / "Keep the affected view marked incomplete until validation passes." / "Load time and event time are different." / "This view is complete through Monday only." / "Publish the aligned period and report the remaining source delay."
Vocabulary: data quality: Fitness of data for its intended use. / freshness: How recent data is relative to the intended use. / timeliness: Availability of data within the required time. / completeness: Presence of the required records or values. / accuracy: Agreement between data and the facts it represents. / validity: Conformance to defined formats or rules. / consistency: Agreement across related representations or rules. / uniqueness: Absence of unintended duplicate records. / refresh timestamp: The time a report or model was last updated. / source cutoff: The boundary through which source data is available or complete. / event time: When the represented business event occurred. / load time: When data entered the relevant system. / upstream source: An earlier system supplying data to a pipeline. / pipeline: A sequence of data movement and transformation steps. / ingestion delay: A lag in receiving data from a source. / late-arriving data: Records received after the expected processing point. / backfill: Loading previously missing historical records. / watermark: A tracked boundary used to process or assess data progress. / coverage window: The period or population represented by available data. / reconciliation check: A comparison used to verify agreement between records or totals. / null value: A marker for missing or unknown information in a data field. / zero value: A recorded quantity of none, not automatically a missing value. / data-quality notice: A visible explanation of a known data limitation. / recovery estimate: A qualified expectation for restoration of a data flow.
Speaking task: Read turns 1-10. Contrast the refresh timestamp with each source cutoff. Switch roles for turns 11-20. Stress event time rather than the later load time. Check the transfer. Read the Wednesday-only option without turning Thursday unknowns into zeros.
Partner: Asha: Reporting analyst / Tomas: Operations manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A report refreshed Friday. Sales are verified complete through Thursday, but returns only through Wednesday. Thursday returns are unknown. Both sources are complete for Wednesday.
Model for comparison AFTER my attempt, not a response to give me first: Tomas: When the delivery arrives, who checks that it is complete? I do not want the warning removed just because the refresh turns green.
Asha: Validate the backfill and document the checks. A green refresh icon should not be our only evidence that the previously incomplete reporting period is now fit for use.
Tomas: I will take the Monday-only view to the meeting, explain the Tuesday refund gap, and avoid promising a two-day net result before it is verified.
Asha: That is the right timeliness message: a useful aligned result now, a specific limitation, and a clear validation step before the fuller figure is released.
END REFERENCE
END PROMPT

Lesson 02 · Data Quality and Trust | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 02: Data Quality and Trust
Original fictional case: Reporting analyst Asha reviews a dashboard with operations manager Tomas on Wednesday at 09:00 UTC. The dashboard refresh completed, and the orders source is verified complete through Tuesday 23:59 UTC. The refunds source is verified complete only through Monday 23:59 UTC because its next delivery is delayed. A Monday-Tuesday net-order-value figure subtracts available refunds from orders, so the periods are misaligned. Asha can publish a verified Monday-only comparison; Tuesday refunds are unknown, not confirmed zero. No delivery time for the missing source is confirmed.
Language workshop: Refreshed today, complete only through Monday
Communication goal: Explain mixed source freshness and set an appropriate reporting boundary without mislabeling missing data as zero.
Language guidance: A refresh timestamp records when processing ran, not how current every input was. Even a latest event timestamp alone would not prove completeness. Here, the brief explicitly verifies different complete-through cutoffs for the two sources.
Useful expressions (preserve the supplied facts): "The dashboard refresh completed at 09:00 UTC." / "That does not mean every source is current through Tuesday." / "Refunds are complete only through Monday." / "Orders are verified through Tuesday 23:59 UTC." / "The two-day net figure mixes coverage periods." / "Tuesday refunds are unknown, not confirmed zero." / "We can publish the verified Monday-only comparison." / "Place the source-cutoff note beside the figure." / "The missing delivery time is not confirmed." / "Check source completeness, not only job completion." / "The calculation depends on both orders and refunds." / "Reconcile the backfill before republishing the two-day figure." / "Keep the affected view marked incomplete until validation passes." / "Load time and event time are different." / "This view is complete through Monday only." / "Publish the aligned period and report the remaining source delay."
Vocabulary: data quality: Fitness of data for its intended use. / freshness: How recent data is relative to the intended use. / timeliness: Availability of data within the required time. / completeness: Presence of the required records or values. / accuracy: Agreement between data and the facts it represents. / validity: Conformance to defined formats or rules. / consistency: Agreement across related representations or rules. / uniqueness: Absence of unintended duplicate records. / refresh timestamp: The time a report or model was last updated. / source cutoff: The boundary through which source data is available or complete. / event time: When the represented business event occurred. / load time: When data entered the relevant system. / upstream source: An earlier system supplying data to a pipeline. / pipeline: A sequence of data movement and transformation steps. / ingestion delay: A lag in receiving data from a source. / late-arriving data: Records received after the expected processing point. / backfill: Loading previously missing historical records. / watermark: A tracked boundary used to process or assess data progress. / coverage window: The period or population represented by available data. / reconciliation check: A comparison used to verify agreement between records or totals. / null value: A marker for missing or unknown information in a data field. / zero value: A recorded quantity of none, not automatically a missing value. / data-quality notice: A visible explanation of a known data limitation. / recovery estimate: A qualified expectation for restoration of a data flow.
Speaking task: Read turns 1-10. Contrast the refresh timestamp with each source cutoff. Switch roles for turns 11-20. Stress event time rather than the later load time. Check the transfer. Read the Wednesday-only option without turning Thursday unknowns into zeros.
Partner: Asha: Reporting analyst / Tomas: Operations manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A report refreshed Friday. Sales are verified complete through Thursday, but returns only through Wednesday. Thursday returns are unknown. Both sources are complete for Wednesday.
Model for comparison AFTER my attempt, not a response to give me first: Tomas: When the delivery arrives, who checks that it is complete? I do not want the warning removed just because the refresh turns green.
Asha: Validate the backfill and document the checks. A green refresh icon should not be our only evidence that the previously incomplete reporting period is now fit for use.
Tomas: I will take the Monday-only view to the meeting, explain the Tuesday refund gap, and avoid promising a two-day net result before it is verified.
Asha: That is the right timeliness message: a useful aligned result now, a specific limitation, and a clear validation step before the fuller figure is released.
END REFERENCE
END PROMPT

Lesson 02 · Data Quality and Trust | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 02: Data Quality and Trust
Original fictional case: Reporting analyst Asha reviews a dashboard with operations manager Tomas on Wednesday at 09:00 UTC. The dashboard refresh completed, and the orders source is verified complete through Tuesday 23:59 UTC. The refunds source is verified complete only through Monday 23:59 UTC because its next delivery is delayed. A Monday-Tuesday net-order-value figure subtracts available refunds from orders, so the periods are misaligned. Asha can publish a verified Monday-only comparison; Tuesday refunds are unknown, not confirmed zero. No delivery time for the missing source is confirmed.
Language workshop: Refreshed today, complete only through Monday
Communication goal: Explain mixed source freshness and set an appropriate reporting boundary without mislabeling missing data as zero.
Language guidance: A refresh timestamp records when processing ran, not how current every input was. Even a latest event timestamp alone would not prove completeness. Here, the brief explicitly verifies different complete-through cutoffs for the two sources.
Useful expressions (preserve the supplied facts): "The dashboard refresh completed at 09:00 UTC." / "That does not mean every source is current through Tuesday." / "Refunds are complete only through Monday." / "Orders are verified through Tuesday 23:59 UTC." / "The two-day net figure mixes coverage periods." / "Tuesday refunds are unknown, not confirmed zero." / "We can publish the verified Monday-only comparison." / "Place the source-cutoff note beside the figure." / "The missing delivery time is not confirmed." / "Check source completeness, not only job completion." / "The calculation depends on both orders and refunds." / "Reconcile the backfill before republishing the two-day figure." / "Keep the affected view marked incomplete until validation passes." / "Load time and event time are different." / "This view is complete through Monday only." / "Publish the aligned period and report the remaining source delay."
Vocabulary: data quality: Fitness of data for its intended use. / freshness: How recent data is relative to the intended use. / timeliness: Availability of data within the required time. / completeness: Presence of the required records or values. / accuracy: Agreement between data and the facts it represents. / validity: Conformance to defined formats or rules. / consistency: Agreement across related representations or rules. / uniqueness: Absence of unintended duplicate records. / refresh timestamp: The time a report or model was last updated. / source cutoff: The boundary through which source data is available or complete. / event time: When the represented business event occurred. / load time: When data entered the relevant system. / upstream source: An earlier system supplying data to a pipeline. / pipeline: A sequence of data movement and transformation steps. / ingestion delay: A lag in receiving data from a source. / late-arriving data: Records received after the expected processing point. / backfill: Loading previously missing historical records. / watermark: A tracked boundary used to process or assess data progress. / coverage window: The period or population represented by available data. / reconciliation check: A comparison used to verify agreement between records or totals. / null value: A marker for missing or unknown information in a data field. / zero value: A recorded quantity of none, not automatically a missing value. / data-quality notice: A visible explanation of a known data limitation. / recovery estimate: A qualified expectation for restoration of a data flow.
Speaking task: Read turns 1-10. Contrast the refresh timestamp with each source cutoff. Switch roles for turns 11-20. Stress event time rather than the later load time. Check the transfer. Read the Wednesday-only option without turning Thursday unknowns into zeros.
Partner: Asha: Reporting analyst / Tomas: Operations manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A report refreshed Friday. Sales are verified complete through Thursday, but returns only through Wednesday. Thursday returns are unknown. Both sources are complete for Wednesday.
Model for comparison AFTER my attempt, not a response to give me first: Tomas: When the delivery arrives, who checks that it is complete? I do not want the warning removed just because the refresh turns green.
Asha: Validate the backfill and document the checks. A green refresh icon should not be our only evidence that the previously incomplete reporting period is now fit for use.
Tomas: I will take the Monday-only view to the meeting, explain the Tuesday refund gap, and avoid promising a two-day net result before it is verified.
Asha: That is the right timeliness message: a useful aligned result now, a specific limitation, and a clear validation step before the fuller figure is released.
END REFERENCE
END PROMPT

Lesson 03 · Dashboards and Executive Reporting | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 03: Dashboards and Executive Reporting
Original fictional case: BI analyst Jonas reviews a card labeled 480 with service director Elena. It counts September requests completed within 24 hours of receipt: 480 of 500 eligible requests. All requests have a complete observation window, and the remaining 20 finished late. The approved target is at least 95%. August had 450 timely completions among 500 eligible requests under the same definition. Jonas must report the current rate, position against target, and change from August without calling a percentage-point change a relative percentage increase.
Language workshop: Four hundred eighty needs a denominator and a target
Communication goal: Turn an isolated monthly count into a clear performance statement with definition, target, comparison, and units.
Language guidance: September is 96%: 480/500. August is 90%: 450/500. The increase is 6 percentage points, or approximately 6.67% relative to August. September exceeds the 95% target by 1 percentage point.
Useful expressions (preserve the supplied facts): "This is the share completed within 24 hours." / "The clock starts when the request is received." / "September recorded 480 timely completions out of 500." / "The timely-completion rate is 96%." / "That is one percentage point above the 95% target." / "August was 450 of 500, or 90%." / "The rate rose by six percentage points." / "That is about a 6.67% relative increase." / "Both months use the same definition." / "Every request has a complete observation window." / "Twenty September requests finished late." / "These totals do not explain the improvement." / "This is a two-month comparison, not a sustained-trend claim." / "Add the definition, denominator, target, and comparison." / "The drill-down can show the late requests." / "September met the target and improved from August on the same basis."
Vocabulary: KPI: Key performance indicator, a measure tied to an objective. / dashboard card: A compact display of a selected metric. / performance target: A specified desired level of a measure. / actual result: The observed value of the defined measure. / comparison period: An earlier or alternative interval used as a reference. / variance: A difference from a specified reference value. / percentage point: One unit of difference between percentage values. / relative change: Change divided by the original reference value. / month-on-month: Compared with the immediately preceding month. / year-on-year: Compared with the corresponding period a year earlier. / service-level target: An agreed performance threshold for a service measure. / timely completion: Completion within the specified permitted duration. / elapsed time: Duration between defined start and end events. / observation window: The period available to observe the relevant outcome. / threshold: A boundary used for a rule or decision. / direction of improvement: Whether higher or lower values are favorable. / trend: A pattern across a sequence of observations. / seasonality: Recurring variation related to calendar patterns. / run chart: A display of values ordered through time. / annotation: Explanatory text attached to a chart or figure. / drill-down: Moving from a summary to more detailed data. / exception queue: Items selected for attention under a defined rule. / comparability: The extent to which measures use compatible bases. / executive summary: A concise account of the main evidence and decision relevance.
Speaking task: Read turns 1-10. Say percentage points and relative percent distinctly. Switch roles for turns 11-20. Keep the twenty late requests in the summary. Check the transfer. Contrast five points above last month with two above target.
Partner: Jonas: Business-intelligence analyst / Elena: Service director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A service completes 180 of 200 eligible requests on time this month. Last month was 170 of 200. The target is 88%, and both months use the same fully observed definition.
Model for comparison AFTER my attempt, not a response to give me first: Elena: The clock begins on receipt and stops on completion. We should also state that the data covers fully observed requests, not a partial month of immature outcomes.
Jonas: Yes, the observation window is complete for every request here. That matters because unresolved timing can otherwise distort a rate even when the arithmetic itself is correct.
Elena: September was ninety-six percent: one point above target, six above August, twenty requests late. The cause is unestablished.
Jonas: That is a useful executive summary. The card will include the definition and base, and the detail will support the late-case review rather than asking the audience to infer everything from 480.
END REFERENCE
END PROMPT

Lesson 03 · Dashboards and Executive Reporting | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 03: Dashboards and Executive Reporting
Original fictional case: BI analyst Jonas reviews a card labeled 480 with service director Elena. It counts September requests completed within 24 hours of receipt: 480 of 500 eligible requests. All requests have a complete observation window, and the remaining 20 finished late. The approved target is at least 95%. August had 450 timely completions among 500 eligible requests under the same definition. Jonas must report the current rate, position against target, and change from August without calling a percentage-point change a relative percentage increase.
Language workshop: Four hundred eighty needs a denominator and a target
Communication goal: Turn an isolated monthly count into a clear performance statement with definition, target, comparison, and units.
Language guidance: September is 96%: 480/500. August is 90%: 450/500. The increase is 6 percentage points, or approximately 6.67% relative to August. September exceeds the 95% target by 1 percentage point.
Useful expressions (preserve the supplied facts): "This is the share completed within 24 hours." / "The clock starts when the request is received." / "September recorded 480 timely completions out of 500." / "The timely-completion rate is 96%." / "That is one percentage point above the 95% target." / "August was 450 of 500, or 90%." / "The rate rose by six percentage points." / "That is about a 6.67% relative increase." / "Both months use the same definition." / "Every request has a complete observation window." / "Twenty September requests finished late." / "These totals do not explain the improvement." / "This is a two-month comparison, not a sustained-trend claim." / "Add the definition, denominator, target, and comparison." / "The drill-down can show the late requests." / "September met the target and improved from August on the same basis."
Vocabulary: KPI: Key performance indicator, a measure tied to an objective. / dashboard card: A compact display of a selected metric. / performance target: A specified desired level of a measure. / actual result: The observed value of the defined measure. / comparison period: An earlier or alternative interval used as a reference. / variance: A difference from a specified reference value. / percentage point: One unit of difference between percentage values. / relative change: Change divided by the original reference value. / month-on-month: Compared with the immediately preceding month. / year-on-year: Compared with the corresponding period a year earlier. / service-level target: An agreed performance threshold for a service measure. / timely completion: Completion within the specified permitted duration. / elapsed time: Duration between defined start and end events. / observation window: The period available to observe the relevant outcome. / threshold: A boundary used for a rule or decision. / direction of improvement: Whether higher or lower values are favorable. / trend: A pattern across a sequence of observations. / seasonality: Recurring variation related to calendar patterns. / run chart: A display of values ordered through time. / annotation: Explanatory text attached to a chart or figure. / drill-down: Moving from a summary to more detailed data. / exception queue: Items selected for attention under a defined rule. / comparability: The extent to which measures use compatible bases. / executive summary: A concise account of the main evidence and decision relevance.
Speaking task: Read turns 1-10. Say percentage points and relative percent distinctly. Switch roles for turns 11-20. Keep the twenty late requests in the summary. Check the transfer. Contrast five points above last month with two above target.
Partner: Jonas: Business-intelligence analyst / Elena: Service director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A service completes 180 of 200 eligible requests on time this month. Last month was 170 of 200. The target is 88%, and both months use the same fully observed definition.
Model for comparison AFTER my attempt, not a response to give me first: Elena: The clock begins on receipt and stops on completion. We should also state that the data covers fully observed requests, not a partial month of immature outcomes.
Jonas: Yes, the observation window is complete for every request here. That matters because unresolved timing can otherwise distort a rate even when the arithmetic itself is correct.
Elena: September was ninety-six percent: one point above target, six above August, twenty requests late. The cause is unestablished.
Jonas: That is a useful executive summary. The card will include the definition and base, and the detail will support the late-case review rather than asking the audience to infer everything from 480.
END REFERENCE
END PROMPT

Lesson 03 · Dashboards and Executive Reporting | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 03: Dashboards and Executive Reporting
Original fictional case: BI analyst Jonas reviews a card labeled 480 with service director Elena. It counts September requests completed within 24 hours of receipt: 480 of 500 eligible requests. All requests have a complete observation window, and the remaining 20 finished late. The approved target is at least 95%. August had 450 timely completions among 500 eligible requests under the same definition. Jonas must report the current rate, position against target, and change from August without calling a percentage-point change a relative percentage increase.
Language workshop: Four hundred eighty needs a denominator and a target
Communication goal: Turn an isolated monthly count into a clear performance statement with definition, target, comparison, and units.
Language guidance: September is 96%: 480/500. August is 90%: 450/500. The increase is 6 percentage points, or approximately 6.67% relative to August. September exceeds the 95% target by 1 percentage point.
Useful expressions (preserve the supplied facts): "This is the share completed within 24 hours." / "The clock starts when the request is received." / "September recorded 480 timely completions out of 500." / "The timely-completion rate is 96%." / "That is one percentage point above the 95% target." / "August was 450 of 500, or 90%." / "The rate rose by six percentage points." / "That is about a 6.67% relative increase." / "Both months use the same definition." / "Every request has a complete observation window." / "Twenty September requests finished late." / "These totals do not explain the improvement." / "This is a two-month comparison, not a sustained-trend claim." / "Add the definition, denominator, target, and comparison." / "The drill-down can show the late requests." / "September met the target and improved from August on the same basis."
Vocabulary: KPI: Key performance indicator, a measure tied to an objective. / dashboard card: A compact display of a selected metric. / performance target: A specified desired level of a measure. / actual result: The observed value of the defined measure. / comparison period: An earlier or alternative interval used as a reference. / variance: A difference from a specified reference value. / percentage point: One unit of difference between percentage values. / relative change: Change divided by the original reference value. / month-on-month: Compared with the immediately preceding month. / year-on-year: Compared with the corresponding period a year earlier. / service-level target: An agreed performance threshold for a service measure. / timely completion: Completion within the specified permitted duration. / elapsed time: Duration between defined start and end events. / observation window: The period available to observe the relevant outcome. / threshold: A boundary used for a rule or decision. / direction of improvement: Whether higher or lower values are favorable. / trend: A pattern across a sequence of observations. / seasonality: Recurring variation related to calendar patterns. / run chart: A display of values ordered through time. / annotation: Explanatory text attached to a chart or figure. / drill-down: Moving from a summary to more detailed data. / exception queue: Items selected for attention under a defined rule. / comparability: The extent to which measures use compatible bases. / executive summary: A concise account of the main evidence and decision relevance.
Speaking task: Read turns 1-10. Say percentage points and relative percent distinctly. Switch roles for turns 11-20. Keep the twenty late requests in the summary. Check the transfer. Contrast five points above last month with two above target.
Partner: Jonas: Business-intelligence analyst / Elena: Service director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A service completes 180 of 200 eligible requests on time this month. Last month was 170 of 200. The target is 88%, and both months use the same fully observed definition.
Model for comparison AFTER my attempt, not a response to give me first: Elena: The clock begins on receipt and stops on completion. We should also state that the data covers fully observed requests, not a partial month of immature outcomes.
Jonas: Yes, the observation window is complete for every request here. That matters because unresolved timing can otherwise distort a rate even when the arithmetic itself is correct.
Elena: September was ninety-six percent: one point above target, six above August, twenty requests late. The cause is unestablished.
Jonas: That is a useful executive summary. The card will include the definition and base, and the detail will support the late-case review rather than asking the audience to infer everything from 480.
END REFERENCE
END PROMPT

Lesson 03 · Dashboards and Executive Reporting | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 03: Dashboards and Executive Reporting
Original fictional case: BI analyst Jonas reviews a card labeled 480 with service director Elena. It counts September requests completed within 24 hours of receipt: 480 of 500 eligible requests. All requests have a complete observation window, and the remaining 20 finished late. The approved target is at least 95%. August had 450 timely completions among 500 eligible requests under the same definition. Jonas must report the current rate, position against target, and change from August without calling a percentage-point change a relative percentage increase.
Language workshop: Four hundred eighty needs a denominator and a target
Communication goal: Turn an isolated monthly count into a clear performance statement with definition, target, comparison, and units.
Language guidance: September is 96%: 480/500. August is 90%: 450/500. The increase is 6 percentage points, or approximately 6.67% relative to August. September exceeds the 95% target by 1 percentage point.
Useful expressions (preserve the supplied facts): "This is the share completed within 24 hours." / "The clock starts when the request is received." / "September recorded 480 timely completions out of 500." / "The timely-completion rate is 96%." / "That is one percentage point above the 95% target." / "August was 450 of 500, or 90%." / "The rate rose by six percentage points." / "That is about a 6.67% relative increase." / "Both months use the same definition." / "Every request has a complete observation window." / "Twenty September requests finished late." / "These totals do not explain the improvement." / "This is a two-month comparison, not a sustained-trend claim." / "Add the definition, denominator, target, and comparison." / "The drill-down can show the late requests." / "September met the target and improved from August on the same basis."
Vocabulary: KPI: Key performance indicator, a measure tied to an objective. / dashboard card: A compact display of a selected metric. / performance target: A specified desired level of a measure. / actual result: The observed value of the defined measure. / comparison period: An earlier or alternative interval used as a reference. / variance: A difference from a specified reference value. / percentage point: One unit of difference between percentage values. / relative change: Change divided by the original reference value. / month-on-month: Compared with the immediately preceding month. / year-on-year: Compared with the corresponding period a year earlier. / service-level target: An agreed performance threshold for a service measure. / timely completion: Completion within the specified permitted duration. / elapsed time: Duration between defined start and end events. / observation window: The period available to observe the relevant outcome. / threshold: A boundary used for a rule or decision. / direction of improvement: Whether higher or lower values are favorable. / trend: A pattern across a sequence of observations. / seasonality: Recurring variation related to calendar patterns. / run chart: A display of values ordered through time. / annotation: Explanatory text attached to a chart or figure. / drill-down: Moving from a summary to more detailed data. / exception queue: Items selected for attention under a defined rule. / comparability: The extent to which measures use compatible bases. / executive summary: A concise account of the main evidence and decision relevance.
Speaking task: Read turns 1-10. Say percentage points and relative percent distinctly. Switch roles for turns 11-20. Keep the twenty late requests in the summary. Check the transfer. Contrast five points above last month with two above target.
Partner: Jonas: Business-intelligence analyst / Elena: Service director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A service completes 180 of 200 eligible requests on time this month. Last month was 170 of 200. The target is 88%, and both months use the same fully observed definition.
Model for comparison AFTER my attempt, not a response to give me first: Elena: The clock begins on receipt and stops on completion. We should also state that the data covers fully observed requests, not a partial month of immature outcomes.
Jonas: Yes, the observation window is complete for every request here. That matters because unresolved timing can otherwise distort a rate even when the arithmetic itself is correct.
Elena: September was ninety-six percent: one point above target, six above August, twenty requests late. The cause is unestablished.
Jonas: That is a useful executive summary. The card will include the definition and base, and the detail will support the late-case review rather than asking the audience to infer everything from 480.
END REFERENCE
END PROMPT

Lesson 04 · Causation, Correlation, and Caveats | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 04: Causation, Correlation, and Caveats
Original fictional case: Analyst Priya reviews voluntary customer-training results with customer-success lead Marcus. Over the same renewal window, 90 of 100 eligible attendees renewed, compared with 160 of 200 eligible non-attendees. Attendance was not randomized. Baseline motivation and engagement may differ between the groups and were not measured. The records establish a 90% versus 80% renewal association, not the effect of making everyone attend. Priya recommends a reviewed evaluation design before the team uses the difference as a causal benefit claim.
Language workshop: Training attendees renewed more often
Communication goal: Report a meaningful association while separating the observed difference from an unestablished causal effect.
Language guidance: The observed difference is 10 percentage points: 90%-80%. Relative to the non-attendee rate, it is 12.5%. Neither expression turns the voluntary comparison into an estimated causal benefit for mandatory training.
Useful expressions (preserve the supplied facts): "Attendees renewed at 90%; non-attendees at 80%." / "That is 90 of 100 versus 160 of 200." / "The observed gap is ten percentage points." / "This is an association in the supplied data." / "Customers chose whether to attend." / "Baseline engagement may differ between the groups." / "Those baseline factors were not measured." / "We cannot attribute the whole difference to training." / "This does not prove that training has no effect." / "We need to know what would have happened to comparable customers without training." / "Both rates use the same renewal window." / "The result concerns these eligible customer groups." / "Adjusting measured factors would not automatically remove every unmeasured difference." / "Review a design that can better isolate the training effect." / "Use higher observed renewal among attendees." / "Keep the association and remove the unsupported promise."
Vocabulary: association: An observed relationship between variables or groups. / correlation: A measure or description of co-variation. / causal effect: A change attributable to a specified intervention. / confounding: Distortion from factors related to both exposure and outcome. / self-selection: Participation determined partly by people's own choices. / selection bias: Systematic distortion related to how observations enter groups. / baseline characteristic: A feature measured before the exposure or intervention. / motivation: A person's underlying inclination to act or engage. / engagement: Participation or involvement under a specified definition. / observational study: Analysis of naturally occurring exposures without assigned treatment. / random assignment: Allocation to groups by a defined random process. / treatment group: The group assigned or exposed to the studied intervention. / comparison group: The group used as a reference for the outcome. / counterfactual: The outcome that would occur under an alternative exposure. / renewal: Continuation of an eligible customer contract or relationship. / renewal window: The period over which renewal outcomes are observed. / eligible customer: A customer meeting the defined inclusion conditions. / absolute difference: A difference expressed in the original measure's units. / relative lift: A difference expressed relative to a comparison value. / adjustment: Accounting for specified variables in an analysis. / unmeasured factor: A relevant characteristic not recorded in the data. / generalizability: Applicability of a result beyond the studied group. / causal claim: A statement that an intervention produced an outcome. / evaluation design: The planned method for assessing a program or intervention.
Speaking task: Read turns 1-10. Stress observed association and voluntary attendance. Switch roles for turns 11-20. Keep a possible confounder distinct from a proven explanation. Check the transfer. Read both group rates without attributing the gap to training.
Partner: Priya: Data analyst / Marcus: Customer-success lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: In a voluntary program, 45 of 50 attendees renew and 80 of 100 non-attendees renew. Baseline engagement is unmeasured. Attendance was not randomized.
Model for comparison AFTER my attempt, not a response to give me first: Marcus: And a mandatory program could reach people unlike the voluntary attendees. Even a stronger estimate in this group might not transfer unchanged to everyone.
Priya: That is a generalizability issue as well as a causal one. The population, intervention, and implementation matter when translating evidence into a wider operational recommendation.
Marcus: I will revise the slide to higher observed renewal among attendees, show both counts and rates, and recommend a better evaluation before claiming a guaranteed benefit.
Priya: Good. A reviewed evaluation design can address the decision we actually face. We have kept the useful finding, corrected its interpretation, and made the next evidence step clear.
END REFERENCE
END PROMPT

Lesson 04 · Causation, Correlation, and Caveats | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 04: Causation, Correlation, and Caveats
Original fictional case: Analyst Priya reviews voluntary customer-training results with customer-success lead Marcus. Over the same renewal window, 90 of 100 eligible attendees renewed, compared with 160 of 200 eligible non-attendees. Attendance was not randomized. Baseline motivation and engagement may differ between the groups and were not measured. The records establish a 90% versus 80% renewal association, not the effect of making everyone attend. Priya recommends a reviewed evaluation design before the team uses the difference as a causal benefit claim.
Language workshop: Training attendees renewed more often
Communication goal: Report a meaningful association while separating the observed difference from an unestablished causal effect.
Language guidance: The observed difference is 10 percentage points: 90%-80%. Relative to the non-attendee rate, it is 12.5%. Neither expression turns the voluntary comparison into an estimated causal benefit for mandatory training.
Useful expressions (preserve the supplied facts): "Attendees renewed at 90%; non-attendees at 80%." / "That is 90 of 100 versus 160 of 200." / "The observed gap is ten percentage points." / "This is an association in the supplied data." / "Customers chose whether to attend." / "Baseline engagement may differ between the groups." / "Those baseline factors were not measured." / "We cannot attribute the whole difference to training." / "This does not prove that training has no effect." / "We need to know what would have happened to comparable customers without training." / "Both rates use the same renewal window." / "The result concerns these eligible customer groups." / "Adjusting measured factors would not automatically remove every unmeasured difference." / "Review a design that can better isolate the training effect." / "Use higher observed renewal among attendees." / "Keep the association and remove the unsupported promise."
Vocabulary: association: An observed relationship between variables or groups. / correlation: A measure or description of co-variation. / causal effect: A change attributable to a specified intervention. / confounding: Distortion from factors related to both exposure and outcome. / self-selection: Participation determined partly by people's own choices. / selection bias: Systematic distortion related to how observations enter groups. / baseline characteristic: A feature measured before the exposure or intervention. / motivation: A person's underlying inclination to act or engage. / engagement: Participation or involvement under a specified definition. / observational study: Analysis of naturally occurring exposures without assigned treatment. / random assignment: Allocation to groups by a defined random process. / treatment group: The group assigned or exposed to the studied intervention. / comparison group: The group used as a reference for the outcome. / counterfactual: The outcome that would occur under an alternative exposure. / renewal: Continuation of an eligible customer contract or relationship. / renewal window: The period over which renewal outcomes are observed. / eligible customer: A customer meeting the defined inclusion conditions. / absolute difference: A difference expressed in the original measure's units. / relative lift: A difference expressed relative to a comparison value. / adjustment: Accounting for specified variables in an analysis. / unmeasured factor: A relevant characteristic not recorded in the data. / generalizability: Applicability of a result beyond the studied group. / causal claim: A statement that an intervention produced an outcome. / evaluation design: The planned method for assessing a program or intervention.
Speaking task: Read turns 1-10. Stress observed association and voluntary attendance. Switch roles for turns 11-20. Keep a possible confounder distinct from a proven explanation. Check the transfer. Read both group rates without attributing the gap to training.
Partner: Priya: Data analyst / Marcus: Customer-success lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: In a voluntary program, 45 of 50 attendees renew and 80 of 100 non-attendees renew. Baseline engagement is unmeasured. Attendance was not randomized.
Model for comparison AFTER my attempt, not a response to give me first: Marcus: And a mandatory program could reach people unlike the voluntary attendees. Even a stronger estimate in this group might not transfer unchanged to everyone.
Priya: That is a generalizability issue as well as a causal one. The population, intervention, and implementation matter when translating evidence into a wider operational recommendation.
Marcus: I will revise the slide to higher observed renewal among attendees, show both counts and rates, and recommend a better evaluation before claiming a guaranteed benefit.
Priya: Good. A reviewed evaluation design can address the decision we actually face. We have kept the useful finding, corrected its interpretation, and made the next evidence step clear.
END REFERENCE
END PROMPT

Lesson 04 · Causation, Correlation, and Caveats | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 04: Causation, Correlation, and Caveats
Original fictional case: Analyst Priya reviews voluntary customer-training results with customer-success lead Marcus. Over the same renewal window, 90 of 100 eligible attendees renewed, compared with 160 of 200 eligible non-attendees. Attendance was not randomized. Baseline motivation and engagement may differ between the groups and were not measured. The records establish a 90% versus 80% renewal association, not the effect of making everyone attend. Priya recommends a reviewed evaluation design before the team uses the difference as a causal benefit claim.
Language workshop: Training attendees renewed more often
Communication goal: Report a meaningful association while separating the observed difference from an unestablished causal effect.
Language guidance: The observed difference is 10 percentage points: 90%-80%. Relative to the non-attendee rate, it is 12.5%. Neither expression turns the voluntary comparison into an estimated causal benefit for mandatory training.
Useful expressions (preserve the supplied facts): "Attendees renewed at 90%; non-attendees at 80%." / "That is 90 of 100 versus 160 of 200." / "The observed gap is ten percentage points." / "This is an association in the supplied data." / "Customers chose whether to attend." / "Baseline engagement may differ between the groups." / "Those baseline factors were not measured." / "We cannot attribute the whole difference to training." / "This does not prove that training has no effect." / "We need to know what would have happened to comparable customers without training." / "Both rates use the same renewal window." / "The result concerns these eligible customer groups." / "Adjusting measured factors would not automatically remove every unmeasured difference." / "Review a design that can better isolate the training effect." / "Use higher observed renewal among attendees." / "Keep the association and remove the unsupported promise."
Vocabulary: association: An observed relationship between variables or groups. / correlation: A measure or description of co-variation. / causal effect: A change attributable to a specified intervention. / confounding: Distortion from factors related to both exposure and outcome. / self-selection: Participation determined partly by people's own choices. / selection bias: Systematic distortion related to how observations enter groups. / baseline characteristic: A feature measured before the exposure or intervention. / motivation: A person's underlying inclination to act or engage. / engagement: Participation or involvement under a specified definition. / observational study: Analysis of naturally occurring exposures without assigned treatment. / random assignment: Allocation to groups by a defined random process. / treatment group: The group assigned or exposed to the studied intervention. / comparison group: The group used as a reference for the outcome. / counterfactual: The outcome that would occur under an alternative exposure. / renewal: Continuation of an eligible customer contract or relationship. / renewal window: The period over which renewal outcomes are observed. / eligible customer: A customer meeting the defined inclusion conditions. / absolute difference: A difference expressed in the original measure's units. / relative lift: A difference expressed relative to a comparison value. / adjustment: Accounting for specified variables in an analysis. / unmeasured factor: A relevant characteristic not recorded in the data. / generalizability: Applicability of a result beyond the studied group. / causal claim: A statement that an intervention produced an outcome. / evaluation design: The planned method for assessing a program or intervention.
Speaking task: Read turns 1-10. Stress observed association and voluntary attendance. Switch roles for turns 11-20. Keep a possible confounder distinct from a proven explanation. Check the transfer. Read both group rates without attributing the gap to training.
Partner: Priya: Data analyst / Marcus: Customer-success lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: In a voluntary program, 45 of 50 attendees renew and 80 of 100 non-attendees renew. Baseline engagement is unmeasured. Attendance was not randomized.
Model for comparison AFTER my attempt, not a response to give me first: Marcus: And a mandatory program could reach people unlike the voluntary attendees. Even a stronger estimate in this group might not transfer unchanged to everyone.
Priya: That is a generalizability issue as well as a causal one. The population, intervention, and implementation matter when translating evidence into a wider operational recommendation.
Marcus: I will revise the slide to higher observed renewal among attendees, show both counts and rates, and recommend a better evaluation before claiming a guaranteed benefit.
Priya: Good. A reviewed evaluation design can address the decision we actually face. We have kept the useful finding, corrected its interpretation, and made the next evidence step clear.
END REFERENCE
END PROMPT

Lesson 04 · Causation, Correlation, and Caveats | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 04: Causation, Correlation, and Caveats
Original fictional case: Analyst Priya reviews voluntary customer-training results with customer-success lead Marcus. Over the same renewal window, 90 of 100 eligible attendees renewed, compared with 160 of 200 eligible non-attendees. Attendance was not randomized. Baseline motivation and engagement may differ between the groups and were not measured. The records establish a 90% versus 80% renewal association, not the effect of making everyone attend. Priya recommends a reviewed evaluation design before the team uses the difference as a causal benefit claim.
Language workshop: Training attendees renewed more often
Communication goal: Report a meaningful association while separating the observed difference from an unestablished causal effect.
Language guidance: The observed difference is 10 percentage points: 90%-80%. Relative to the non-attendee rate, it is 12.5%. Neither expression turns the voluntary comparison into an estimated causal benefit for mandatory training.
Useful expressions (preserve the supplied facts): "Attendees renewed at 90%; non-attendees at 80%." / "That is 90 of 100 versus 160 of 200." / "The observed gap is ten percentage points." / "This is an association in the supplied data." / "Customers chose whether to attend." / "Baseline engagement may differ between the groups." / "Those baseline factors were not measured." / "We cannot attribute the whole difference to training." / "This does not prove that training has no effect." / "We need to know what would have happened to comparable customers without training." / "Both rates use the same renewal window." / "The result concerns these eligible customer groups." / "Adjusting measured factors would not automatically remove every unmeasured difference." / "Review a design that can better isolate the training effect." / "Use higher observed renewal among attendees." / "Keep the association and remove the unsupported promise."
Vocabulary: association: An observed relationship between variables or groups. / correlation: A measure or description of co-variation. / causal effect: A change attributable to a specified intervention. / confounding: Distortion from factors related to both exposure and outcome. / self-selection: Participation determined partly by people's own choices. / selection bias: Systematic distortion related to how observations enter groups. / baseline characteristic: A feature measured before the exposure or intervention. / motivation: A person's underlying inclination to act or engage. / engagement: Participation or involvement under a specified definition. / observational study: Analysis of naturally occurring exposures without assigned treatment. / random assignment: Allocation to groups by a defined random process. / treatment group: The group assigned or exposed to the studied intervention. / comparison group: The group used as a reference for the outcome. / counterfactual: The outcome that would occur under an alternative exposure. / renewal: Continuation of an eligible customer contract or relationship. / renewal window: The period over which renewal outcomes are observed. / eligible customer: A customer meeting the defined inclusion conditions. / absolute difference: A difference expressed in the original measure's units. / relative lift: A difference expressed relative to a comparison value. / adjustment: Accounting for specified variables in an analysis. / unmeasured factor: A relevant characteristic not recorded in the data. / generalizability: Applicability of a result beyond the studied group. / causal claim: A statement that an intervention produced an outcome. / evaluation design: The planned method for assessing a program or intervention.
Speaking task: Read turns 1-10. Stress observed association and voluntary attendance. Switch roles for turns 11-20. Keep a possible confounder distinct from a proven explanation. Check the transfer. Read both group rates without attributing the gap to training.
Partner: Priya: Data analyst / Marcus: Customer-success lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: In a voluntary program, 45 of 50 attendees renew and 80 of 100 non-attendees renew. Baseline engagement is unmeasured. Attendance was not randomized.
Model for comparison AFTER my attempt, not a response to give me first: Marcus: And a mandatory program could reach people unlike the voluntary attendees. Even a stronger estimate in this group might not transfer unchanged to everyone.
Priya: That is a generalizability issue as well as a causal one. The population, intervention, and implementation matter when translating evidence into a wider operational recommendation.
Marcus: I will revise the slide to higher observed renewal among attendees, show both counts and rates, and recommend a better evaluation before claiming a guaranteed benefit.
Priya: Good. A reviewed evaluation design can address the decision we actually face. We have kept the useful finding, corrected its interpretation, and made the next evidence step clear.
END REFERENCE
END PROMPT

Lesson 05 · SQL, Models, and Transformation Logic | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 05: SQL, Models, and Transformation Logic
Original fictional case: Analytics engineer Lina reviews a report with analyst Owen. The complete teaching dataset has two orders: O1 is $100 and O2 is $100. Payment rows are O1: $60 and $40; O2: $100. Joining orders to payments on order ID creates three rows. Summing the repeated order amount then gives $300, although total order value is $200. SUM(DISTINCT order_amount) gives $100 because the two legitimate orders share an amount. Lina proposes aggregating payments to one row per order before joining, with key and total checks.
Language workshop: The join adds rows, not order value
Communication goal: Explain row grain and join multiplicity, diagnose a duplicated aggregate, and reject a misleading distinct-value fix.
Language guidance: The joined order amounts are 100, 100, and 100: O1 appears twice because it has two payments. The correct order total is 200. The payment amounts themselves are 60, 40, and 100, also totaling 200 for this dataset.
Useful expressions (preserve the supplied facts): "What does one row represent before the join?" / "The tables match on order ID." / "O1 has two payment rows." / "The order row is repeated for each matching payment." / "The extra row is not an extra order." / "Summing joined order amounts produces $300." / "The order-level total is $200." / "Distinct amounts do not mean distinct orders." / "Both legitimate orders have an amount of $100." / "Aggregate payments to one row per order before joining." / "Check uniqueness of order ID in the summarized payments." / "The intended order population must survive the join." / "Reconcile the repaired output to the source order total." / "Order value and payment value are different measures." / "Define how orders without payments are represented." / "Fix the grain and verify the result before republishing."
Vocabulary: SQL: Structured Query Language, used to query relational data. / row grain: What one row represents in a dataset. / primary key: A non-null column or set of columns uniquely identifying each row. / foreign key: A column or set of columns constrained to reference a key in a table. / join key: The field or fields used to match tables. / join cardinality: The relationship in match counts between joined entities. / one-to-many relationship: One entity matching multiple related records. / fanout: Multiplication of rows caused by multiple join matches. / aggregation: Combining records into summary values. / pre-aggregation: Summarizing data before another transformation or join. / GROUP BY: SQL grouping of rows for aggregate calculations. / SUM: An aggregate that adds non-null numeric values. / DISTINCT: SQL removal of duplicate values or rows in its specified scope. / COUNT: An aggregate that counts rows or non-null expressions. / inner join: A join returning matching combinations from both sides. / left join: A join retaining left rows even without a right match. / null handling: Rules for processing missing or unknown values. / filter: A condition selecting which records remain. / CTE: Common table expression, a named query expression. / data model: A representation of entities, relationships, and measures. / fact table: A table storing business events or measurements at a defined grain. / dimension table: A table holding descriptive attributes for analysis. / reconciliation total: A reference total used to verify transformed output. / uniqueness test: A check that a defined key has no duplicates.
Speaking task: Read turns 1-10. Contrast an order identity with its amount. Switch roles for turns 11-20. Stress one row per order and both reconciliation checks. Check the transfer. Read the correct total, inflated sum, and distinct-value sum separately.
Partner: Lina: Analytics engineer / Owen: Reporting analyst
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Order A is $80 with two $40 payments. Order B is $80 with one $80 payment. An order-to-payment join yields three rows. The report must count each order amount once.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will check both the two-order count and the two-hundred-dollar total. Could those totals look right even if one missing order offsets a duplicate?
Lina: Use the original reconciliation total as a reference and inspect differences. A plausible-looking grand total alone is not enough if missing orders and duplicated orders happen to offset each other.
Owen: My explanation will say the join repeated an order-level amount; it did not create revenue. I will withhold the inflated result while the transformation is corrected.
Lina: Add a uniqueness test for the summarized order key and document the grain. That makes the repair repeatable rather than relying on someone noticing another surprising total later.
END REFERENCE
END PROMPT

Lesson 05 · SQL, Models, and Transformation Logic | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 05: SQL, Models, and Transformation Logic
Original fictional case: Analytics engineer Lina reviews a report with analyst Owen. The complete teaching dataset has two orders: O1 is $100 and O2 is $100. Payment rows are O1: $60 and $40; O2: $100. Joining orders to payments on order ID creates three rows. Summing the repeated order amount then gives $300, although total order value is $200. SUM(DISTINCT order_amount) gives $100 because the two legitimate orders share an amount. Lina proposes aggregating payments to one row per order before joining, with key and total checks.
Language workshop: The join adds rows, not order value
Communication goal: Explain row grain and join multiplicity, diagnose a duplicated aggregate, and reject a misleading distinct-value fix.
Language guidance: The joined order amounts are 100, 100, and 100: O1 appears twice because it has two payments. The correct order total is 200. The payment amounts themselves are 60, 40, and 100, also totaling 200 for this dataset.
Useful expressions (preserve the supplied facts): "What does one row represent before the join?" / "The tables match on order ID." / "O1 has two payment rows." / "The order row is repeated for each matching payment." / "The extra row is not an extra order." / "Summing joined order amounts produces $300." / "The order-level total is $200." / "Distinct amounts do not mean distinct orders." / "Both legitimate orders have an amount of $100." / "Aggregate payments to one row per order before joining." / "Check uniqueness of order ID in the summarized payments." / "The intended order population must survive the join." / "Reconcile the repaired output to the source order total." / "Order value and payment value are different measures." / "Define how orders without payments are represented." / "Fix the grain and verify the result before republishing."
Vocabulary: SQL: Structured Query Language, used to query relational data. / row grain: What one row represents in a dataset. / primary key: A non-null column or set of columns uniquely identifying each row. / foreign key: A column or set of columns constrained to reference a key in a table. / join key: The field or fields used to match tables. / join cardinality: The relationship in match counts between joined entities. / one-to-many relationship: One entity matching multiple related records. / fanout: Multiplication of rows caused by multiple join matches. / aggregation: Combining records into summary values. / pre-aggregation: Summarizing data before another transformation or join. / GROUP BY: SQL grouping of rows for aggregate calculations. / SUM: An aggregate that adds non-null numeric values. / DISTINCT: SQL removal of duplicate values or rows in its specified scope. / COUNT: An aggregate that counts rows or non-null expressions. / inner join: A join returning matching combinations from both sides. / left join: A join retaining left rows even without a right match. / null handling: Rules for processing missing or unknown values. / filter: A condition selecting which records remain. / CTE: Common table expression, a named query expression. / data model: A representation of entities, relationships, and measures. / fact table: A table storing business events or measurements at a defined grain. / dimension table: A table holding descriptive attributes for analysis. / reconciliation total: A reference total used to verify transformed output. / uniqueness test: A check that a defined key has no duplicates.
Speaking task: Read turns 1-10. Contrast an order identity with its amount. Switch roles for turns 11-20. Stress one row per order and both reconciliation checks. Check the transfer. Read the correct total, inflated sum, and distinct-value sum separately.
Partner: Lina: Analytics engineer / Owen: Reporting analyst
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Order A is $80 with two $40 payments. Order B is $80 with one $80 payment. An order-to-payment join yields three rows. The report must count each order amount once.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will check both the two-order count and the two-hundred-dollar total. Could those totals look right even if one missing order offsets a duplicate?
Lina: Use the original reconciliation total as a reference and inspect differences. A plausible-looking grand total alone is not enough if missing orders and duplicated orders happen to offset each other.
Owen: My explanation will say the join repeated an order-level amount; it did not create revenue. I will withhold the inflated result while the transformation is corrected.
Lina: Add a uniqueness test for the summarized order key and document the grain. That makes the repair repeatable rather than relying on someone noticing another surprising total later.
END REFERENCE
END PROMPT

Lesson 05 · SQL, Models, and Transformation Logic | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 05: SQL, Models, and Transformation Logic
Original fictional case: Analytics engineer Lina reviews a report with analyst Owen. The complete teaching dataset has two orders: O1 is $100 and O2 is $100. Payment rows are O1: $60 and $40; O2: $100. Joining orders to payments on order ID creates three rows. Summing the repeated order amount then gives $300, although total order value is $200. SUM(DISTINCT order_amount) gives $100 because the two legitimate orders share an amount. Lina proposes aggregating payments to one row per order before joining, with key and total checks.
Language workshop: The join adds rows, not order value
Communication goal: Explain row grain and join multiplicity, diagnose a duplicated aggregate, and reject a misleading distinct-value fix.
Language guidance: The joined order amounts are 100, 100, and 100: O1 appears twice because it has two payments. The correct order total is 200. The payment amounts themselves are 60, 40, and 100, also totaling 200 for this dataset.
Useful expressions (preserve the supplied facts): "What does one row represent before the join?" / "The tables match on order ID." / "O1 has two payment rows." / "The order row is repeated for each matching payment." / "The extra row is not an extra order." / "Summing joined order amounts produces $300." / "The order-level total is $200." / "Distinct amounts do not mean distinct orders." / "Both legitimate orders have an amount of $100." / "Aggregate payments to one row per order before joining." / "Check uniqueness of order ID in the summarized payments." / "The intended order population must survive the join." / "Reconcile the repaired output to the source order total." / "Order value and payment value are different measures." / "Define how orders without payments are represented." / "Fix the grain and verify the result before republishing."
Vocabulary: SQL: Structured Query Language, used to query relational data. / row grain: What one row represents in a dataset. / primary key: A non-null column or set of columns uniquely identifying each row. / foreign key: A column or set of columns constrained to reference a key in a table. / join key: The field or fields used to match tables. / join cardinality: The relationship in match counts between joined entities. / one-to-many relationship: One entity matching multiple related records. / fanout: Multiplication of rows caused by multiple join matches. / aggregation: Combining records into summary values. / pre-aggregation: Summarizing data before another transformation or join. / GROUP BY: SQL grouping of rows for aggregate calculations. / SUM: An aggregate that adds non-null numeric values. / DISTINCT: SQL removal of duplicate values or rows in its specified scope. / COUNT: An aggregate that counts rows or non-null expressions. / inner join: A join returning matching combinations from both sides. / left join: A join retaining left rows even without a right match. / null handling: Rules for processing missing or unknown values. / filter: A condition selecting which records remain. / CTE: Common table expression, a named query expression. / data model: A representation of entities, relationships, and measures. / fact table: A table storing business events or measurements at a defined grain. / dimension table: A table holding descriptive attributes for analysis. / reconciliation total: A reference total used to verify transformed output. / uniqueness test: A check that a defined key has no duplicates.
Speaking task: Read turns 1-10. Contrast an order identity with its amount. Switch roles for turns 11-20. Stress one row per order and both reconciliation checks. Check the transfer. Read the correct total, inflated sum, and distinct-value sum separately.
Partner: Lina: Analytics engineer / Owen: Reporting analyst
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Order A is $80 with two $40 payments. Order B is $80 with one $80 payment. An order-to-payment join yields three rows. The report must count each order amount once.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will check both the two-order count and the two-hundred-dollar total. Could those totals look right even if one missing order offsets a duplicate?
Lina: Use the original reconciliation total as a reference and inspect differences. A plausible-looking grand total alone is not enough if missing orders and duplicated orders happen to offset each other.
Owen: My explanation will say the join repeated an order-level amount; it did not create revenue. I will withhold the inflated result while the transformation is corrected.
Lina: Add a uniqueness test for the summarized order key and document the grain. That makes the repair repeatable rather than relying on someone noticing another surprising total later.
END REFERENCE
END PROMPT

Lesson 05 · SQL, Models, and Transformation Logic | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 05: SQL, Models, and Transformation Logic
Original fictional case: Analytics engineer Lina reviews a report with analyst Owen. The complete teaching dataset has two orders: O1 is $100 and O2 is $100. Payment rows are O1: $60 and $40; O2: $100. Joining orders to payments on order ID creates three rows. Summing the repeated order amount then gives $300, although total order value is $200. SUM(DISTINCT order_amount) gives $100 because the two legitimate orders share an amount. Lina proposes aggregating payments to one row per order before joining, with key and total checks.
Language workshop: The join adds rows, not order value
Communication goal: Explain row grain and join multiplicity, diagnose a duplicated aggregate, and reject a misleading distinct-value fix.
Language guidance: The joined order amounts are 100, 100, and 100: O1 appears twice because it has two payments. The correct order total is 200. The payment amounts themselves are 60, 40, and 100, also totaling 200 for this dataset.
Useful expressions (preserve the supplied facts): "What does one row represent before the join?" / "The tables match on order ID." / "O1 has two payment rows." / "The order row is repeated for each matching payment." / "The extra row is not an extra order." / "Summing joined order amounts produces $300." / "The order-level total is $200." / "Distinct amounts do not mean distinct orders." / "Both legitimate orders have an amount of $100." / "Aggregate payments to one row per order before joining." / "Check uniqueness of order ID in the summarized payments." / "The intended order population must survive the join." / "Reconcile the repaired output to the source order total." / "Order value and payment value are different measures." / "Define how orders without payments are represented." / "Fix the grain and verify the result before republishing."
Vocabulary: SQL: Structured Query Language, used to query relational data. / row grain: What one row represents in a dataset. / primary key: A non-null column or set of columns uniquely identifying each row. / foreign key: A column or set of columns constrained to reference a key in a table. / join key: The field or fields used to match tables. / join cardinality: The relationship in match counts between joined entities. / one-to-many relationship: One entity matching multiple related records. / fanout: Multiplication of rows caused by multiple join matches. / aggregation: Combining records into summary values. / pre-aggregation: Summarizing data before another transformation or join. / GROUP BY: SQL grouping of rows for aggregate calculations. / SUM: An aggregate that adds non-null numeric values. / DISTINCT: SQL removal of duplicate values or rows in its specified scope. / COUNT: An aggregate that counts rows or non-null expressions. / inner join: A join returning matching combinations from both sides. / left join: A join retaining left rows even without a right match. / null handling: Rules for processing missing or unknown values. / filter: A condition selecting which records remain. / CTE: Common table expression, a named query expression. / data model: A representation of entities, relationships, and measures. / fact table: A table storing business events or measurements at a defined grain. / dimension table: A table holding descriptive attributes for analysis. / reconciliation total: A reference total used to verify transformed output. / uniqueness test: A check that a defined key has no duplicates.
Speaking task: Read turns 1-10. Contrast an order identity with its amount. Switch roles for turns 11-20. Stress one row per order and both reconciliation checks. Check the transfer. Read the correct total, inflated sum, and distinct-value sum separately.
Partner: Lina: Analytics engineer / Owen: Reporting analyst
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Order A is $80 with two $40 payments. Order B is $80 with one $80 payment. An order-to-payment join yields three rows. The report must count each order amount once.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will check both the two-order count and the two-hundred-dollar total. Could those totals look right even if one missing order offsets a duplicate?
Lina: Use the original reconciliation total as a reference and inspect differences. A plausible-looking grand total alone is not enough if missing orders and duplicated orders happen to offset each other.
Owen: My explanation will say the join repeated an order-level amount; it did not create revenue. I will withhold the inflated result while the transformation is corrected.
Lina: Add a uniqueness test for the summarized order key and document the grain. That makes the repair repeatable rather than relying on someone noticing another surprising total later.
END REFERENCE
END PROMPT

Lesson 06 · Experiment Readouts and Statistical Thinking | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 06: Experiment Readouts and Statistical Thinking
Original fictional case: Experiment analyst Theo reviews a completed randomized test with product director Hana. The validated readout estimates a 1.2-percentage-point increase in completion, with a 95% confidence interval from -0.4 to +2.8 points. The pre-agreed rollout rule requires the interval lower bound to exceed +1.0 point, with guardrails passing. Guardrails passed, but the lower-bound condition did not. The slide currently shows only +1.2. The test has reached its planned endpoint; no unplanned extension or new rollout approval is authorized.
Language workshop: A positive estimate is not the rollout rule
Communication goal: Present an experiment estimate with its interval, practical threshold, and pre-agreed decision rule.
Language guidance: The point estimate is +1.2 points, but the interval runs from -0.4 to +2.8. It includes zero and values below the practical threshold. Under the supplied rule, a passing guardrail cannot compensate for a failing lower bound.
Useful expressions (preserve the supplied facts): "The estimated effect is plus 1.2 percentage points." / "The 95% interval runs from minus 0.4 to plus 2.8 points." / "The interval includes zero." / "These are percentage points, not relative percentages." / "The lower bound must exceed plus 1.0 point." / "The lower-bound condition was not met." / "The guardrails passed." / "Passing guardrails does not replace the effect requirement." / "This readout does not authorize rollout under our rule." / "It also does not prove the true effect is zero." / "The planned test has ended." / "We cannot keep collecting until the result looks favorable." / "Any new study needs an explicitly reviewed design." / "Place both bounds beside the estimate." / "The signal may merit follow-up without passing this launch rule." / "Report the estimate, interval, guardrails, and unmet decision condition together."
Vocabulary: randomized experiment: A study allocating exposure through a random process. / point estimate: A single value estimating an unknown quantity. / interval estimate: A range estimating an unknown quantity under a method. / confidence interval: An interval from a method with specified long-run coverage. / confidence level: The nominal long-run coverage rate of the interval method. / lower bound: The smaller endpoint of an interval. / upper bound: The larger endpoint of an interval. / effect size: The magnitude of a difference or relationship. / no-change value: The parameter value representing no effect on the stated scale. / practical threshold: The effect boundary relevant to a business decision. / decision rule: A predefined condition governing a conclusion or action. / guardrail: A measure limiting unacceptable side effects. / primary outcome: The main measure used to assess the intervention. / planned endpoint: The pre-agreed point for completing the analysis or test. / statistical significance: A result meeting a specified statistical testing criterion. / practical significance: Importance of an effect for a real decision. / null hypothesis: A specified claim assessed by a statistical test. / standard error: The standard deviation of an estimator's sampling distribution, usually estimated. / sampling variability: Variation in estimates across possible samples. / statistical power: Probability of detecting a specified effect under assumptions. / minimum detectable effect: An effect size used in the study's power planning. / sequential analysis: A method allowing planned repeated statistical decisions. / equivalence: Similarity within a predefined acceptable difference margin. / inconclusive result: Evidence insufficient for the specified conclusion.
Speaking task: Read turns 1-10. Say minus and plus clearly for both interval endpoints. Switch roles for turns 11-20. Contrast an unmet rollout rule with proof of no effect. Check the transfer. Stress the lower bound rather than the positive point estimate.
Partner: Theo: Experiment analyst / Hana: Product director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An experiment estimates +0.8 points with a 95% interval from -0.2 to +1.8. The rule requires the lower bound to exceed +0.5, and guardrails pass. The planned test has ended.
Model for comparison AFTER my attempt, not a response to give me first: Hana: I will also keep the units visible. Plus one point two means percentage points, not a one-point-two-percent relative increase from an unstated baseline.
Theo: Good. The practical threshold should be displayed on the same scale. Statistical uncertainty and business value are related in the decision, but they are not interchangeable labels.
Hana: My revised readout will show the center, both bounds, passing guardrails, and the unmet rollout condition. No launch approval or no-effect conclusion will be implied.
Theo: That preserves practical significance as a separate question. The signal may merit well-designed follow-up, but this completed test has not passed the agreed rule for rollout.
END REFERENCE
END PROMPT

Lesson 06 · Experiment Readouts and Statistical Thinking | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 06: Experiment Readouts and Statistical Thinking
Original fictional case: Experiment analyst Theo reviews a completed randomized test with product director Hana. The validated readout estimates a 1.2-percentage-point increase in completion, with a 95% confidence interval from -0.4 to +2.8 points. The pre-agreed rollout rule requires the interval lower bound to exceed +1.0 point, with guardrails passing. Guardrails passed, but the lower-bound condition did not. The slide currently shows only +1.2. The test has reached its planned endpoint; no unplanned extension or new rollout approval is authorized.
Language workshop: A positive estimate is not the rollout rule
Communication goal: Present an experiment estimate with its interval, practical threshold, and pre-agreed decision rule.
Language guidance: The point estimate is +1.2 points, but the interval runs from -0.4 to +2.8. It includes zero and values below the practical threshold. Under the supplied rule, a passing guardrail cannot compensate for a failing lower bound.
Useful expressions (preserve the supplied facts): "The estimated effect is plus 1.2 percentage points." / "The 95% interval runs from minus 0.4 to plus 2.8 points." / "The interval includes zero." / "These are percentage points, not relative percentages." / "The lower bound must exceed plus 1.0 point." / "The lower-bound condition was not met." / "The guardrails passed." / "Passing guardrails does not replace the effect requirement." / "This readout does not authorize rollout under our rule." / "It also does not prove the true effect is zero." / "The planned test has ended." / "We cannot keep collecting until the result looks favorable." / "Any new study needs an explicitly reviewed design." / "Place both bounds beside the estimate." / "The signal may merit follow-up without passing this launch rule." / "Report the estimate, interval, guardrails, and unmet decision condition together."
Vocabulary: randomized experiment: A study allocating exposure through a random process. / point estimate: A single value estimating an unknown quantity. / interval estimate: A range estimating an unknown quantity under a method. / confidence interval: An interval from a method with specified long-run coverage. / confidence level: The nominal long-run coverage rate of the interval method. / lower bound: The smaller endpoint of an interval. / upper bound: The larger endpoint of an interval. / effect size: The magnitude of a difference or relationship. / no-change value: The parameter value representing no effect on the stated scale. / practical threshold: The effect boundary relevant to a business decision. / decision rule: A predefined condition governing a conclusion or action. / guardrail: A measure limiting unacceptable side effects. / primary outcome: The main measure used to assess the intervention. / planned endpoint: The pre-agreed point for completing the analysis or test. / statistical significance: A result meeting a specified statistical testing criterion. / practical significance: Importance of an effect for a real decision. / null hypothesis: A specified claim assessed by a statistical test. / standard error: The standard deviation of an estimator's sampling distribution, usually estimated. / sampling variability: Variation in estimates across possible samples. / statistical power: Probability of detecting a specified effect under assumptions. / minimum detectable effect: An effect size used in the study's power planning. / sequential analysis: A method allowing planned repeated statistical decisions. / equivalence: Similarity within a predefined acceptable difference margin. / inconclusive result: Evidence insufficient for the specified conclusion.
Speaking task: Read turns 1-10. Say minus and plus clearly for both interval endpoints. Switch roles for turns 11-20. Contrast an unmet rollout rule with proof of no effect. Check the transfer. Stress the lower bound rather than the positive point estimate.
Partner: Theo: Experiment analyst / Hana: Product director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An experiment estimates +0.8 points with a 95% interval from -0.2 to +1.8. The rule requires the lower bound to exceed +0.5, and guardrails pass. The planned test has ended.
Model for comparison AFTER my attempt, not a response to give me first: Hana: I will also keep the units visible. Plus one point two means percentage points, not a one-point-two-percent relative increase from an unstated baseline.
Theo: Good. The practical threshold should be displayed on the same scale. Statistical uncertainty and business value are related in the decision, but they are not interchangeable labels.
Hana: My revised readout will show the center, both bounds, passing guardrails, and the unmet rollout condition. No launch approval or no-effect conclusion will be implied.
Theo: That preserves practical significance as a separate question. The signal may merit well-designed follow-up, but this completed test has not passed the agreed rule for rollout.
END REFERENCE
END PROMPT

Lesson 06 · Experiment Readouts and Statistical Thinking | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 06: Experiment Readouts and Statistical Thinking
Original fictional case: Experiment analyst Theo reviews a completed randomized test with product director Hana. The validated readout estimates a 1.2-percentage-point increase in completion, with a 95% confidence interval from -0.4 to +2.8 points. The pre-agreed rollout rule requires the interval lower bound to exceed +1.0 point, with guardrails passing. Guardrails passed, but the lower-bound condition did not. The slide currently shows only +1.2. The test has reached its planned endpoint; no unplanned extension or new rollout approval is authorized.
Language workshop: A positive estimate is not the rollout rule
Communication goal: Present an experiment estimate with its interval, practical threshold, and pre-agreed decision rule.
Language guidance: The point estimate is +1.2 points, but the interval runs from -0.4 to +2.8. It includes zero and values below the practical threshold. Under the supplied rule, a passing guardrail cannot compensate for a failing lower bound.
Useful expressions (preserve the supplied facts): "The estimated effect is plus 1.2 percentage points." / "The 95% interval runs from minus 0.4 to plus 2.8 points." / "The interval includes zero." / "These are percentage points, not relative percentages." / "The lower bound must exceed plus 1.0 point." / "The lower-bound condition was not met." / "The guardrails passed." / "Passing guardrails does not replace the effect requirement." / "This readout does not authorize rollout under our rule." / "It also does not prove the true effect is zero." / "The planned test has ended." / "We cannot keep collecting until the result looks favorable." / "Any new study needs an explicitly reviewed design." / "Place both bounds beside the estimate." / "The signal may merit follow-up without passing this launch rule." / "Report the estimate, interval, guardrails, and unmet decision condition together."
Vocabulary: randomized experiment: A study allocating exposure through a random process. / point estimate: A single value estimating an unknown quantity. / interval estimate: A range estimating an unknown quantity under a method. / confidence interval: An interval from a method with specified long-run coverage. / confidence level: The nominal long-run coverage rate of the interval method. / lower bound: The smaller endpoint of an interval. / upper bound: The larger endpoint of an interval. / effect size: The magnitude of a difference or relationship. / no-change value: The parameter value representing no effect on the stated scale. / practical threshold: The effect boundary relevant to a business decision. / decision rule: A predefined condition governing a conclusion or action. / guardrail: A measure limiting unacceptable side effects. / primary outcome: The main measure used to assess the intervention. / planned endpoint: The pre-agreed point for completing the analysis or test. / statistical significance: A result meeting a specified statistical testing criterion. / practical significance: Importance of an effect for a real decision. / null hypothesis: A specified claim assessed by a statistical test. / standard error: The standard deviation of an estimator's sampling distribution, usually estimated. / sampling variability: Variation in estimates across possible samples. / statistical power: Probability of detecting a specified effect under assumptions. / minimum detectable effect: An effect size used in the study's power planning. / sequential analysis: A method allowing planned repeated statistical decisions. / equivalence: Similarity within a predefined acceptable difference margin. / inconclusive result: Evidence insufficient for the specified conclusion.
Speaking task: Read turns 1-10. Say minus and plus clearly for both interval endpoints. Switch roles for turns 11-20. Contrast an unmet rollout rule with proof of no effect. Check the transfer. Stress the lower bound rather than the positive point estimate.
Partner: Theo: Experiment analyst / Hana: Product director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An experiment estimates +0.8 points with a 95% interval from -0.2 to +1.8. The rule requires the lower bound to exceed +0.5, and guardrails pass. The planned test has ended.
Model for comparison AFTER my attempt, not a response to give me first: Hana: I will also keep the units visible. Plus one point two means percentage points, not a one-point-two-percent relative increase from an unstated baseline.
Theo: Good. The practical threshold should be displayed on the same scale. Statistical uncertainty and business value are related in the decision, but they are not interchangeable labels.
Hana: My revised readout will show the center, both bounds, passing guardrails, and the unmet rollout condition. No launch approval or no-effect conclusion will be implied.
Theo: That preserves practical significance as a separate question. The signal may merit well-designed follow-up, but this completed test has not passed the agreed rule for rollout.
END REFERENCE
END PROMPT

Lesson 06 · Experiment Readouts and Statistical Thinking | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 06: Experiment Readouts and Statistical Thinking
Original fictional case: Experiment analyst Theo reviews a completed randomized test with product director Hana. The validated readout estimates a 1.2-percentage-point increase in completion, with a 95% confidence interval from -0.4 to +2.8 points. The pre-agreed rollout rule requires the interval lower bound to exceed +1.0 point, with guardrails passing. Guardrails passed, but the lower-bound condition did not. The slide currently shows only +1.2. The test has reached its planned endpoint; no unplanned extension or new rollout approval is authorized.
Language workshop: A positive estimate is not the rollout rule
Communication goal: Present an experiment estimate with its interval, practical threshold, and pre-agreed decision rule.
Language guidance: The point estimate is +1.2 points, but the interval runs from -0.4 to +2.8. It includes zero and values below the practical threshold. Under the supplied rule, a passing guardrail cannot compensate for a failing lower bound.
Useful expressions (preserve the supplied facts): "The estimated effect is plus 1.2 percentage points." / "The 95% interval runs from minus 0.4 to plus 2.8 points." / "The interval includes zero." / "These are percentage points, not relative percentages." / "The lower bound must exceed plus 1.0 point." / "The lower-bound condition was not met." / "The guardrails passed." / "Passing guardrails does not replace the effect requirement." / "This readout does not authorize rollout under our rule." / "It also does not prove the true effect is zero." / "The planned test has ended." / "We cannot keep collecting until the result looks favorable." / "Any new study needs an explicitly reviewed design." / "Place both bounds beside the estimate." / "The signal may merit follow-up without passing this launch rule." / "Report the estimate, interval, guardrails, and unmet decision condition together."
Vocabulary: randomized experiment: A study allocating exposure through a random process. / point estimate: A single value estimating an unknown quantity. / interval estimate: A range estimating an unknown quantity under a method. / confidence interval: An interval from a method with specified long-run coverage. / confidence level: The nominal long-run coverage rate of the interval method. / lower bound: The smaller endpoint of an interval. / upper bound: The larger endpoint of an interval. / effect size: The magnitude of a difference or relationship. / no-change value: The parameter value representing no effect on the stated scale. / practical threshold: The effect boundary relevant to a business decision. / decision rule: A predefined condition governing a conclusion or action. / guardrail: A measure limiting unacceptable side effects. / primary outcome: The main measure used to assess the intervention. / planned endpoint: The pre-agreed point for completing the analysis or test. / statistical significance: A result meeting a specified statistical testing criterion. / practical significance: Importance of an effect for a real decision. / null hypothesis: A specified claim assessed by a statistical test. / standard error: The standard deviation of an estimator's sampling distribution, usually estimated. / sampling variability: Variation in estimates across possible samples. / statistical power: Probability of detecting a specified effect under assumptions. / minimum detectable effect: An effect size used in the study's power planning. / sequential analysis: A method allowing planned repeated statistical decisions. / equivalence: Similarity within a predefined acceptable difference margin. / inconclusive result: Evidence insufficient for the specified conclusion.
Speaking task: Read turns 1-10. Say minus and plus clearly for both interval endpoints. Switch roles for turns 11-20. Contrast an unmet rollout rule with proof of no effect. Check the transfer. Stress the lower bound rather than the positive point estimate.
Partner: Theo: Experiment analyst / Hana: Product director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An experiment estimates +0.8 points with a 95% interval from -0.2 to +1.8. The rule requires the lower bound to exceed +0.5, and guardrails pass. The planned test has ended.
Model for comparison AFTER my attempt, not a response to give me first: Hana: I will also keep the units visible. Plus one point two means percentage points, not a one-point-two-percent relative increase from an unstated baseline.
Theo: Good. The practical threshold should be displayed on the same scale. Statistical uncertainty and business value are related in the decision, but they are not interchangeable labels.
Hana: My revised readout will show the center, both bounds, passing guardrails, and the unmet rollout condition. No launch approval or no-effect conclusion will be implied.
Theo: That preserves practical significance as a separate question. The signal may merit well-designed follow-up, but this completed test has not passed the agreed rule for rollout.
END REFERENCE
END PROMPT

Lesson 07 · Data Governance and Privacy | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 07: Data Governance and Privacy
Original fictional case: Analyst Sara asks data steward Malik for a full customer export to compare weekly late-resolution rates by product tier. The supplied analysis can use week, tier, eligible-case count, and late-case count; names, emails, phone numbers, and free-text comments are unnecessary. A team proposal uses a reviewed aggregate table in the approved workspace with 30-day access, subject to owner approval and disclosure review. Approval is pending. Small groups still require review. Replacing names with stable IDs would not automatically make row-level data anonymous or remove controls.
Language workshop: The analysis needs weekly counts, not customer names
Communication goal: Specify a purpose-limited data request, distinguish pseudonymization from anonymity, and preserve approval and retention controls.
Language guidance: The rate needs late-case count divided by eligible-case count within each week and tier. Names and contact details do not support that supplied calculation. Data minimization means enough relevant data for the purpose, not an unusably stripped dataset.
Useful expressions (preserve the supplied facts): "We are comparing weekly late-resolution rates by tier." / "The calculation needs counts by week and tier." / "Names and contact details are unnecessary for this question." / "Use the reviewed aggregate table." / "Include eligible-case counts as well as late-case counts." / "Owner approval is still pending." / "The work belongs in the approved workspace." / "The proposed access duration is thirty days." / "Access expiry is not automatically the data-retention rule." / "Small groups still need disclosure review." / "Stable IDs do not automatically make the records anonymous." / "Confirm who may receive the output." / "Do not assume approval permits an external export." / "A different question may need a new review." / "Keep the source and transformation lineage." / "Submit the purpose, four fields, workspace, duration, and review conditions."
Vocabulary: data governance: Responsibilities and rules for managing data use. / data steward: A role supporting defined data quality and handling responsibilities. / data owner: The role accountable for specified data decisions. / purpose limitation: Restricting data use to defined appropriate purposes. / data minimization: Limiting data to what the stated purpose needs. / personal data: Information relating to an identifiable person under the applicable rules. / direct identifier: A field that directly identifies a person. / indirect identifier: A field that may identify someone when combined with other information. / pseudonymization: Replacing identifying details while retaining possible linkage. / anonymization: Processing intended to prevent identification under the relevant standard. / re-identification risk: The possibility of connecting data back to an individual. / aggregation: Combining records into group-level summaries. / small cell: A reported group with few contributing observations. / disclosure review: Assessment of risks from releasing or sharing information. / access scope: The specific data and actions a permission covers. / retention period: The duration for which data is kept under defined rules. / access expiry: The point when an access permission ends. / approved workspace: An environment authorized for the stated data work. / data lineage: The traceable path of data through sources and transformations. / data catalog: An organized inventory of datasets and their metadata. / processing purpose: The defined reason for collecting or using data. / permitted audience: The people authorized to receive a result or dataset. / export restriction: A limit on moving data outside an approved environment. / secondary use: A use beyond the original stated purpose.
Speaking task: Read turns 1-10. Stress the four needed fields and remaining disclosure review. Switch roles for turns 11-20. Keep access expiry distinct from retention. Check the transfer. Read the fourteen-day proposal without implying approval already exists.
Partner: Sara: Data analyst / Malik: Data steward
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An analyst needs monthly complaint rates by region. The approved design uses month, region, complaint count, and eligible-order count. Names and phone numbers are unnecessary. Access approval is pending; proposed access lasts 14 days.
Model for comparison AFTER my attempt, not a response to give me first: Sara: If we later need customer-level linkage, I will bring a new purpose and field list. This request should not become permission for unrelated analysis.
Malik: That would be a secondary use review. We can assess the new need on its facts, but the current weekly-rate purpose should not become a blanket authorization for every future analysis.
Sara: My request will list the four fields, rate, workspace, thirty-day access, audience, and required reviews. Approval remains pending.
Malik: Include the data lineage for the aggregate counts as well. That preserves both analytical trust and the handling boundary while giving you the information the actual question needs.
END REFERENCE
END PROMPT

Lesson 07 · Data Governance and Privacy | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 07: Data Governance and Privacy
Original fictional case: Analyst Sara asks data steward Malik for a full customer export to compare weekly late-resolution rates by product tier. The supplied analysis can use week, tier, eligible-case count, and late-case count; names, emails, phone numbers, and free-text comments are unnecessary. A team proposal uses a reviewed aggregate table in the approved workspace with 30-day access, subject to owner approval and disclosure review. Approval is pending. Small groups still require review. Replacing names with stable IDs would not automatically make row-level data anonymous or remove controls.
Language workshop: The analysis needs weekly counts, not customer names
Communication goal: Specify a purpose-limited data request, distinguish pseudonymization from anonymity, and preserve approval and retention controls.
Language guidance: The rate needs late-case count divided by eligible-case count within each week and tier. Names and contact details do not support that supplied calculation. Data minimization means enough relevant data for the purpose, not an unusably stripped dataset.
Useful expressions (preserve the supplied facts): "We are comparing weekly late-resolution rates by tier." / "The calculation needs counts by week and tier." / "Names and contact details are unnecessary for this question." / "Use the reviewed aggregate table." / "Include eligible-case counts as well as late-case counts." / "Owner approval is still pending." / "The work belongs in the approved workspace." / "The proposed access duration is thirty days." / "Access expiry is not automatically the data-retention rule." / "Small groups still need disclosure review." / "Stable IDs do not automatically make the records anonymous." / "Confirm who may receive the output." / "Do not assume approval permits an external export." / "A different question may need a new review." / "Keep the source and transformation lineage." / "Submit the purpose, four fields, workspace, duration, and review conditions."
Vocabulary: data governance: Responsibilities and rules for managing data use. / data steward: A role supporting defined data quality and handling responsibilities. / data owner: The role accountable for specified data decisions. / purpose limitation: Restricting data use to defined appropriate purposes. / data minimization: Limiting data to what the stated purpose needs. / personal data: Information relating to an identifiable person under the applicable rules. / direct identifier: A field that directly identifies a person. / indirect identifier: A field that may identify someone when combined with other information. / pseudonymization: Replacing identifying details while retaining possible linkage. / anonymization: Processing intended to prevent identification under the relevant standard. / re-identification risk: The possibility of connecting data back to an individual. / aggregation: Combining records into group-level summaries. / small cell: A reported group with few contributing observations. / disclosure review: Assessment of risks from releasing or sharing information. / access scope: The specific data and actions a permission covers. / retention period: The duration for which data is kept under defined rules. / access expiry: The point when an access permission ends. / approved workspace: An environment authorized for the stated data work. / data lineage: The traceable path of data through sources and transformations. / data catalog: An organized inventory of datasets and their metadata. / processing purpose: The defined reason for collecting or using data. / permitted audience: The people authorized to receive a result or dataset. / export restriction: A limit on moving data outside an approved environment. / secondary use: A use beyond the original stated purpose.
Speaking task: Read turns 1-10. Stress the four needed fields and remaining disclosure review. Switch roles for turns 11-20. Keep access expiry distinct from retention. Check the transfer. Read the fourteen-day proposal without implying approval already exists.
Partner: Sara: Data analyst / Malik: Data steward
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An analyst needs monthly complaint rates by region. The approved design uses month, region, complaint count, and eligible-order count. Names and phone numbers are unnecessary. Access approval is pending; proposed access lasts 14 days.
Model for comparison AFTER my attempt, not a response to give me first: Sara: If we later need customer-level linkage, I will bring a new purpose and field list. This request should not become permission for unrelated analysis.
Malik: That would be a secondary use review. We can assess the new need on its facts, but the current weekly-rate purpose should not become a blanket authorization for every future analysis.
Sara: My request will list the four fields, rate, workspace, thirty-day access, audience, and required reviews. Approval remains pending.
Malik: Include the data lineage for the aggregate counts as well. That preserves both analytical trust and the handling boundary while giving you the information the actual question needs.
END REFERENCE
END PROMPT

Lesson 07 · Data Governance and Privacy | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 07: Data Governance and Privacy
Original fictional case: Analyst Sara asks data steward Malik for a full customer export to compare weekly late-resolution rates by product tier. The supplied analysis can use week, tier, eligible-case count, and late-case count; names, emails, phone numbers, and free-text comments are unnecessary. A team proposal uses a reviewed aggregate table in the approved workspace with 30-day access, subject to owner approval and disclosure review. Approval is pending. Small groups still require review. Replacing names with stable IDs would not automatically make row-level data anonymous or remove controls.
Language workshop: The analysis needs weekly counts, not customer names
Communication goal: Specify a purpose-limited data request, distinguish pseudonymization from anonymity, and preserve approval and retention controls.
Language guidance: The rate needs late-case count divided by eligible-case count within each week and tier. Names and contact details do not support that supplied calculation. Data minimization means enough relevant data for the purpose, not an unusably stripped dataset.
Useful expressions (preserve the supplied facts): "We are comparing weekly late-resolution rates by tier." / "The calculation needs counts by week and tier." / "Names and contact details are unnecessary for this question." / "Use the reviewed aggregate table." / "Include eligible-case counts as well as late-case counts." / "Owner approval is still pending." / "The work belongs in the approved workspace." / "The proposed access duration is thirty days." / "Access expiry is not automatically the data-retention rule." / "Small groups still need disclosure review." / "Stable IDs do not automatically make the records anonymous." / "Confirm who may receive the output." / "Do not assume approval permits an external export." / "A different question may need a new review." / "Keep the source and transformation lineage." / "Submit the purpose, four fields, workspace, duration, and review conditions."
Vocabulary: data governance: Responsibilities and rules for managing data use. / data steward: A role supporting defined data quality and handling responsibilities. / data owner: The role accountable for specified data decisions. / purpose limitation: Restricting data use to defined appropriate purposes. / data minimization: Limiting data to what the stated purpose needs. / personal data: Information relating to an identifiable person under the applicable rules. / direct identifier: A field that directly identifies a person. / indirect identifier: A field that may identify someone when combined with other information. / pseudonymization: Replacing identifying details while retaining possible linkage. / anonymization: Processing intended to prevent identification under the relevant standard. / re-identification risk: The possibility of connecting data back to an individual. / aggregation: Combining records into group-level summaries. / small cell: A reported group with few contributing observations. / disclosure review: Assessment of risks from releasing or sharing information. / access scope: The specific data and actions a permission covers. / retention period: The duration for which data is kept under defined rules. / access expiry: The point when an access permission ends. / approved workspace: An environment authorized for the stated data work. / data lineage: The traceable path of data through sources and transformations. / data catalog: An organized inventory of datasets and their metadata. / processing purpose: The defined reason for collecting or using data. / permitted audience: The people authorized to receive a result or dataset. / export restriction: A limit on moving data outside an approved environment. / secondary use: A use beyond the original stated purpose.
Speaking task: Read turns 1-10. Stress the four needed fields and remaining disclosure review. Switch roles for turns 11-20. Keep access expiry distinct from retention. Check the transfer. Read the fourteen-day proposal without implying approval already exists.
Partner: Sara: Data analyst / Malik: Data steward
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An analyst needs monthly complaint rates by region. The approved design uses month, region, complaint count, and eligible-order count. Names and phone numbers are unnecessary. Access approval is pending; proposed access lasts 14 days.
Model for comparison AFTER my attempt, not a response to give me first: Sara: If we later need customer-level linkage, I will bring a new purpose and field list. This request should not become permission for unrelated analysis.
Malik: That would be a secondary use review. We can assess the new need on its facts, but the current weekly-rate purpose should not become a blanket authorization for every future analysis.
Sara: My request will list the four fields, rate, workspace, thirty-day access, audience, and required reviews. Approval remains pending.
Malik: Include the data lineage for the aggregate counts as well. That preserves both analytical trust and the handling boundary while giving you the information the actual question needs.
END REFERENCE
END PROMPT

Lesson 07 · Data Governance and Privacy | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 07: Data Governance and Privacy
Original fictional case: Analyst Sara asks data steward Malik for a full customer export to compare weekly late-resolution rates by product tier. The supplied analysis can use week, tier, eligible-case count, and late-case count; names, emails, phone numbers, and free-text comments are unnecessary. A team proposal uses a reviewed aggregate table in the approved workspace with 30-day access, subject to owner approval and disclosure review. Approval is pending. Small groups still require review. Replacing names with stable IDs would not automatically make row-level data anonymous or remove controls.
Language workshop: The analysis needs weekly counts, not customer names
Communication goal: Specify a purpose-limited data request, distinguish pseudonymization from anonymity, and preserve approval and retention controls.
Language guidance: The rate needs late-case count divided by eligible-case count within each week and tier. Names and contact details do not support that supplied calculation. Data minimization means enough relevant data for the purpose, not an unusably stripped dataset.
Useful expressions (preserve the supplied facts): "We are comparing weekly late-resolution rates by tier." / "The calculation needs counts by week and tier." / "Names and contact details are unnecessary for this question." / "Use the reviewed aggregate table." / "Include eligible-case counts as well as late-case counts." / "Owner approval is still pending." / "The work belongs in the approved workspace." / "The proposed access duration is thirty days." / "Access expiry is not automatically the data-retention rule." / "Small groups still need disclosure review." / "Stable IDs do not automatically make the records anonymous." / "Confirm who may receive the output." / "Do not assume approval permits an external export." / "A different question may need a new review." / "Keep the source and transformation lineage." / "Submit the purpose, four fields, workspace, duration, and review conditions."
Vocabulary: data governance: Responsibilities and rules for managing data use. / data steward: A role supporting defined data quality and handling responsibilities. / data owner: The role accountable for specified data decisions. / purpose limitation: Restricting data use to defined appropriate purposes. / data minimization: Limiting data to what the stated purpose needs. / personal data: Information relating to an identifiable person under the applicable rules. / direct identifier: A field that directly identifies a person. / indirect identifier: A field that may identify someone when combined with other information. / pseudonymization: Replacing identifying details while retaining possible linkage. / anonymization: Processing intended to prevent identification under the relevant standard. / re-identification risk: The possibility of connecting data back to an individual. / aggregation: Combining records into group-level summaries. / small cell: A reported group with few contributing observations. / disclosure review: Assessment of risks from releasing or sharing information. / access scope: The specific data and actions a permission covers. / retention period: The duration for which data is kept under defined rules. / access expiry: The point when an access permission ends. / approved workspace: An environment authorized for the stated data work. / data lineage: The traceable path of data through sources and transformations. / data catalog: An organized inventory of datasets and their metadata. / processing purpose: The defined reason for collecting or using data. / permitted audience: The people authorized to receive a result or dataset. / export restriction: A limit on moving data outside an approved environment. / secondary use: A use beyond the original stated purpose.
Speaking task: Read turns 1-10. Stress the four needed fields and remaining disclosure review. Switch roles for turns 11-20. Keep access expiry distinct from retention. Check the transfer. Read the fourteen-day proposal without implying approval already exists.
Partner: Sara: Data analyst / Malik: Data steward
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An analyst needs monthly complaint rates by region. The approved design uses month, region, complaint count, and eligible-order count. Names and phone numbers are unnecessary. Access approval is pending; proposed access lasts 14 days.
Model for comparison AFTER my attempt, not a response to give me first: Sara: If we later need customer-level linkage, I will bring a new purpose and field list. This request should not become permission for unrelated analysis.
Malik: That would be a secondary use review. We can assess the new need on its facts, but the current weekly-rate purpose should not become a blanket authorization for every future analysis.
Sara: My request will list the four fields, rate, workspace, thirty-day access, audience, and required reviews. Approval remains pending.
Malik: Include the data lineage for the aggregate counts as well. That preserves both analytical trust and the handling boundary while giving you the information the actual question needs.
END REFERENCE
END PROMPT

Lesson 08 · Insight Storytelling and Recommendations | Build vocabulary and collocations

START PROMPT
TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 08: Insight Storytelling and Recommendations
Original fictional case: Analyst Oren has five minutes with operations director Claudia. Two complete weeks use the same ticket definition: issue Q appears in 20 of 1,000 tickets in week one and 80 of 1,000 in week two. Seventy of the later 80 issue-Q tickets are mobile-related; the total mobile-ticket denominator is not supplied. A release occurred between weeks, but cause is unestablished. Oren requests a two-day investigation led by the service analyst, with a readout afterward. Approval is for investigation only, not a production change.
Language workshop: Five minutes to authorize the right investigation
Communication goal: Lead a short briefing with a bounded action, quantified evidence, explicit limits, and a review point.
Language guidance: Issue Q rises from 2% to 8% of tickets: +6 percentage points, four times the earlier rate, or a 300% relative increase. The later mobile share is 70/80 = 87.5% of issue-Q tickets, not of mobile users.
Useful expressions (preserve the supplied facts): "I recommend a two-day investigation of issue Q." / "The ticket rate rose from 2% to 8%." / "Those rates describe tickets, not unique users." / "That is a six-percentage-point increase." / "The counts are 20 of 1,000 and 80 of 1,000." / "Seventy of the later eighty issue tickets are mobile-related." / "We do not have the total mobile-ticket denominator." / "The release timing is a lead, not proof of cause." / "Examine affected mobile paths and classification consistency." / "The service analyst would lead the investigation." / "The proposed time box is two days." / "Return with evidence, remaining uncertainty, and a next-step recommendation." / "This request does not authorize a production change." / "The readout date is not a guaranteed fix date." / "Please approve or decline that investigation scope." / "The evidence supports investigating now without pretending the cause is settled."
Vocabulary: insight: A decision-relevant interpretation supported by evidence. / recommendation: A proposed action with a reasoned basis. / decision ask: The precise choice requested from the audience. / headline finding: The main evidence statement in a short briefing. / supporting evidence: Facts that substantiate a conclusion or recommendation. / issue category: A defined class used to group reported problems. / ticket mix: The composition of support records across categories or groups. / segment concentration: A large share of observations within a particular subgroup. / base rate: The underlying frequency relative to an eligible population. / denominator gap: Missing information needed to compute the relevant rate. / descriptive finding: A statement about observed data without a causal conclusion. / causal hypothesis: A proposed explanation of what produced an outcome. / release timing: The timing of a product or system change. / diagnostic follow-up: Targeted analysis to investigate an observed issue. / investigation owner: The role accountable for the defined inquiry. / time box: A specified limit on the duration of work. / readout: A presentation of findings and their implications. / action boundary: The limit of what a decision authorizes. / production change: A modification to a live operating system or service. / decision log: A record of choices, reasons, and responsible people. / priority criterion: A stated basis for ordering work. / evidence threshold: The support required for a specified conclusion or next action. / leading question: A question that steers toward a preferred answer. / alternative explanation: Another plausible account of an observed pattern.
Speaking task: Read turns 1-10. Keep issue-ticket composition distinct from a mobile failure rate. Switch roles for turns 11-20. Stress investigation only and the two-day readout. Check the transfer. Read the 80% composition result with the issue-ticket denominator.
Partner: Oren: Data analyst / Claudia: Operations director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Issue R appears in 10 of 500 tickets, then 30 of 500. Twenty-four of the later 30 issue tickets concern mobile. The total mobile base is unknown. The request is a one-day investigation, not a live change.
Model for comparison AFTER my attempt, not a response to give me first: Claudia: Does approving this request also allow the analyst to change production if a likely cause appears? I want that distinction written clearly before I decide.
Oren: The action boundary is investigation only. Any production change would need its separate evidence, review, and authority. We are not asking this meeting to bypass that process.
Claudia: Then the decision is whether to allocate two days to a documented service issue, with the mobile concentration as a lead and the cause still open.
Oren: Yes. The decision ask is approval of that scope. I will record your decision and preserve the ticket units, missing denominator, and causal limitation in the briefing.
END REFERENCE
END PROMPT

Lesson 08 · Insight Storytelling and Recommendations | Practice grammar in context

START PROMPT
TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 08: Insight Storytelling and Recommendations
Original fictional case: Analyst Oren has five minutes with operations director Claudia. Two complete weeks use the same ticket definition: issue Q appears in 20 of 1,000 tickets in week one and 80 of 1,000 in week two. Seventy of the later 80 issue-Q tickets are mobile-related; the total mobile-ticket denominator is not supplied. A release occurred between weeks, but cause is unestablished. Oren requests a two-day investigation led by the service analyst, with a readout afterward. Approval is for investigation only, not a production change.
Language workshop: Five minutes to authorize the right investigation
Communication goal: Lead a short briefing with a bounded action, quantified evidence, explicit limits, and a review point.
Language guidance: Issue Q rises from 2% to 8% of tickets: +6 percentage points, four times the earlier rate, or a 300% relative increase. The later mobile share is 70/80 = 87.5% of issue-Q tickets, not of mobile users.
Useful expressions (preserve the supplied facts): "I recommend a two-day investigation of issue Q." / "The ticket rate rose from 2% to 8%." / "Those rates describe tickets, not unique users." / "That is a six-percentage-point increase." / "The counts are 20 of 1,000 and 80 of 1,000." / "Seventy of the later eighty issue tickets are mobile-related." / "We do not have the total mobile-ticket denominator." / "The release timing is a lead, not proof of cause." / "Examine affected mobile paths and classification consistency." / "The service analyst would lead the investigation." / "The proposed time box is two days." / "Return with evidence, remaining uncertainty, and a next-step recommendation." / "This request does not authorize a production change." / "The readout date is not a guaranteed fix date." / "Please approve or decline that investigation scope." / "The evidence supports investigating now without pretending the cause is settled."
Vocabulary: insight: A decision-relevant interpretation supported by evidence. / recommendation: A proposed action with a reasoned basis. / decision ask: The precise choice requested from the audience. / headline finding: The main evidence statement in a short briefing. / supporting evidence: Facts that substantiate a conclusion or recommendation. / issue category: A defined class used to group reported problems. / ticket mix: The composition of support records across categories or groups. / segment concentration: A large share of observations within a particular subgroup. / base rate: The underlying frequency relative to an eligible population. / denominator gap: Missing information needed to compute the relevant rate. / descriptive finding: A statement about observed data without a causal conclusion. / causal hypothesis: A proposed explanation of what produced an outcome. / release timing: The timing of a product or system change. / diagnostic follow-up: Targeted analysis to investigate an observed issue. / investigation owner: The role accountable for the defined inquiry. / time box: A specified limit on the duration of work. / readout: A presentation of findings and their implications. / action boundary: The limit of what a decision authorizes. / production change: A modification to a live operating system or service. / decision log: A record of choices, reasons, and responsible people. / priority criterion: A stated basis for ordering work. / evidence threshold: The support required for a specified conclusion or next action. / leading question: A question that steers toward a preferred answer. / alternative explanation: Another plausible account of an observed pattern.
Speaking task: Read turns 1-10. Keep issue-ticket composition distinct from a mobile failure rate. Switch roles for turns 11-20. Stress investigation only and the two-day readout. Check the transfer. Read the 80% composition result with the issue-ticket denominator.
Partner: Oren: Data analyst / Claudia: Operations director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Issue R appears in 10 of 500 tickets, then 30 of 500. Twenty-four of the later 30 issue tickets concern mobile. The total mobile base is unknown. The request is a one-day investigation, not a live change.
Model for comparison AFTER my attempt, not a response to give me first: Claudia: Does approving this request also allow the analyst to change production if a likely cause appears? I want that distinction written clearly before I decide.
Oren: The action boundary is investigation only. Any production change would need its separate evidence, review, and authority. We are not asking this meeting to bypass that process.
Claudia: Then the decision is whether to allocate two days to a documented service issue, with the mobile concentration as a lead and the cause still open.
Oren: Yes. The decision ask is approval of that scope. I will record your decision and preserve the ticket units, missing denominator, and causal limitation in the briefing.
END REFERENCE
END PROMPT

Lesson 08 · Insight Storytelling and Recommendations | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 08: Insight Storytelling and Recommendations
Original fictional case: Analyst Oren has five minutes with operations director Claudia. Two complete weeks use the same ticket definition: issue Q appears in 20 of 1,000 tickets in week one and 80 of 1,000 in week two. Seventy of the later 80 issue-Q tickets are mobile-related; the total mobile-ticket denominator is not supplied. A release occurred between weeks, but cause is unestablished. Oren requests a two-day investigation led by the service analyst, with a readout afterward. Approval is for investigation only, not a production change.
Language workshop: Five minutes to authorize the right investigation
Communication goal: Lead a short briefing with a bounded action, quantified evidence, explicit limits, and a review point.
Language guidance: Issue Q rises from 2% to 8% of tickets: +6 percentage points, four times the earlier rate, or a 300% relative increase. The later mobile share is 70/80 = 87.5% of issue-Q tickets, not of mobile users.
Useful expressions (preserve the supplied facts): "I recommend a two-day investigation of issue Q." / "The ticket rate rose from 2% to 8%." / "Those rates describe tickets, not unique users." / "That is a six-percentage-point increase." / "The counts are 20 of 1,000 and 80 of 1,000." / "Seventy of the later eighty issue tickets are mobile-related." / "We do not have the total mobile-ticket denominator." / "The release timing is a lead, not proof of cause." / "Examine affected mobile paths and classification consistency." / "The service analyst would lead the investigation." / "The proposed time box is two days." / "Return with evidence, remaining uncertainty, and a next-step recommendation." / "This request does not authorize a production change." / "The readout date is not a guaranteed fix date." / "Please approve or decline that investigation scope." / "The evidence supports investigating now without pretending the cause is settled."
Vocabulary: insight: A decision-relevant interpretation supported by evidence. / recommendation: A proposed action with a reasoned basis. / decision ask: The precise choice requested from the audience. / headline finding: The main evidence statement in a short briefing. / supporting evidence: Facts that substantiate a conclusion or recommendation. / issue category: A defined class used to group reported problems. / ticket mix: The composition of support records across categories or groups. / segment concentration: A large share of observations within a particular subgroup. / base rate: The underlying frequency relative to an eligible population. / denominator gap: Missing information needed to compute the relevant rate. / descriptive finding: A statement about observed data without a causal conclusion. / causal hypothesis: A proposed explanation of what produced an outcome. / release timing: The timing of a product or system change. / diagnostic follow-up: Targeted analysis to investigate an observed issue. / investigation owner: The role accountable for the defined inquiry. / time box: A specified limit on the duration of work. / readout: A presentation of findings and their implications. / action boundary: The limit of what a decision authorizes. / production change: A modification to a live operating system or service. / decision log: A record of choices, reasons, and responsible people. / priority criterion: A stated basis for ordering work. / evidence threshold: The support required for a specified conclusion or next action. / leading question: A question that steers toward a preferred answer. / alternative explanation: Another plausible account of an observed pattern.
Speaking task: Read turns 1-10. Keep issue-ticket composition distinct from a mobile failure rate. Switch roles for turns 11-20. Stress investigation only and the two-day readout. Check the transfer. Read the 80% composition result with the issue-ticket denominator.
Partner: Oren: Data analyst / Claudia: Operations director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Issue R appears in 10 of 500 tickets, then 30 of 500. Twenty-four of the later 30 issue tickets concern mobile. The total mobile base is unknown. The request is a one-day investigation, not a live change.
Model for comparison AFTER my attempt, not a response to give me first: Claudia: Does approving this request also allow the analyst to change production if a likely cause appears? I want that distinction written clearly before I decide.
Oren: The action boundary is investigation only. Any production change would need its separate evidence, review, and authority. We are not asking this meeting to bypass that process.
Claudia: Then the decision is whether to allocate two days to a documented service issue, with the mobile concentration as a lead and the cause still open.
Oren: Yes. The decision ask is approval of that scope. I will record your decision and preserve the ticket units, missing denominator, and causal limitation in the briefing.
END REFERENCE
END PROMPT

Lesson 08 · Insight Storytelling and Recommendations | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Lesson 08: Insight Storytelling and Recommendations
Original fictional case: Analyst Oren has five minutes with operations director Claudia. Two complete weeks use the same ticket definition: issue Q appears in 20 of 1,000 tickets in week one and 80 of 1,000 in week two. Seventy of the later 80 issue-Q tickets are mobile-related; the total mobile-ticket denominator is not supplied. A release occurred between weeks, but cause is unestablished. Oren requests a two-day investigation led by the service analyst, with a readout afterward. Approval is for investigation only, not a production change.
Language workshop: Five minutes to authorize the right investigation
Communication goal: Lead a short briefing with a bounded action, quantified evidence, explicit limits, and a review point.
Language guidance: Issue Q rises from 2% to 8% of tickets: +6 percentage points, four times the earlier rate, or a 300% relative increase. The later mobile share is 70/80 = 87.5% of issue-Q tickets, not of mobile users.
Useful expressions (preserve the supplied facts): "I recommend a two-day investigation of issue Q." / "The ticket rate rose from 2% to 8%." / "Those rates describe tickets, not unique users." / "That is a six-percentage-point increase." / "The counts are 20 of 1,000 and 80 of 1,000." / "Seventy of the later eighty issue tickets are mobile-related." / "We do not have the total mobile-ticket denominator." / "The release timing is a lead, not proof of cause." / "Examine affected mobile paths and classification consistency." / "The service analyst would lead the investigation." / "The proposed time box is two days." / "Return with evidence, remaining uncertainty, and a next-step recommendation." / "This request does not authorize a production change." / "The readout date is not a guaranteed fix date." / "Please approve or decline that investigation scope." / "The evidence supports investigating now without pretending the cause is settled."
Vocabulary: insight: A decision-relevant interpretation supported by evidence. / recommendation: A proposed action with a reasoned basis. / decision ask: The precise choice requested from the audience. / headline finding: The main evidence statement in a short briefing. / supporting evidence: Facts that substantiate a conclusion or recommendation. / issue category: A defined class used to group reported problems. / ticket mix: The composition of support records across categories or groups. / segment concentration: A large share of observations within a particular subgroup. / base rate: The underlying frequency relative to an eligible population. / denominator gap: Missing information needed to compute the relevant rate. / descriptive finding: A statement about observed data without a causal conclusion. / causal hypothesis: A proposed explanation of what produced an outcome. / release timing: The timing of a product or system change. / diagnostic follow-up: Targeted analysis to investigate an observed issue. / investigation owner: The role accountable for the defined inquiry. / time box: A specified limit on the duration of work. / readout: A presentation of findings and their implications. / action boundary: The limit of what a decision authorizes. / production change: A modification to a live operating system or service. / decision log: A record of choices, reasons, and responsible people. / priority criterion: A stated basis for ordering work. / evidence threshold: The support required for a specified conclusion or next action. / leading question: A question that steers toward a preferred answer. / alternative explanation: Another plausible account of an observed pattern.
Speaking task: Read turns 1-10. Keep issue-ticket composition distinct from a mobile failure rate. Switch roles for turns 11-20. Stress investigation only and the two-day readout. Check the transfer. Read the 80% composition result with the issue-ticket denominator.
Partner: Oren: Data analyst / Claudia: Operations director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Issue R appears in 10 of 500 tickets, then 30 of 500. Twenty-four of the later 30 issue tickets concern mobile. The total mobile base is unknown. The request is a one-day investigation, not a live change.
Model for comparison AFTER my attempt, not a response to give me first: Claudia: Does approving this request also allow the analyst to change production if a likely cause appears? I want that distinction written clearly before I decide.
Oren: The action boundary is investigation only. Any production change would need its separate evidence, review, and authority. We are not asking this meeting to bypass that process.
Claudia: Then the decision is whether to allocate two days to a documented service issue, with the mobile concentration as a lead and the cause still open.
Oren: Yes. The decision ask is approval of that scope. I will record your decision and preserve the ticket units, missing denominator, and causal limitation in the briefing.
END REFERENCE
END PROMPT

Dialogue 01 · Agreeing on a metric | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 01: Agreeing on a metric
Original fictional setting: An analyst and stakeholder define active customers.
Professional roles: BI analyst / Sales operations manager
Published dialogue (reference script, not my own performance):
BI analyst: Does active customer mean a signed contract or a purchase in the reporting period?
Sales operations manager: For this dashboard, at least one completed purchase in the last 90 days.
BI analyst: Should canceled and fully refunded orders count?
Sales operations manager: No. Let's write those exclusions into the definition.
BI analyst: I'll document the time zone, source tables, and refresh schedule too.
Sales operations manager: Send the definition for review before building the chart so other teams can use the same measure.
Vocabulary in this exchange: dashboard: Visual summary of selected measures used to monitor status, performance, or risk.
END REFERENCE
END PROMPT

Dialogue 01 · Agreeing on a metric | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 01: Agreeing on a metric
Original fictional setting: An analyst and stakeholder define active customers.
Professional roles: BI analyst / Sales operations manager
Published dialogue (reference script, not my own performance):
BI analyst: Does active customer mean a signed contract or a purchase in the reporting period?
Sales operations manager: For this dashboard, at least one completed purchase in the last 90 days.
BI analyst: Should canceled and fully refunded orders count?
Sales operations manager: No. Let's write those exclusions into the definition.
BI analyst: I'll document the time zone, source tables, and refresh schedule too.
Sales operations manager: Send the definition for review before building the chart so other teams can use the same measure.
Vocabulary in this exchange: dashboard: Visual summary of selected measures used to monitor status, performance, or risk.
END REFERENCE
END PROMPT

Dialogue 02 · Dashboard refresh failure | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 02: Dashboard refresh failure
Original fictional setting: A stakeholder reports stale dashboard figures.
Professional roles: Business stakeholder / Data engineer
Published dialogue (reference script, not my own performance):
Business stakeholder: The dashboard hasn't changed since yesterday. Have sales stopped?
Data engineer: No conclusion about sales follows from that. The scheduled data load failed overnight.
Business stakeholder: Can you show users the last successful refresh time?
Data engineer: Yes. I'll mark the dashboard as stale and investigate the failed job.
Business stakeholder: I'll pause this morning's performance comparison until the data are current.
Data engineer: I'll confirm the repaired load and completeness checks before telling you the dashboard is ready.
Vocabulary in this exchange: completeness: The extent to which required information or records are present. / dashboard: Visual summary of selected measures used to monitor status, performance, or risk.
END REFERENCE
END PROMPT

Dialogue 02 · Dashboard refresh failure | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 02: Dashboard refresh failure
Original fictional setting: A stakeholder reports stale dashboard figures.
Professional roles: Business stakeholder / Data engineer
Published dialogue (reference script, not my own performance):
Business stakeholder: The dashboard hasn't changed since yesterday. Have sales stopped?
Data engineer: No conclusion about sales follows from that. The scheduled data load failed overnight.
Business stakeholder: Can you show users the last successful refresh time?
Data engineer: Yes. I'll mark the dashboard as stale and investigate the failed job.
Business stakeholder: I'll pause this morning's performance comparison until the data are current.
Data engineer: I'll confirm the repaired load and completeness checks before telling you the dashboard is ready.
Vocabulary in this exchange: completeness: The extent to which required information or records are present. / dashboard: Visual summary of selected measures used to monitor status, performance, or risk.
END REFERENCE
END PROMPT

Dialogue 03 · Duplicate records | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 03: Duplicate records
Original fictional setting: An analyst finds a sudden increase after a data join.
Professional roles: Data analyst / Analytics engineer
Published dialogue (reference script, not my own performance):
Data analyst: Revenue doubles after I join orders to shipments. The source order total hasn't changed.
Analytics engineer: Is the join one-to-many? An order can have several shipments.
Data analyst: Yes. I'm repeating the order amount for each shipment row.
Analytics engineer: Aggregate at the intended grain before comparing, and check the join keys.
Data analyst: I'll reconcile distinct orders and revenue to the source totals.
Analytics engineer: Document the grain in the model so future reports don't repeat the same error.
Vocabulary in this exchange: grain: What one row or record represents in a dataset.
END REFERENCE
END PROMPT

Dialogue 03 · Duplicate records | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 03: Duplicate records
Original fictional setting: An analyst finds a sudden increase after a data join.
Professional roles: Data analyst / Analytics engineer
Published dialogue (reference script, not my own performance):
Data analyst: Revenue doubles after I join orders to shipments. The source order total hasn't changed.
Analytics engineer: Is the join one-to-many? An order can have several shipments.
Data analyst: Yes. I'm repeating the order amount for each shipment row.
Analytics engineer: Aggregate at the intended grain before comparing, and check the join keys.
Data analyst: I'll reconcile distinct orders and revenue to the source totals.
Analytics engineer: Document the grain in the model so future reports don't repeat the same error.
Vocabulary in this exchange: grain: What one row or record represents in a dataset.
END REFERENCE
END PROMPT

Dialogue 04 · Clarifying a request | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 04: Clarifying a request
Original fictional setting: A manager asks for every available customer field.
Professional roles: Analytics lead / Marketing manager
Published dialogue (reference script, not my own performance):
Analytics lead: What decision will the customer extract support?
Marketing manager: We want to understand which onboarding step has the highest drop-off.
Analytics lead: Then we may need event counts by step rather than a broad personal-data export.
Marketing manager: Agreed. Could we also compare acquisition channels?
Analytics lead: Yes, subject to data availability and access rules. I'll propose the smallest useful dataset.
Marketing manager: I'll confirm the decision and reporting period so we can review whether the analysis answers the question.
END REFERENCE
END PROMPT

Dialogue 04 · Clarifying a request | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 04: Clarifying a request
Original fictional setting: A manager asks for every available customer field.
Professional roles: Analytics lead / Marketing manager
Published dialogue (reference script, not my own performance):
Analytics lead: What decision will the customer extract support?
Marketing manager: We want to understand which onboarding step has the highest drop-off.
Analytics lead: Then we may need event counts by step rather than a broad personal-data export.
Marketing manager: Agreed. Could we also compare acquisition channels?
Analytics lead: Yes, subject to data availability and access rules. I'll propose the smallest useful dataset.
Marketing manager: I'll confirm the decision and reporting period so we can review whether the analysis answers the question.
END REFERENCE
END PROMPT

Dialogue 05 · Association and causation | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 05: Association and causation
Original fictional setting: A team reviews a regional sales comparison.
Professional roles: Analyst / Regional manager
Published dialogue (reference script, not my own performance):
Analyst: Regions using the new script sold more, but the comparison is observational.
Regional manager: Can we say the script caused the increase?
Analyst: Not from this alone. Those regions also had different staffing and customer mixes.
Regional manager: What would strengthen the evidence?
Analyst: A suitable experimental or carefully justified comparison design, with its limitations explicit.
Regional manager: For now, describe the association accurately and recommend how to evaluate the script more rigorously.
END REFERENCE
END PROMPT

Dialogue 05 · Association and causation | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 05: Association and causation
Original fictional setting: A team reviews a regional sales comparison.
Professional roles: Analyst / Regional manager
Published dialogue (reference script, not my own performance):
Analyst: Regions using the new script sold more, but the comparison is observational.
Regional manager: Can we say the script caused the increase?
Analyst: Not from this alone. Those regions also had different staffing and customer mixes.
Regional manager: What would strengthen the evidence?
Analyst: A suitable experimental or carefully justified comparison design, with its limitations explicit.
Regional manager: For now, describe the association accurately and recommend how to evaluate the script more rigorously.
END REFERENCE
END PROMPT

Dialogue 06 · Experiment imbalance | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 06: Experiment imbalance
Original fictional setting: An analyst checks an experiment before interpreting results.
Professional roles: Experiment analyst / Product lead
Published dialogue (reference script, not my own performance):
Experiment analyst: The allocation ratio differs sharply from the planned split. We need to investigate that first.
Product lead: Could the favorable result still be real?
Experiment analyst: Possibly, but assignment or logging problems could bias it. Significance doesn't fix a broken design.
Product lead: I'll keep the rollout decision pending.
Experiment analyst: I'll review eligibility, assignment, and event completeness with engineering.
Product lead: Bring the validity findings alongside the outcome metrics, so the decision reflects the quality of the evidence.
Vocabulary in this exchange: completeness: The extent to which required information or records are present.
END REFERENCE
END PROMPT

Dialogue 06 · Experiment imbalance | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 06: Experiment imbalance
Original fictional setting: An analyst checks an experiment before interpreting results.
Professional roles: Experiment analyst / Product lead
Published dialogue (reference script, not my own performance):
Experiment analyst: The allocation ratio differs sharply from the planned split. We need to investigate that first.
Product lead: Could the favorable result still be real?
Experiment analyst: Possibly, but assignment or logging problems could bias it. Significance doesn't fix a broken design.
Product lead: I'll keep the rollout decision pending.
Experiment analyst: I'll review eligibility, assignment, and event completeness with engineering.
Product lead: Bring the validity findings alongside the outcome metrics, so the decision reflects the quality of the evidence.
Vocabulary in this exchange: completeness: The extent to which required information or records are present.
END REFERENCE
END PROMPT

Dialogue 07 · Data access request | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 07: Data access request
Original fictional setting: A department requests access to a restricted dataset.
Professional roles: Department analyst / Data steward
Published dialogue (reference script, not my own performance):
Department analyst: I need the employee-level dataset for a turnover report. What access is appropriate?
Data steward: Start with the purpose and required fields. An aggregated dataset may meet the need.
Department analyst: I only need trends by department and tenure band.
Data steward: Then let's assess that output and any small-group disclosure concerns under our policy.
Department analyst: I'll submit the request with the audience and retention period.
Data steward: I'll route it for the required approval and confirm the permitted dataset and handling conditions.
Vocabulary in this exchange: retention: Keeping customers, users, staff, or records over a stated period; specify which meaning applies.
END REFERENCE
END PROMPT

Dialogue 07 · Data access request | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 07: Data access request
Original fictional setting: A department requests access to a restricted dataset.
Professional roles: Department analyst / Data steward
Published dialogue (reference script, not my own performance):
Department analyst: I need the employee-level dataset for a turnover report. What access is appropriate?
Data steward: Start with the purpose and required fields. An aggregated dataset may meet the need.
Department analyst: I only need trends by department and tenure band.
Data steward: Then let's assess that output and any small-group disclosure concerns under our policy.
Department analyst: I'll submit the request with the audience and retention period.
Data steward: I'll route it for the required approval and confirm the permitted dataset and handling conditions.
Vocabulary in this exchange: retention: Keeping customers, users, staff, or records over a stated period; specify which meaning applies.
END REFERENCE
END PROMPT

Dialogue 08 · An executive readout | Rehearse with an AI colleague

START PROMPT
TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 08: An executive readout
Original fictional setting: An analyst prepares a concise performance explanation.
Professional roles: Senior analyst / Finance director
Published dialogue (reference script, not my own performance):
Senior analyst: Orders fell eight percent, while revenue fell three percent. Higher average order value offset part of the volume decline.
Finance director: Is that price or product mix?
Senior analyst: The current bridge suggests mix, but I still need to reconcile discount effects.
Finance director: Lead with the confirmed movement, then identify that open question.
Senior analyst: I'll include the comparison period, reconciliation status, and the largest contributing categories.
Finance director: Good. Recommend the next analysis without presenting an unverified driver as a settled explanation.
END REFERENCE
END PROMPT

Dialogue 08 · An executive readout | Create more scenario dialogues

START PROMPT
TASK: Extend the conversation library
1. Propose six distinct, common scenarios in this field beyond the supplied case or script. For each, name the setting, two or more professional roles, the communication problem and one useful terminology focus. Include routine coordination, clarification, a complication, disagreement, handoff and follow-up where relevant. Choose scenarios that fit this profession, rather than forcing unsuitable situations into it.
2. Ask me to choose one scenario, or request all six in sequence. Stop and wait. Do not write all the scripts before I choose.
3. For the selected scenario, write an original fictional dialogue of 12-18 substantial speaking turns between two or three professionals. Name each role, establish an actual work problem, and let the exchange progress through questions, clarification, competing constraints and a credible next step or explicitly unresolved issue. Use the occupation's natural nomenclature and register. Avoid an interview between a teacher and a learner, generic small talk, and inserting a glossary definition into every reply. Explain specialist terms outside the dialogue instead.
4. After the script, explain five useful expressions in context and identify two grammar or register choices. Give three four-choice questions about the speakers' reasoning, with exactly one answer supported by the dialogue. Wait for my selections, then explain why each answer fits and why its alternatives fail. Add a role-switch reading using the supplied script; do not ask for an essay or invented written reply.
5. Before presenting a script, check names, numbers, chronology, roles and terminology for consistency. Label invented facts and acknowledge uncertain specialist usage. If I requested all six, deliver one complete script at a time and wait for "next". Make each scenario materially different.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Data Analytics and Business Intelligence English
Professional audience: data analysts, BI developers, analytics engineers, data scientists, reporting teams, business analysts, and data-driven managers
Scope: Original fictional English practice, not statistical certification, legal advice, a privacy determination, or authorization to use customer data. All datasets, thresholds, local approval rules, and business decisions are invented. Actual analysis must follow the applicable definitions, methods, access controls, and responsible review.
Dialogue 08: An executive readout
Original fictional setting: An analyst prepares a concise performance explanation.
Professional roles: Senior analyst / Finance director
Published dialogue (reference script, not my own performance):
Senior analyst: Orders fell eight percent, while revenue fell three percent. Higher average order value offset part of the volume decline.
Finance director: Is that price or product mix?
Senior analyst: The current bridge suggests mix, but I still need to reconcile discount effects.
Finance director: Lead with the confirmed movement, then identify that open question.
Senior analyst: I'll include the comparison period, reconciliation status, and the largest contributing categories.
Finance director: Good. Recommend the next analysis without presenting an unverified driver as a settled explanation.
END REFERENCE
END PROMPT