Medical Devices English — COMPLETE AI PRACTICE PROMPTS

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

Lesson 01 · User Needs and Design Inputs | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 01: User Needs and Design Inputs
Original fictional case: Design engineer Mira and product lead Owen review a fictional monitoring-device brief. It says easy to use and suitable everywhere. The agreed initial audience is trained clinic staff, but an appended slide also mentions home caregivers. No home-use assessment is supplied. A proposed setup-time target of two minutes has not been reviewed or approved. Mira and Owen must distinguish the agreed scope, the proposed expansion, and the missing basis for a measurable design input.
Language workshop: What does easy to use mean?
Communication goal: Turn an ambiguous design discussion into a scoped request for users, conditions, and measurable criteria.
Language guidance: A proposed two-minute target is not an approved acceptance criterion. The team must identify what setup includes, who performs it, under which conditions, and why the target is appropriate before treating the number as a settled requirement.
Useful expressions (preserve the supplied facts): Ease of use matters; we need to define the task behind that phrase. / The agreed initial users are trained clinic staff. / Home caregivers are a proposed additional user group. / Which lighting, noise, and workflow conditions are in scope? / What exactly counts as setup in this requirement? / Two minutes is a candidate target, not an approved criterion. / What evidence supports that time limit? / The requirement should address the user need rather than only our preferred feature. / Link this input to the need and the planned evaluation. / Suitable everywhere goes beyond the environments we have assessed. / We are assuming equivalent training, but that has not been established. / Who will resolve the user-profile question? / The scope change needs review before it enters the baseline. / A new screen layout is an output, not proof that the need is met. / Keep the home-use item marked proposed in the meeting record. / We will return with the defined task, conditions, and criterion basis.
Vocabulary: user need: A requirement expressed from the perspective of the intended user. / design input: A specified requirement that guides device design and development. / design output: A result of design work that can be checked against inputs. / intended user: The person or user group the device is designed for. / intended use: The purpose for which a device is intended. / use environment: The physical and social setting in which a device is used. / user profile: Relevant characteristics of a defined user group. / task analysis: Examination of the actions and decisions needed to perform a task. / use scenario: A description of users performing tasks under specified conditions. / design constraint: A limit that the design must satisfy. / acceptance criterion: A specified condition used to decide whether a requirement is met. / measurable requirement: A requirement expressed so its fulfillment can be evaluated. / stakeholder: A person or group with a relevant interest in the product. / voice of the customer: Collected customer needs and expectations. / requirements baseline: The agreed requirement set used as a reference for controlled work. / traceability: The ability to follow links between related records or requirements. / use limitation: A boundary on the conditions or purposes of use. / ergonomics: Design attention to how people physically and cognitively interact with a product. / interface: The elements through which a user interacts with a device. / workflow: The ordered activities through which work is completed. / design assumption: An unconfirmed premise influencing a design decision. / scope expansion: An increase in the users, uses, or conditions covered by a project. / change request: A documented proposal to alter an agreed item. / requirement owner: The person accountable for clarifying and maintaining a requirement.
Speaking task: Read the design-input discussion. Preserve trained clinic staff as the agreed audience and home caregivers as a proposal. Swap roles. State the two-minute target as unapproved; identify setup boundaries and the basis still needed. Read the corrected ninety-second transfer. Keep the outpatient baseline distinct from the proposed home expansion.
Partner: Mira: Design engineer / Owen: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A brief covers trained outpatient staff. A slide proposes home use. A ninety-second task target is suggested but has not been approved.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will separate the clinic requirement from the home-use proposal. The notes will say that the two-minute target remains unreviewed, with a named follow-up owner.
Mira: Keep both proposals outside the approved requirements baseline until the review is complete. Clear status now prevents later teams from treating a meeting idea as an established obligation.
Owen: I will keep easy to use as the customer concern and assign the setup-definition work. The home-use proposal and two-minute target remain open for review.
Mira: Exactly. A well-scoped design input will identify what the design must achieve. The evidence must then show whether the resulting device actually meets the relevant requirement.
END REFERENCE
END PROMPT

Lesson 01 · User Needs and Design Inputs | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 01: User Needs and Design Inputs
Original fictional case: Design engineer Mira and product lead Owen review a fictional monitoring-device brief. It says easy to use and suitable everywhere. The agreed initial audience is trained clinic staff, but an appended slide also mentions home caregivers. No home-use assessment is supplied. A proposed setup-time target of two minutes has not been reviewed or approved. Mira and Owen must distinguish the agreed scope, the proposed expansion, and the missing basis for a measurable design input.
Language workshop: What does easy to use mean?
Communication goal: Turn an ambiguous design discussion into a scoped request for users, conditions, and measurable criteria.
Language guidance: A proposed two-minute target is not an approved acceptance criterion. The team must identify what setup includes, who performs it, under which conditions, and why the target is appropriate before treating the number as a settled requirement.
Useful expressions (preserve the supplied facts): Ease of use matters; we need to define the task behind that phrase. / The agreed initial users are trained clinic staff. / Home caregivers are a proposed additional user group. / Which lighting, noise, and workflow conditions are in scope? / What exactly counts as setup in this requirement? / Two minutes is a candidate target, not an approved criterion. / What evidence supports that time limit? / The requirement should address the user need rather than only our preferred feature. / Link this input to the need and the planned evaluation. / Suitable everywhere goes beyond the environments we have assessed. / We are assuming equivalent training, but that has not been established. / Who will resolve the user-profile question? / The scope change needs review before it enters the baseline. / A new screen layout is an output, not proof that the need is met. / Keep the home-use item marked proposed in the meeting record. / We will return with the defined task, conditions, and criterion basis.
Vocabulary: user need: A requirement expressed from the perspective of the intended user. / design input: A specified requirement that guides device design and development. / design output: A result of design work that can be checked against inputs. / intended user: The person or user group the device is designed for. / intended use: The purpose for which a device is intended. / use environment: The physical and social setting in which a device is used. / user profile: Relevant characteristics of a defined user group. / task analysis: Examination of the actions and decisions needed to perform a task. / use scenario: A description of users performing tasks under specified conditions. / design constraint: A limit that the design must satisfy. / acceptance criterion: A specified condition used to decide whether a requirement is met. / measurable requirement: A requirement expressed so its fulfillment can be evaluated. / stakeholder: A person or group with a relevant interest in the product. / voice of the customer: Collected customer needs and expectations. / requirements baseline: The agreed requirement set used as a reference for controlled work. / traceability: The ability to follow links between related records or requirements. / use limitation: A boundary on the conditions or purposes of use. / ergonomics: Design attention to how people physically and cognitively interact with a product. / interface: The elements through which a user interacts with a device. / workflow: The ordered activities through which work is completed. / design assumption: An unconfirmed premise influencing a design decision. / scope expansion: An increase in the users, uses, or conditions covered by a project. / change request: A documented proposal to alter an agreed item. / requirement owner: The person accountable for clarifying and maintaining a requirement.
Speaking task: Read the design-input discussion. Preserve trained clinic staff as the agreed audience and home caregivers as a proposal. Swap roles. State the two-minute target as unapproved; identify setup boundaries and the basis still needed. Read the corrected ninety-second transfer. Keep the outpatient baseline distinct from the proposed home expansion.
Partner: Mira: Design engineer / Owen: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A brief covers trained outpatient staff. A slide proposes home use. A ninety-second task target is suggested but has not been approved.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will separate the clinic requirement from the home-use proposal. The notes will say that the two-minute target remains unreviewed, with a named follow-up owner.
Mira: Keep both proposals outside the approved requirements baseline until the review is complete. Clear status now prevents later teams from treating a meeting idea as an established obligation.
Owen: I will keep easy to use as the customer concern and assign the setup-definition work. The home-use proposal and two-minute target remain open for review.
Mira: Exactly. A well-scoped design input will identify what the design must achieve. The evidence must then show whether the resulting device actually meets the relevant requirement.
END REFERENCE
END PROMPT

Lesson 01 · User Needs and Design Inputs | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 01: User Needs and Design Inputs
Original fictional case: Design engineer Mira and product lead Owen review a fictional monitoring-device brief. It says easy to use and suitable everywhere. The agreed initial audience is trained clinic staff, but an appended slide also mentions home caregivers. No home-use assessment is supplied. A proposed setup-time target of two minutes has not been reviewed or approved. Mira and Owen must distinguish the agreed scope, the proposed expansion, and the missing basis for a measurable design input.
Language workshop: What does easy to use mean?
Communication goal: Turn an ambiguous design discussion into a scoped request for users, conditions, and measurable criteria.
Language guidance: A proposed two-minute target is not an approved acceptance criterion. The team must identify what setup includes, who performs it, under which conditions, and why the target is appropriate before treating the number as a settled requirement.
Useful expressions (preserve the supplied facts): Ease of use matters; we need to define the task behind that phrase. / The agreed initial users are trained clinic staff. / Home caregivers are a proposed additional user group. / Which lighting, noise, and workflow conditions are in scope? / What exactly counts as setup in this requirement? / Two minutes is a candidate target, not an approved criterion. / What evidence supports that time limit? / The requirement should address the user need rather than only our preferred feature. / Link this input to the need and the planned evaluation. / Suitable everywhere goes beyond the environments we have assessed. / We are assuming equivalent training, but that has not been established. / Who will resolve the user-profile question? / The scope change needs review before it enters the baseline. / A new screen layout is an output, not proof that the need is met. / Keep the home-use item marked proposed in the meeting record. / We will return with the defined task, conditions, and criterion basis.
Vocabulary: user need: A requirement expressed from the perspective of the intended user. / design input: A specified requirement that guides device design and development. / design output: A result of design work that can be checked against inputs. / intended user: The person or user group the device is designed for. / intended use: The purpose for which a device is intended. / use environment: The physical and social setting in which a device is used. / user profile: Relevant characteristics of a defined user group. / task analysis: Examination of the actions and decisions needed to perform a task. / use scenario: A description of users performing tasks under specified conditions. / design constraint: A limit that the design must satisfy. / acceptance criterion: A specified condition used to decide whether a requirement is met. / measurable requirement: A requirement expressed so its fulfillment can be evaluated. / stakeholder: A person or group with a relevant interest in the product. / voice of the customer: Collected customer needs and expectations. / requirements baseline: The agreed requirement set used as a reference for controlled work. / traceability: The ability to follow links between related records or requirements. / use limitation: A boundary on the conditions or purposes of use. / ergonomics: Design attention to how people physically and cognitively interact with a product. / interface: The elements through which a user interacts with a device. / workflow: The ordered activities through which work is completed. / design assumption: An unconfirmed premise influencing a design decision. / scope expansion: An increase in the users, uses, or conditions covered by a project. / change request: A documented proposal to alter an agreed item. / requirement owner: The person accountable for clarifying and maintaining a requirement.
Speaking task: Read the design-input discussion. Preserve trained clinic staff as the agreed audience and home caregivers as a proposal. Swap roles. State the two-minute target as unapproved; identify setup boundaries and the basis still needed. Read the corrected ninety-second transfer. Keep the outpatient baseline distinct from the proposed home expansion.
Partner: Mira: Design engineer / Owen: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A brief covers trained outpatient staff. A slide proposes home use. A ninety-second task target is suggested but has not been approved.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will separate the clinic requirement from the home-use proposal. The notes will say that the two-minute target remains unreviewed, with a named follow-up owner.
Mira: Keep both proposals outside the approved requirements baseline until the review is complete. Clear status now prevents later teams from treating a meeting idea as an established obligation.
Owen: I will keep easy to use as the customer concern and assign the setup-definition work. The home-use proposal and two-minute target remain open for review.
Mira: Exactly. A well-scoped design input will identify what the design must achieve. The evidence must then show whether the resulting device actually meets the relevant requirement.
END REFERENCE
END PROMPT

Lesson 01 · User Needs and Design Inputs | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 01: User Needs and Design Inputs
Original fictional case: Design engineer Mira and product lead Owen review a fictional monitoring-device brief. It says easy to use and suitable everywhere. The agreed initial audience is trained clinic staff, but an appended slide also mentions home caregivers. No home-use assessment is supplied. A proposed setup-time target of two minutes has not been reviewed or approved. Mira and Owen must distinguish the agreed scope, the proposed expansion, and the missing basis for a measurable design input.
Language workshop: What does easy to use mean?
Communication goal: Turn an ambiguous design discussion into a scoped request for users, conditions, and measurable criteria.
Language guidance: A proposed two-minute target is not an approved acceptance criterion. The team must identify what setup includes, who performs it, under which conditions, and why the target is appropriate before treating the number as a settled requirement.
Useful expressions (preserve the supplied facts): Ease of use matters; we need to define the task behind that phrase. / The agreed initial users are trained clinic staff. / Home caregivers are a proposed additional user group. / Which lighting, noise, and workflow conditions are in scope? / What exactly counts as setup in this requirement? / Two minutes is a candidate target, not an approved criterion. / What evidence supports that time limit? / The requirement should address the user need rather than only our preferred feature. / Link this input to the need and the planned evaluation. / Suitable everywhere goes beyond the environments we have assessed. / We are assuming equivalent training, but that has not been established. / Who will resolve the user-profile question? / The scope change needs review before it enters the baseline. / A new screen layout is an output, not proof that the need is met. / Keep the home-use item marked proposed in the meeting record. / We will return with the defined task, conditions, and criterion basis.
Vocabulary: user need: A requirement expressed from the perspective of the intended user. / design input: A specified requirement that guides device design and development. / design output: A result of design work that can be checked against inputs. / intended user: The person or user group the device is designed for. / intended use: The purpose for which a device is intended. / use environment: The physical and social setting in which a device is used. / user profile: Relevant characteristics of a defined user group. / task analysis: Examination of the actions and decisions needed to perform a task. / use scenario: A description of users performing tasks under specified conditions. / design constraint: A limit that the design must satisfy. / acceptance criterion: A specified condition used to decide whether a requirement is met. / measurable requirement: A requirement expressed so its fulfillment can be evaluated. / stakeholder: A person or group with a relevant interest in the product. / voice of the customer: Collected customer needs and expectations. / requirements baseline: The agreed requirement set used as a reference for controlled work. / traceability: The ability to follow links between related records or requirements. / use limitation: A boundary on the conditions or purposes of use. / ergonomics: Design attention to how people physically and cognitively interact with a product. / interface: The elements through which a user interacts with a device. / workflow: The ordered activities through which work is completed. / design assumption: An unconfirmed premise influencing a design decision. / scope expansion: An increase in the users, uses, or conditions covered by a project. / change request: A documented proposal to alter an agreed item. / requirement owner: The person accountable for clarifying and maintaining a requirement.
Speaking task: Read the design-input discussion. Preserve trained clinic staff as the agreed audience and home caregivers as a proposal. Swap roles. State the two-minute target as unapproved; identify setup boundaries and the basis still needed. Read the corrected ninety-second transfer. Keep the outpatient baseline distinct from the proposed home expansion.
Partner: Mira: Design engineer / Owen: Product lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A brief covers trained outpatient staff. A slide proposes home use. A ninety-second task target is suggested but has not been approved.
Model for comparison AFTER my attempt, not a response to give me first: Owen: I will separate the clinic requirement from the home-use proposal. The notes will say that the two-minute target remains unreviewed, with a named follow-up owner.
Mira: Keep both proposals outside the approved requirements baseline until the review is complete. Clear status now prevents later teams from treating a meeting idea as an established obligation.
Owen: I will keep easy to use as the customer concern and assign the setup-definition work. The home-use proposal and two-minute target remain open for review.
Mira: Exactly. A well-scoped design input will identify what the design must achieve. The evidence must then show whether the resulting device actually meets the relevant requirement.
END REFERENCE
END PROMPT

Lesson 02 · Risk Management and Hazard Analysis | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 02: Risk Management and Hazard Analysis
Original fictional case: Risk engineer Elena and mechanical lead Sam review a fictional enclosure-heating concern. The worksheet labels skin burn as the hazard and says low risk because no complaints have been received. The team has identified a potentially hot accessible surface, possible prolonged contact, and possible skin injury. No likelihood estimate or verified control result is supplied. An insulating cover is only a proposal. Their task is to correct the chain of reasoning without deciding that the device is safe.
Language workshop: The hot surface is not the injury
Communication goal: Separate a hazard, an exposure situation, possible harm, and the evidence for a risk-control claim.
Language guidance: Hazard, hazardous situation, and harm are not interchangeable. In this case, the potentially hot surface is the source; prolonged contact describes exposure; a burn is the possible injury. These distinctions clarify the analysis without supplying a likelihood estimate.
Useful expressions (preserve the supplied facts): The accessible hot surface is the potential source of harm. / Prolonged contact is the exposure situation we need to examine. / A skin burn is the possible harm, not the source. / Severity and probability answer different questions. / What evidence supports this likelihood estimate? / No complaints received does not establish zero risk. / The cover is a candidate protective measure. / We have not yet verified the control's effectiveness. / Which sequence could lead from this condition to injury? / The current record does not support the low-risk conclusion. / Could the proposed cover introduce another risk? / We cannot describe post-control risk before assessing the implemented measure. / Which acceptability criteria are being applied? / Connect the analysis, control, verification, and review decision. / This review does not establish that every risk has been eliminated. / Assign the missing evidence to an owner before the next review.
Vocabulary: hazard: A potential source of injury or other harm. / harm: Injury or damage to health, property, or the environment. / hazardous situation: Circumstances in which people or other protected things are exposed to a hazard. / sequence of events: The linked events that can lead to exposure and harm. / severity: The degree of possible harm. / probability of harm: The likelihood that the specified harm will occur. / risk: The combination of the probability of harm and its severity. / risk analysis: Systematic identification of hazards and estimation of associated risks. / risk evaluation: Comparing estimated risk with established acceptability criteria. / risk control: A measure intended to reduce risk. / residual risk: Risk remaining after risk-control measures have been implemented. / risk acceptability: Whether risk meets the applicable acceptance criteria. / protective measure: A safeguard intended to reduce exposure or its consequences. / inherent safety: Safety achieved through the design itself. / information for safety: Warnings or instructions intended to support risk reduction. / benefit-risk analysis: Evaluation of relevant benefits against remaining risks. / risk management file: The organized records of risk-management activities and results. / foreseeable misuse: Incorrect use that can reasonably be anticipated. / normal condition: Operation without a fault being present. / fault condition: A state in which a component or function has failed. / control effectiveness: The demonstrated ability of a measure to reduce the identified risk. / newly introduced risk: A risk created or changed by a design or control modification. / risk estimate: An assessment of harm probability and severity. / objective evidence: Verifiable information supporting a conclusion.
Speaking task: Read the risk review. Name the hot surface, prolonged contact, and possible burn as source, exposure, and harm. Swap roles. Keep the cover proposed and its effect unverified; do not use complaint absence as a probability estimate. Read the corrected sharp-edge transfer. Distinguish the redesign proposal from evidence of control effectiveness.
Partner: Elena: Risk engineer / Sam: Mechanical lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional handle may have a sharp edge. Hand contact could cause a cut. A rounded redesign is proposed but has not been evaluated.
Model for comparison AFTER my attempt, not a response to give me first: Sam: I will change the status to evidence incomplete and retain the proposed cover as an action for engineering review. We also need the criterion behind any acceptance decision.
Elena: Yes, document the applicable risk acceptability criteria. The reviewer needs the reasoning and evidence, not simply a low label attached to an unfinished analysis.
Sam: I will separate the hot surface, prolonged contact, and possible burn in the record. Send me the evidence needed before we can judge the proposed cover.
Elena: That gives the next review useful objective evidence to request and evaluate. We can make progress on the concern without converting a proposal into a completed safety conclusion.
END REFERENCE
END PROMPT

