General IT English

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 01: IT Service Language, Tickets, and Triage
Original fictional case: Ren reports that the finance system is down. Ren can sign in and view invoices, but exporting the current month produces an error. Two colleagues report the same export problem; other users and functions have not been checked. The billing team needs its file by 3 p.m. Asha owns service-desk triage and can escalate the ticket, but cannot promise a repair time.
Language workshop: "The system is down" means the export fails
Communication goal: Narrow an ambiguous incident report and agree on an evidence-based update.
Language guidance: Urgency concerns time pressure; impact concerns consequences and scope. Priority normally reflects an organization's agreed assessment, not just the strongest wording in a ticket. A response commitment is not a repair guarantee.
Useful expressions (preserve the supplied facts): I understand the export is blocking your billing file. / Which action fails after you sign in? / Can you still view the invoices on screen? / Who else has tried the same export and seen the error? / Please send the exact error text through the approved support channel. / Your billing deadline is 3 p.m.; the repair time is not yet known. / I will escalate the ticket and update you by noon. / Sign-in and viewing work; the current-month export fails for three reported users. / Has anyone verified that the alternative produces the required file? / I cannot confirm a restoration time before the technical assessment. / I am asking the application team to investigate this function. / Other functions and users have not yet been checked. / I will link the reports so the investigation has one shared record. / Which team is accepting the next investigation step? / We will confirm that the required export works before closing the incident. / The next message will include findings, outstanding questions, and the next owner.
Vocabulary: service desk: The contact point coordinating user support. / ticket: A recorded request or issue for tracking. / triage: Initial assessment of impact, priority, and ownership. / incident: An unplanned disruption or reduction in service. / service request: A request for a routine agreed service. / impact: The effect on users or business work. / urgency: How quickly action is needed in the circumstances. / priority: The relative order or importance assigned to work. / affected user: A person experiencing the reported problem. / scope: The functions, users, or locations included. / symptom: An observed sign of a problem. / error message: Text identifying or describing an error condition. / reproduce: Make the reported behavior occur again. / workaround: A temporary way to reduce impact without fixing the cause. / resolution: Restoration or completion according to the agreed criteria. / response time: Time until support responds under a defined measure. / restoration time: Time until a disrupted service is restored. / escalation: Referral for higher authority or specialist attention. / assignment group: The team designated to handle a ticket. / service owner: The role accountable for the service. / knowledge article: A maintained support reference for a known task or issue. / duplicate ticket: Another ticket reporting the same underlying incident. / status update: A communication of progress and remaining uncertainty. / closure criterion: A condition required before work is marked closed.
Speaking task: Check the dialogue. Read the confirmed boundary: Ren can sign in and view invoices, but current-month export fails for three reported users. Switch roles. Keep the 3 p.m. billing deadline separate from the unknown repair time; repeat the noon progress-update commitment. Complete the printer exchange. Preserve the untested alternative and do not promise restoration before the 2 p.m. meeting.
Partner: Asha: Service-desk analyst / Ren: Billing coordinator
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 user can edit and save documents but cannot print to one office printer. Another printer has not been tested. The user needs printed copies for a 2 p.m. meeting.
Model for comparison AFTER my attempt, not a response to give me first: Ren: Could you read that back before you send it? I don't want the team checking invoice viewing when it's the export I need.
Asha: Certainly. Sign-in and viewing work for you; current-month export fails for three reported users. Other functions remain unchecked. Billing needs the file by three, and the assignment group is the application support team.
Ren: That captures it. Please include me on the noon update. Once they say it is fixed, I can verify the export and compare the file totals.
Asha: I will record that as the closure criterion. We will distinguish a reported fix from your confirmation that the required task works again.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 01: IT Service Language, Tickets, and Triage
Original fictional case: Ren reports that the finance system is down. Ren can sign in and view invoices, but exporting the current month produces an error. Two colleagues report the same export problem; other users and functions have not been checked. The billing team needs its file by 3 p.m. Asha owns service-desk triage and can escalate the ticket, but cannot promise a repair time.
Language workshop: "The system is down" means the export fails
Communication goal: Narrow an ambiguous incident report and agree on an evidence-based update.
Language guidance: Urgency concerns time pressure; impact concerns consequences and scope. Priority normally reflects an organization's agreed assessment, not just the strongest wording in a ticket. A response commitment is not a repair guarantee.
Useful expressions (preserve the supplied facts): I understand the export is blocking your billing file. / Which action fails after you sign in? / Can you still view the invoices on screen? / Who else has tried the same export and seen the error? / Please send the exact error text through the approved support channel. / Your billing deadline is 3 p.m.; the repair time is not yet known. / I will escalate the ticket and update you by noon. / Sign-in and viewing work; the current-month export fails for three reported users. / Has anyone verified that the alternative produces the required file? / I cannot confirm a restoration time before the technical assessment. / I am asking the application team to investigate this function. / Other functions and users have not yet been checked. / I will link the reports so the investigation has one shared record. / Which team is accepting the next investigation step? / We will confirm that the required export works before closing the incident. / The next message will include findings, outstanding questions, and the next owner.
Vocabulary: service desk: The contact point coordinating user support. / ticket: A recorded request or issue for tracking. / triage: Initial assessment of impact, priority, and ownership. / incident: An unplanned disruption or reduction in service. / service request: A request for a routine agreed service. / impact: The effect on users or business work. / urgency: How quickly action is needed in the circumstances. / priority: The relative order or importance assigned to work. / affected user: A person experiencing the reported problem. / scope: The functions, users, or locations included. / symptom: An observed sign of a problem. / error message: Text identifying or describing an error condition. / reproduce: Make the reported behavior occur again. / workaround: A temporary way to reduce impact without fixing the cause. / resolution: Restoration or completion according to the agreed criteria. / response time: Time until support responds under a defined measure. / restoration time: Time until a disrupted service is restored. / escalation: Referral for higher authority or specialist attention. / assignment group: The team designated to handle a ticket. / service owner: The role accountable for the service. / knowledge article: A maintained support reference for a known task or issue. / duplicate ticket: Another ticket reporting the same underlying incident. / status update: A communication of progress and remaining uncertainty. / closure criterion: A condition required before work is marked closed.
Speaking task: Check the dialogue. Read the confirmed boundary: Ren can sign in and view invoices, but current-month export fails for three reported users. Switch roles. Keep the 3 p.m. billing deadline separate from the unknown repair time; repeat the noon progress-update commitment. Complete the printer exchange. Preserve the untested alternative and do not promise restoration before the 2 p.m. meeting.
Partner: Asha: Service-desk analyst / Ren: Billing coordinator
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 user can edit and save documents but cannot print to one office printer. Another printer has not been tested. The user needs printed copies for a 2 p.m. meeting.
Model for comparison AFTER my attempt, not a response to give me first: Ren: Could you read that back before you send it? I don't want the team checking invoice viewing when it's the export I need.
Asha: Certainly. Sign-in and viewing work for you; current-month export fails for three reported users. Other functions remain unchecked. Billing needs the file by three, and the assignment group is the application support team.
Ren: That captures it. Please include me on the noon update. Once they say it is fixed, I can verify the export and compare the file totals.
Asha: I will record that as the closure criterion. We will distinguish a reported fix from your confirmation that the required task works again.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 01: IT Service Language, Tickets, and Triage
Original fictional case: Ren reports that the finance system is down. Ren can sign in and view invoices, but exporting the current month produces an error. Two colleagues report the same export problem; other users and functions have not been checked. The billing team needs its file by 3 p.m. Asha owns service-desk triage and can escalate the ticket, but cannot promise a repair time.
Language workshop: "The system is down" means the export fails
Communication goal: Narrow an ambiguous incident report and agree on an evidence-based update.
Language guidance: Urgency concerns time pressure; impact concerns consequences and scope. Priority normally reflects an organization's agreed assessment, not just the strongest wording in a ticket. A response commitment is not a repair guarantee.
Useful expressions (preserve the supplied facts): I understand the export is blocking your billing file. / Which action fails after you sign in? / Can you still view the invoices on screen? / Who else has tried the same export and seen the error? / Please send the exact error text through the approved support channel. / Your billing deadline is 3 p.m.; the repair time is not yet known. / I will escalate the ticket and update you by noon. / Sign-in and viewing work; the current-month export fails for three reported users. / Has anyone verified that the alternative produces the required file? / I cannot confirm a restoration time before the technical assessment. / I am asking the application team to investigate this function. / Other functions and users have not yet been checked. / I will link the reports so the investigation has one shared record. / Which team is accepting the next investigation step? / We will confirm that the required export works before closing the incident. / The next message will include findings, outstanding questions, and the next owner.
Vocabulary: service desk: The contact point coordinating user support. / ticket: A recorded request or issue for tracking. / triage: Initial assessment of impact, priority, and ownership. / incident: An unplanned disruption or reduction in service. / service request: A request for a routine agreed service. / impact: The effect on users or business work. / urgency: How quickly action is needed in the circumstances. / priority: The relative order or importance assigned to work. / affected user: A person experiencing the reported problem. / scope: The functions, users, or locations included. / symptom: An observed sign of a problem. / error message: Text identifying or describing an error condition. / reproduce: Make the reported behavior occur again. / workaround: A temporary way to reduce impact without fixing the cause. / resolution: Restoration or completion according to the agreed criteria. / response time: Time until support responds under a defined measure. / restoration time: Time until a disrupted service is restored. / escalation: Referral for higher authority or specialist attention. / assignment group: The team designated to handle a ticket. / service owner: The role accountable for the service. / knowledge article: A maintained support reference for a known task or issue. / duplicate ticket: Another ticket reporting the same underlying incident. / status update: A communication of progress and remaining uncertainty. / closure criterion: A condition required before work is marked closed.
Speaking task: Check the dialogue. Read the confirmed boundary: Ren can sign in and view invoices, but current-month export fails for three reported users. Switch roles. Keep the 3 p.m. billing deadline separate from the unknown repair time; repeat the noon progress-update commitment. Complete the printer exchange. Preserve the untested alternative and do not promise restoration before the 2 p.m. meeting.
Partner: Asha: Service-desk analyst / Ren: Billing coordinator
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 user can edit and save documents but cannot print to one office printer. Another printer has not been tested. The user needs printed copies for a 2 p.m. meeting.
Model for comparison AFTER my attempt, not a response to give me first: Ren: Could you read that back before you send it? I don't want the team checking invoice viewing when it's the export I need.
Asha: Certainly. Sign-in and viewing work for you; current-month export fails for three reported users. Other functions remain unchecked. Billing needs the file by three, and the assignment group is the application support team.
Ren: That captures it. Please include me on the noon update. Once they say it is fixed, I can verify the export and compare the file totals.
Asha: I will record that as the closure criterion. We will distinguish a reported fix from your confirmation that the required task works again.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 02: Networks, Connectivity, and Root-Cause Hypotheses
Original fictional case: The staff portal works from the office network but fails for four people connected through the virtual private network (VPN). The same portal address is used. Nobody has checked name resolution, routing, or access-policy logs for those requests. Eli says DNS must be the cause. Nia coordinates network investigation. The team has an approved diagnostic process and must not change production settings merely to test a guess.
Language workshop: The VPN pattern is a clue, not a DNS diagnosis
Communication goal: Challenge premature certainty and agree on comparisons that separate hypotheses.
Language guidance: A timeout, a refused connection, and a certificate warning are different observations. "The VPN is connected" does not establish that every destination is reachable. Name the source, destination, and observed result.
Useful expressions (preserve the supplied facts): The reports do point to a difference between access paths. / What evidence establishes DNS rather than another path issue? / Name resolution is one explanation we still need to test. / Was it a timeout, a refusal, or a certificate warning? / Compare the same destination from the two approved paths. / We should not change production settings to test an unverified guess. / We have not checked the resolver or policy logs for those requests. / The pattern narrows the investigation; it does not yet establish a cause. / Were all four reports from the same VPN profile? / A successful name lookup does not prove application access. / The portal worked for this office test at this time. / We have not tested every VPN user or destination. / Please include the time and time zone for each failed request. / Who will collect the approved comparison and record the results? / That check did not support the DNS hypothesis. / Keep the observed results separate from the proposed explanation.
Vocabulary: VPN: Virtual private network; a connection providing a defined private access path. / DNS: Domain Name System; the system that resolves names to records. / name resolution: Translating a name into the records needed for a connection. / IP address: A numerical network address used by the Internet Protocol. / hostname: A name identifying a host or service endpoint. / resolver: A service that answers or obtains DNS responses. / cache: Stored data reused to avoid repeating work. / TTL: Time to live; a lifetime limit, with meaning depending on context. / routing: Selection of paths for network traffic. / route: A path or forwarding rule for reaching a destination. / gateway: A system providing a path between networks or services. / subnet: A defined subdivision of an IP network. / firewall: A control that permits or blocks network traffic under rules. / access policy: Rules determining permitted access under stated conditions. / port: A numbered transport endpoint associated with a service. / packet loss: Failure of transmitted network packets to reach their destination. / round-trip time: Time for a request and return response across a path. / timeout: Expiry of a waiting period before a response completes. / connection refusal: An explicit rejection of a connection attempt. / TLS: Transport Layer Security; protection for communication in transit. / certificate: A signed digital statement used to bind identity and a public key. / proxy: An intermediary handling requests between client and destination. / reachability: Whether a destination can be contacted under specified conditions. / diagnostic hypothesis: A proposed explanation that still requires testing.
Speaking task: Check the dialogue. Contrast the working office path with four reported VPN failures; keep DNS as a hypothesis, not a finding. Switch roles. Request the exact warning, path and timestamp through the approved process, without proposing a speculative production change. Complete the certificate exchange. Retain the unreviewed proxy hypothesis and the instruction not to bypass the warning.
Partner: Eli: Support engineer / Nia: Network engineer
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: The same portal opens in an approved office test, while a remote user reports a certificate warning. No certificate or proxy review has occurred. The team must describe the actual warning without telling the user to bypass it.
Model for comparison AFTER my attempt, not a response to give me first: Eli: I will revise the update: four reports through the VPN, one successful office test, exact errors being collected, and no verified root cause yet.
Nia: Good. The comparison should show what differs and what remains unchanged. That gives the next team something concrete to investigate.
Eli: I'll remove the definite DNS diagnosis from the update now. Send me the comparison when it's ready and I'll add what it shows.
Nia: Exactly. A useful diagnosis depends on the evidence, not on keeping the first guess. We can be decisive about the next test while remaining uncertain about the cause.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 02: Networks, Connectivity, and Root-Cause Hypotheses
Original fictional case: The staff portal works from the office network but fails for four people connected through the virtual private network (VPN). The same portal address is used. Nobody has checked name resolution, routing, or access-policy logs for those requests. Eli says DNS must be the cause. Nia coordinates network investigation. The team has an approved diagnostic process and must not change production settings merely to test a guess.
Language workshop: The VPN pattern is a clue, not a DNS diagnosis
Communication goal: Challenge premature certainty and agree on comparisons that separate hypotheses.
Language guidance: A timeout, a refused connection, and a certificate warning are different observations. "The VPN is connected" does not establish that every destination is reachable. Name the source, destination, and observed result.
Useful expressions (preserve the supplied facts): The reports do point to a difference between access paths. / What evidence establishes DNS rather than another path issue? / Name resolution is one explanation we still need to test. / Was it a timeout, a refusal, or a certificate warning? / Compare the same destination from the two approved paths. / We should not change production settings to test an unverified guess. / We have not checked the resolver or policy logs for those requests. / The pattern narrows the investigation; it does not yet establish a cause. / Were all four reports from the same VPN profile? / A successful name lookup does not prove application access. / The portal worked for this office test at this time. / We have not tested every VPN user or destination. / Please include the time and time zone for each failed request. / Who will collect the approved comparison and record the results? / That check did not support the DNS hypothesis. / Keep the observed results separate from the proposed explanation.
Vocabulary: VPN: Virtual private network; a connection providing a defined private access path. / DNS: Domain Name System; the system that resolves names to records. / name resolution: Translating a name into the records needed for a connection. / IP address: A numerical network address used by the Internet Protocol. / hostname: A name identifying a host or service endpoint. / resolver: A service that answers or obtains DNS responses. / cache: Stored data reused to avoid repeating work. / TTL: Time to live; a lifetime limit, with meaning depending on context. / routing: Selection of paths for network traffic. / route: A path or forwarding rule for reaching a destination. / gateway: A system providing a path between networks or services. / subnet: A defined subdivision of an IP network. / firewall: A control that permits or blocks network traffic under rules. / access policy: Rules determining permitted access under stated conditions. / port: A numbered transport endpoint associated with a service. / packet loss: Failure of transmitted network packets to reach their destination. / round-trip time: Time for a request and return response across a path. / timeout: Expiry of a waiting period before a response completes. / connection refusal: An explicit rejection of a connection attempt. / TLS: Transport Layer Security; protection for communication in transit. / certificate: A signed digital statement used to bind identity and a public key. / proxy: An intermediary handling requests between client and destination. / reachability: Whether a destination can be contacted under specified conditions. / diagnostic hypothesis: A proposed explanation that still requires testing.
Speaking task: Check the dialogue. Contrast the working office path with four reported VPN failures; keep DNS as a hypothesis, not a finding. Switch roles. Request the exact warning, path and timestamp through the approved process, without proposing a speculative production change. Complete the certificate exchange. Retain the unreviewed proxy hypothesis and the instruction not to bypass the warning.
Partner: Eli: Support engineer / Nia: Network engineer
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: The same portal opens in an approved office test, while a remote user reports a certificate warning. No certificate or proxy review has occurred. The team must describe the actual warning without telling the user to bypass it.
Model for comparison AFTER my attempt, not a response to give me first: Eli: I will revise the update: four reports through the VPN, one successful office test, exact errors being collected, and no verified root cause yet.
Nia: Good. The comparison should show what differs and what remains unchanged. That gives the next team something concrete to investigate.
Eli: I'll remove the definite DNS diagnosis from the update now. Send me the comparison when it's ready and I'll add what it shows.
Nia: Exactly. A useful diagnosis depends on the evidence, not on keeping the first guess. We can be decisive about the next test while remaining uncertain about the cause.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 02: Networks, Connectivity, and Root-Cause Hypotheses
Original fictional case: The staff portal works from the office network but fails for four people connected through the virtual private network (VPN). The same portal address is used. Nobody has checked name resolution, routing, or access-policy logs for those requests. Eli says DNS must be the cause. Nia coordinates network investigation. The team has an approved diagnostic process and must not change production settings merely to test a guess.
Language workshop: The VPN pattern is a clue, not a DNS diagnosis
Communication goal: Challenge premature certainty and agree on comparisons that separate hypotheses.
Language guidance: A timeout, a refused connection, and a certificate warning are different observations. "The VPN is connected" does not establish that every destination is reachable. Name the source, destination, and observed result.
Useful expressions (preserve the supplied facts): The reports do point to a difference between access paths. / What evidence establishes DNS rather than another path issue? / Name resolution is one explanation we still need to test. / Was it a timeout, a refusal, or a certificate warning? / Compare the same destination from the two approved paths. / We should not change production settings to test an unverified guess. / We have not checked the resolver or policy logs for those requests. / The pattern narrows the investigation; it does not yet establish a cause. / Were all four reports from the same VPN profile? / A successful name lookup does not prove application access. / The portal worked for this office test at this time. / We have not tested every VPN user or destination. / Please include the time and time zone for each failed request. / Who will collect the approved comparison and record the results? / That check did not support the DNS hypothesis. / Keep the observed results separate from the proposed explanation.
Vocabulary: VPN: Virtual private network; a connection providing a defined private access path. / DNS: Domain Name System; the system that resolves names to records. / name resolution: Translating a name into the records needed for a connection. / IP address: A numerical network address used by the Internet Protocol. / hostname: A name identifying a host or service endpoint. / resolver: A service that answers or obtains DNS responses. / cache: Stored data reused to avoid repeating work. / TTL: Time to live; a lifetime limit, with meaning depending on context. / routing: Selection of paths for network traffic. / route: A path or forwarding rule for reaching a destination. / gateway: A system providing a path between networks or services. / subnet: A defined subdivision of an IP network. / firewall: A control that permits or blocks network traffic under rules. / access policy: Rules determining permitted access under stated conditions. / port: A numbered transport endpoint associated with a service. / packet loss: Failure of transmitted network packets to reach their destination. / round-trip time: Time for a request and return response across a path. / timeout: Expiry of a waiting period before a response completes. / connection refusal: An explicit rejection of a connection attempt. / TLS: Transport Layer Security; protection for communication in transit. / certificate: A signed digital statement used to bind identity and a public key. / proxy: An intermediary handling requests between client and destination. / reachability: Whether a destination can be contacted under specified conditions. / diagnostic hypothesis: A proposed explanation that still requires testing.
Speaking task: Check the dialogue. Contrast the working office path with four reported VPN failures; keep DNS as a hypothesis, not a finding. Switch roles. Request the exact warning, path and timestamp through the approved process, without proposing a speculative production change. Complete the certificate exchange. Retain the unreviewed proxy hypothesis and the instruction not to bypass the warning.
Partner: Eli: Support engineer / Nia: Network engineer
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: The same portal opens in an approved office test, while a remote user reports a certificate warning. No certificate or proxy review has occurred. The team must describe the actual warning without telling the user to bypass it.
Model for comparison AFTER my attempt, not a response to give me first: Eli: I will revise the update: four reports through the VPN, one successful office test, exact errors being collected, and no verified root cause yet.
Nia: Good. The comparison should show what differs and what remains unchanged. That gives the next team something concrete to investigate.
Eli: I'll remove the definite DNS diagnosis from the update now. Send me the comparison when it's ready and I'll add what it shows.
Nia: Exactly. A useful diagnosis depends on the evidence, not on keeping the first guess. We can be decisive about the next test while remaining uncertain about the cause.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 03: Identity, Access, and Permissions
Original fictional case: A temporary analyst, Jo, needs to download a monthly report. Jo requests administrator access because the current account shows an access-denied message. A reporting role may allow the required download, but its exact permissions have not been verified. Imani handles access requests. The manager can confirm Jo's business need; the system owner approves the role. The assignment ends on 30 November.
Language workshop: A report request does not justify administrator access
Communication goal: Clarify the required task and refuse excessive access while offering a legitimate route.
Language guidance: Authentication establishes identity evidence; authorization governs permitted actions. Being able to sign in does not imply permission to download every report. A role name alone does not prove its actual rights.
Useful expressions (preserve the supplied facts): Which report do you need, and what action must you perform? / You can sign in; the download permission is a different question. / I cannot justify administrator rights from the stated reporting task. / Let us verify whether the reporting role covers that download. / Your manager confirms the need; the system owner approves the role. / The requested access should match the assignment ending on 30 November. / The role may fit, but its permissions still need checking. / I will submit the task, resource, duration, and approval route together. / Please use your own approved account rather than another person's credentials. / Which entitlement is currently assigned to your account? / The request should provide the required action without unrelated control. / I can flag the deadline without bypassing the approval process. / After provisioning, confirm the authorized report action works. / Who will verify removal when the assignment finishes? / A reporting role and an administrator role serve different purposes. / Approval is pending; the request has been submitted, not granted.
Vocabulary: identity: The representation of a user or service in a system. / authentication: Establishing that a claimant controls the required identity evidence. / authorization: Permission to perform an action on a resource. / permission: An allowed action or access right. / role: A defined collection of access rights or responsibilities. / RBAC: Role-based access control; access organized through defined roles. / least privilege: Access limited to what is needed for the task. / administrator: A role with broad system-management permissions. / privileged access: Access allowing sensitive or powerful actions. / entitlement: A specific granted right to use a resource or capability. / provisioning: Creating or assigning accounts and access. / deprovisioning: Removing accounts or access no longer required. / access review: A check that granted access remains appropriate. / access request: A recorded request for specified permissions. / business justification: The work-related reason supporting a request. / approver: The person authorized to approve a request. / expiration: The point at which an entitlement or credential ends. / temporary access: Access granted for a defined limited period. / separation of duties: Dividing incompatible responsibilities to reduce risk. / SSO: Single sign-on; using one authentication session across services. / MFA: Multifactor authentication; use of distinct factor types. / service account: An identity used by an application or automated process. / audit log: A record of relevant actions for review. / access denied: A message indicating that an attempted action was not permitted.
Speaking task: Check the answers. Read the required monthly-report action, assignment ending 30 November, and unverified fit of the reporting role. Switch roles. Distinguish the manager's confirmation of need from the system owner's approval; do not substitute administrator rights for the scoped request. Complete the dashboard exchange. Retain viewing-only access for two weeks and pending approval.
Partner: Jo: Temporary analyst / Imani: Identity and access 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: A contractor needs to view one project dashboard for two weeks, not edit it. The project manager confirms the need; the dashboard owner approves access. No approval has yet been recorded.
Model for comparison AFTER my attempt, not a response to give me first: Jo: Will the approval email mean I can download immediately, or is there another step after that?
Imani: Approval and provisioning are separate states. After the role is assigned, confirm that the authorized download works with your own account.
Jo: And at the end of November, the access should be removed unless an extension is reviewed. Please include who checks that so it is not forgotten.
Imani: I will record deprovisioning ownership. For now the status is submitted for review, not granted, and we have a legitimate route that matches the work you actually need to do.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 03: Identity, Access, and Permissions
Original fictional case: A temporary analyst, Jo, needs to download a monthly report. Jo requests administrator access because the current account shows an access-denied message. A reporting role may allow the required download, but its exact permissions have not been verified. Imani handles access requests. The manager can confirm Jo's business need; the system owner approves the role. The assignment ends on 30 November.
Language workshop: A report request does not justify administrator access
Communication goal: Clarify the required task and refuse excessive access while offering a legitimate route.
Language guidance: Authentication establishes identity evidence; authorization governs permitted actions. Being able to sign in does not imply permission to download every report. A role name alone does not prove its actual rights.
Useful expressions (preserve the supplied facts): Which report do you need, and what action must you perform? / You can sign in; the download permission is a different question. / I cannot justify administrator rights from the stated reporting task. / Let us verify whether the reporting role covers that download. / Your manager confirms the need; the system owner approves the role. / The requested access should match the assignment ending on 30 November. / The role may fit, but its permissions still need checking. / I will submit the task, resource, duration, and approval route together. / Please use your own approved account rather than another person's credentials. / Which entitlement is currently assigned to your account? / The request should provide the required action without unrelated control. / I can flag the deadline without bypassing the approval process. / After provisioning, confirm the authorized report action works. / Who will verify removal when the assignment finishes? / A reporting role and an administrator role serve different purposes. / Approval is pending; the request has been submitted, not granted.
Vocabulary: identity: The representation of a user or service in a system. / authentication: Establishing that a claimant controls the required identity evidence. / authorization: Permission to perform an action on a resource. / permission: An allowed action or access right. / role: A defined collection of access rights or responsibilities. / RBAC: Role-based access control; access organized through defined roles. / least privilege: Access limited to what is needed for the task. / administrator: A role with broad system-management permissions. / privileged access: Access allowing sensitive or powerful actions. / entitlement: A specific granted right to use a resource or capability. / provisioning: Creating or assigning accounts and access. / deprovisioning: Removing accounts or access no longer required. / access review: A check that granted access remains appropriate. / access request: A recorded request for specified permissions. / business justification: The work-related reason supporting a request. / approver: The person authorized to approve a request. / expiration: The point at which an entitlement or credential ends. / temporary access: Access granted for a defined limited period. / separation of duties: Dividing incompatible responsibilities to reduce risk. / SSO: Single sign-on; using one authentication session across services. / MFA: Multifactor authentication; use of distinct factor types. / service account: An identity used by an application or automated process. / audit log: A record of relevant actions for review. / access denied: A message indicating that an attempted action was not permitted.
Speaking task: Check the answers. Read the required monthly-report action, assignment ending 30 November, and unverified fit of the reporting role. Switch roles. Distinguish the manager's confirmation of need from the system owner's approval; do not substitute administrator rights for the scoped request. Complete the dashboard exchange. Retain viewing-only access for two weeks and pending approval.
Partner: Jo: Temporary analyst / Imani: Identity and access 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: A contractor needs to view one project dashboard for two weeks, not edit it. The project manager confirms the need; the dashboard owner approves access. No approval has yet been recorded.
Model for comparison AFTER my attempt, not a response to give me first: Jo: Will the approval email mean I can download immediately, or is there another step after that?
Imani: Approval and provisioning are separate states. After the role is assigned, confirm that the authorized download works with your own account.
Jo: And at the end of November, the access should be removed unless an extension is reviewed. Please include who checks that so it is not forgotten.
Imani: I will record deprovisioning ownership. For now the status is submitted for review, not granted, and we have a legitimate route that matches the work you actually need to do.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 03: Identity, Access, and Permissions
Original fictional case: A temporary analyst, Jo, needs to download a monthly report. Jo requests administrator access because the current account shows an access-denied message. A reporting role may allow the required download, but its exact permissions have not been verified. Imani handles access requests. The manager can confirm Jo's business need; the system owner approves the role. The assignment ends on 30 November.
Language workshop: A report request does not justify administrator access
Communication goal: Clarify the required task and refuse excessive access while offering a legitimate route.
Language guidance: Authentication establishes identity evidence; authorization governs permitted actions. Being able to sign in does not imply permission to download every report. A role name alone does not prove its actual rights.
Useful expressions (preserve the supplied facts): Which report do you need, and what action must you perform? / You can sign in; the download permission is a different question. / I cannot justify administrator rights from the stated reporting task. / Let us verify whether the reporting role covers that download. / Your manager confirms the need; the system owner approves the role. / The requested access should match the assignment ending on 30 November. / The role may fit, but its permissions still need checking. / I will submit the task, resource, duration, and approval route together. / Please use your own approved account rather than another person's credentials. / Which entitlement is currently assigned to your account? / The request should provide the required action without unrelated control. / I can flag the deadline without bypassing the approval process. / After provisioning, confirm the authorized report action works. / Who will verify removal when the assignment finishes? / A reporting role and an administrator role serve different purposes. / Approval is pending; the request has been submitted, not granted.
Vocabulary: identity: The representation of a user or service in a system. / authentication: Establishing that a claimant controls the required identity evidence. / authorization: Permission to perform an action on a resource. / permission: An allowed action or access right. / role: A defined collection of access rights or responsibilities. / RBAC: Role-based access control; access organized through defined roles. / least privilege: Access limited to what is needed for the task. / administrator: A role with broad system-management permissions. / privileged access: Access allowing sensitive or powerful actions. / entitlement: A specific granted right to use a resource or capability. / provisioning: Creating or assigning accounts and access. / deprovisioning: Removing accounts or access no longer required. / access review: A check that granted access remains appropriate. / access request: A recorded request for specified permissions. / business justification: The work-related reason supporting a request. / approver: The person authorized to approve a request. / expiration: The point at which an entitlement or credential ends. / temporary access: Access granted for a defined limited period. / separation of duties: Dividing incompatible responsibilities to reduce risk. / SSO: Single sign-on; using one authentication session across services. / MFA: Multifactor authentication; use of distinct factor types. / service account: An identity used by an application or automated process. / audit log: A record of relevant actions for review. / access denied: A message indicating that an attempted action was not permitted.
Speaking task: Check the answers. Read the required monthly-report action, assignment ending 30 November, and unverified fit of the reporting role. Switch roles. Distinguish the manager's confirmation of need from the system owner's approval; do not substitute administrator rights for the scoped request. Complete the dashboard exchange. Retain viewing-only access for two weeks and pending approval.
Partner: Jo: Temporary analyst / Imani: Identity and access 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: A contractor needs to view one project dashboard for two weeks, not edit it. The project manager confirms the need; the dashboard owner approves access. No approval has yet been recorded.
Model for comparison AFTER my attempt, not a response to give me first: Jo: Will the approval email mean I can download immediately, or is there another step after that?
Imani: Approval and provisioning are separate states. After the role is assigned, confirm that the authorized download works with your own account.
Jo: And at the end of November, the access should be removed unless an extension is reviewed. Please include who checks that so it is not forgotten.
Imani: I will record deprovisioning ownership. For now the status is submitted for review, not granted, and we have a legitimate route that matches the work you actually need to do.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 04: Cloud, Infrastructure, and Cost-Aware Operations
Original fictional case: Two monthly cloud planning estimates cover the same application. Option A is $800 and excludes backup storage. Option B is $1,050 and includes backup storage. Transfer charges and support coverage have not been confirmed for either option. Jordan prepares the comparison; Sal owns infrastructure planning. These are fictional estimates, not provider prices. No purchasing decision has been approved.
Language workshop: The cheaper estimate leaves out backup storage
Communication goal: Compare incomplete estimates and qualify a recommendation without inventing missing costs.
Language guidance: The $250 difference compares two headline estimates with different inclusions. It is not a verified saving for equivalent services. RPO describes a data-loss interval; RTO describes a restoration-time target.
Useful expressions (preserve the supplied facts): The estimates do not include the same services. / Option A excludes backup storage; Option B includes it. / The headline difference is $250, not a confirmed like-for-like saving. / Can we compare both options against the same workload and retention assumptions? / Transfer charges remain unconfirmed for both options. / Does support cover the hours and response level we need? / Including storage does not establish that restoration has been tested. / I cannot recommend the lower total until the missing items are priced. / Is that per month, per stored unit, or per transfer volume? / Which usage pattern does this estimate assume? / What term or minimum spend is attached to that figure? / Put the excluded items next to the headline total. / I will mark the amount unknown rather than enter zero. / Is that the tolerated data-loss interval or the restoration-time target? / Show how the estimate changes under the agreed higher-use scenario. / We will reconcile the scope before asking for a purchasing decision.
Vocabulary: cloud service: Computing capability delivered through a service model. / infrastructure: The underlying computing and network resources. / instance: A running or configured unit of computing capacity. / virtual machine: A software-defined computing environment emulating a machine. / region: A provider-defined geographical deployment area. / availability zone: A provider-defined location grouping within a region. / object storage: Storage that manages data as objects with metadata. / block storage: Storage presented as addressable blocks. / snapshot: A point-in-time representation of data or system state. / backup: A retained copy intended to support recovery. / retention period: The length of time data is kept. / restore test: A check that retained data can be recovered as required. / RPO: Recovery point objective; tolerated data-loss interval. / RTO: Recovery time objective; target time to restore service. / egress: Data leaving a defined network or service boundary. / ingress: Data entering a defined network or service boundary. / consumption: Measured resource use over a period. / reservation: A commitment or capacity allocation under stated terms. / on-demand: Resource use without the particular advance commitment being discussed. / right-sizing: Matching resource allocation to workload needs. / cost allocation: Assignment of expenses to services or owners. / line item: An individual entry in an estimate or bill. / exclusion: A cost or service left outside the stated scope. / total cost: Combined cost under explicitly defined inclusions.
Speaking task: Check the dialogue. Read $800 and $1,050 as unequal-scope estimates: $250 is their headline difference, not verified savings. Switch roles. Ask for missing backup, transfer and support terms; keep unknown charges distinct from zero. Complete the annual-quote exchange. Identify the migration exclusion before requesting a like-for-like $12,000 versus $14,000 comparison.
Partner: Jordan: Cloud operations analyst / Sal: Infrastructure planning 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: Quote A is $12,000 annually without migration support. Quote B is $14,000 with migration support. The required migration scope and any additional charges remain unconfirmed.
Model for comparison AFTER my attempt, not a response to give me first: Jordan: I'll hold the recommendation. For today's note, I'll show the two prices and the missing items, with provisional above the totals.
Sal: Yes. We are aiming for like-for-like totals and clearly stated differences. We do not need to pretend the two options are identical if meaningful differences remain.
Jordan: I'll put the inclusions and unresolved amounts in one table. Can we review it again when the provider answers the backup and support questions?
Sal: Good. That creates an audit trail for the recommendation. We can explain what changed when the final numbers arrive instead of defending a saving we never actually verified.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 04: Cloud, Infrastructure, and Cost-Aware Operations
Original fictional case: Two monthly cloud planning estimates cover the same application. Option A is $800 and excludes backup storage. Option B is $1,050 and includes backup storage. Transfer charges and support coverage have not been confirmed for either option. Jordan prepares the comparison; Sal owns infrastructure planning. These are fictional estimates, not provider prices. No purchasing decision has been approved.
Language workshop: The cheaper estimate leaves out backup storage
Communication goal: Compare incomplete estimates and qualify a recommendation without inventing missing costs.
Language guidance: The $250 difference compares two headline estimates with different inclusions. It is not a verified saving for equivalent services. RPO describes a data-loss interval; RTO describes a restoration-time target.
Useful expressions (preserve the supplied facts): The estimates do not include the same services. / Option A excludes backup storage; Option B includes it. / The headline difference is $250, not a confirmed like-for-like saving. / Can we compare both options against the same workload and retention assumptions? / Transfer charges remain unconfirmed for both options. / Does support cover the hours and response level we need? / Including storage does not establish that restoration has been tested. / I cannot recommend the lower total until the missing items are priced. / Is that per month, per stored unit, or per transfer volume? / Which usage pattern does this estimate assume? / What term or minimum spend is attached to that figure? / Put the excluded items next to the headline total. / I will mark the amount unknown rather than enter zero. / Is that the tolerated data-loss interval or the restoration-time target? / Show how the estimate changes under the agreed higher-use scenario. / We will reconcile the scope before asking for a purchasing decision.
Vocabulary: cloud service: Computing capability delivered through a service model. / infrastructure: The underlying computing and network resources. / instance: A running or configured unit of computing capacity. / virtual machine: A software-defined computing environment emulating a machine. / region: A provider-defined geographical deployment area. / availability zone: A provider-defined location grouping within a region. / object storage: Storage that manages data as objects with metadata. / block storage: Storage presented as addressable blocks. / snapshot: A point-in-time representation of data or system state. / backup: A retained copy intended to support recovery. / retention period: The length of time data is kept. / restore test: A check that retained data can be recovered as required. / RPO: Recovery point objective; tolerated data-loss interval. / RTO: Recovery time objective; target time to restore service. / egress: Data leaving a defined network or service boundary. / ingress: Data entering a defined network or service boundary. / consumption: Measured resource use over a period. / reservation: A commitment or capacity allocation under stated terms. / on-demand: Resource use without the particular advance commitment being discussed. / right-sizing: Matching resource allocation to workload needs. / cost allocation: Assignment of expenses to services or owners. / line item: An individual entry in an estimate or bill. / exclusion: A cost or service left outside the stated scope. / total cost: Combined cost under explicitly defined inclusions.
Speaking task: Check the dialogue. Read $800 and $1,050 as unequal-scope estimates: $250 is their headline difference, not verified savings. Switch roles. Ask for missing backup, transfer and support terms; keep unknown charges distinct from zero. Complete the annual-quote exchange. Identify the migration exclusion before requesting a like-for-like $12,000 versus $14,000 comparison.
Partner: Jordan: Cloud operations analyst / Sal: Infrastructure planning 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: Quote A is $12,000 annually without migration support. Quote B is $14,000 with migration support. The required migration scope and any additional charges remain unconfirmed.
Model for comparison AFTER my attempt, not a response to give me first: Jordan: I'll hold the recommendation. For today's note, I'll show the two prices and the missing items, with provisional above the totals.
Sal: Yes. We are aiming for like-for-like totals and clearly stated differences. We do not need to pretend the two options are identical if meaningful differences remain.
Jordan: I'll put the inclusions and unresolved amounts in one table. Can we review it again when the provider answers the backup and support questions?
Sal: Good. That creates an audit trail for the recommendation. We can explain what changed when the final numbers arrive instead of defending a saving we never actually verified.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 04: Cloud, Infrastructure, and Cost-Aware Operations
Original fictional case: Two monthly cloud planning estimates cover the same application. Option A is $800 and excludes backup storage. Option B is $1,050 and includes backup storage. Transfer charges and support coverage have not been confirmed for either option. Jordan prepares the comparison; Sal owns infrastructure planning. These are fictional estimates, not provider prices. No purchasing decision has been approved.
Language workshop: The cheaper estimate leaves out backup storage
Communication goal: Compare incomplete estimates and qualify a recommendation without inventing missing costs.
Language guidance: The $250 difference compares two headline estimates with different inclusions. It is not a verified saving for equivalent services. RPO describes a data-loss interval; RTO describes a restoration-time target.
Useful expressions (preserve the supplied facts): The estimates do not include the same services. / Option A excludes backup storage; Option B includes it. / The headline difference is $250, not a confirmed like-for-like saving. / Can we compare both options against the same workload and retention assumptions? / Transfer charges remain unconfirmed for both options. / Does support cover the hours and response level we need? / Including storage does not establish that restoration has been tested. / I cannot recommend the lower total until the missing items are priced. / Is that per month, per stored unit, or per transfer volume? / Which usage pattern does this estimate assume? / What term or minimum spend is attached to that figure? / Put the excluded items next to the headline total. / I will mark the amount unknown rather than enter zero. / Is that the tolerated data-loss interval or the restoration-time target? / Show how the estimate changes under the agreed higher-use scenario. / We will reconcile the scope before asking for a purchasing decision.
Vocabulary: cloud service: Computing capability delivered through a service model. / infrastructure: The underlying computing and network resources. / instance: A running or configured unit of computing capacity. / virtual machine: A software-defined computing environment emulating a machine. / region: A provider-defined geographical deployment area. / availability zone: A provider-defined location grouping within a region. / object storage: Storage that manages data as objects with metadata. / block storage: Storage presented as addressable blocks. / snapshot: A point-in-time representation of data or system state. / backup: A retained copy intended to support recovery. / retention period: The length of time data is kept. / restore test: A check that retained data can be recovered as required. / RPO: Recovery point objective; tolerated data-loss interval. / RTO: Recovery time objective; target time to restore service. / egress: Data leaving a defined network or service boundary. / ingress: Data entering a defined network or service boundary. / consumption: Measured resource use over a period. / reservation: A commitment or capacity allocation under stated terms. / on-demand: Resource use without the particular advance commitment being discussed. / right-sizing: Matching resource allocation to workload needs. / cost allocation: Assignment of expenses to services or owners. / line item: An individual entry in an estimate or bill. / exclusion: A cost or service left outside the stated scope. / total cost: Combined cost under explicitly defined inclusions.
Speaking task: Check the dialogue. Read $800 and $1,050 as unequal-scope estimates: $250 is their headline difference, not verified savings. Switch roles. Ask for missing backup, transfer and support terms; keep unknown charges distinct from zero. Complete the annual-quote exchange. Identify the migration exclusion before requesting a like-for-like $12,000 versus $14,000 comparison.
Partner: Jordan: Cloud operations analyst / Sal: Infrastructure planning 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: Quote A is $12,000 annually without migration support. Quote B is $14,000 with migration support. The required migration scope and any additional charges remain unconfirmed.
Model for comparison AFTER my attempt, not a response to give me first: Jordan: I'll hold the recommendation. For today's note, I'll show the two prices and the missing items, with provisional above the totals.
Sal: Yes. We are aiming for like-for-like totals and clearly stated differences. We do not need to pretend the two options are identical if meaningful differences remain.
Jordan: I'll put the inclusions and unresolved amounts in one table. Can we review it again when the provider answers the backup and support questions?
Sal: Good. That creates an audit trail for the recommendation. We can explain what changed when the final numbers arrive instead of defending a saving we never actually verified.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 05: Endpoints, Servers, Patching, and Configuration Management
Original fictional case: A patch was assigned to 200 managed laptops. The console reports successful installation on 180, twelve laptops were offline, and eight returned installation errors. Post-installation verification has not been completed on all successful devices. Arun manages endpoints; Casey coordinates the rollout. A manager asks whether the deployment is complete. There is no approved exception for the remaining twenty laptops.
Language workshop: Ninety percent installed is not complete
Communication goal: Report deployment states accurately and define evidence needed for completion.
Language guidance: Assigned, downloaded, installed, restarted, and verified are not synonyms. A successful installation report may still require a restart or verification under the approved procedure. Report the actual evidence, not the most optimistic label.
Useful expressions (preserve the supplied facts): Installation succeeded on 180 of 200 managed laptops. / Twelve were offline; eight returned installation errors. / Verification is not yet complete on all reported successes. / I would report progress, not mark the deployment complete. / The planned scope remains 200 devices unless a change is approved. / Offline status is not an approved exception. / Which error codes are shared across the eight failures? / Assign owners for the offline follow-up, errors, and verification. / Does the required state depend on a pending reboot? / Keep installation failure separate from devices we could not reach. / What evidence must every in-scope device provide for completion? / Ninety percent installed does not mean the full rollout is verified. / A retry is scheduled; its outcome is not yet known. / Any removal from scope needs a documented reason and approval. / Keep the approved rollback route available during the rollout. / The next update will show verified devices and each unresolved group.
Vocabulary: endpoint: A user device or other terminal system on a network. / managed device: A device enrolled under an organization's management controls. / asset inventory: A record of devices and their relevant attributes. / patch: A software update intended to correct or change behavior. / patch level: The installed state of relevant software updates. / deployment: Distribution and application of a configuration or update. / installation: Placement and setup of software on a system. / verification: Checking evidence that the required state has been achieved. / reboot: Restarting a system. / maintenance window: An approved period for planned service work. / offline: Not currently connected or available to the management system. / retry: Another attempt after an earlier incomplete or failed action. / error code: A code identifying a reported error condition. / compliance state: A device's status against defined requirements. / configuration baseline: The agreed reference configuration. / configuration drift: Difference from the expected configuration over time. / exception: An approved departure from a requirement under stated conditions. / remediation: Work to correct a deficiency or failure. / deployment ring: A defined group receiving a staged rollout. / pilot group: A limited group used to test a change before expansion. / supersedence: Replacement of an earlier update by another. / dependency: A prerequisite needed for another action to succeed. / rollback: Return to an earlier configuration or version. / completion criterion: A condition defining when work counts as complete.
Speaking task: Check the answers. Read 180 installed, twelve offline and eight errors out of 200; distinguish the 90-percent installation rate from completion. Switch roles. Treat pending verification as a possible subset of installed devices, not extra inventory; retain the approved 200-device scope. Complete the server exchange. Keep the required restart and service check pending instead of reporting the update complete.
Partner: Arun: Endpoint administrator / Casey: Rollout coordinator
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 approved server update reports successful installation. A required restart is pending, and the service check has not run. The maintenance owner must receive an accurate status.
Model for comparison AFTER my attempt, not a response to give me first: Casey: Can you send the verified count before this afternoon's review, with an owner for each outstanding group? That's what the manager will ask for.
Arun: Yes. I will include the current evidence and remediation status. Where an action depends on a user or another team, I will make that dependency visible.
Casey: Then my message will say installation is progressing, twenty devices lack success reports, verification remains open, and no exception has been approved for those twenty.
Arun: That is accurate. We will close the rollout only when the agreed criteria are met or an authorized scope decision changes them. Clear state labels let the manager decide without being misled by done.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 05: Endpoints, Servers, Patching, and Configuration Management
Original fictional case: A patch was assigned to 200 managed laptops. The console reports successful installation on 180, twelve laptops were offline, and eight returned installation errors. Post-installation verification has not been completed on all successful devices. Arun manages endpoints; Casey coordinates the rollout. A manager asks whether the deployment is complete. There is no approved exception for the remaining twenty laptops.
Language workshop: Ninety percent installed is not complete
Communication goal: Report deployment states accurately and define evidence needed for completion.
Language guidance: Assigned, downloaded, installed, restarted, and verified are not synonyms. A successful installation report may still require a restart or verification under the approved procedure. Report the actual evidence, not the most optimistic label.
Useful expressions (preserve the supplied facts): Installation succeeded on 180 of 200 managed laptops. / Twelve were offline; eight returned installation errors. / Verification is not yet complete on all reported successes. / I would report progress, not mark the deployment complete. / The planned scope remains 200 devices unless a change is approved. / Offline status is not an approved exception. / Which error codes are shared across the eight failures? / Assign owners for the offline follow-up, errors, and verification. / Does the required state depend on a pending reboot? / Keep installation failure separate from devices we could not reach. / What evidence must every in-scope device provide for completion? / Ninety percent installed does not mean the full rollout is verified. / A retry is scheduled; its outcome is not yet known. / Any removal from scope needs a documented reason and approval. / Keep the approved rollback route available during the rollout. / The next update will show verified devices and each unresolved group.
Vocabulary: endpoint: A user device or other terminal system on a network. / managed device: A device enrolled under an organization's management controls. / asset inventory: A record of devices and their relevant attributes. / patch: A software update intended to correct or change behavior. / patch level: The installed state of relevant software updates. / deployment: Distribution and application of a configuration or update. / installation: Placement and setup of software on a system. / verification: Checking evidence that the required state has been achieved. / reboot: Restarting a system. / maintenance window: An approved period for planned service work. / offline: Not currently connected or available to the management system. / retry: Another attempt after an earlier incomplete or failed action. / error code: A code identifying a reported error condition. / compliance state: A device's status against defined requirements. / configuration baseline: The agreed reference configuration. / configuration drift: Difference from the expected configuration over time. / exception: An approved departure from a requirement under stated conditions. / remediation: Work to correct a deficiency or failure. / deployment ring: A defined group receiving a staged rollout. / pilot group: A limited group used to test a change before expansion. / supersedence: Replacement of an earlier update by another. / dependency: A prerequisite needed for another action to succeed. / rollback: Return to an earlier configuration or version. / completion criterion: A condition defining when work counts as complete.
Speaking task: Check the answers. Read 180 installed, twelve offline and eight errors out of 200; distinguish the 90-percent installation rate from completion. Switch roles. Treat pending verification as a possible subset of installed devices, not extra inventory; retain the approved 200-device scope. Complete the server exchange. Keep the required restart and service check pending instead of reporting the update complete.
Partner: Arun: Endpoint administrator / Casey: Rollout coordinator
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 approved server update reports successful installation. A required restart is pending, and the service check has not run. The maintenance owner must receive an accurate status.
Model for comparison AFTER my attempt, not a response to give me first: Casey: Can you send the verified count before this afternoon's review, with an owner for each outstanding group? That's what the manager will ask for.
Arun: Yes. I will include the current evidence and remediation status. Where an action depends on a user or another team, I will make that dependency visible.
Casey: Then my message will say installation is progressing, twenty devices lack success reports, verification remains open, and no exception has been approved for those twenty.
Arun: That is accurate. We will close the rollout only when the agreed criteria are met or an authorized scope decision changes them. Clear state labels let the manager decide without being misled by done.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 05: Endpoints, Servers, Patching, and Configuration Management
Original fictional case: A patch was assigned to 200 managed laptops. The console reports successful installation on 180, twelve laptops were offline, and eight returned installation errors. Post-installation verification has not been completed on all successful devices. Arun manages endpoints; Casey coordinates the rollout. A manager asks whether the deployment is complete. There is no approved exception for the remaining twenty laptops.
Language workshop: Ninety percent installed is not complete
Communication goal: Report deployment states accurately and define evidence needed for completion.
Language guidance: Assigned, downloaded, installed, restarted, and verified are not synonyms. A successful installation report may still require a restart or verification under the approved procedure. Report the actual evidence, not the most optimistic label.
Useful expressions (preserve the supplied facts): Installation succeeded on 180 of 200 managed laptops. / Twelve were offline; eight returned installation errors. / Verification is not yet complete on all reported successes. / I would report progress, not mark the deployment complete. / The planned scope remains 200 devices unless a change is approved. / Offline status is not an approved exception. / Which error codes are shared across the eight failures? / Assign owners for the offline follow-up, errors, and verification. / Does the required state depend on a pending reboot? / Keep installation failure separate from devices we could not reach. / What evidence must every in-scope device provide for completion? / Ninety percent installed does not mean the full rollout is verified. / A retry is scheduled; its outcome is not yet known. / Any removal from scope needs a documented reason and approval. / Keep the approved rollback route available during the rollout. / The next update will show verified devices and each unresolved group.
Vocabulary: endpoint: A user device or other terminal system on a network. / managed device: A device enrolled under an organization's management controls. / asset inventory: A record of devices and their relevant attributes. / patch: A software update intended to correct or change behavior. / patch level: The installed state of relevant software updates. / deployment: Distribution and application of a configuration or update. / installation: Placement and setup of software on a system. / verification: Checking evidence that the required state has been achieved. / reboot: Restarting a system. / maintenance window: An approved period for planned service work. / offline: Not currently connected or available to the management system. / retry: Another attempt after an earlier incomplete or failed action. / error code: A code identifying a reported error condition. / compliance state: A device's status against defined requirements. / configuration baseline: The agreed reference configuration. / configuration drift: Difference from the expected configuration over time. / exception: An approved departure from a requirement under stated conditions. / remediation: Work to correct a deficiency or failure. / deployment ring: A defined group receiving a staged rollout. / pilot group: A limited group used to test a change before expansion. / supersedence: Replacement of an earlier update by another. / dependency: A prerequisite needed for another action to succeed. / rollback: Return to an earlier configuration or version. / completion criterion: A condition defining when work counts as complete.
Speaking task: Check the answers. Read 180 installed, twelve offline and eight errors out of 200; distinguish the 90-percent installation rate from completion. Switch roles. Treat pending verification as a possible subset of installed devices, not extra inventory; retain the approved 200-device scope. Complete the server exchange. Keep the required restart and service check pending instead of reporting the update complete.
Partner: Arun: Endpoint administrator / Casey: Rollout coordinator
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 approved server update reports successful installation. A required restart is pending, and the service check has not run. The maintenance owner must receive an accurate status.
Model for comparison AFTER my attempt, not a response to give me first: Casey: Can you send the verified count before this afternoon's review, with an owner for each outstanding group? That's what the manager will ask for.
Arun: Yes. I will include the current evidence and remediation status. Where an action depends on a user or another team, I will make that dependency visible.
Casey: Then my message will say installation is progressing, twenty devices lack success reports, verification remains open, and no exception has been approved for those twenty.
Arun: That is accurate. We will close the rollout only when the agreed criteria are met or an authorized scope decision changes them. Clear state labels let the manager decide without being misled by done.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 06: Security Operations, Risk, and Incident Response
Original fictional case: An alert flags an unusual sign-in for a staff account at 09:12 UTC. The account owner has not confirmed whether the activity was legitimate. No data-access review has occurred. Bea detected the alert; Tomas coordinates the authorized response team. The team has a restricted evidence channel and an on-call contact. Only authorized responders decide containment actions in this fictional organization.
Language workshop: An unusual sign-in is not yet a confirmed compromise
Communication goal: Escalate a security observation with urgency, accurate scope, and controlled evidence.
Language guidance: An alert is a signal to assess, not automatic proof of compromise. A location estimate is not proof of a person's physical location. Preserve the difference between observed evidence, an interpretation, and an authorized classification.
Useful expressions (preserve the supplied facts): An unusual-sign-in alert was recorded at 09:12 UTC. / The account owner has not yet confirmed the activity. / I am referring this through the approved response channel now. / We have not established compromise or data exposure. / The complete evidence is in the restricted channel. / The authorized responder will decide containment actions. / Keep the original timestamp and its time zone in the timeline. / The next update will distinguish confirmed findings from open questions. / The alert reports a location estimate, not verified physical travel. / Which accounts and assets have actually been reviewed? / Share account details only with the designated recipients. / An unconfirmed alert is not the same as a cleared alert. / Please confirm who has accepted response ownership. / Technical response and external notification have different owners. / Follow the approved handling process before altering relevant records. / The finding remains under review; no final classification has been made.
Vocabulary: alert: A signal that a condition may require attention. / event: An observed occurrence in a system. / indicator: A piece of information that may point to relevant activity. / compromise: Unauthorized access or loss of a system's trusted state. / breach: A security or privacy violation whose exact meaning depends on context. / false positive: An alert or finding that identifies a condition not actually present. / sign-in log: A record of authentication attempts or sessions. / session: A period or context of authenticated interaction. / geolocation: An estimate of geographical position from available signals. / anomaly: A departure from an expected pattern. / SOC: Security operations center; a function coordinating monitoring and response. / on-call: Assigned availability to respond during a defined period. / escalation threshold: A condition requiring referral or higher attention. / containment: Actions intended to limit an incident's consequences. / eradication: Removal of identified causes or malicious elements under a response process. / recovery: Restoration of services or operations after disruption. / evidence preservation: Keeping relevant records intact for authorized review. / chain of custody: A record of evidence handling and transfers. / timeline: An ordered account of events with times. / scope assessment: Determination of affected assets, accounts, or data. / severity: The assessed seriousness of an incident or finding. / notification: Communication to designated recipients under defined rules. / need to know: A principle restricting information to necessary recipients. / post-incident review: Examination of an incident and lessons after response.
Speaking task: Check the dialogue. Read the 09:12 UTC alert without claiming confirmed compromise or a cleared false positive. Switch roles. Preserve pending account-owner confirmation and data-access review; use the restricted evidence route. Complete the email exchange. Keep attachment content and user interaction unconfirmed.
Partner: Bea: Security monitoring analyst / Tomas: Incident response coordinator
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 employee reports a suspicious email. The attachment has not been analyzed, and no interaction has been confirmed. The approved reporting route accepts the original message for authorized review.
Model for comparison AFTER my attempt, not a response to give me first: Bea: I'll send the business lead a short status update: who has the case, which checks are running, and what we still don't know. No account details.
Tomas: Exactly. Use a need-to-know summary for the audience. Clear communication does not mean every recipient receives every piece of evidence.
Bea: I'll submit it now. If the on-call responder hasn't accepted it, I'll follow the escalation route rather than leave it in the queue.
Tomas: That is the right distinction. Keep the finding under review until the authorized decision is recorded, and preserve the evidence and uncertainty in every shortened update.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 06: Security Operations, Risk, and Incident Response
Original fictional case: An alert flags an unusual sign-in for a staff account at 09:12 UTC. The account owner has not confirmed whether the activity was legitimate. No data-access review has occurred. Bea detected the alert; Tomas coordinates the authorized response team. The team has a restricted evidence channel and an on-call contact. Only authorized responders decide containment actions in this fictional organization.
Language workshop: An unusual sign-in is not yet a confirmed compromise
Communication goal: Escalate a security observation with urgency, accurate scope, and controlled evidence.
Language guidance: An alert is a signal to assess, not automatic proof of compromise. A location estimate is not proof of a person's physical location. Preserve the difference between observed evidence, an interpretation, and an authorized classification.
Useful expressions (preserve the supplied facts): An unusual-sign-in alert was recorded at 09:12 UTC. / The account owner has not yet confirmed the activity. / I am referring this through the approved response channel now. / We have not established compromise or data exposure. / The complete evidence is in the restricted channel. / The authorized responder will decide containment actions. / Keep the original timestamp and its time zone in the timeline. / The next update will distinguish confirmed findings from open questions. / The alert reports a location estimate, not verified physical travel. / Which accounts and assets have actually been reviewed? / Share account details only with the designated recipients. / An unconfirmed alert is not the same as a cleared alert. / Please confirm who has accepted response ownership. / Technical response and external notification have different owners. / Follow the approved handling process before altering relevant records. / The finding remains under review; no final classification has been made.
Vocabulary: alert: A signal that a condition may require attention. / event: An observed occurrence in a system. / indicator: A piece of information that may point to relevant activity. / compromise: Unauthorized access or loss of a system's trusted state. / breach: A security or privacy violation whose exact meaning depends on context. / false positive: An alert or finding that identifies a condition not actually present. / sign-in log: A record of authentication attempts or sessions. / session: A period or context of authenticated interaction. / geolocation: An estimate of geographical position from available signals. / anomaly: A departure from an expected pattern. / SOC: Security operations center; a function coordinating monitoring and response. / on-call: Assigned availability to respond during a defined period. / escalation threshold: A condition requiring referral or higher attention. / containment: Actions intended to limit an incident's consequences. / eradication: Removal of identified causes or malicious elements under a response process. / recovery: Restoration of services or operations after disruption. / evidence preservation: Keeping relevant records intact for authorized review. / chain of custody: A record of evidence handling and transfers. / timeline: An ordered account of events with times. / scope assessment: Determination of affected assets, accounts, or data. / severity: The assessed seriousness of an incident or finding. / notification: Communication to designated recipients under defined rules. / need to know: A principle restricting information to necessary recipients. / post-incident review: Examination of an incident and lessons after response.
Speaking task: Check the dialogue. Read the 09:12 UTC alert without claiming confirmed compromise or a cleared false positive. Switch roles. Preserve pending account-owner confirmation and data-access review; use the restricted evidence route. Complete the email exchange. Keep attachment content and user interaction unconfirmed.
Partner: Bea: Security monitoring analyst / Tomas: Incident response coordinator
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 employee reports a suspicious email. The attachment has not been analyzed, and no interaction has been confirmed. The approved reporting route accepts the original message for authorized review.
Model for comparison AFTER my attempt, not a response to give me first: Bea: I'll send the business lead a short status update: who has the case, which checks are running, and what we still don't know. No account details.
Tomas: Exactly. Use a need-to-know summary for the audience. Clear communication does not mean every recipient receives every piece of evidence.
Bea: I'll submit it now. If the on-call responder hasn't accepted it, I'll follow the escalation route rather than leave it in the queue.
Tomas: That is the right distinction. Keep the finding under review until the authorized decision is recorded, and preserve the evidence and uncertainty in every shortened update.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 06: Security Operations, Risk, and Incident Response
Original fictional case: An alert flags an unusual sign-in for a staff account at 09:12 UTC. The account owner has not confirmed whether the activity was legitimate. No data-access review has occurred. Bea detected the alert; Tomas coordinates the authorized response team. The team has a restricted evidence channel and an on-call contact. Only authorized responders decide containment actions in this fictional organization.
Language workshop: An unusual sign-in is not yet a confirmed compromise
Communication goal: Escalate a security observation with urgency, accurate scope, and controlled evidence.
Language guidance: An alert is a signal to assess, not automatic proof of compromise. A location estimate is not proof of a person's physical location. Preserve the difference between observed evidence, an interpretation, and an authorized classification.
Useful expressions (preserve the supplied facts): An unusual-sign-in alert was recorded at 09:12 UTC. / The account owner has not yet confirmed the activity. / I am referring this through the approved response channel now. / We have not established compromise or data exposure. / The complete evidence is in the restricted channel. / The authorized responder will decide containment actions. / Keep the original timestamp and its time zone in the timeline. / The next update will distinguish confirmed findings from open questions. / The alert reports a location estimate, not verified physical travel. / Which accounts and assets have actually been reviewed? / Share account details only with the designated recipients. / An unconfirmed alert is not the same as a cleared alert. / Please confirm who has accepted response ownership. / Technical response and external notification have different owners. / Follow the approved handling process before altering relevant records. / The finding remains under review; no final classification has been made.
Vocabulary: alert: A signal that a condition may require attention. / event: An observed occurrence in a system. / indicator: A piece of information that may point to relevant activity. / compromise: Unauthorized access or loss of a system's trusted state. / breach: A security or privacy violation whose exact meaning depends on context. / false positive: An alert or finding that identifies a condition not actually present. / sign-in log: A record of authentication attempts or sessions. / session: A period or context of authenticated interaction. / geolocation: An estimate of geographical position from available signals. / anomaly: A departure from an expected pattern. / SOC: Security operations center; a function coordinating monitoring and response. / on-call: Assigned availability to respond during a defined period. / escalation threshold: A condition requiring referral or higher attention. / containment: Actions intended to limit an incident's consequences. / eradication: Removal of identified causes or malicious elements under a response process. / recovery: Restoration of services or operations after disruption. / evidence preservation: Keeping relevant records intact for authorized review. / chain of custody: A record of evidence handling and transfers. / timeline: An ordered account of events with times. / scope assessment: Determination of affected assets, accounts, or data. / severity: The assessed seriousness of an incident or finding. / notification: Communication to designated recipients under defined rules. / need to know: A principle restricting information to necessary recipients. / post-incident review: Examination of an incident and lessons after response.
Speaking task: Check the dialogue. Read the 09:12 UTC alert without claiming confirmed compromise or a cleared false positive. Switch roles. Preserve pending account-owner confirmation and data-access review; use the restricted evidence route. Complete the email exchange. Keep attachment content and user interaction unconfirmed.
Partner: Bea: Security monitoring analyst / Tomas: Incident response coordinator
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 employee reports a suspicious email. The attachment has not been analyzed, and no interaction has been confirmed. The approved reporting route accepts the original message for authorized review.
Model for comparison AFTER my attempt, not a response to give me first: Bea: I'll send the business lead a short status update: who has the case, which checks are running, and what we still don't know. No account details.
Tomas: Exactly. Use a need-to-know summary for the audience. Clear communication does not mean every recipient receives every piece of evidence.
Bea: I'll submit it now. If the on-call responder hasn't accepted it, I'll follow the escalation route rather than leave it in the queue.
Tomas: That is the right distinction. Keep the finding under review until the authorized decision is recorded, and preserve the evidence and uncertainty in every shortened update.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 07: Change, Release, Problem, and Post-Incident Communication
Original fictional case: A maintenance notice sent to users says Tuesday from 8 to 9 p.m. The approved change record says Thursday from 8 to 9 p.m., local branch time. The work has not begun. One team moved its export schedule in response to the incorrect notice. Mina sent the notice; Owen owns change coordination. A correction must reach the original recipients and clearly replace the earlier message.
Language workshop: Correct the maintenance date before users act on it
Communication goal: Replace an inaccurate notice, acknowledge impact, and confirm the controlling record.
Language guidance: A mistaken notice is not automatically a changed authorization. "The date has moved" would imply an actual schedule change; "the Tuesday date was incorrect" identifies the communication error. Preserve the exact time zone.
Useful expressions (preserve the supplied facts): The Tuesday date in my earlier notice was incorrect. / The approved window is Thursday, 8 to 9 p.m., local branch time. / This correction supersedes the earlier maintenance notice. / The approved window has not changed; the notice was wrong. / I understand your team rescheduled an export based on that message. / Please confirm that the corrected date has reached the affected team. / The approved change record remains the source of truth. / I will send the correction and contact the team that already changed its schedule. / Use the original recipient list and any known forwarded recipients. / Include local branch time in the subject and body where appropriate. / Acknowledging this correction does not provide change approval. / Which other scheduled work depended on the incorrect date? / We should not assume a second email has been read. / Note the export rescheduling as a known impact of the error. / Review how the mismatch occurred after the immediate correction is sent. / Assign an owner to verify the notice against the approved record before sending.
Vocabulary: change record: Record describing a proposed change and its review or approval status. / change owner: The role responsible for a proposed or approved change. / change approval: Permission to carry out a specified change. / maintenance notice: A communication of planned service work and impact. / maintenance window: The authorized time period for planned work. / release: A version or package made available under a process. / deployment: Introduction of a release or configuration into an environment. / rollback plan: An approved route for returning to an earlier state. / implementation plan: The defined plan for carrying out a change. / validation: Checks that a change meets its intended requirements. / stakeholder: A person or group with an interest in the outcome. / recipient list: The designated audience for a message. / correction: A statement replacing inaccurate information. / supersede: Replace an earlier record or statement as controlling. / source of truth: The agreed authoritative record for a particular fact. / acknowledgment: Confirmation of receipt or understanding. / dependency: Work or a condition another action relies on. / change freeze: A defined restriction on changes during a period. / emergency change: A change handled under an authorized urgent process. / problem record: A record tracking an underlying cause or recurring issue. / known error: A recognized problem with documented diagnostic context or handling. / post-implementation review: Review of a change's outcome after implementation. / action owner: The person accountable for an agreed follow-up. / due date: The agreed date by which an action is expected.
Speaking task: Check the answers. Read Thursday, 8 to 9 p.m., local branch time as the approved window; Tuesday was a notice error. Switch roles. Send the correction to the original recipients and address the known export rescheduling; do not describe a newly changed approval. Complete the version exchange. Preserve approved version 4.1 and correct the erroneous 4.2 notice without suggesting deployment has begun.
Partner: Mina: Service communications analyst / Owen: Change coordinator
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 notice says version 4.2 will be deployed. The approved record specifies version 4.1. Deployment has not begun, and the approved version has not changed.
Model for comparison AFTER my attempt, not a response to give me first: Mina: After the urgent correction, we should review how the wrong date entered the notice. I copied an earlier planning note instead of checking the approved record.
Owen: Record a concrete follow-up with an action owner: verify the date, scope, and time zone against the approved record before each notice is sent.
Mina: I'll send it now and call the export team next. I'll let you know this afternoon if anyone still has a conflict with Thursday.
Owen: Thank you. Keep the correction and its audit trail. Clear replacement, accurate timing, and accountable follow-up matter more than making the original mistake disappear.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 07: Change, Release, Problem, and Post-Incident Communication
Original fictional case: A maintenance notice sent to users says Tuesday from 8 to 9 p.m. The approved change record says Thursday from 8 to 9 p.m., local branch time. The work has not begun. One team moved its export schedule in response to the incorrect notice. Mina sent the notice; Owen owns change coordination. A correction must reach the original recipients and clearly replace the earlier message.
Language workshop: Correct the maintenance date before users act on it
Communication goal: Replace an inaccurate notice, acknowledge impact, and confirm the controlling record.
Language guidance: A mistaken notice is not automatically a changed authorization. "The date has moved" would imply an actual schedule change; "the Tuesday date was incorrect" identifies the communication error. Preserve the exact time zone.
Useful expressions (preserve the supplied facts): The Tuesday date in my earlier notice was incorrect. / The approved window is Thursday, 8 to 9 p.m., local branch time. / This correction supersedes the earlier maintenance notice. / The approved window has not changed; the notice was wrong. / I understand your team rescheduled an export based on that message. / Please confirm that the corrected date has reached the affected team. / The approved change record remains the source of truth. / I will send the correction and contact the team that already changed its schedule. / Use the original recipient list and any known forwarded recipients. / Include local branch time in the subject and body where appropriate. / Acknowledging this correction does not provide change approval. / Which other scheduled work depended on the incorrect date? / We should not assume a second email has been read. / Note the export rescheduling as a known impact of the error. / Review how the mismatch occurred after the immediate correction is sent. / Assign an owner to verify the notice against the approved record before sending.
Vocabulary: change record: Record describing a proposed change and its review or approval status. / change owner: The role responsible for a proposed or approved change. / change approval: Permission to carry out a specified change. / maintenance notice: A communication of planned service work and impact. / maintenance window: The authorized time period for planned work. / release: A version or package made available under a process. / deployment: Introduction of a release or configuration into an environment. / rollback plan: An approved route for returning to an earlier state. / implementation plan: The defined plan for carrying out a change. / validation: Checks that a change meets its intended requirements. / stakeholder: A person or group with an interest in the outcome. / recipient list: The designated audience for a message. / correction: A statement replacing inaccurate information. / supersede: Replace an earlier record or statement as controlling. / source of truth: The agreed authoritative record for a particular fact. / acknowledgment: Confirmation of receipt or understanding. / dependency: Work or a condition another action relies on. / change freeze: A defined restriction on changes during a period. / emergency change: A change handled under an authorized urgent process. / problem record: A record tracking an underlying cause or recurring issue. / known error: A recognized problem with documented diagnostic context or handling. / post-implementation review: Review of a change's outcome after implementation. / action owner: The person accountable for an agreed follow-up. / due date: The agreed date by which an action is expected.
Speaking task: Check the answers. Read Thursday, 8 to 9 p.m., local branch time as the approved window; Tuesday was a notice error. Switch roles. Send the correction to the original recipients and address the known export rescheduling; do not describe a newly changed approval. Complete the version exchange. Preserve approved version 4.1 and correct the erroneous 4.2 notice without suggesting deployment has begun.
Partner: Mina: Service communications analyst / Owen: Change coordinator
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 notice says version 4.2 will be deployed. The approved record specifies version 4.1. Deployment has not begun, and the approved version has not changed.
Model for comparison AFTER my attempt, not a response to give me first: Mina: After the urgent correction, we should review how the wrong date entered the notice. I copied an earlier planning note instead of checking the approved record.
Owen: Record a concrete follow-up with an action owner: verify the date, scope, and time zone against the approved record before each notice is sent.
Mina: I'll send it now and call the export team next. I'll let you know this afternoon if anyone still has a conflict with Thursday.
Owen: Thank you. Keep the correction and its audit trail. Clear replacement, accurate timing, and accountable follow-up matter more than making the original mistake disappear.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the 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: General IT English
Professional audience: IT operations, service desk, infrastructure, cloud, endpoint, security, and platform teams
Scope: Fictional workplace language practice, not instructions for administering real systems or handling live incidents. Follow authorized procedures, access controls, and qualified security review. Use invented accounts and records in practice.
Lesson 07: Change, Release, Problem, and Post-Incident Communication
Original fictional case: A maintenance notice sent to users says Tuesday from 8 to 9 p.m. The approved change record says Thursday from 8 to 9 p.m., local branch time. The work has not begun. One team moved its export schedule in response to the incorrect notice. Mina sent the notice; Owen owns change coordination. A correction must reach the original recipients and clearly replace the earlier message.
Language workshop: Correct the maintenance date before users act on it
Communication goal: Replace an inaccurate notice, acknowledge impact, and confirm the controlling record.
Language guidance: A mistaken notice is not automatically a changed authorization. "The date has moved" would imply an actual schedule change; "the Tuesday date was incorrect" identifies the communication error. Preserve the exact time zone.
Useful expressions (preserve the supplied facts): The Tuesday date in my earlier notice was incorrect. / The approved window is Thursday, 8 to 9 p.m., local branch time. / This correction supersedes the earlier maintenance notice. / The approved window has not changed; the notice was wrong. / I understand your team rescheduled an export based on that message. / Please confirm that the corrected date has reached the affected team. / The approved change record remains the source of truth. / I will send the correction and contact the team that already changed its schedule. / Use the original recipient list and any known forwarded recipients. / Include local branch time in the subject and body where appropriate. / Acknowledging this correction does not provide change approval. / Which other scheduled work depended on the incorrect date? / We should not assume a second email has been read. / Note the export rescheduling as a known impact of the error. / Review how the mismatch occurred after the immediate correction is sent. / Assign an owner to verify the notice against the approved record before sending.
Vocabulary: change record: Record describing a proposed change and its review or approval status. / change owner: The role responsible for a proposed or approved change. / change approval: Permission to carry out a specified change. / maintenance notice: A communication of planned service work and impact. / maintenance window: The authorized time period for planned work. / release: A version or package made available under a process. / deployment: Introduction of a release or configuration into an environment. / rollback plan: An approved route for returning to an earlier state. / implementation plan: The defined plan for carrying out a change. / validation: Checks that a change meets its intended requirements. / stakeholder: A person or group with an interest in the outcome. / recipient list: The designated audience for a message. / correction: A statement replacing inaccurate information. / supersede: Replace an earlier record or statement as controlling. / source of truth: The agreed authoritative record for a particular fact. / acknowledgment: Confirmation of receipt or understanding. / dependency: Work or a condition another action relies on. / change freeze: A defined restriction on changes during a period. / emergency change: A change handled under an authorized urgent process. / problem record: A record tracking an underlying cause or recurring issue. / known error: A recognized problem with documented diagnostic context or handling. / post-implementation review: Review of a change's outcome after implementation. / action owner: The person accountable for an agreed follow-up. / due date: The agreed date by which an action is expected.
Speaking task: Check the answers. Read Thursday, 8 to 9 p.m., local branch time as the approved window; Tuesday was a notice error. Switch roles. Send the correction to the original recipients and address the known export rescheduling; do not describe a newly changed approval. Complete the version exchange. Preserve approved version 4.1 and correct the erroneous 4.2 notice without suggesting deployment has begun.
Partner: Mina: Service communications analyst / Owen: Change coordinator
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 notice says version 4.2 will be deployed. The approved record specifies version 4.1. Deployment has not begun, and the approved version has not changed.
Model for comparison AFTER my attempt, not a response to give me first: Mina: After the urgent correction, we should review how the wrong date entered the notice. I copied an earlier planning note instead of checking the approved record.
Owen: Record a concrete follow-up with an action owner: verify the date, scope, and time zone against the approved record before each notice is sent.
Mina: I'll send it now and call the export team next. I'll let you know this afternoon if anyone still has a conflict with Thursday.
Owen: Thank you. Keep the correction and its audit trail. Clear replacement, accurate timing, and accountable follow-up matter more than making the original mistake disappear.
END REFERENCE