A ticket says "Improve the dashboard performance." Before starting, you need clarification. Which message is best?
Effective clarification requests are numbered, specific, and solution-oriented. Option B asks exactly three questions, each scoped to a real decision point (which page, which metric, what target), and offers a fallback ("I'll scope it myself") so the conversation doesn't stall. Option A is correct in identifying vagueness but provides no structure — it puts all the work back on the requester. Options C and D are blunt or passive-aggressive, which damages collaboration.
2 / 5
Complete this clarification request: "Before I _____ (start) the migration, I _____ (want) to confirm the rollback strategy. _____ (be) there a documented procedure if the schema change _____ (fail) in production?"
Before I start uses present simple in the time clause (not "will start" — English uses present tense in before/when/after clauses for future events). I want is the direct, professional phrasing for a genuine need — "am wanting" (continuous) is unnatural for a cognitive/mental state. Is there — yes/no questions use inverted subject-verb. If the schema change fails — again, present simple in conditional clauses, not "would fail" (that belongs in the main clause). This is the classic "if + present simple, … would …" conditional structure.
3 / 5
You receive requirements that contradict each other. Which message handles this most professionally?
When requirements conflict, the professional response is to name the conflict precisely, cite the specific sections, and offer paths forward. Option B: names the sections (3.2 and 5.1), describes the conflict in concrete terms (24-hour cache vs. real-time accuracy), asks the decision question (which takes priority?), and signals that two implementation options are ready — so the reply can immediately unlock progress. Option A is technically correct but sounds confrontational and unhelpful. Option C sounds vague and puts the burden on others without doing analysis work. Option D is risky — silently choosing can waste significant effort.
4 / 5
Which clarification email subject line is best?
A subject line should tell the recipient what the email is about, what's being asked, and when it matters. Option B: references the specific topic (API Rate Limits), states the quantity of questions (2 — so they know the scope), and anchors the urgency to a real event (design review on Thursday). This lets the recipient prioritize accurately. Option A is too vague — the inbox reader learns nothing. Option C uses "URGENT" which is often filtered or ignored, and doesn't specify what is urgent. Option D is similarly vague and the "ASAP" is imprecise.
5 / 5
Choose the correct phrasing to check your own understanding: "Just _____ (want) to make sure I _____ (understand) correctly — when you say the feature should 'scale', you _____ (mean) it should handle 10× current traffic without re-architecture, _____ (correct)?"
Wanted to make sure — using past tense ("wanted") softens the check slightly, making it sound like a background concern rather than a challenge. This is a common politeness strategy in professional English. I understand (present simple) describes your current state of understanding. You mean (present simple) checks the meaning in the current context — not "you meant" (past), which would imply the conversation is already over. Correct? — this is a tag used at the end of a paraphrase to invite confirmation. "Is that correct?" also works (option C), but the question structure mid-sentence is slightly awkward after a comma.