Lesson 02 · Risk Management and Hazard Analysis | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 02: Risk Management and Hazard Analysis
Original fictional case: Risk engineer Elena and mechanical lead Sam review a fictional enclosure-heating concern. The worksheet labels skin burn as the hazard and says low risk because no complaints have been received. The team has identified a potentially hot accessible surface, possible prolonged contact, and possible skin injury. No likelihood estimate or verified control result is supplied. An insulating cover is only a proposal. Their task is to correct the chain of reasoning without deciding that the device is safe.
Language workshop: The hot surface is not the injury
Communication goal: Separate a hazard, an exposure situation, possible harm, and the evidence for a risk-control claim.
Language guidance: Hazard, hazardous situation, and harm are not interchangeable. In this case, the potentially hot surface is the source; prolonged contact describes exposure; a burn is the possible injury. These distinctions clarify the analysis without supplying a likelihood estimate.
Useful expressions (preserve the supplied facts): The accessible hot surface is the potential source of harm. / Prolonged contact is the exposure situation we need to examine. / A skin burn is the possible harm, not the source. / Severity and probability answer different questions. / What evidence supports this likelihood estimate? / No complaints received does not establish zero risk. / The cover is a candidate protective measure. / We have not yet verified the control's effectiveness. / Which sequence could lead from this condition to injury? / The current record does not support the low-risk conclusion. / Could the proposed cover introduce another risk? / We cannot describe post-control risk before assessing the implemented measure. / Which acceptability criteria are being applied? / Connect the analysis, control, verification, and review decision. / This review does not establish that every risk has been eliminated. / Assign the missing evidence to an owner before the next review.
Vocabulary: hazard: A potential source of injury or other harm. / harm: Injury or damage to health, property, or the environment. / hazardous situation: Circumstances in which people or other protected things are exposed to a hazard. / sequence of events: The linked events that can lead to exposure and harm. / severity: The degree of possible harm. / probability of harm: The likelihood that the specified harm will occur. / risk: The combination of the probability of harm and its severity. / risk analysis: Systematic identification of hazards and estimation of associated risks. / risk evaluation: Comparing estimated risk with established acceptability criteria. / risk control: A measure intended to reduce risk. / residual risk: Risk remaining after risk-control measures have been implemented. / risk acceptability: Whether risk meets the applicable acceptance criteria. / protective measure: A safeguard intended to reduce exposure or its consequences. / inherent safety: Safety achieved through the design itself. / information for safety: Warnings or instructions intended to support risk reduction. / benefit-risk analysis: Evaluation of relevant benefits against remaining risks. / risk management file: The organized records of risk-management activities and results. / foreseeable misuse: Incorrect use that can reasonably be anticipated. / normal condition: Operation without a fault being present. / fault condition: A state in which a component or function has failed. / control effectiveness: The demonstrated ability of a measure to reduce the identified risk. / newly introduced risk: A risk created or changed by a design or control modification. / risk estimate: An assessment of harm probability and severity. / objective evidence: Verifiable information supporting a conclusion.
Speaking task: Read the risk review. Name the hot surface, prolonged contact, and possible burn as source, exposure, and harm. Swap roles. Keep the cover proposed and its effect unverified; do not use complaint absence as a probability estimate. Read the corrected sharp-edge transfer. Distinguish the redesign proposal from evidence of control effectiveness.
Partner: Elena: Risk engineer / Sam: Mechanical lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional handle may have a sharp edge. Hand contact could cause a cut. A rounded redesign is proposed but has not been evaluated.
Model for comparison AFTER my attempt, not a response to give me first: Sam: I will change the status to evidence incomplete and retain the proposed cover as an action for engineering review. We also need the criterion behind any acceptance decision.
Elena: Yes, document the applicable risk acceptability criteria. The reviewer needs the reasoning and evidence, not simply a low label attached to an unfinished analysis.
Sam: I will separate the hot surface, prolonged contact, and possible burn in the record. Send me the evidence needed before we can judge the proposed cover.
Elena: That gives the next review useful objective evidence to request and evaluate. We can make progress on the concern without converting a proposal into a completed safety conclusion.
END REFERENCE
END PROMPT

Lesson 02 · Risk Management and Hazard Analysis | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 02: Risk Management and Hazard Analysis
Original fictional case: Risk engineer Elena and mechanical lead Sam review a fictional enclosure-heating concern. The worksheet labels skin burn as the hazard and says low risk because no complaints have been received. The team has identified a potentially hot accessible surface, possible prolonged contact, and possible skin injury. No likelihood estimate or verified control result is supplied. An insulating cover is only a proposal. Their task is to correct the chain of reasoning without deciding that the device is safe.
Language workshop: The hot surface is not the injury
Communication goal: Separate a hazard, an exposure situation, possible harm, and the evidence for a risk-control claim.
Language guidance: Hazard, hazardous situation, and harm are not interchangeable. In this case, the potentially hot surface is the source; prolonged contact describes exposure; a burn is the possible injury. These distinctions clarify the analysis without supplying a likelihood estimate.
Useful expressions (preserve the supplied facts): The accessible hot surface is the potential source of harm. / Prolonged contact is the exposure situation we need to examine. / A skin burn is the possible harm, not the source. / Severity and probability answer different questions. / What evidence supports this likelihood estimate? / No complaints received does not establish zero risk. / The cover is a candidate protective measure. / We have not yet verified the control's effectiveness. / Which sequence could lead from this condition to injury? / The current record does not support the low-risk conclusion. / Could the proposed cover introduce another risk? / We cannot describe post-control risk before assessing the implemented measure. / Which acceptability criteria are being applied? / Connect the analysis, control, verification, and review decision. / This review does not establish that every risk has been eliminated. / Assign the missing evidence to an owner before the next review.
Vocabulary: hazard: A potential source of injury or other harm. / harm: Injury or damage to health, property, or the environment. / hazardous situation: Circumstances in which people or other protected things are exposed to a hazard. / sequence of events: The linked events that can lead to exposure and harm. / severity: The degree of possible harm. / probability of harm: The likelihood that the specified harm will occur. / risk: The combination of the probability of harm and its severity. / risk analysis: Systematic identification of hazards and estimation of associated risks. / risk evaluation: Comparing estimated risk with established acceptability criteria. / risk control: A measure intended to reduce risk. / residual risk: Risk remaining after risk-control measures have been implemented. / risk acceptability: Whether risk meets the applicable acceptance criteria. / protective measure: A safeguard intended to reduce exposure or its consequences. / inherent safety: Safety achieved through the design itself. / information for safety: Warnings or instructions intended to support risk reduction. / benefit-risk analysis: Evaluation of relevant benefits against remaining risks. / risk management file: The organized records of risk-management activities and results. / foreseeable misuse: Incorrect use that can reasonably be anticipated. / normal condition: Operation without a fault being present. / fault condition: A state in which a component or function has failed. / control effectiveness: The demonstrated ability of a measure to reduce the identified risk. / newly introduced risk: A risk created or changed by a design or control modification. / risk estimate: An assessment of harm probability and severity. / objective evidence: Verifiable information supporting a conclusion.
Speaking task: Read the risk review. Name the hot surface, prolonged contact, and possible burn as source, exposure, and harm. Swap roles. Keep the cover proposed and its effect unverified; do not use complaint absence as a probability estimate. Read the corrected sharp-edge transfer. Distinguish the redesign proposal from evidence of control effectiveness.
Partner: Elena: Risk engineer / Sam: Mechanical lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional handle may have a sharp edge. Hand contact could cause a cut. A rounded redesign is proposed but has not been evaluated.
Model for comparison AFTER my attempt, not a response to give me first: Sam: I will change the status to evidence incomplete and retain the proposed cover as an action for engineering review. We also need the criterion behind any acceptance decision.
Elena: Yes, document the applicable risk acceptability criteria. The reviewer needs the reasoning and evidence, not simply a low label attached to an unfinished analysis.
Sam: I will separate the hot surface, prolonged contact, and possible burn in the record. Send me the evidence needed before we can judge the proposed cover.
Elena: That gives the next review useful objective evidence to request and evaluate. We can make progress on the concern without converting a proposal into a completed safety conclusion.
END REFERENCE
END PROMPT

Lesson 02 · Risk Management and Hazard Analysis | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 02: Risk Management and Hazard Analysis
Original fictional case: Risk engineer Elena and mechanical lead Sam review a fictional enclosure-heating concern. The worksheet labels skin burn as the hazard and says low risk because no complaints have been received. The team has identified a potentially hot accessible surface, possible prolonged contact, and possible skin injury. No likelihood estimate or verified control result is supplied. An insulating cover is only a proposal. Their task is to correct the chain of reasoning without deciding that the device is safe.
Language workshop: The hot surface is not the injury
Communication goal: Separate a hazard, an exposure situation, possible harm, and the evidence for a risk-control claim.
Language guidance: Hazard, hazardous situation, and harm are not interchangeable. In this case, the potentially hot surface is the source; prolonged contact describes exposure; a burn is the possible injury. These distinctions clarify the analysis without supplying a likelihood estimate.
Useful expressions (preserve the supplied facts): The accessible hot surface is the potential source of harm. / Prolonged contact is the exposure situation we need to examine. / A skin burn is the possible harm, not the source. / Severity and probability answer different questions. / What evidence supports this likelihood estimate? / No complaints received does not establish zero risk. / The cover is a candidate protective measure. / We have not yet verified the control's effectiveness. / Which sequence could lead from this condition to injury? / The current record does not support the low-risk conclusion. / Could the proposed cover introduce another risk? / We cannot describe post-control risk before assessing the implemented measure. / Which acceptability criteria are being applied? / Connect the analysis, control, verification, and review decision. / This review does not establish that every risk has been eliminated. / Assign the missing evidence to an owner before the next review.
Vocabulary: hazard: A potential source of injury or other harm. / harm: Injury or damage to health, property, or the environment. / hazardous situation: Circumstances in which people or other protected things are exposed to a hazard. / sequence of events: The linked events that can lead to exposure and harm. / severity: The degree of possible harm. / probability of harm: The likelihood that the specified harm will occur. / risk: The combination of the probability of harm and its severity. / risk analysis: Systematic identification of hazards and estimation of associated risks. / risk evaluation: Comparing estimated risk with established acceptability criteria. / risk control: A measure intended to reduce risk. / residual risk: Risk remaining after risk-control measures have been implemented. / risk acceptability: Whether risk meets the applicable acceptance criteria. / protective measure: A safeguard intended to reduce exposure or its consequences. / inherent safety: Safety achieved through the design itself. / information for safety: Warnings or instructions intended to support risk reduction. / benefit-risk analysis: Evaluation of relevant benefits against remaining risks. / risk management file: The organized records of risk-management activities and results. / foreseeable misuse: Incorrect use that can reasonably be anticipated. / normal condition: Operation without a fault being present. / fault condition: A state in which a component or function has failed. / control effectiveness: The demonstrated ability of a measure to reduce the identified risk. / newly introduced risk: A risk created or changed by a design or control modification. / risk estimate: An assessment of harm probability and severity. / objective evidence: Verifiable information supporting a conclusion.
Speaking task: Read the risk review. Name the hot surface, prolonged contact, and possible burn as source, exposure, and harm. Swap roles. Keep the cover proposed and its effect unverified; do not use complaint absence as a probability estimate. Read the corrected sharp-edge transfer. Distinguish the redesign proposal from evidence of control effectiveness.
Partner: Elena: Risk engineer / Sam: Mechanical lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional handle may have a sharp edge. Hand contact could cause a cut. A rounded redesign is proposed but has not been evaluated.
Model for comparison AFTER my attempt, not a response to give me first: Sam: I will change the status to evidence incomplete and retain the proposed cover as an action for engineering review. We also need the criterion behind any acceptance decision.
Elena: Yes, document the applicable risk acceptability criteria. The reviewer needs the reasoning and evidence, not simply a low label attached to an unfinished analysis.
Sam: I will separate the hot surface, prolonged contact, and possible burn in the record. Send me the evidence needed before we can judge the proposed cover.
Elena: That gives the next review useful objective evidence to request and evaluate. We can make progress on the concern without converting a proposal into a completed safety conclusion.
END REFERENCE
END PROMPT

Lesson 03 · Verification, Validation, and Design Review | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 03: Verification, Validation, and Design Review
Original fictional case: Verification lead Arun and development manager Beth review the status of a fictional device. All twelve planned specification checks in the current package passed. The separate intended-user evaluation has not started. The slide nevertheless says validation complete and ready for release. No release authorization is supplied. A review meeting is scheduled tomorrow. Arun and Beth must present the completed evidence, the unperformed work, and the decision still required without treating the meeting itself as approval.
Language workshop: Twelve checks passed, one evaluation still open
Communication goal: Report completed specification checks without implying that intended-use evaluation or release authorization is complete.
Language guidance: The twelve checks support the specified requirements they address, in the tested configuration. They do not automatically cover every user need, later version, or intended-use condition. Report completion at the level supported by the actual evidence.
Useful expressions (preserve the supplied facts): All twelve checks in this specification package passed. / That result applies to the tested configuration and covered requirements. / The intended-user evaluation has not started. / Replace validation complete with specification checks complete. / Which requirement does this result address? / Were any departures from the protocol assessed and documented? / A passed test package is not release authorization. / The review is scheduled; its conclusion is not yet available. / Assign an owner and closure evidence for each open item. / Confirm that the report covers the version presented for review. / What supports the representativeness of this test article? / A later modification needs an impact assessment before relying on these results. / We have not demonstrated every intended-use requirement. / The review package should show completed evidence and unresolved work separately. / Capture the actual decision and any conditions after the review. / Ready for review does not mean ready for release.
Vocabulary: verification: Confirmation with evidence that specified requirements have been fulfilled. / validation: Confirmation with evidence that requirements for an intended use are fulfilled. / design review: A systematic evaluation of design progress, evidence, and issues. / test protocol: A documented plan describing how a test will be performed and assessed. / test report: A record of test execution, results, and conclusions. / test article: The item or configuration used in a test. / configuration: The defined arrangement and versions of a product's elements. / requirement coverage: The extent to which requirements are addressed by specified evidence. / traceability matrix: A structured table linking requirements to related evidence. / test deviation: A departure from the planned test method or conditions. / unresolved anomaly: An observed irregularity whose significance or resolution remains open. / acceptance result: The recorded outcome against a specified acceptance criterion. / representativeness: How well an item or setting reflects the intended evaluated population or use. / simulated use: Evaluation under conditions designed to represent actual use. / review action: A task assigned as a result of a review. / action closure: Documented completion and acceptance of an assigned task. / release authorization: A formal decision permitting a product or version to be released. / design transfer: Translation of the design into production specifications and processes. / document control: Management of document versions, approval, and availability. / change impact: The consequences of a proposed or implemented alteration. / regression testing: Rechecking affected behavior after a change. / evidence package: The organized records supporting a specific conclusion or decision. / review quorum: The required participation for a particular review under its procedure. / decision record: A documented conclusion, rationale, and associated conditions.
Speaking task: Read the review exchange. State twelve passed specification checks and the intended-user evaluation not started. Swap roles. Distinguish the tested configuration, tomorrow's review, and the release decision still unmade. Read the corrected version-B transfer. Friday remains a review date, not evidence that release is authorized.
Partner: Arun: Verification lead / Beth: Development manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Six specification checks passed on version B. The intended-use evaluation is pending, and a review is booked for Friday. No release decision has been made.
Model for comparison AFTER my attempt, not a response to give me first: Beth: Tomorrow, each unresolved item needs an owner. But the minutes should not show those items as closed simply because someone agrees to take responsibility.
Arun: Yes. Action closure needs the required evidence and acceptance. Ownership makes follow-up possible; it does not demonstrate that the remaining task has already been completed.
Beth: I will separate the twelve passed checks from the unstarted user evaluation. Please confirm the tested build and keep release authorization off the slide until it exists.
Arun: After the meeting, add the actual decision record and its conditions. That keeps completed testing, open evaluation, review conclusions, and release status distinct throughout the handoff.
END REFERENCE
END PROMPT

Lesson 03 · Verification, Validation, and Design Review | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 03: Verification, Validation, and Design Review
Original fictional case: Verification lead Arun and development manager Beth review the status of a fictional device. All twelve planned specification checks in the current package passed. The separate intended-user evaluation has not started. The slide nevertheless says validation complete and ready for release. No release authorization is supplied. A review meeting is scheduled tomorrow. Arun and Beth must present the completed evidence, the unperformed work, and the decision still required without treating the meeting itself as approval.
Language workshop: Twelve checks passed, one evaluation still open
Communication goal: Report completed specification checks without implying that intended-use evaluation or release authorization is complete.
Language guidance: The twelve checks support the specified requirements they address, in the tested configuration. They do not automatically cover every user need, later version, or intended-use condition. Report completion at the level supported by the actual evidence.
Useful expressions (preserve the supplied facts): All twelve checks in this specification package passed. / That result applies to the tested configuration and covered requirements. / The intended-user evaluation has not started. / Replace validation complete with specification checks complete. / Which requirement does this result address? / Were any departures from the protocol assessed and documented? / A passed test package is not release authorization. / The review is scheduled; its conclusion is not yet available. / Assign an owner and closure evidence for each open item. / Confirm that the report covers the version presented for review. / What supports the representativeness of this test article? / A later modification needs an impact assessment before relying on these results. / We have not demonstrated every intended-use requirement. / The review package should show completed evidence and unresolved work separately. / Capture the actual decision and any conditions after the review. / Ready for review does not mean ready for release.
Vocabulary: verification: Confirmation with evidence that specified requirements have been fulfilled. / validation: Confirmation with evidence that requirements for an intended use are fulfilled. / design review: A systematic evaluation of design progress, evidence, and issues. / test protocol: A documented plan describing how a test will be performed and assessed. / test report: A record of test execution, results, and conclusions. / test article: The item or configuration used in a test. / configuration: The defined arrangement and versions of a product's elements. / requirement coverage: The extent to which requirements are addressed by specified evidence. / traceability matrix: A structured table linking requirements to related evidence. / test deviation: A departure from the planned test method or conditions. / unresolved anomaly: An observed irregularity whose significance or resolution remains open. / acceptance result: The recorded outcome against a specified acceptance criterion. / representativeness: How well an item or setting reflects the intended evaluated population or use. / simulated use: Evaluation under conditions designed to represent actual use. / review action: A task assigned as a result of a review. / action closure: Documented completion and acceptance of an assigned task. / release authorization: A formal decision permitting a product or version to be released. / design transfer: Translation of the design into production specifications and processes. / document control: Management of document versions, approval, and availability. / change impact: The consequences of a proposed or implemented alteration. / regression testing: Rechecking affected behavior after a change. / evidence package: The organized records supporting a specific conclusion or decision. / review quorum: The required participation for a particular review under its procedure. / decision record: A documented conclusion, rationale, and associated conditions.
Speaking task: Read the review exchange. State twelve passed specification checks and the intended-user evaluation not started. Swap roles. Distinguish the tested configuration, tomorrow's review, and the release decision still unmade. Read the corrected version-B transfer. Friday remains a review date, not evidence that release is authorized.
Partner: Arun: Verification lead / Beth: Development manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Six specification checks passed on version B. The intended-use evaluation is pending, and a review is booked for Friday. No release decision has been made.
Model for comparison AFTER my attempt, not a response to give me first: Beth: Tomorrow, each unresolved item needs an owner. But the minutes should not show those items as closed simply because someone agrees to take responsibility.
Arun: Yes. Action closure needs the required evidence and acceptance. Ownership makes follow-up possible; it does not demonstrate that the remaining task has already been completed.
Beth: I will separate the twelve passed checks from the unstarted user evaluation. Please confirm the tested build and keep release authorization off the slide until it exists.
Arun: After the meeting, add the actual decision record and its conditions. That keeps completed testing, open evaluation, review conclusions, and release status distinct throughout the handoff.
END REFERENCE
END PROMPT

Lesson 03 · Verification, Validation, and Design Review | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 03: Verification, Validation, and Design Review
Original fictional case: Verification lead Arun and development manager Beth review the status of a fictional device. All twelve planned specification checks in the current package passed. The separate intended-user evaluation has not started. The slide nevertheless says validation complete and ready for release. No release authorization is supplied. A review meeting is scheduled tomorrow. Arun and Beth must present the completed evidence, the unperformed work, and the decision still required without treating the meeting itself as approval.
Language workshop: Twelve checks passed, one evaluation still open
Communication goal: Report completed specification checks without implying that intended-use evaluation or release authorization is complete.
Language guidance: The twelve checks support the specified requirements they address, in the tested configuration. They do not automatically cover every user need, later version, or intended-use condition. Report completion at the level supported by the actual evidence.
Useful expressions (preserve the supplied facts): All twelve checks in this specification package passed. / That result applies to the tested configuration and covered requirements. / The intended-user evaluation has not started. / Replace validation complete with specification checks complete. / Which requirement does this result address? / Were any departures from the protocol assessed and documented? / A passed test package is not release authorization. / The review is scheduled; its conclusion is not yet available. / Assign an owner and closure evidence for each open item. / Confirm that the report covers the version presented for review. / What supports the representativeness of this test article? / A later modification needs an impact assessment before relying on these results. / We have not demonstrated every intended-use requirement. / The review package should show completed evidence and unresolved work separately. / Capture the actual decision and any conditions after the review. / Ready for review does not mean ready for release.
Vocabulary: verification: Confirmation with evidence that specified requirements have been fulfilled. / validation: Confirmation with evidence that requirements for an intended use are fulfilled. / design review: A systematic evaluation of design progress, evidence, and issues. / test protocol: A documented plan describing how a test will be performed and assessed. / test report: A record of test execution, results, and conclusions. / test article: The item or configuration used in a test. / configuration: The defined arrangement and versions of a product's elements. / requirement coverage: The extent to which requirements are addressed by specified evidence. / traceability matrix: A structured table linking requirements to related evidence. / test deviation: A departure from the planned test method or conditions. / unresolved anomaly: An observed irregularity whose significance or resolution remains open. / acceptance result: The recorded outcome against a specified acceptance criterion. / representativeness: How well an item or setting reflects the intended evaluated population or use. / simulated use: Evaluation under conditions designed to represent actual use. / review action: A task assigned as a result of a review. / action closure: Documented completion and acceptance of an assigned task. / release authorization: A formal decision permitting a product or version to be released. / design transfer: Translation of the design into production specifications and processes. / document control: Management of document versions, approval, and availability. / change impact: The consequences of a proposed or implemented alteration. / regression testing: Rechecking affected behavior after a change. / evidence package: The organized records supporting a specific conclusion or decision. / review quorum: The required participation for a particular review under its procedure. / decision record: A documented conclusion, rationale, and associated conditions.
Speaking task: Read the review exchange. State twelve passed specification checks and the intended-user evaluation not started. Swap roles. Distinguish the tested configuration, tomorrow's review, and the release decision still unmade. Read the corrected version-B transfer. Friday remains a review date, not evidence that release is authorized.
Partner: Arun: Verification lead / Beth: Development manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Six specification checks passed on version B. The intended-use evaluation is pending, and a review is booked for Friday. No release decision has been made.
Model for comparison AFTER my attempt, not a response to give me first: Beth: Tomorrow, each unresolved item needs an owner. But the minutes should not show those items as closed simply because someone agrees to take responsibility.
Arun: Yes. Action closure needs the required evidence and acceptance. Ownership makes follow-up possible; it does not demonstrate that the remaining task has already been completed.
Beth: I will separate the twelve passed checks from the unstarted user evaluation. Please confirm the tested build and keep release authorization off the slide until it exists.
Arun: After the meeting, add the actual decision record and its conditions. That keeps completed testing, open evaluation, review conclusions, and release status distinct throughout the handoff.
END REFERENCE
END PROMPT

Lesson 03 · Verification, Validation, and Design Review | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 03: Verification, Validation, and Design Review
Original fictional case: Verification lead Arun and development manager Beth review the status of a fictional device. All twelve planned specification checks in the current package passed. The separate intended-user evaluation has not started. The slide nevertheless says validation complete and ready for release. No release authorization is supplied. A review meeting is scheduled tomorrow. Arun and Beth must present the completed evidence, the unperformed work, and the decision still required without treating the meeting itself as approval.
Language workshop: Twelve checks passed, one evaluation still open
Communication goal: Report completed specification checks without implying that intended-use evaluation or release authorization is complete.
Language guidance: The twelve checks support the specified requirements they address, in the tested configuration. They do not automatically cover every user need, later version, or intended-use condition. Report completion at the level supported by the actual evidence.
Useful expressions (preserve the supplied facts): All twelve checks in this specification package passed. / That result applies to the tested configuration and covered requirements. / The intended-user evaluation has not started. / Replace validation complete with specification checks complete. / Which requirement does this result address? / Were any departures from the protocol assessed and documented? / A passed test package is not release authorization. / The review is scheduled; its conclusion is not yet available. / Assign an owner and closure evidence for each open item. / Confirm that the report covers the version presented for review. / What supports the representativeness of this test article? / A later modification needs an impact assessment before relying on these results. / We have not demonstrated every intended-use requirement. / The review package should show completed evidence and unresolved work separately. / Capture the actual decision and any conditions after the review. / Ready for review does not mean ready for release.
Vocabulary: verification: Confirmation with evidence that specified requirements have been fulfilled. / validation: Confirmation with evidence that requirements for an intended use are fulfilled. / design review: A systematic evaluation of design progress, evidence, and issues. / test protocol: A documented plan describing how a test will be performed and assessed. / test report: A record of test execution, results, and conclusions. / test article: The item or configuration used in a test. / configuration: The defined arrangement and versions of a product's elements. / requirement coverage: The extent to which requirements are addressed by specified evidence. / traceability matrix: A structured table linking requirements to related evidence. / test deviation: A departure from the planned test method or conditions. / unresolved anomaly: An observed irregularity whose significance or resolution remains open. / acceptance result: The recorded outcome against a specified acceptance criterion. / representativeness: How well an item or setting reflects the intended evaluated population or use. / simulated use: Evaluation under conditions designed to represent actual use. / review action: A task assigned as a result of a review. / action closure: Documented completion and acceptance of an assigned task. / release authorization: A formal decision permitting a product or version to be released. / design transfer: Translation of the design into production specifications and processes. / document control: Management of document versions, approval, and availability. / change impact: The consequences of a proposed or implemented alteration. / regression testing: Rechecking affected behavior after a change. / evidence package: The organized records supporting a specific conclusion or decision. / review quorum: The required participation for a particular review under its procedure. / decision record: A documented conclusion, rationale, and associated conditions.
Speaking task: Read the review exchange. State twelve passed specification checks and the intended-user evaluation not started. Swap roles. Distinguish the tested configuration, tomorrow's review, and the release decision still unmade. Read the corrected version-B transfer. Friday remains a review date, not evidence that release is authorized.
Partner: Arun: Verification lead / Beth: Development manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Six specification checks passed on version B. The intended-use evaluation is pending, and a review is booked for Friday. No release decision has been made.
Model for comparison AFTER my attempt, not a response to give me first: Beth: Tomorrow, each unresolved item needs an owner. But the minutes should not show those items as closed simply because someone agrees to take responsibility.
Arun: Yes. Action closure needs the required evidence and acceptance. Ownership makes follow-up possible; it does not demonstrate that the remaining task has already been completed.
Beth: I will separate the twelve passed checks from the unstarted user evaluation. Please confirm the tested build and keep release authorization off the slide until it exists.
Arun: After the meeting, add the actual decision record and its conditions. That keeps completed testing, open evaluation, review conclusions, and release status distinct throughout the handoff.
END REFERENCE
END PROMPT

Lesson 04 · Usability and Human Factors | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 04: Usability and Human Factors
Original fictional case: Human-factors specialist Laila and interface designer Victor review a formative study of a fictional device label. Three of eight participants selected the wrong status label during a simulated task. The draft summary calls them careless and concludes that a larger font will solve the problem. No revised label has been tested, and the study does not establish a population error rate. Laila and Victor must preserve the observation, investigate the interface, and describe the proposed revision without declaring success.
Language workshop: Three participants read the label differently
Communication goal: Report observed use difficulties neutrally and distinguish exploratory findings from validation or population-level rates.
Language guidance: Three of eight is 37.5% of this study group, not an established error rate for the user population. Report the count and study context. A formative finding can identify a design concern without providing a final validation conclusion.
Useful expressions (preserve the supplied facts): Three of eight participants selected the wrong status label. / This occurred in the simulated task used in the formative study. / The notes do not establish that the participants were careless. / The selection is observed; the reason still needs investigation. / Did participants distinguish the meanings of the two labels? / Was the relevant text readily legible under the study conditions? / Record whether the moderator prompted the participant. / That percentage describes this study group, not the user population. / A larger font is proposed but has not been evaluated. / We cannot yet say the change resolves the problem. / Font size, wording, and hierarchy are different possible contributors. / Retain the observation notes when revising the summary. / Assess the task's safety significance through the appropriate process. / These formative findings inform development; they are not a completed validation claim. / Evaluate the revised label against the specific difficulty observed. / State the finding, the open explanation, and the next evaluation separately.
Vocabulary: human factors: Study and application of how people interact with systems and products. / usability engineering: A structured approach to evaluating and improving user interaction. / formative evaluation: An exploratory assessment used to inform design development. / summative evaluation: An assessment of a sufficiently developed design against defined evaluation goals. / human-factors validation: Evaluation of intended users performing relevant tasks under representative conditions. / critical task: A task whose error or omission could seriously harm a patient or user, including compromised care. / use error: An action or omission producing a result different from that intended or expected. / close call: A situation in which a problem nearly occurs but is avoided. / use difficulty: Observed trouble completing or understanding a task. / participant: A person taking part in a study. / moderator: The person guiding a study session under its protocol. / prompting: Assistance that may influence a participant's performance. / task success: Completion of a defined task under stated evaluation criteria. / observation note: A factual record of behavior or events during a study. / root-cause analysis: Investigation of underlying contributors to an observed problem. / mental model: A user's understanding of how a system works. / affordance: A feature suggesting how an object or control can be used. / label comprehension: Understanding the meaning conveyed by a label. / visual hierarchy: The arrangement that makes some information more prominent than other information. / legibility: How readily individual text or symbols can be distinguished. / cognitive load: The mental effort needed to process information and perform a task. / training decay: Loss of retained training knowledge or skill over time. / representative sample: A participant group suited to the intended study population and question. / design iteration: A revised version created through successive development cycles.
Speaking task: Read the formative-study discussion. State three of eight wrong selections and distinguish behavior from an inferred cause. Swap roles. Contrast readable text with understood meaning and assisted completion with unassisted performance. Read the corrected two-of-ten transfer. Keep the revised wording untested and the comprehension issue unresolved.
Partner: Laila: Human-factors specialist / Victor: Interface designer
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: Two of ten participants read a label accurately but misunderstand its meaning in a formative session. Revised wording is proposed and has not been tested.
Model for comparison AFTER my attempt, not a response to give me first: Victor: Then I should not describe this as our final usability validation either. We used the session to find weaknesses while the interface was still developing.
Laila: Correct. Completed human-factors validation is not established by a formative session and an untested revision. State the evaluation stage and conditions clearly.
Victor: I will retain the three-of-eight count, the reading-versus-meaning observation, and the assisted completion. Proposed changes will sit in a separate section.
Laila: That gives the root-cause analysis useful evidence. We can investigate the difficulty without blaming participants or promising that one easy design change resolves it.
END REFERENCE
END PROMPT

Lesson 04 · Usability and Human Factors | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 04: Usability and Human Factors
Original fictional case: Human-factors specialist Laila and interface designer Victor review a formative study of a fictional device label. Three of eight participants selected the wrong status label during a simulated task. The draft summary calls them careless and concludes that a larger font will solve the problem. No revised label has been tested, and the study does not establish a population error rate. Laila and Victor must preserve the observation, investigate the interface, and describe the proposed revision without declaring success.
Language workshop: Three participants read the label differently
Communication goal: Report observed use difficulties neutrally and distinguish exploratory findings from validation or population-level rates.
Language guidance: Three of eight is 37.5% of this study group, not an established error rate for the user population. Report the count and study context. A formative finding can identify a design concern without providing a final validation conclusion.
Useful expressions (preserve the supplied facts): Three of eight participants selected the wrong status label. / This occurred in the simulated task used in the formative study. / The notes do not establish that the participants were careless. / The selection is observed; the reason still needs investigation. / Did participants distinguish the meanings of the two labels? / Was the relevant text readily legible under the study conditions? / Record whether the moderator prompted the participant. / That percentage describes this study group, not the user population. / A larger font is proposed but has not been evaluated. / We cannot yet say the change resolves the problem. / Font size, wording, and hierarchy are different possible contributors. / Retain the observation notes when revising the summary. / Assess the task's safety significance through the appropriate process. / These formative findings inform development; they are not a completed validation claim. / Evaluate the revised label against the specific difficulty observed. / State the finding, the open explanation, and the next evaluation separately.
Vocabulary: human factors: Study and application of how people interact with systems and products. / usability engineering: A structured approach to evaluating and improving user interaction. / formative evaluation: An exploratory assessment used to inform design development. / summative evaluation: An assessment of a sufficiently developed design against defined evaluation goals. / human-factors validation: Evaluation of intended users performing relevant tasks under representative conditions. / critical task: A task whose error or omission could seriously harm a patient or user, including compromised care. / use error: An action or omission producing a result different from that intended or expected. / close call: A situation in which a problem nearly occurs but is avoided. / use difficulty: Observed trouble completing or understanding a task. / participant: A person taking part in a study. / moderator: The person guiding a study session under its protocol. / prompting: Assistance that may influence a participant's performance. / task success: Completion of a defined task under stated evaluation criteria. / observation note: A factual record of behavior or events during a study. / root-cause analysis: Investigation of underlying contributors to an observed problem. / mental model: A user's understanding of how a system works. / affordance: A feature suggesting how an object or control can be used. / label comprehension: Understanding the meaning conveyed by a label. / visual hierarchy: The arrangement that makes some information more prominent than other information. / legibility: How readily individual text or symbols can be distinguished. / cognitive load: The mental effort needed to process information and perform a task. / training decay: Loss of retained training knowledge or skill over time. / representative sample: A participant group suited to the intended study population and question. / design iteration: A revised version created through successive development cycles.
Speaking task: Read the formative-study discussion. State three of eight wrong selections and distinguish behavior from an inferred cause. Swap roles. Contrast readable text with understood meaning and assisted completion with unassisted performance. Read the corrected two-of-ten transfer. Keep the revised wording untested and the comprehension issue unresolved.
Partner: Laila: Human-factors specialist / Victor: Interface designer
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: Two of ten participants read a label accurately but misunderstand its meaning in a formative session. Revised wording is proposed and has not been tested.
Model for comparison AFTER my attempt, not a response to give me first: Victor: Then I should not describe this as our final usability validation either. We used the session to find weaknesses while the interface was still developing.
Laila: Correct. Completed human-factors validation is not established by a formative session and an untested revision. State the evaluation stage and conditions clearly.
Victor: I will retain the three-of-eight count, the reading-versus-meaning observation, and the assisted completion. Proposed changes will sit in a separate section.
Laila: That gives the root-cause analysis useful evidence. We can investigate the difficulty without blaming participants or promising that one easy design change resolves it.
END REFERENCE
END PROMPT

Lesson 04 · Usability and Human Factors | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 04: Usability and Human Factors
Original fictional case: Human-factors specialist Laila and interface designer Victor review a formative study of a fictional device label. Three of eight participants selected the wrong status label during a simulated task. The draft summary calls them careless and concludes that a larger font will solve the problem. No revised label has been tested, and the study does not establish a population error rate. Laila and Victor must preserve the observation, investigate the interface, and describe the proposed revision without declaring success.
Language workshop: Three participants read the label differently
Communication goal: Report observed use difficulties neutrally and distinguish exploratory findings from validation or population-level rates.
Language guidance: Three of eight is 37.5% of this study group, not an established error rate for the user population. Report the count and study context. A formative finding can identify a design concern without providing a final validation conclusion.
Useful expressions (preserve the supplied facts): Three of eight participants selected the wrong status label. / This occurred in the simulated task used in the formative study. / The notes do not establish that the participants were careless. / The selection is observed; the reason still needs investigation. / Did participants distinguish the meanings of the two labels? / Was the relevant text readily legible under the study conditions? / Record whether the moderator prompted the participant. / That percentage describes this study group, not the user population. / A larger font is proposed but has not been evaluated. / We cannot yet say the change resolves the problem. / Font size, wording, and hierarchy are different possible contributors. / Retain the observation notes when revising the summary. / Assess the task's safety significance through the appropriate process. / These formative findings inform development; they are not a completed validation claim. / Evaluate the revised label against the specific difficulty observed. / State the finding, the open explanation, and the next evaluation separately.
Vocabulary: human factors: Study and application of how people interact with systems and products. / usability engineering: A structured approach to evaluating and improving user interaction. / formative evaluation: An exploratory assessment used to inform design development. / summative evaluation: An assessment of a sufficiently developed design against defined evaluation goals. / human-factors validation: Evaluation of intended users performing relevant tasks under representative conditions. / critical task: A task whose error or omission could seriously harm a patient or user, including compromised care. / use error: An action or omission producing a result different from that intended or expected. / close call: A situation in which a problem nearly occurs but is avoided. / use difficulty: Observed trouble completing or understanding a task. / participant: A person taking part in a study. / moderator: The person guiding a study session under its protocol. / prompting: Assistance that may influence a participant's performance. / task success: Completion of a defined task under stated evaluation criteria. / observation note: A factual record of behavior or events during a study. / root-cause analysis: Investigation of underlying contributors to an observed problem. / mental model: A user's understanding of how a system works. / affordance: A feature suggesting how an object or control can be used. / label comprehension: Understanding the meaning conveyed by a label. / visual hierarchy: The arrangement that makes some information more prominent than other information. / legibility: How readily individual text or symbols can be distinguished. / cognitive load: The mental effort needed to process information and perform a task. / training decay: Loss of retained training knowledge or skill over time. / representative sample: A participant group suited to the intended study population and question. / design iteration: A revised version created through successive development cycles.
Speaking task: Read the formative-study discussion. State three of eight wrong selections and distinguish behavior from an inferred cause. Swap roles. Contrast readable text with understood meaning and assisted completion with unassisted performance. Read the corrected two-of-ten transfer. Keep the revised wording untested and the comprehension issue unresolved.
Partner: Laila: Human-factors specialist / Victor: Interface designer
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: Two of ten participants read a label accurately but misunderstand its meaning in a formative session. Revised wording is proposed and has not been tested.
Model for comparison AFTER my attempt, not a response to give me first: Victor: Then I should not describe this as our final usability validation either. We used the session to find weaknesses while the interface was still developing.
Laila: Correct. Completed human-factors validation is not established by a formative session and an untested revision. State the evaluation stage and conditions clearly.
Victor: I will retain the three-of-eight count, the reading-versus-meaning observation, and the assisted completion. Proposed changes will sit in a separate section.
Laila: That gives the root-cause analysis useful evidence. We can investigate the difficulty without blaming participants or promising that one easy design change resolves it.
END REFERENCE
END PROMPT

Lesson 04 · Usability and Human Factors | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 04: Usability and Human Factors
Original fictional case: Human-factors specialist Laila and interface designer Victor review a formative study of a fictional device label. Three of eight participants selected the wrong status label during a simulated task. The draft summary calls them careless and concludes that a larger font will solve the problem. No revised label has been tested, and the study does not establish a population error rate. Laila and Victor must preserve the observation, investigate the interface, and describe the proposed revision without declaring success.
Language workshop: Three participants read the label differently
Communication goal: Report observed use difficulties neutrally and distinguish exploratory findings from validation or population-level rates.
Language guidance: Three of eight is 37.5% of this study group, not an established error rate for the user population. Report the count and study context. A formative finding can identify a design concern without providing a final validation conclusion.
Useful expressions (preserve the supplied facts): Three of eight participants selected the wrong status label. / This occurred in the simulated task used in the formative study. / The notes do not establish that the participants were careless. / The selection is observed; the reason still needs investigation. / Did participants distinguish the meanings of the two labels? / Was the relevant text readily legible under the study conditions? / Record whether the moderator prompted the participant. / That percentage describes this study group, not the user population. / A larger font is proposed but has not been evaluated. / We cannot yet say the change resolves the problem. / Font size, wording, and hierarchy are different possible contributors. / Retain the observation notes when revising the summary. / Assess the task's safety significance through the appropriate process. / These formative findings inform development; they are not a completed validation claim. / Evaluate the revised label against the specific difficulty observed. / State the finding, the open explanation, and the next evaluation separately.
Vocabulary: human factors: Study and application of how people interact with systems and products. / usability engineering: A structured approach to evaluating and improving user interaction. / formative evaluation: An exploratory assessment used to inform design development. / summative evaluation: An assessment of a sufficiently developed design against defined evaluation goals. / human-factors validation: Evaluation of intended users performing relevant tasks under representative conditions. / critical task: A task whose error or omission could seriously harm a patient or user, including compromised care. / use error: An action or omission producing a result different from that intended or expected. / close call: A situation in which a problem nearly occurs but is avoided. / use difficulty: Observed trouble completing or understanding a task. / participant: A person taking part in a study. / moderator: The person guiding a study session under its protocol. / prompting: Assistance that may influence a participant's performance. / task success: Completion of a defined task under stated evaluation criteria. / observation note: A factual record of behavior or events during a study. / root-cause analysis: Investigation of underlying contributors to an observed problem. / mental model: A user's understanding of how a system works. / affordance: A feature suggesting how an object or control can be used. / label comprehension: Understanding the meaning conveyed by a label. / visual hierarchy: The arrangement that makes some information more prominent than other information. / legibility: How readily individual text or symbols can be distinguished. / cognitive load: The mental effort needed to process information and perform a task. / training decay: Loss of retained training knowledge or skill over time. / representative sample: A participant group suited to the intended study population and question. / design iteration: A revised version created through successive development cycles.
Speaking task: Read the formative-study discussion. State three of eight wrong selections and distinguish behavior from an inferred cause. Swap roles. Contrast readable text with understood meaning and assisted completion with unassisted performance. Read the corrected two-of-ten transfer. Keep the revised wording untested and the comprehension issue unresolved.
Partner: Laila: Human-factors specialist / Victor: Interface designer
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: Two of ten participants read a label accurately but misunderstand its meaning in a formative session. Revised wording is proposed and has not been tested.
Model for comparison AFTER my attempt, not a response to give me first: Victor: Then I should not describe this as our final usability validation either. We used the session to find weaknesses while the interface was still developing.
Laila: Correct. Completed human-factors validation is not established by a formative session and an untested revision. State the evaluation stage and conditions clearly.
Victor: I will retain the three-of-eight count, the reading-versus-meaning observation, and the assisted completion. Proposed changes will sit in a separate section.
Laila: That gives the root-cause analysis useful evidence. We can investigate the difficulty without blaming participants or promising that one easy design change resolves it.
END REFERENCE
END PROMPT

Lesson 05 · Regulatory Pathways and Submissions | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 05: Regulatory Pathways and Submissions
Original fictional case: Regulatory specialist Inez and commercial director Caleb review a fictional US launch plan. The team is evaluating a possible 510(k) pathway and has identified a candidate predicate, but its suitability is still under review. No submission has been filed and no FDA decision exists. A sales slide says FDA approved and promises an October launch. Inez must correct both the status and the certainty of the timeline while preserving a clear planning discussion.
Language workshop: A route under review is not a clearance
Communication goal: Distinguish a proposed US submission pathway, supporting evidence, and an actual regulatory decision.
Language guidance: For a US 510(k), clearance is the relevant decision term; it should not be casually called PMA approval. A candidate predicate, a pathway assessment, a submitted file, and an agency decision are four different statuses.
Useful expressions (preserve the supplied facts): We are evaluating a possible 510(k) pathway. / The predicate candidate remains under review. / No FDA decision has been issued for this device. / The submission has not yet been filed. / A favorable 510(k) determination is clearance, not PMA approval. / Similar appearance alone does not establish substantial equivalence. / The proposed indications must be consistent across the evidence and materials. / October is a planning assumption, not an authorized launch date. / The pathway assessment and evidence requirements remain unresolved. / An open assessment does not mean the device has been rejected. / Regulatory needs to assess the proposed use and comparison. / A pre-submission discussion is not a marketing authorization. / Replace FDA approved with the actual development status. / Use the exact decision and scope when an authorization exists. / The next step is the pathway assessment, not a launch announcement. / We can plan around dependencies without promising the agency's decision.
Vocabulary: regulatory pathway: The applicable route for obtaining a required regulatory decision. / device classification: A regulatory category reflecting the device type and applicable controls. / product code: A code used by FDA to identify a device type. / 510(k): A US premarket notification seeking a substantial-equivalence determination. / predicate device: A legally marketed comparator used in a 510(k) assessment. / substantial equivalence: The comparative regulatory determination central to a 510(k) decision. / De Novo request: A US request for risk-based classification of a novel eligible device. / premarket approval: The US PMA pathway requiring an independent safety-and-effectiveness demonstration. / clearance: A favorable 510(k) determination permitting marketing within its scope. / approval: A formal favorable decision under an applicable approval pathway. / indications for use: The specific purposes and population described for a device's use. / technological characteristics: Design and operating features relevant to a regulatory comparison. / general controls: Baseline regulatory controls applicable to medical devices. / special controls: Additional controls applicable to certain device types. / submission dossier: The organized documents and evidence submitted for regulatory review. / evidence plan: A plan for generating and organizing support for specified claims. / regulatory strategy: A coordinated approach to regulatory requirements and decisions. / pre-submission interaction: A planned exchange with FDA before a later submission. / review question: A request for clarification or evidence during review. / deficiency: A shortcoming identified in the submitted information. / response package: Documents addressing specified reviewer questions or deficiencies. / marketing authorization: The applicable permission to market a device within a defined scope. / regulatory dependency: An unresolved regulatory matter affecting another planned step. / launch assumption: A planning premise underlying the proposed market-entry date.
Speaking task: Read the launch discussion. Distinguish pathway assessment, candidate predicate, filing, and an actual agency decision. Swap roles. Use clearance for the 510(k) outcome and describe October as an internal conditional target. Read the corrected filing transfer. A filed submission with ongoing review is not a granted clearance.
Partner: Inez: Regulatory specialist / Caleb: Commercial director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional US 510(k) submission has been filed. Review is ongoing, and no decision has been issued. The commercial team has an internal target date.
Model for comparison AFTER my attempt, not a response to give me first: Caleb: We may seek feedback before filing. I will make sure the team does not describe a discussion with the agency as permission to market the device.
Inez: Correct. A pre-submission interaction is not the marketing decision. Any feedback and its scope should be recorded accurately without converting it into blanket approval.
Caleb: I will remove FDA approved and mark October as conditional. Send me the pathway-assessment milestone and its dependencies for the planning slide.
Inez: Good. The communication must distinguish planning from marketing authorization. We can describe the work confidently while leaving the unresolved regulatory decision exactly where it belongs.
END REFERENCE
END PROMPT

Lesson 05 · Regulatory Pathways and Submissions | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 05: Regulatory Pathways and Submissions
Original fictional case: Regulatory specialist Inez and commercial director Caleb review a fictional US launch plan. The team is evaluating a possible 510(k) pathway and has identified a candidate predicate, but its suitability is still under review. No submission has been filed and no FDA decision exists. A sales slide says FDA approved and promises an October launch. Inez must correct both the status and the certainty of the timeline while preserving a clear planning discussion.
Language workshop: A route under review is not a clearance
Communication goal: Distinguish a proposed US submission pathway, supporting evidence, and an actual regulatory decision.
Language guidance: For a US 510(k), clearance is the relevant decision term; it should not be casually called PMA approval. A candidate predicate, a pathway assessment, a submitted file, and an agency decision are four different statuses.
Useful expressions (preserve the supplied facts): We are evaluating a possible 510(k) pathway. / The predicate candidate remains under review. / No FDA decision has been issued for this device. / The submission has not yet been filed. / A favorable 510(k) determination is clearance, not PMA approval. / Similar appearance alone does not establish substantial equivalence. / The proposed indications must be consistent across the evidence and materials. / October is a planning assumption, not an authorized launch date. / The pathway assessment and evidence requirements remain unresolved. / An open assessment does not mean the device has been rejected. / Regulatory needs to assess the proposed use and comparison. / A pre-submission discussion is not a marketing authorization. / Replace FDA approved with the actual development status. / Use the exact decision and scope when an authorization exists. / The next step is the pathway assessment, not a launch announcement. / We can plan around dependencies without promising the agency's decision.
Vocabulary: regulatory pathway: The applicable route for obtaining a required regulatory decision. / device classification: A regulatory category reflecting the device type and applicable controls. / product code: A code used by FDA to identify a device type. / 510(k): A US premarket notification seeking a substantial-equivalence determination. / predicate device: A legally marketed comparator used in a 510(k) assessment. / substantial equivalence: The comparative regulatory determination central to a 510(k) decision. / De Novo request: A US request for risk-based classification of a novel eligible device. / premarket approval: The US PMA pathway requiring an independent safety-and-effectiveness demonstration. / clearance: A favorable 510(k) determination permitting marketing within its scope. / approval: A formal favorable decision under an applicable approval pathway. / indications for use: The specific purposes and population described for a device's use. / technological characteristics: Design and operating features relevant to a regulatory comparison. / general controls: Baseline regulatory controls applicable to medical devices. / special controls: Additional controls applicable to certain device types. / submission dossier: The organized documents and evidence submitted for regulatory review. / evidence plan: A plan for generating and organizing support for specified claims. / regulatory strategy: A coordinated approach to regulatory requirements and decisions. / pre-submission interaction: A planned exchange with FDA before a later submission. / review question: A request for clarification or evidence during review. / deficiency: A shortcoming identified in the submitted information. / response package: Documents addressing specified reviewer questions or deficiencies. / marketing authorization: The applicable permission to market a device within a defined scope. / regulatory dependency: An unresolved regulatory matter affecting another planned step. / launch assumption: A planning premise underlying the proposed market-entry date.
Speaking task: Read the launch discussion. Distinguish pathway assessment, candidate predicate, filing, and an actual agency decision. Swap roles. Use clearance for the 510(k) outcome and describe October as an internal conditional target. Read the corrected filing transfer. A filed submission with ongoing review is not a granted clearance.
Partner: Inez: Regulatory specialist / Caleb: Commercial director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional US 510(k) submission has been filed. Review is ongoing, and no decision has been issued. The commercial team has an internal target date.
Model for comparison AFTER my attempt, not a response to give me first: Caleb: We may seek feedback before filing. I will make sure the team does not describe a discussion with the agency as permission to market the device.
Inez: Correct. A pre-submission interaction is not the marketing decision. Any feedback and its scope should be recorded accurately without converting it into blanket approval.
Caleb: I will remove FDA approved and mark October as conditional. Send me the pathway-assessment milestone and its dependencies for the planning slide.
Inez: Good. The communication must distinguish planning from marketing authorization. We can describe the work confidently while leaving the unresolved regulatory decision exactly where it belongs.
END REFERENCE
END PROMPT

Lesson 05 · Regulatory Pathways and Submissions | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 05: Regulatory Pathways and Submissions
Original fictional case: Regulatory specialist Inez and commercial director Caleb review a fictional US launch plan. The team is evaluating a possible 510(k) pathway and has identified a candidate predicate, but its suitability is still under review. No submission has been filed and no FDA decision exists. A sales slide says FDA approved and promises an October launch. Inez must correct both the status and the certainty of the timeline while preserving a clear planning discussion.
Language workshop: A route under review is not a clearance
Communication goal: Distinguish a proposed US submission pathway, supporting evidence, and an actual regulatory decision.
Language guidance: For a US 510(k), clearance is the relevant decision term; it should not be casually called PMA approval. A candidate predicate, a pathway assessment, a submitted file, and an agency decision are four different statuses.
Useful expressions (preserve the supplied facts): We are evaluating a possible 510(k) pathway. / The predicate candidate remains under review. / No FDA decision has been issued for this device. / The submission has not yet been filed. / A favorable 510(k) determination is clearance, not PMA approval. / Similar appearance alone does not establish substantial equivalence. / The proposed indications must be consistent across the evidence and materials. / October is a planning assumption, not an authorized launch date. / The pathway assessment and evidence requirements remain unresolved. / An open assessment does not mean the device has been rejected. / Regulatory needs to assess the proposed use and comparison. / A pre-submission discussion is not a marketing authorization. / Replace FDA approved with the actual development status. / Use the exact decision and scope when an authorization exists. / The next step is the pathway assessment, not a launch announcement. / We can plan around dependencies without promising the agency's decision.
Vocabulary: regulatory pathway: The applicable route for obtaining a required regulatory decision. / device classification: A regulatory category reflecting the device type and applicable controls. / product code: A code used by FDA to identify a device type. / 510(k): A US premarket notification seeking a substantial-equivalence determination. / predicate device: A legally marketed comparator used in a 510(k) assessment. / substantial equivalence: The comparative regulatory determination central to a 510(k) decision. / De Novo request: A US request for risk-based classification of a novel eligible device. / premarket approval: The US PMA pathway requiring an independent safety-and-effectiveness demonstration. / clearance: A favorable 510(k) determination permitting marketing within its scope. / approval: A formal favorable decision under an applicable approval pathway. / indications for use: The specific purposes and population described for a device's use. / technological characteristics: Design and operating features relevant to a regulatory comparison. / general controls: Baseline regulatory controls applicable to medical devices. / special controls: Additional controls applicable to certain device types. / submission dossier: The organized documents and evidence submitted for regulatory review. / evidence plan: A plan for generating and organizing support for specified claims. / regulatory strategy: A coordinated approach to regulatory requirements and decisions. / pre-submission interaction: A planned exchange with FDA before a later submission. / review question: A request for clarification or evidence during review. / deficiency: A shortcoming identified in the submitted information. / response package: Documents addressing specified reviewer questions or deficiencies. / marketing authorization: The applicable permission to market a device within a defined scope. / regulatory dependency: An unresolved regulatory matter affecting another planned step. / launch assumption: A planning premise underlying the proposed market-entry date.
Speaking task: Read the launch discussion. Distinguish pathway assessment, candidate predicate, filing, and an actual agency decision. Swap roles. Use clearance for the 510(k) outcome and describe October as an internal conditional target. Read the corrected filing transfer. A filed submission with ongoing review is not a granted clearance.
Partner: Inez: Regulatory specialist / Caleb: Commercial director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional US 510(k) submission has been filed. Review is ongoing, and no decision has been issued. The commercial team has an internal target date.
Model for comparison AFTER my attempt, not a response to give me first: Caleb: We may seek feedback before filing. I will make sure the team does not describe a discussion with the agency as permission to market the device.
Inez: Correct. A pre-submission interaction is not the marketing decision. Any feedback and its scope should be recorded accurately without converting it into blanket approval.
Caleb: I will remove FDA approved and mark October as conditional. Send me the pathway-assessment milestone and its dependencies for the planning slide.
Inez: Good. The communication must distinguish planning from marketing authorization. We can describe the work confidently while leaving the unresolved regulatory decision exactly where it belongs.
END REFERENCE
END PROMPT

Lesson 05 · Regulatory Pathways and Submissions | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 05: Regulatory Pathways and Submissions
Original fictional case: Regulatory specialist Inez and commercial director Caleb review a fictional US launch plan. The team is evaluating a possible 510(k) pathway and has identified a candidate predicate, but its suitability is still under review. No submission has been filed and no FDA decision exists. A sales slide says FDA approved and promises an October launch. Inez must correct both the status and the certainty of the timeline while preserving a clear planning discussion.
Language workshop: A route under review is not a clearance
Communication goal: Distinguish a proposed US submission pathway, supporting evidence, and an actual regulatory decision.
Language guidance: For a US 510(k), clearance is the relevant decision term; it should not be casually called PMA approval. A candidate predicate, a pathway assessment, a submitted file, and an agency decision are four different statuses.
Useful expressions (preserve the supplied facts): We are evaluating a possible 510(k) pathway. / The predicate candidate remains under review. / No FDA decision has been issued for this device. / The submission has not yet been filed. / A favorable 510(k) determination is clearance, not PMA approval. / Similar appearance alone does not establish substantial equivalence. / The proposed indications must be consistent across the evidence and materials. / October is a planning assumption, not an authorized launch date. / The pathway assessment and evidence requirements remain unresolved. / An open assessment does not mean the device has been rejected. / Regulatory needs to assess the proposed use and comparison. / A pre-submission discussion is not a marketing authorization. / Replace FDA approved with the actual development status. / Use the exact decision and scope when an authorization exists. / The next step is the pathway assessment, not a launch announcement. / We can plan around dependencies without promising the agency's decision.
Vocabulary: regulatory pathway: The applicable route for obtaining a required regulatory decision. / device classification: A regulatory category reflecting the device type and applicable controls. / product code: A code used by FDA to identify a device type. / 510(k): A US premarket notification seeking a substantial-equivalence determination. / predicate device: A legally marketed comparator used in a 510(k) assessment. / substantial equivalence: The comparative regulatory determination central to a 510(k) decision. / De Novo request: A US request for risk-based classification of a novel eligible device. / premarket approval: The US PMA pathway requiring an independent safety-and-effectiveness demonstration. / clearance: A favorable 510(k) determination permitting marketing within its scope. / approval: A formal favorable decision under an applicable approval pathway. / indications for use: The specific purposes and population described for a device's use. / technological characteristics: Design and operating features relevant to a regulatory comparison. / general controls: Baseline regulatory controls applicable to medical devices. / special controls: Additional controls applicable to certain device types. / submission dossier: The organized documents and evidence submitted for regulatory review. / evidence plan: A plan for generating and organizing support for specified claims. / regulatory strategy: A coordinated approach to regulatory requirements and decisions. / pre-submission interaction: A planned exchange with FDA before a later submission. / review question: A request for clarification or evidence during review. / deficiency: A shortcoming identified in the submitted information. / response package: Documents addressing specified reviewer questions or deficiencies. / marketing authorization: The applicable permission to market a device within a defined scope. / regulatory dependency: An unresolved regulatory matter affecting another planned step. / launch assumption: A planning premise underlying the proposed market-entry date.
Speaking task: Read the launch discussion. Distinguish pathway assessment, candidate predicate, filing, and an actual agency decision. Swap roles. Use clearance for the 510(k) outcome and describe October as an internal conditional target. Read the corrected filing transfer. A filed submission with ongoing review is not a granted clearance.
Partner: Inez: Regulatory specialist / Caleb: Commercial director
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A fictional US 510(k) submission has been filed. Review is ongoing, and no decision has been issued. The commercial team has an internal target date.
Model for comparison AFTER my attempt, not a response to give me first: Caleb: We may seek feedback before filing. I will make sure the team does not describe a discussion with the agency as permission to market the device.
Inez: Correct. A pre-submission interaction is not the marketing decision. Any feedback and its scope should be recorded accurately without converting it into blanket approval.
Caleb: I will remove FDA approved and mark October as conditional. Send me the pathway-assessment milestone and its dependencies for the planning slide.
Inez: Good. The communication must distinguish planning from marketing authorization. We can describe the work confidently while leaving the unresolved regulatory decision exactly where it belongs.
END REFERENCE
END PROMPT

Lesson 06 · Complaints, MDRs, and Postmarket Signals | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 06: Complaints, MDRs, and Postmarket Signals
Original fictional case: Complaint specialist Nora and service lead Dev review a caller's report that a fictional monitor unexpectedly stopped displaying. The event date, device identifier, and patient outcome are not yet known. The call was received today at 14:10. Dev proposes waiting for every field before routing it. A separate dashboard shows eight complaints this quarter versus four last quarter, without use-volume data. Nora must preserve the unknowns, arrange the required internal review, and prevent either dataset from implying an unsupported conclusion.
Language workshop: Incomplete information still needs a handoff
Communication goal: Capture a complaint accurately, route missing information promptly, and distinguish counts from rates and reports from causation.
Language guidance: The receipt time is not the event time. Unknown patient outcome is not the same as no injury. Preserve the reporter's account and route the available information through the applicable process while actively seeking missing facts.
Useful expressions (preserve the supplied facts): The caller reported that the display stopped unexpectedly. / The call was received today; the event date is still unknown. / We have not yet confirmed the device identifier. / Patient outcome has not been established. / This report does not by itself establish the cause. / Send the available information for prompt internal assessment. / Record the questions asked and the attempts to obtain missing information. / Reportability needs assessment under the applicable requirements. / Missing fields do not justify withholding the initial internal handoff. / We need the relevant exposure data before describing a rate. / The count increased from four to eight. / Confirm whether separate records describe the same event. / An incomplete account still needs appropriate review. / Keep the initial narrative alongside later clarifications. / New required information must follow the applicable reporting process. / The case is routed, follow-up is open, and no cause is confirmed.
Vocabulary: complaint: A reported concern about a device's quality, performance, safety, or related service. / adverse event: An unfavorable occurrence that may require assessment of its relationship to a device. / malfunction: A failure to perform as intended or meet relevant performance specifications. / Medical Device Reporting: The US system for reporting specified device events under applicable requirements. / reportability: Whether an event meets applicable reporting requirements. / initial reporter: The person or organization first providing event information. / awareness date: The date relevant event information becomes known for the applicable assessment. / event date: The date on which the reported occurrence took place. / receipt date: The date the organization received the communication. / Unique Device Identifier: A device-identification code with defined identification components. / serial number: An identifier distinguishing an individual unit. / lot number: An identifier linking items to a production batch. / patient outcome: The reported effect on the patient's condition or health. / causal relationship: A supported connection between a device and an observed event. / event narrative: A factual account of the reported occurrence and its context. / reasonably known information: Information available or obtainable as defined by the applicable reporting requirement. / follow-up attempt: A documented effort to obtain missing or clarifying information. / supplemental report: A later report providing required additional information. / postmarket surveillance: Systematic collection and review of information after market introduction. / safety signal: Information suggesting a potential safety issue that needs assessment. / trend analysis: Review of patterns in data over time. / exposure denominator: The relevant use or exposure quantity against which events are compared. / duplicate report: Another record potentially describing an already reported event. / complaint closure: Documented completion of the required complaint-review process.
Speaking task: Read the intake exchange. Route the account and confirm receipt before discussing missing details; preserve 14:10 as call receipt. Swap roles. Say outcome unknown rather than no injury, and doubled count rather than doubled use-based rate. Read the corrected six-complaint transfer. Keep event date unknown and the exposure denominator unavailable.
Partner: Nora: Complaint specialist / Dev: Service lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A caller reports a device issue today. The event date and outcome are unknown. Six complaints were recorded this month, but the number of uses is unavailable.
Model for comparison AFTER my attempt, not a response to give me first: Dev: Some records might refer to the same occurrence. We should check that before treating every entry as a separate event or comparing the clinical outcomes.
Nora: Yes, assess each possible duplicate report while preserving the source information. Deduplication needs a basis; a similar description alone should not make us erase a separate event.
Dev: The account is routed and you have confirmed receipt. I will correct the unknown fields and retain eight versus four complaints without inventing a rate or injury outcome.
Nora: Good. Any required later information must follow the applicable supplemental report process. Keep investigation, reporting assessment, and complaint closure distinct so the record never suggests an unfinished task has already been completed.
END REFERENCE
END PROMPT

Lesson 06 · Complaints, MDRs, and Postmarket Signals | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 06: Complaints, MDRs, and Postmarket Signals
Original fictional case: Complaint specialist Nora and service lead Dev review a caller's report that a fictional monitor unexpectedly stopped displaying. The event date, device identifier, and patient outcome are not yet known. The call was received today at 14:10. Dev proposes waiting for every field before routing it. A separate dashboard shows eight complaints this quarter versus four last quarter, without use-volume data. Nora must preserve the unknowns, arrange the required internal review, and prevent either dataset from implying an unsupported conclusion.
Language workshop: Incomplete information still needs a handoff
Communication goal: Capture a complaint accurately, route missing information promptly, and distinguish counts from rates and reports from causation.
Language guidance: The receipt time is not the event time. Unknown patient outcome is not the same as no injury. Preserve the reporter's account and route the available information through the applicable process while actively seeking missing facts.
Useful expressions (preserve the supplied facts): The caller reported that the display stopped unexpectedly. / The call was received today; the event date is still unknown. / We have not yet confirmed the device identifier. / Patient outcome has not been established. / This report does not by itself establish the cause. / Send the available information for prompt internal assessment. / Record the questions asked and the attempts to obtain missing information. / Reportability needs assessment under the applicable requirements. / Missing fields do not justify withholding the initial internal handoff. / We need the relevant exposure data before describing a rate. / The count increased from four to eight. / Confirm whether separate records describe the same event. / An incomplete account still needs appropriate review. / Keep the initial narrative alongside later clarifications. / New required information must follow the applicable reporting process. / The case is routed, follow-up is open, and no cause is confirmed.
Vocabulary: complaint: A reported concern about a device's quality, performance, safety, or related service. / adverse event: An unfavorable occurrence that may require assessment of its relationship to a device. / malfunction: A failure to perform as intended or meet relevant performance specifications. / Medical Device Reporting: The US system for reporting specified device events under applicable requirements. / reportability: Whether an event meets applicable reporting requirements. / initial reporter: The person or organization first providing event information. / awareness date: The date relevant event information becomes known for the applicable assessment. / event date: The date on which the reported occurrence took place. / receipt date: The date the organization received the communication. / Unique Device Identifier: A device-identification code with defined identification components. / serial number: An identifier distinguishing an individual unit. / lot number: An identifier linking items to a production batch. / patient outcome: The reported effect on the patient's condition or health. / causal relationship: A supported connection between a device and an observed event. / event narrative: A factual account of the reported occurrence and its context. / reasonably known information: Information available or obtainable as defined by the applicable reporting requirement. / follow-up attempt: A documented effort to obtain missing or clarifying information. / supplemental report: A later report providing required additional information. / postmarket surveillance: Systematic collection and review of information after market introduction. / safety signal: Information suggesting a potential safety issue that needs assessment. / trend analysis: Review of patterns in data over time. / exposure denominator: The relevant use or exposure quantity against which events are compared. / duplicate report: Another record potentially describing an already reported event. / complaint closure: Documented completion of the required complaint-review process.
Speaking task: Read the intake exchange. Route the account and confirm receipt before discussing missing details; preserve 14:10 as call receipt. Swap roles. Say outcome unknown rather than no injury, and doubled count rather than doubled use-based rate. Read the corrected six-complaint transfer. Keep event date unknown and the exposure denominator unavailable.
Partner: Nora: Complaint specialist / Dev: Service lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A caller reports a device issue today. The event date and outcome are unknown. Six complaints were recorded this month, but the number of uses is unavailable.
Model for comparison AFTER my attempt, not a response to give me first: Dev: Some records might refer to the same occurrence. We should check that before treating every entry as a separate event or comparing the clinical outcomes.
Nora: Yes, assess each possible duplicate report while preserving the source information. Deduplication needs a basis; a similar description alone should not make us erase a separate event.
Dev: The account is routed and you have confirmed receipt. I will correct the unknown fields and retain eight versus four complaints without inventing a rate or injury outcome.
Nora: Good. Any required later information must follow the applicable supplemental report process. Keep investigation, reporting assessment, and complaint closure distinct so the record never suggests an unfinished task has already been completed.
END REFERENCE
END PROMPT

Lesson 06 · Complaints, MDRs, and Postmarket Signals | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 06: Complaints, MDRs, and Postmarket Signals
Original fictional case: Complaint specialist Nora and service lead Dev review a caller's report that a fictional monitor unexpectedly stopped displaying. The event date, device identifier, and patient outcome are not yet known. The call was received today at 14:10. Dev proposes waiting for every field before routing it. A separate dashboard shows eight complaints this quarter versus four last quarter, without use-volume data. Nora must preserve the unknowns, arrange the required internal review, and prevent either dataset from implying an unsupported conclusion.
Language workshop: Incomplete information still needs a handoff
Communication goal: Capture a complaint accurately, route missing information promptly, and distinguish counts from rates and reports from causation.
Language guidance: The receipt time is not the event time. Unknown patient outcome is not the same as no injury. Preserve the reporter's account and route the available information through the applicable process while actively seeking missing facts.
Useful expressions (preserve the supplied facts): The caller reported that the display stopped unexpectedly. / The call was received today; the event date is still unknown. / We have not yet confirmed the device identifier. / Patient outcome has not been established. / This report does not by itself establish the cause. / Send the available information for prompt internal assessment. / Record the questions asked and the attempts to obtain missing information. / Reportability needs assessment under the applicable requirements. / Missing fields do not justify withholding the initial internal handoff. / We need the relevant exposure data before describing a rate. / The count increased from four to eight. / Confirm whether separate records describe the same event. / An incomplete account still needs appropriate review. / Keep the initial narrative alongside later clarifications. / New required information must follow the applicable reporting process. / The case is routed, follow-up is open, and no cause is confirmed.
Vocabulary: complaint: A reported concern about a device's quality, performance, safety, or related service. / adverse event: An unfavorable occurrence that may require assessment of its relationship to a device. / malfunction: A failure to perform as intended or meet relevant performance specifications. / Medical Device Reporting: The US system for reporting specified device events under applicable requirements. / reportability: Whether an event meets applicable reporting requirements. / initial reporter: The person or organization first providing event information. / awareness date: The date relevant event information becomes known for the applicable assessment. / event date: The date on which the reported occurrence took place. / receipt date: The date the organization received the communication. / Unique Device Identifier: A device-identification code with defined identification components. / serial number: An identifier distinguishing an individual unit. / lot number: An identifier linking items to a production batch. / patient outcome: The reported effect on the patient's condition or health. / causal relationship: A supported connection between a device and an observed event. / event narrative: A factual account of the reported occurrence and its context. / reasonably known information: Information available or obtainable as defined by the applicable reporting requirement. / follow-up attempt: A documented effort to obtain missing or clarifying information. / supplemental report: A later report providing required additional information. / postmarket surveillance: Systematic collection and review of information after market introduction. / safety signal: Information suggesting a potential safety issue that needs assessment. / trend analysis: Review of patterns in data over time. / exposure denominator: The relevant use or exposure quantity against which events are compared. / duplicate report: Another record potentially describing an already reported event. / complaint closure: Documented completion of the required complaint-review process.
Speaking task: Read the intake exchange. Route the account and confirm receipt before discussing missing details; preserve 14:10 as call receipt. Swap roles. Say outcome unknown rather than no injury, and doubled count rather than doubled use-based rate. Read the corrected six-complaint transfer. Keep event date unknown and the exposure denominator unavailable.
Partner: Nora: Complaint specialist / Dev: Service lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A caller reports a device issue today. The event date and outcome are unknown. Six complaints were recorded this month, but the number of uses is unavailable.
Model for comparison AFTER my attempt, not a response to give me first: Dev: Some records might refer to the same occurrence. We should check that before treating every entry as a separate event or comparing the clinical outcomes.
Nora: Yes, assess each possible duplicate report while preserving the source information. Deduplication needs a basis; a similar description alone should not make us erase a separate event.
Dev: The account is routed and you have confirmed receipt. I will correct the unknown fields and retain eight versus four complaints without inventing a rate or injury outcome.
Nora: Good. Any required later information must follow the applicable supplemental report process. Keep investigation, reporting assessment, and complaint closure distinct so the record never suggests an unfinished task has already been completed.
END REFERENCE
END PROMPT

Lesson 06 · Complaints, MDRs, and Postmarket Signals | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 06: Complaints, MDRs, and Postmarket Signals
Original fictional case: Complaint specialist Nora and service lead Dev review a caller's report that a fictional monitor unexpectedly stopped displaying. The event date, device identifier, and patient outcome are not yet known. The call was received today at 14:10. Dev proposes waiting for every field before routing it. A separate dashboard shows eight complaints this quarter versus four last quarter, without use-volume data. Nora must preserve the unknowns, arrange the required internal review, and prevent either dataset from implying an unsupported conclusion.
Language workshop: Incomplete information still needs a handoff
Communication goal: Capture a complaint accurately, route missing information promptly, and distinguish counts from rates and reports from causation.
Language guidance: The receipt time is not the event time. Unknown patient outcome is not the same as no injury. Preserve the reporter's account and route the available information through the applicable process while actively seeking missing facts.
Useful expressions (preserve the supplied facts): The caller reported that the display stopped unexpectedly. / The call was received today; the event date is still unknown. / We have not yet confirmed the device identifier. / Patient outcome has not been established. / This report does not by itself establish the cause. / Send the available information for prompt internal assessment. / Record the questions asked and the attempts to obtain missing information. / Reportability needs assessment under the applicable requirements. / Missing fields do not justify withholding the initial internal handoff. / We need the relevant exposure data before describing a rate. / The count increased from four to eight. / Confirm whether separate records describe the same event. / An incomplete account still needs appropriate review. / Keep the initial narrative alongside later clarifications. / New required information must follow the applicable reporting process. / The case is routed, follow-up is open, and no cause is confirmed.
Vocabulary: complaint: A reported concern about a device's quality, performance, safety, or related service. / adverse event: An unfavorable occurrence that may require assessment of its relationship to a device. / malfunction: A failure to perform as intended or meet relevant performance specifications. / Medical Device Reporting: The US system for reporting specified device events under applicable requirements. / reportability: Whether an event meets applicable reporting requirements. / initial reporter: The person or organization first providing event information. / awareness date: The date relevant event information becomes known for the applicable assessment. / event date: The date on which the reported occurrence took place. / receipt date: The date the organization received the communication. / Unique Device Identifier: A device-identification code with defined identification components. / serial number: An identifier distinguishing an individual unit. / lot number: An identifier linking items to a production batch. / patient outcome: The reported effect on the patient's condition or health. / causal relationship: A supported connection between a device and an observed event. / event narrative: A factual account of the reported occurrence and its context. / reasonably known information: Information available or obtainable as defined by the applicable reporting requirement. / follow-up attempt: A documented effort to obtain missing or clarifying information. / supplemental report: A later report providing required additional information. / postmarket surveillance: Systematic collection and review of information after market introduction. / safety signal: Information suggesting a potential safety issue that needs assessment. / trend analysis: Review of patterns in data over time. / exposure denominator: The relevant use or exposure quantity against which events are compared. / duplicate report: Another record potentially describing an already reported event. / complaint closure: Documented completion of the required complaint-review process.
Speaking task: Read the intake exchange. Route the account and confirm receipt before discussing missing details; preserve 14:10 as call receipt. Swap roles. Say outcome unknown rather than no injury, and doubled count rather than doubled use-based rate. Read the corrected six-complaint transfer. Keep event date unknown and the exposure denominator unavailable.
Partner: Nora: Complaint specialist / Dev: Service lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A caller reports a device issue today. The event date and outcome are unknown. Six complaints were recorded this month, but the number of uses is unavailable.
Model for comparison AFTER my attempt, not a response to give me first: Dev: Some records might refer to the same occurrence. We should check that before treating every entry as a separate event or comparing the clinical outcomes.
Nora: Yes, assess each possible duplicate report while preserving the source information. Deduplication needs a basis; a similar description alone should not make us erase a separate event.
Dev: The account is routed and you have confirmed receipt. I will correct the unknown fields and retain eight versus four complaints without inventing a rate or injury outcome.
Nora: Good. Any required later information must follow the applicable supplemental report process. Keep investigation, reporting assessment, and complaint closure distinct so the record never suggests an unfinished task has already been completed.
END REFERENCE
END PROMPT

Lesson 07 · Manufacturing, Suppliers, and Nonconformance | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 07: Manufacturing, Suppliers, and Nonconformance
Original fictional case: Quality engineer Tomas and supply planner Grace review two incoming component lots containing 120 and 180 pieces. One sampled piece from each lot failed a specified dimensional check. Both lots are on hold under the fictional site procedure. The cause is not established, and no release or rework disposition is authorized. Production needs parts tomorrow. Grace proposes describing all 300 pieces as defective, then releasing the second lot because its supplier certificate says conforming.
Language workshop: Three hundred pieces on hold
Communication goal: Separate affected-lot scope, observed failures, containment, cause, and authorized disposition in a supplier discussion.
Language guidance: The held population is 300 pieces. The supplied observation is two failed sampled pieces, one from each lot. Do not call all 300 individually confirmed defective, or treat uninspected pieces as conforming. The hold and the observed failures describe different scopes.
Useful expressions (preserve the supplied facts): Both lots are on hold, totaling 300 pieces. / One sampled piece from each lot failed the dimensional check. / We have not inspected and confirmed every piece as defective. / The uninspected pieces are not thereby proven conforming. / Reference the specified dimension and applicable tolerance. / No release or rework disposition is authorized. / I understand tomorrow's need; the material status still has to be respected. / The certificate does not erase the failed inspection result. / The hold limits unintended use while the issue is assessed. / The supplier cause has not been established. / Ask for evidence addressing the specified nonconformance. / Fixing a piece and preventing recurrence are different objectives. / Include calibration status and relevant measurement information in the review. / Use lot records to assess what other material may be affected. / Only the designated process can approve the material disposition. / Give production the confirmed status and the next review time, not an assumed release.
Vocabulary: incoming inspection: Examination of received material against specified requirements. / nonconformance: Failure to fulfill a specified requirement. / nonconforming material: Material identified as not meeting a specified requirement. / containment: Immediate action to limit the scope or spread of a problem. / quarantine: Controlled segregation or status preventing unintended use. / disposition: An authorized decision on how identified material will be handled. / rework: Action intended to bring nonconforming product into conformity. / scrap: Material designated not to be used for its intended production purpose. / concession: An authorized permission to use or release specified nonconforming product under defined conditions. / certificate of conformity: A supplier statement that supplied material meets specified requirements. / supplier corrective action request: A formal request for a supplier to address a quality problem. / corrective action: Action addressing the cause of a nonconformity to prevent recurrence. / correction: Action addressing a detected nonconformity itself. / CAPA: Corrective and preventive action within a quality-system process. / lot genealogy: Records linking material lots through production and distribution. / acceptance sampling: Evaluation of a lot using a defined sample and decision plan. / dimensional tolerance: The permitted variation in a specified measurement. / measurement uncertainty: The quantified uncertainty associated with a measurement result. / calibration status: Whether a measuring instrument's calibration requirements are satisfied. / supplier qualification: Evaluation and approval of a supplier for a defined purpose. / change notification: Communication of a proposed or implemented change affecting supply. / release status: The current authorization state for using or distributing material. / Quality Management System Regulation: The current US device quality-system regulation, commonly called QMSR. / ISO 13485: An international standard for medical-device quality management systems.
Speaking task: Read the supplier exchange. State 120 plus 180 equals 300 held, with two observed sampled failures. Swap roles. Keep both lots held, cause open, and release or rework unapproved despite the certificate and deadline. Read the corrected ninety-piece transfer. Distinguish ninety held from two sampled failures and a disposition still required.
Partner: Tomas: Quality engineer / Grace: Supply planner
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 lot contains 90 pieces. Two sampled pieces failed a check. The whole lot is held, and no rework or release is authorized.
Model for comparison AFTER my attempt, not a response to give me first: Grace: Once a cause is supported, I will ask what action addresses it and how effectiveness will be checked. A promise about future lots is not enough.
Tomas: That is the purpose of corrective action. Distinguish the action against recurrence from replacing a piece or maintaining the current hold.
Grace: For now: three hundred held, two sampled failures, cause open, no release or rework authorized. I will send that exact status to production.
Tomas: Use lot genealogy to check whether other material may be involved. Keep any wider scope qualified until the records support it.
END REFERENCE
END PROMPT

Lesson 07 · Manufacturing, Suppliers, and Nonconformance | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 07: Manufacturing, Suppliers, and Nonconformance
Original fictional case: Quality engineer Tomas and supply planner Grace review two incoming component lots containing 120 and 180 pieces. One sampled piece from each lot failed a specified dimensional check. Both lots are on hold under the fictional site procedure. The cause is not established, and no release or rework disposition is authorized. Production needs parts tomorrow. Grace proposes describing all 300 pieces as defective, then releasing the second lot because its supplier certificate says conforming.
Language workshop: Three hundred pieces on hold
Communication goal: Separate affected-lot scope, observed failures, containment, cause, and authorized disposition in a supplier discussion.
Language guidance: The held population is 300 pieces. The supplied observation is two failed sampled pieces, one from each lot. Do not call all 300 individually confirmed defective, or treat uninspected pieces as conforming. The hold and the observed failures describe different scopes.
Useful expressions (preserve the supplied facts): Both lots are on hold, totaling 300 pieces. / One sampled piece from each lot failed the dimensional check. / We have not inspected and confirmed every piece as defective. / The uninspected pieces are not thereby proven conforming. / Reference the specified dimension and applicable tolerance. / No release or rework disposition is authorized. / I understand tomorrow's need; the material status still has to be respected. / The certificate does not erase the failed inspection result. / The hold limits unintended use while the issue is assessed. / The supplier cause has not been established. / Ask for evidence addressing the specified nonconformance. / Fixing a piece and preventing recurrence are different objectives. / Include calibration status and relevant measurement information in the review. / Use lot records to assess what other material may be affected. / Only the designated process can approve the material disposition. / Give production the confirmed status and the next review time, not an assumed release.
Vocabulary: incoming inspection: Examination of received material against specified requirements. / nonconformance: Failure to fulfill a specified requirement. / nonconforming material: Material identified as not meeting a specified requirement. / containment: Immediate action to limit the scope or spread of a problem. / quarantine: Controlled segregation or status preventing unintended use. / disposition: An authorized decision on how identified material will be handled. / rework: Action intended to bring nonconforming product into conformity. / scrap: Material designated not to be used for its intended production purpose. / concession: An authorized permission to use or release specified nonconforming product under defined conditions. / certificate of conformity: A supplier statement that supplied material meets specified requirements. / supplier corrective action request: A formal request for a supplier to address a quality problem. / corrective action: Action addressing the cause of a nonconformity to prevent recurrence. / correction: Action addressing a detected nonconformity itself. / CAPA: Corrective and preventive action within a quality-system process. / lot genealogy: Records linking material lots through production and distribution. / acceptance sampling: Evaluation of a lot using a defined sample and decision plan. / dimensional tolerance: The permitted variation in a specified measurement. / measurement uncertainty: The quantified uncertainty associated with a measurement result. / calibration status: Whether a measuring instrument's calibration requirements are satisfied. / supplier qualification: Evaluation and approval of a supplier for a defined purpose. / change notification: Communication of a proposed or implemented change affecting supply. / release status: The current authorization state for using or distributing material. / Quality Management System Regulation: The current US device quality-system regulation, commonly called QMSR. / ISO 13485: An international standard for medical-device quality management systems.
Speaking task: Read the supplier exchange. State 120 plus 180 equals 300 held, with two observed sampled failures. Swap roles. Keep both lots held, cause open, and release or rework unapproved despite the certificate and deadline. Read the corrected ninety-piece transfer. Distinguish ninety held from two sampled failures and a disposition still required.
Partner: Tomas: Quality engineer / Grace: Supply planner
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 lot contains 90 pieces. Two sampled pieces failed a check. The whole lot is held, and no rework or release is authorized.
Model for comparison AFTER my attempt, not a response to give me first: Grace: Once a cause is supported, I will ask what action addresses it and how effectiveness will be checked. A promise about future lots is not enough.
Tomas: That is the purpose of corrective action. Distinguish the action against recurrence from replacing a piece or maintaining the current hold.
Grace: For now: three hundred held, two sampled failures, cause open, no release or rework authorized. I will send that exact status to production.
Tomas: Use lot genealogy to check whether other material may be involved. Keep any wider scope qualified until the records support it.
END REFERENCE
END PROMPT

Lesson 07 · Manufacturing, Suppliers, and Nonconformance | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 07: Manufacturing, Suppliers, and Nonconformance
Original fictional case: Quality engineer Tomas and supply planner Grace review two incoming component lots containing 120 and 180 pieces. One sampled piece from each lot failed a specified dimensional check. Both lots are on hold under the fictional site procedure. The cause is not established, and no release or rework disposition is authorized. Production needs parts tomorrow. Grace proposes describing all 300 pieces as defective, then releasing the second lot because its supplier certificate says conforming.
Language workshop: Three hundred pieces on hold
Communication goal: Separate affected-lot scope, observed failures, containment, cause, and authorized disposition in a supplier discussion.
Language guidance: The held population is 300 pieces. The supplied observation is two failed sampled pieces, one from each lot. Do not call all 300 individually confirmed defective, or treat uninspected pieces as conforming. The hold and the observed failures describe different scopes.
Useful expressions (preserve the supplied facts): Both lots are on hold, totaling 300 pieces. / One sampled piece from each lot failed the dimensional check. / We have not inspected and confirmed every piece as defective. / The uninspected pieces are not thereby proven conforming. / Reference the specified dimension and applicable tolerance. / No release or rework disposition is authorized. / I understand tomorrow's need; the material status still has to be respected. / The certificate does not erase the failed inspection result. / The hold limits unintended use while the issue is assessed. / The supplier cause has not been established. / Ask for evidence addressing the specified nonconformance. / Fixing a piece and preventing recurrence are different objectives. / Include calibration status and relevant measurement information in the review. / Use lot records to assess what other material may be affected. / Only the designated process can approve the material disposition. / Give production the confirmed status and the next review time, not an assumed release.
Vocabulary: incoming inspection: Examination of received material against specified requirements. / nonconformance: Failure to fulfill a specified requirement. / nonconforming material: Material identified as not meeting a specified requirement. / containment: Immediate action to limit the scope or spread of a problem. / quarantine: Controlled segregation or status preventing unintended use. / disposition: An authorized decision on how identified material will be handled. / rework: Action intended to bring nonconforming product into conformity. / scrap: Material designated not to be used for its intended production purpose. / concession: An authorized permission to use or release specified nonconforming product under defined conditions. / certificate of conformity: A supplier statement that supplied material meets specified requirements. / supplier corrective action request: A formal request for a supplier to address a quality problem. / corrective action: Action addressing the cause of a nonconformity to prevent recurrence. / correction: Action addressing a detected nonconformity itself. / CAPA: Corrective and preventive action within a quality-system process. / lot genealogy: Records linking material lots through production and distribution. / acceptance sampling: Evaluation of a lot using a defined sample and decision plan. / dimensional tolerance: The permitted variation in a specified measurement. / measurement uncertainty: The quantified uncertainty associated with a measurement result. / calibration status: Whether a measuring instrument's calibration requirements are satisfied. / supplier qualification: Evaluation and approval of a supplier for a defined purpose. / change notification: Communication of a proposed or implemented change affecting supply. / release status: The current authorization state for using or distributing material. / Quality Management System Regulation: The current US device quality-system regulation, commonly called QMSR. / ISO 13485: An international standard for medical-device quality management systems.
Speaking task: Read the supplier exchange. State 120 plus 180 equals 300 held, with two observed sampled failures. Swap roles. Keep both lots held, cause open, and release or rework unapproved despite the certificate and deadline. Read the corrected ninety-piece transfer. Distinguish ninety held from two sampled failures and a disposition still required.
Partner: Tomas: Quality engineer / Grace: Supply planner
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 lot contains 90 pieces. Two sampled pieces failed a check. The whole lot is held, and no rework or release is authorized.
Model for comparison AFTER my attempt, not a response to give me first: Grace: Once a cause is supported, I will ask what action addresses it and how effectiveness will be checked. A promise about future lots is not enough.
Tomas: That is the purpose of corrective action. Distinguish the action against recurrence from replacing a piece or maintaining the current hold.
Grace: For now: three hundred held, two sampled failures, cause open, no release or rework authorized. I will send that exact status to production.
Tomas: Use lot genealogy to check whether other material may be involved. Keep any wider scope qualified until the records support it.
END REFERENCE
END PROMPT

Lesson 07 · Manufacturing, Suppliers, and Nonconformance | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 07: Manufacturing, Suppliers, and Nonconformance
Original fictional case: Quality engineer Tomas and supply planner Grace review two incoming component lots containing 120 and 180 pieces. One sampled piece from each lot failed a specified dimensional check. Both lots are on hold under the fictional site procedure. The cause is not established, and no release or rework disposition is authorized. Production needs parts tomorrow. Grace proposes describing all 300 pieces as defective, then releasing the second lot because its supplier certificate says conforming.
Language workshop: Three hundred pieces on hold
Communication goal: Separate affected-lot scope, observed failures, containment, cause, and authorized disposition in a supplier discussion.
Language guidance: The held population is 300 pieces. The supplied observation is two failed sampled pieces, one from each lot. Do not call all 300 individually confirmed defective, or treat uninspected pieces as conforming. The hold and the observed failures describe different scopes.
Useful expressions (preserve the supplied facts): Both lots are on hold, totaling 300 pieces. / One sampled piece from each lot failed the dimensional check. / We have not inspected and confirmed every piece as defective. / The uninspected pieces are not thereby proven conforming. / Reference the specified dimension and applicable tolerance. / No release or rework disposition is authorized. / I understand tomorrow's need; the material status still has to be respected. / The certificate does not erase the failed inspection result. / The hold limits unintended use while the issue is assessed. / The supplier cause has not been established. / Ask for evidence addressing the specified nonconformance. / Fixing a piece and preventing recurrence are different objectives. / Include calibration status and relevant measurement information in the review. / Use lot records to assess what other material may be affected. / Only the designated process can approve the material disposition. / Give production the confirmed status and the next review time, not an assumed release.
Vocabulary: incoming inspection: Examination of received material against specified requirements. / nonconformance: Failure to fulfill a specified requirement. / nonconforming material: Material identified as not meeting a specified requirement. / containment: Immediate action to limit the scope or spread of a problem. / quarantine: Controlled segregation or status preventing unintended use. / disposition: An authorized decision on how identified material will be handled. / rework: Action intended to bring nonconforming product into conformity. / scrap: Material designated not to be used for its intended production purpose. / concession: An authorized permission to use or release specified nonconforming product under defined conditions. / certificate of conformity: A supplier statement that supplied material meets specified requirements. / supplier corrective action request: A formal request for a supplier to address a quality problem. / corrective action: Action addressing the cause of a nonconformity to prevent recurrence. / correction: Action addressing a detected nonconformity itself. / CAPA: Corrective and preventive action within a quality-system process. / lot genealogy: Records linking material lots through production and distribution. / acceptance sampling: Evaluation of a lot using a defined sample and decision plan. / dimensional tolerance: The permitted variation in a specified measurement. / measurement uncertainty: The quantified uncertainty associated with a measurement result. / calibration status: Whether a measuring instrument's calibration requirements are satisfied. / supplier qualification: Evaluation and approval of a supplier for a defined purpose. / change notification: Communication of a proposed or implemented change affecting supply. / release status: The current authorization state for using or distributing material. / Quality Management System Regulation: The current US device quality-system regulation, commonly called QMSR. / ISO 13485: An international standard for medical-device quality management systems.
Speaking task: Read the supplier exchange. State 120 plus 180 equals 300 held, with two observed sampled failures. Swap roles. Keep both lots held, cause open, and release or rework unapproved despite the certificate and deadline. Read the corrected ninety-piece transfer. Distinguish ninety held from two sampled failures and a disposition still required.
Partner: Tomas: Quality engineer / Grace: Supply planner
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 lot contains 90 pieces. Two sampled pieces failed a check. The whole lot is held, and no rework or release is authorized.
Model for comparison AFTER my attempt, not a response to give me first: Grace: Once a cause is supported, I will ask what action addresses it and how effectiveness will be checked. A promise about future lots is not enough.
Tomas: That is the purpose of corrective action. Distinguish the action against recurrence from replacing a piece or maintaining the current hold.
Grace: For now: three hundred held, two sampled failures, cause open, no release or rework authorized. I will send that exact status to production.
Tomas: Use lot genealogy to check whether other material may be involved. Keep any wider scope qualified until the records support it.
END REFERENCE
END PROMPT

Lesson 08 · Clinical Training and Labeling Boundaries | Build vocabulary and collocations

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 08: Clinical Training and Labeling Boundaries
Original fictional case: Clinical trainer Sora is delivering a fictional device session using version 4 of internally approved materials for adult outpatient use. Clinician Alex asks for a pediatric home-use demonstration that the session materials do not cover. A version 3 slide remains in Sora's folder, but its current status has not been checked. No expanded-use authorization or reviewed response is supplied. Sora must acknowledge the question, avoid improvising the requested demonstration, and route it without implying that the clinician's question is improper.
Language workshop: A useful question outside this session
Communication goal: Acknowledge an out-of-scope product-use request, keep the demonstration within authorized materials, and arrange a precise follow-up.
Language guidance: Internally approved training material is not the same thing as a new regulatory authorization. A version number in a folder does not establish that the document is current. Confirm status through the controlled source rather than using an unchecked older slide.
Useful expressions (preserve the supplied facts): That is a specific and useful question about a different population and setting. / Today we are covering adult outpatient use with version 4 materials. / These materials do not cover pediatric home use. / I cannot improvise that demonstration within this session. / The limitation is the scope of my materials, not your ability to ask. / I can document the question for the appropriate reviewed response. / I will preserve the population and setting you asked about. / I need to confirm the current controlled version before using that slide. / Internal material approval does not create an expanded product authorization. / Adding a disclaimer would not resolve the missing reviewed content. / I am not making a patient-specific treatment recommendation. / Session attendance is not the same as a completed competency assessment. / I can confirm that the request was routed; I cannot promise a particular answer. / We will continue with the functions covered by the current session materials. / Please restate which use context today's session covers. / I will follow up through the designated route while we keep this session within scope.
Vocabulary: labeling: Device-related written, printed, or graphic information accompanying or relating to the product. / instructions for use: The device's documented directions and relevant use information. / indication: A specified condition or purpose for which use is described. / contraindication: A circumstance in which the device should not be used. / warning: Information highlighting a significant hazard or safety concern. / precaution: Information about care needed to avoid problems during appropriate use. / training scope: The users, tasks, settings, and content covered by a session. / approved material: Content authorized through the relevant internal review process. / version control: Management of revisions so the appropriate version is used. / obsolete copy: A superseded document that is no longer the current controlled version. / demonstration unit: A device or model designated for showing functions under specified conditions. / simulation: A representation of a task or setting used for training or evaluation. / in-service training: Instruction delivered to professionals in their work context. / competency assessment: Evaluation against defined knowledge or performance criteria. / attendance record: A record that a person participated in a session. / scope boundary: The limit of what a session or role is authorized to cover. / off-label use: Use outside the product's authorized labeling, where that concept applies. / unsolicited question: A question initiated by the recipient rather than prompted by the presenter. / medical information request: A request routed for an appropriate reviewed scientific or product response. / promotional claim: A statement used to encourage product selection or use. / disclaimer: A statement explaining a limitation or qualification. / escalation route: The designated path for a question beyond the current role or scope. / follow-up commitment: A specified promise about the next communication or action. / teach-back: Asking a learner to restate or demonstrate key information to check understanding.
Speaking task: Read the training exchange. Preserve version 4 adult outpatient scope and the specific pediatric home-use question. Swap roles. Route the request without improvising a demonstration or treating the question as improper. Read the corrected referral transfer. Routing for a reviewed response does not authorize the requested use.
Partner: Sora: Clinical trainer / Alex: Clinician attending the session
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 session covers adult clinic use. A participant asks about pediatric home use. No reviewed material for that request is available, and the trainer will route it.
Model for comparison AFTER my attempt, not a response to give me first: Alex: Then competence requires the relevant assessment; a name on the session list does not demonstrate it.
Sora: Correct. A competency assessment has defined criteria. We should describe exactly what was assessed and avoid extending that result to populations or tasks outside the assessment.
Alex: Please route that question and tell me how we will hear back. We can continue with today's adult outpatient material while the separate response is pending.
Sora: I will make that follow-up commitment through the designated process. I can confirm the action and next contact, but I cannot promise that the reviewed response will endorse the requested use.
END REFERENCE
END PROMPT

Lesson 08 · Clinical Training and Labeling Boundaries | Practice grammar in context

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 08: Clinical Training and Labeling Boundaries
Original fictional case: Clinical trainer Sora is delivering a fictional device session using version 4 of internally approved materials for adult outpatient use. Clinician Alex asks for a pediatric home-use demonstration that the session materials do not cover. A version 3 slide remains in Sora's folder, but its current status has not been checked. No expanded-use authorization or reviewed response is supplied. Sora must acknowledge the question, avoid improvising the requested demonstration, and route it without implying that the clinician's question is improper.
Language workshop: A useful question outside this session
Communication goal: Acknowledge an out-of-scope product-use request, keep the demonstration within authorized materials, and arrange a precise follow-up.
Language guidance: Internally approved training material is not the same thing as a new regulatory authorization. A version number in a folder does not establish that the document is current. Confirm status through the controlled source rather than using an unchecked older slide.
Useful expressions (preserve the supplied facts): That is a specific and useful question about a different population and setting. / Today we are covering adult outpatient use with version 4 materials. / These materials do not cover pediatric home use. / I cannot improvise that demonstration within this session. / The limitation is the scope of my materials, not your ability to ask. / I can document the question for the appropriate reviewed response. / I will preserve the population and setting you asked about. / I need to confirm the current controlled version before using that slide. / Internal material approval does not create an expanded product authorization. / Adding a disclaimer would not resolve the missing reviewed content. / I am not making a patient-specific treatment recommendation. / Session attendance is not the same as a completed competency assessment. / I can confirm that the request was routed; I cannot promise a particular answer. / We will continue with the functions covered by the current session materials. / Please restate which use context today's session covers. / I will follow up through the designated route while we keep this session within scope.
Vocabulary: labeling: Device-related written, printed, or graphic information accompanying or relating to the product. / instructions for use: The device's documented directions and relevant use information. / indication: A specified condition or purpose for which use is described. / contraindication: A circumstance in which the device should not be used. / warning: Information highlighting a significant hazard or safety concern. / precaution: Information about care needed to avoid problems during appropriate use. / training scope: The users, tasks, settings, and content covered by a session. / approved material: Content authorized through the relevant internal review process. / version control: Management of revisions so the appropriate version is used. / obsolete copy: A superseded document that is no longer the current controlled version. / demonstration unit: A device or model designated for showing functions under specified conditions. / simulation: A representation of a task or setting used for training or evaluation. / in-service training: Instruction delivered to professionals in their work context. / competency assessment: Evaluation against defined knowledge or performance criteria. / attendance record: A record that a person participated in a session. / scope boundary: The limit of what a session or role is authorized to cover. / off-label use: Use outside the product's authorized labeling, where that concept applies. / unsolicited question: A question initiated by the recipient rather than prompted by the presenter. / medical information request: A request routed for an appropriate reviewed scientific or product response. / promotional claim: A statement used to encourage product selection or use. / disclaimer: A statement explaining a limitation or qualification. / escalation route: The designated path for a question beyond the current role or scope. / follow-up commitment: A specified promise about the next communication or action. / teach-back: Asking a learner to restate or demonstrate key information to check understanding.
Speaking task: Read the training exchange. Preserve version 4 adult outpatient scope and the specific pediatric home-use question. Swap roles. Route the request without improvising a demonstration or treating the question as improper. Read the corrected referral transfer. Routing for a reviewed response does not authorize the requested use.
Partner: Sora: Clinical trainer / Alex: Clinician attending the session
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 session covers adult clinic use. A participant asks about pediatric home use. No reviewed material for that request is available, and the trainer will route it.
Model for comparison AFTER my attempt, not a response to give me first: Alex: Then competence requires the relevant assessment; a name on the session list does not demonstrate it.
Sora: Correct. A competency assessment has defined criteria. We should describe exactly what was assessed and avoid extending that result to populations or tasks outside the assessment.
Alex: Please route that question and tell me how we will hear back. We can continue with today's adult outpatient material while the separate response is pending.
Sora: I will make that follow-up commitment through the designated process. I can confirm the action and next contact, but I cannot promise that the reviewed response will endorse the requested use.
END REFERENCE
END PROMPT

Lesson 08 · Clinical Training and Labeling Boundaries | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 08: Clinical Training and Labeling Boundaries
Original fictional case: Clinical trainer Sora is delivering a fictional device session using version 4 of internally approved materials for adult outpatient use. Clinician Alex asks for a pediatric home-use demonstration that the session materials do not cover. A version 3 slide remains in Sora's folder, but its current status has not been checked. No expanded-use authorization or reviewed response is supplied. Sora must acknowledge the question, avoid improvising the requested demonstration, and route it without implying that the clinician's question is improper.
Language workshop: A useful question outside this session
Communication goal: Acknowledge an out-of-scope product-use request, keep the demonstration within authorized materials, and arrange a precise follow-up.
Language guidance: Internally approved training material is not the same thing as a new regulatory authorization. A version number in a folder does not establish that the document is current. Confirm status through the controlled source rather than using an unchecked older slide.
Useful expressions (preserve the supplied facts): That is a specific and useful question about a different population and setting. / Today we are covering adult outpatient use with version 4 materials. / These materials do not cover pediatric home use. / I cannot improvise that demonstration within this session. / The limitation is the scope of my materials, not your ability to ask. / I can document the question for the appropriate reviewed response. / I will preserve the population and setting you asked about. / I need to confirm the current controlled version before using that slide. / Internal material approval does not create an expanded product authorization. / Adding a disclaimer would not resolve the missing reviewed content. / I am not making a patient-specific treatment recommendation. / Session attendance is not the same as a completed competency assessment. / I can confirm that the request was routed; I cannot promise a particular answer. / We will continue with the functions covered by the current session materials. / Please restate which use context today's session covers. / I will follow up through the designated route while we keep this session within scope.
Vocabulary: labeling: Device-related written, printed, or graphic information accompanying or relating to the product. / instructions for use: The device's documented directions and relevant use information. / indication: A specified condition or purpose for which use is described. / contraindication: A circumstance in which the device should not be used. / warning: Information highlighting a significant hazard or safety concern. / precaution: Information about care needed to avoid problems during appropriate use. / training scope: The users, tasks, settings, and content covered by a session. / approved material: Content authorized through the relevant internal review process. / version control: Management of revisions so the appropriate version is used. / obsolete copy: A superseded document that is no longer the current controlled version. / demonstration unit: A device or model designated for showing functions under specified conditions. / simulation: A representation of a task or setting used for training or evaluation. / in-service training: Instruction delivered to professionals in their work context. / competency assessment: Evaluation against defined knowledge or performance criteria. / attendance record: A record that a person participated in a session. / scope boundary: The limit of what a session or role is authorized to cover. / off-label use: Use outside the product's authorized labeling, where that concept applies. / unsolicited question: A question initiated by the recipient rather than prompted by the presenter. / medical information request: A request routed for an appropriate reviewed scientific or product response. / promotional claim: A statement used to encourage product selection or use. / disclaimer: A statement explaining a limitation or qualification. / escalation route: The designated path for a question beyond the current role or scope. / follow-up commitment: A specified promise about the next communication or action. / teach-back: Asking a learner to restate or demonstrate key information to check understanding.
Speaking task: Read the training exchange. Preserve version 4 adult outpatient scope and the specific pediatric home-use question. Swap roles. Route the request without improvising a demonstration or treating the question as improper. Read the corrected referral transfer. Routing for a reviewed response does not authorize the requested use.
Partner: Sora: Clinical trainer / Alex: Clinician attending the session
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 session covers adult clinic use. A participant asks about pediatric home use. No reviewed material for that request is available, and the trainer will route it.
Model for comparison AFTER my attempt, not a response to give me first: Alex: Then competence requires the relevant assessment; a name on the session list does not demonstrate it.
Sora: Correct. A competency assessment has defined criteria. We should describe exactly what was assessed and avoid extending that result to populations or tasks outside the assessment.
Alex: Please route that question and tell me how we will hear back. We can continue with today's adult outpatient material while the separate response is pending.
Sora: I will make that follow-up commitment through the designated process. I can confirm the action and next contact, but I cannot promise that the reviewed response will endorse the requested use.
END REFERENCE
END PROMPT

Lesson 08 · Clinical Training and Labeling Boundaries | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Lesson 08: Clinical Training and Labeling Boundaries
Original fictional case: Clinical trainer Sora is delivering a fictional device session using version 4 of internally approved materials for adult outpatient use. Clinician Alex asks for a pediatric home-use demonstration that the session materials do not cover. A version 3 slide remains in Sora's folder, but its current status has not been checked. No expanded-use authorization or reviewed response is supplied. Sora must acknowledge the question, avoid improvising the requested demonstration, and route it without implying that the clinician's question is improper.
Language workshop: A useful question outside this session
Communication goal: Acknowledge an out-of-scope product-use request, keep the demonstration within authorized materials, and arrange a precise follow-up.
Language guidance: Internally approved training material is not the same thing as a new regulatory authorization. A version number in a folder does not establish that the document is current. Confirm status through the controlled source rather than using an unchecked older slide.
Useful expressions (preserve the supplied facts): That is a specific and useful question about a different population and setting. / Today we are covering adult outpatient use with version 4 materials. / These materials do not cover pediatric home use. / I cannot improvise that demonstration within this session. / The limitation is the scope of my materials, not your ability to ask. / I can document the question for the appropriate reviewed response. / I will preserve the population and setting you asked about. / I need to confirm the current controlled version before using that slide. / Internal material approval does not create an expanded product authorization. / Adding a disclaimer would not resolve the missing reviewed content. / I am not making a patient-specific treatment recommendation. / Session attendance is not the same as a completed competency assessment. / I can confirm that the request was routed; I cannot promise a particular answer. / We will continue with the functions covered by the current session materials. / Please restate which use context today's session covers. / I will follow up through the designated route while we keep this session within scope.
Vocabulary: labeling: Device-related written, printed, or graphic information accompanying or relating to the product. / instructions for use: The device's documented directions and relevant use information. / indication: A specified condition or purpose for which use is described. / contraindication: A circumstance in which the device should not be used. / warning: Information highlighting a significant hazard or safety concern. / precaution: Information about care needed to avoid problems during appropriate use. / training scope: The users, tasks, settings, and content covered by a session. / approved material: Content authorized through the relevant internal review process. / version control: Management of revisions so the appropriate version is used. / obsolete copy: A superseded document that is no longer the current controlled version. / demonstration unit: A device or model designated for showing functions under specified conditions. / simulation: A representation of a task or setting used for training or evaluation. / in-service training: Instruction delivered to professionals in their work context. / competency assessment: Evaluation against defined knowledge or performance criteria. / attendance record: A record that a person participated in a session. / scope boundary: The limit of what a session or role is authorized to cover. / off-label use: Use outside the product's authorized labeling, where that concept applies. / unsolicited question: A question initiated by the recipient rather than prompted by the presenter. / medical information request: A request routed for an appropriate reviewed scientific or product response. / promotional claim: A statement used to encourage product selection or use. / disclaimer: A statement explaining a limitation or qualification. / escalation route: The designated path for a question beyond the current role or scope. / follow-up commitment: A specified promise about the next communication or action. / teach-back: Asking a learner to restate or demonstrate key information to check understanding.
Speaking task: Read the training exchange. Preserve version 4 adult outpatient scope and the specific pediatric home-use question. Swap roles. Route the request without improvising a demonstration or treating the question as improper. Read the corrected referral transfer. Routing for a reviewed response does not authorize the requested use.
Partner: Sora: Clinical trainer / Alex: Clinician attending the session
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 session covers adult clinic use. A participant asks about pediatric home use. No reviewed material for that request is available, and the trainer will route it.
Model for comparison AFTER my attempt, not a response to give me first: Alex: Then competence requires the relevant assessment; a name on the session list does not demonstrate it.
Sora: Correct. A competency assessment has defined criteria. We should describe exactly what was assessed and avoid extending that result to populations or tasks outside the assessment.
Alex: Please route that question and tell me how we will hear back. We can continue with today's adult outpatient material while the separate response is pending.
Sora: I will make that follow-up commitment through the designated process. I can confirm the action and next contact, but I cannot promise that the reviewed response will endorse the requested use.
END REFERENCE
END PROMPT

Dialogue 01 · User need to design input | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 01: User need to design input
Original fictional setting: A device team reviews a vague usability requirement.
Professional roles: Product manager / Systems engineer
Published dialogue (reference script, not my own performance):
Product manager: Users want the display to be readable at a glance. How do we turn that into a design input?
Systems engineer: Define the intended users, viewing conditions, information, and a measurable acceptance criterion.
Product manager: Can we reuse the criterion from our desktop product?
Systems engineer: Not without checking the use environment. This device will be used under different lighting and workflow conditions.
Product manager: I'll bring those user-research findings to the requirements review.
Systems engineer: Then we can agree on traceable inputs and an appropriate verification approach.
Vocabulary in this exchange: design input: A documented requirement that guides a product's design. / verification: Checking whether specified requirements have been met.
END REFERENCE
END PROMPT

Dialogue 01 · User need to design input | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 01: User need to design input
Original fictional setting: A device team reviews a vague usability requirement.
Professional roles: Product manager / Systems engineer
Published dialogue (reference script, not my own performance):
Product manager: Users want the display to be readable at a glance. How do we turn that into a design input?
Systems engineer: Define the intended users, viewing conditions, information, and a measurable acceptance criterion.
Product manager: Can we reuse the criterion from our desktop product?
Systems engineer: Not without checking the use environment. This device will be used under different lighting and workflow conditions.
Product manager: I'll bring those user-research findings to the requirements review.
Systems engineer: Then we can agree on traceable inputs and an appropriate verification approach.
Vocabulary in this exchange: design input: A documented requirement that guides a product's design. / verification: Checking whether specified requirements have been met.
END REFERENCE
END PROMPT

Dialogue 02 · Risk review | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 02: Risk review
Original fictional setting: A team discusses an alarm that users sometimes miss.
Professional roles: Risk engineer / Human factors specialist
Published dialogue (reference script, not my own performance):
Risk engineer: The hazard analysis lists a missed alarm. Is a louder tone sufficient as a control?
Human factors specialist: We need to examine the use scenario and contributing factors before deciding that.
Risk engineer: Users reported competing alarms and difficulty identifying which device was sounding.
Human factors specialist: Then recognition and workflow matter as well as volume. Let's review the observations and proposed controls together.
Risk engineer: I'll update the risk file with the evidence and open questions.
Human factors specialist: I'll define the usability questions that the next evaluation needs to address.
Vocabulary in this exchange: hazard: A potential source of harm.
END REFERENCE
END PROMPT

Dialogue 02 · Risk review | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 02: Risk review
Original fictional setting: A team discusses an alarm that users sometimes miss.
Professional roles: Risk engineer / Human factors specialist
Published dialogue (reference script, not my own performance):
Risk engineer: The hazard analysis lists a missed alarm. Is a louder tone sufficient as a control?
Human factors specialist: We need to examine the use scenario and contributing factors before deciding that.
Risk engineer: Users reported competing alarms and difficulty identifying which device was sounding.
Human factors specialist: Then recognition and workflow matter as well as volume. Let's review the observations and proposed controls together.
Risk engineer: I'll update the risk file with the evidence and open questions.
Human factors specialist: I'll define the usability questions that the next evaluation needs to address.
Vocabulary in this exchange: hazard: A potential source of harm.
END REFERENCE
END PROMPT

Dialogue 03 · Verification versus validation | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 03: Verification versus validation
Original fictional setting: A project team reviews a test-completion claim.
Professional roles: Project manager / Quality engineer
Published dialogue (reference script, not my own performance):
Project manager: All bench tests passed. Can we say validation is complete?
Quality engineer: The bench tests address specified design inputs. Validation addresses intended use and user needs under the planned conditions.
Project manager: So the verification results don't automatically close the validation activities?
Quality engineer: Correct. The traceability matrix still shows open usability and intended-use evidence.
Project manager: I'll separate the two statuses in the milestone report.
Quality engineer: Let's review the approved plans and record exactly which acceptance criteria remain open.
Vocabulary in this exchange: intended use: The purpose for which a product is designed and represented to be used. / traceability: The ability to follow an item's history, source, requirements, or records through documented links. / verification: Checking whether specified requirements have been met. / validation: Confirming that an output or system meets needs for its intended use under defined conditions. / acceptance criteria: Specific conditions a deliverable must meet to be accepted.
END REFERENCE
END PROMPT

Dialogue 03 · Verification versus validation | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 03: Verification versus validation
Original fictional setting: A project team reviews a test-completion claim.
Professional roles: Project manager / Quality engineer
Published dialogue (reference script, not my own performance):
Project manager: All bench tests passed. Can we say validation is complete?
Quality engineer: The bench tests address specified design inputs. Validation addresses intended use and user needs under the planned conditions.
Project manager: So the verification results don't automatically close the validation activities?
Quality engineer: Correct. The traceability matrix still shows open usability and intended-use evidence.
Project manager: I'll separate the two statuses in the milestone report.
Quality engineer: Let's review the approved plans and record exactly which acceptance criteria remain open.
Vocabulary in this exchange: intended use: The purpose for which a product is designed and represented to be used. / traceability: The ability to follow an item's history, source, requirements, or records through documented links. / verification: Checking whether specified requirements have been met. / validation: Confirming that an output or system meets needs for its intended use under defined conditions. / acceptance criteria: Specific conditions a deliverable must meet to be accepted.
END REFERENCE
END PROMPT

Dialogue 04 · Formative usability findings | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 04: Formative usability findings
Original fictional setting: A designer and human factors specialist review a simulated-use session.
Professional roles: Human factors specialist / Interface designer
Published dialogue (reference script, not my own performance):
Human factors specialist: Three participants selected the wrong menu before finding the setting. They recovered without assistance.
Interface designer: Can we classify that as successful task completion and move on?
Human factors specialist: Completion matters, but the use difficulties still need analysis. We should examine potential consequences in the intended workflow.
Interface designer: I'll compare the screen labels and navigation paths from the observations.
Human factors specialist: Keep observed behavior separate from our explanation of why it happened.
Interface designer: I'll prepare design options for the next review rather than assume a label change solves it.
END REFERENCE
END PROMPT

Dialogue 04 · Formative usability findings | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 04: Formative usability findings
Original fictional setting: A designer and human factors specialist review a simulated-use session.
Professional roles: Human factors specialist / Interface designer
Published dialogue (reference script, not my own performance):
Human factors specialist: Three participants selected the wrong menu before finding the setting. They recovered without assistance.
Interface designer: Can we classify that as successful task completion and move on?
Human factors specialist: Completion matters, but the use difficulties still need analysis. We should examine potential consequences in the intended workflow.
Interface designer: I'll compare the screen labels and navigation paths from the observations.
Human factors specialist: Keep observed behavior separate from our explanation of why it happened.
Interface designer: I'll prepare design options for the next review rather than assume a label change solves it.
END REFERENCE
END PROMPT

Dialogue 05 · Submission planning | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 05: Submission planning
Original fictional setting: A regulatory lead questions a launch assumption.
Professional roles: Product manager / Regulatory affairs lead
Published dialogue (reference script, not my own performance):
Product manager: A similar device reached market recently. Can we use the same regulatory pathway?
Regulatory affairs lead: Similarity alone doesn't establish the appropriate pathway. Intended use, technology, claims, and jurisdiction all need review.
Product manager: What information do you need to assess it?
Regulatory affairs lead: The current device description, intended-use statement, risk information, and comparison evidence.
Product manager: I'll assemble those and keep the launch date provisional.
Regulatory affairs lead: I'll document the assessment and identify any questions requiring further regulatory clarification.
Vocabulary in this exchange: intended use: The purpose for which a product is designed and represented to be used.
END REFERENCE
END PROMPT

Dialogue 05 · Submission planning | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 05: Submission planning
Original fictional setting: A regulatory lead questions a launch assumption.
Professional roles: Product manager / Regulatory affairs lead
Published dialogue (reference script, not my own performance):
Product manager: A similar device reached market recently. Can we use the same regulatory pathway?
Regulatory affairs lead: Similarity alone doesn't establish the appropriate pathway. Intended use, technology, claims, and jurisdiction all need review.
Product manager: What information do you need to assess it?
Regulatory affairs lead: The current device description, intended-use statement, risk information, and comparison evidence.
Product manager: I'll assemble those and keep the launch date provisional.
Regulatory affairs lead: I'll document the assessment and identify any questions requiring further regulatory clarification.
Vocabulary in this exchange: intended use: The purpose for which a product is designed and represented to be used.
END REFERENCE
END PROMPT

Dialogue 06 · Complaint intake | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 06: Complaint intake
Original fictional setting: A service report enters the complaint process.
Professional roles: Service engineer / Complaint specialist
Published dialogue (reference script, not my own performance):
Service engineer: A customer says the device stopped during use. I have the serial number but not the event time.
Complaint specialist: Record what they reported and seek the missing details through the complaint process.
Service engineer: Should I call it operator error? The settings may have been wrong.
Complaint specialist: That's not established. Separate observations from hypotheses and preserve the available logs.
Service engineer: I'll provide the service history and route the report promptly.
Complaint specialist: I'll coordinate the required complaint and reportability assessment; service troubleshooting doesn't replace that review.
Vocabulary in this exchange: complaint: An expression of dissatisfaction requiring attention under a relevant process.
END REFERENCE
END PROMPT

Dialogue 06 · Complaint intake | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 06: Complaint intake
Original fictional setting: A service report enters the complaint process.
Professional roles: Service engineer / Complaint specialist
Published dialogue (reference script, not my own performance):
Service engineer: A customer says the device stopped during use. I have the serial number but not the event time.
Complaint specialist: Record what they reported and seek the missing details through the complaint process.
Service engineer: Should I call it operator error? The settings may have been wrong.
Complaint specialist: That's not established. Separate observations from hypotheses and preserve the available logs.
Service engineer: I'll provide the service history and route the report promptly.
Complaint specialist: I'll coordinate the required complaint and reportability assessment; service troubleshooting doesn't replace that review.
Vocabulary in this exchange: complaint: An expression of dissatisfaction requiring attention under a relevant process.
END REFERENCE
END PROMPT

Dialogue 07 · Supplier nonconformance | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 07: Supplier nonconformance
Original fictional setting: A receiving inspection finds an out-of-specification component.
Professional roles: Supplier quality engineer / Manufacturing lead
Published dialogue (reference script, not my own performance):
Supplier quality engineer: The connector lot failed dimensional inspection. It's on hold under the nonconformance record.
Manufacturing lead: Can we use selected parts if they appear to fit?
Supplier quality engineer: Any sorting, rework, or use decision needs an approved disposition and defined acceptance criteria.
Manufacturing lead: Production needs to know the supply impact today.
Supplier quality engineer: I'll confirm the affected quantity and ask engineering and quality to review the options.
Manufacturing lead: I'll revise the schedule using approved stock and keep held material out of production.
Vocabulary in this exchange: acceptance criteria: Specific conditions a deliverable must meet to be accepted. / nonconformance: Failure to meet a requirement, specification, contract, standard, or approved procedure.
END REFERENCE
END PROMPT

Dialogue 07 · Supplier nonconformance | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 07: Supplier nonconformance
Original fictional setting: A receiving inspection finds an out-of-specification component.
Professional roles: Supplier quality engineer / Manufacturing lead
Published dialogue (reference script, not my own performance):
Supplier quality engineer: The connector lot failed dimensional inspection. It's on hold under the nonconformance record.
Manufacturing lead: Can we use selected parts if they appear to fit?
Supplier quality engineer: Any sorting, rework, or use decision needs an approved disposition and defined acceptance criteria.
Manufacturing lead: Production needs to know the supply impact today.
Supplier quality engineer: I'll confirm the affected quantity and ask engineering and quality to review the options.
Manufacturing lead: I'll revise the schedule using approved stock and keep held material out of production.
Vocabulary in this exchange: acceptance criteria: Specific conditions a deliverable must meet to be accepted. / nonconformance: Failure to meet a requirement, specification, contract, standard, or approved procedure.
END REFERENCE
END PROMPT

Dialogue 08 · Training within labeling | Rehearse with an AI colleague

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 08: Training within labeling
Original fictional setting: A clinical trainer receives a request beyond approved instructions.
Professional roles: Clinical trainer / Medical affairs colleague
Published dialogue (reference script, not my own performance):
Clinical trainer: A user asked how to adapt the device for a use outside the current labeling.
Medical affairs colleague: Don't improvise operating instructions. Route the question through the approved medical-information process.
Clinical trainer: I can explain the labeled workflow and record the separate question accurately.
Medical affairs colleague: Yes. Keep the user's wording and relevant context without suggesting that an unreviewed use is approved.
Clinical trainer: I'll send the inquiry to the designated team and confirm the response route.
Medical affairs colleague: I'll help ensure the follow-up follows our current labeling and communication procedures.
Vocabulary in this exchange: labeling: The information supplied with or about a regulated product, as defined by applicable rules.
END REFERENCE
END PROMPT

Dialogue 08 · Training within labeling | Create more scenario dialogues

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

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

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

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

REFERENCE
Course: Medical Devices English
Professional audience: medical device engineers, product managers, quality and regulatory staff, clinical specialists, manufacturing teams, field-service teams, and device-company leaders
Scope: Original fictional language practice, not device operating instructions or medical, legal, quality-system, or regulatory advice. US regulatory examples are identified as such; other jurisdictions differ. Use the current labeling, applicable requirements, trained personnel, and your organization's controlled procedures. No scenario authorizes patient care or product release.
Dialogue 08: Training within labeling
Original fictional setting: A clinical trainer receives a request beyond approved instructions.
Professional roles: Clinical trainer / Medical affairs colleague
Published dialogue (reference script, not my own performance):
Clinical trainer: A user asked how to adapt the device for a use outside the current labeling.
Medical affairs colleague: Don't improvise operating instructions. Route the question through the approved medical-information process.
Clinical trainer: I can explain the labeled workflow and record the separate question accurately.
Medical affairs colleague: Yes. Keep the user's wording and relevant context without suggesting that an unreviewed use is approved.
Clinical trainer: I'll send the inquiry to the designated team and confirm the response route.
Medical affairs colleague: I'll help ensure the follow-up follows our current labeling and communication procedures.
Vocabulary in this exchange: labeling: The information supplied with or about a regulated product, as defined by applicable rules.
END REFERENCE
END PROMPT