5 exercises — using if so and if not to branch cleanly after a yes/no question in runbooks, checklists, and status updates, plus when to spell the condition out instead.
0 / 16 completed
1 / 16
A Slack message reads: "Did the migration script run against staging yet? If so, can you share the logs?" What does "if so" replace?
Option B is correct. "If so" is an elliptical conditional where "so" functions as a pro-form standing in for the entire preceding clause ("the migration script ran against staging"), avoiding a clunky repetition: "If the migration script ran against staging, can you share the logs?" This kind of ellipsis is extremely common and idiomatic in follow-up questions after a yes/no question. Its negative counterpart, "if not", stands in for the negated version of the same proposition ("if the migration script did NOT run against staging"). Pattern: ask a yes/no question, then use "if so" (assuming yes) or "if not" (assuming no) to branch the follow-up without restating the whole condition.
2 / 16
Complete the exchange correctly: "Has the incident been resolved? _____, please close the ticket. _____, keep the war room open."
"If so / If not" is correct, in that order, matching the logic: if the incident HAS been resolved ("if so"), close the ticket; if it has NOT ("if not"), keep the war room open. Reversing the order (option A) would produce the opposite, incorrect instructions — telling people to close the ticket only when the incident is unresolved. Option C ("if yes / if no, thanks") is non-standard phrasing; "if so" and "if not" are the idiomatic elliptical forms in English, not "if yes/if no" (which, while sometimes used informally, sounds less natural and the added "thanks" is a non-sequitur here). Option D reverses word order into ungrammatical fragments. Tip: always double check "if so" and "if not" match the correct branch of the original yes/no question — a swapped pair silently inverts your instructions.
3 / 16
Which sentence correctly extends the "if so / if not" pattern with a specific alternative action rather than a generic one?
"Has QA signed off? If so, merge; if not, ping them again" is the correct pattern — a yes/no question followed by two parallel elliptical conditionals, each with its own consequent clause, separated by a semicolon (or period). This structure is common in runbooks, checklists, and PR templates because it compresses a full decision tree into a compact, scannable form. Option B garbles the two branches into a single confused clause with no consequent for the "if so" branch. Option C is missing all punctuation, making it unreadable as multiple sentences. Option D incorrectly appends "so" and "not so" to "if", which is not how the idiom works — it's "if so" and "if not" as fixed two-word units, not "if [condition] so".
4 / 16
In formal technical documentation (e.g., an RFC), which is the more precise, less colloquial alternative to "if not" when referring back to "the flag is enabled"?
Spelling out the full condition — "if the flag is not enabled" — is the more precise, unambiguous choice for formal reference documentation like an RFC, where readers may jump directly to a specific section without reading the preceding sentence, making elliptical forms like "if not" or "if it isn't" ambiguous out of context. "If it isn't" (option A) is grammatically fine and slightly more explicit than bare "if not," but still relies on antecedent context ("isn't" what?) that may not survive skimming or section-jumping. "If nope" (option C) is not standard English. "If otherwise" (option D) is a real but old-fashioned/formal idiom meaning roughly "if the situation is different," and it's vaguer than restating the specific condition. Rule: elliptical "if so / if not" is excellent for conversational and sequential contexts (chat, runbooks read top to bottom); spell out the condition fully in reference docs meant to be read out of order.
5 / 16
A code review checklist item reads: "Does this PR touch the auth module? If so, tag @security-team for review." Why is this an effective use of the elliptical conditional in a checklist?
Option B is correct. Checklists are read repeatedly and quickly, so brevity and scannability matter more than in prose documentation meant to be read once, start to finish out of order. The question-then-"if so" pattern lets the reader's eye jump straight to the action item without re-parsing a long restated condition ("If this PR touches the auth module, tag..."). This is a case where the same elliptical form that would be too ambiguous in an out-of-order reference doc (see the previous exercise) is exactly right, because checklist items are always read in the immediate context of their own question. Option D is an overgeneralization — "if so" is standard in professional English across many genres, including checklists, runbooks, and process documentation; it is informal in tone but not incorrect or unprofessional.
6 / 16
A PR description reads: "This change implements a new rate limiter. If so, ensure the API documentation is updated to reflect the new limits."
The elliptical conditional here is used to direct attention to a specific follow-up action. 'If so' signals that the change has been implemented, prompting the reviewer to check for documentation updates. This avoids simply stating 'ensure…', which lacks urgency and a clear direction.
7 / 16
David: "The feature flag is currently enabled. If not, revert to the previous version and investigate why the flag was unexpectedly set."
The elliptical conditional in this scenario highlights the importance of understanding *why* a flag is unexpectedly not disabled. 'If not' prompts David to investigate the root cause of the unusual state before taking corrective action. Simply disabling the flag without investigation could mask an underlying problem.
8 / 16
A PR description reads: "This change implements a new rate limiter. If so, ensure the API documentation is updated to reflect the new limits."
The elliptical conditional here is used to direct attention to a specific follow-up action. 'If so' signals that the change has been implemented, prompting the reviewer to check for documentation updates. This avoids simply stating 'ensure…', which lacks urgency and a clear direction.
9 / 16
David: "The feature flag is currently enabled. If not, revert to the previous version and investigate why the flag was unexpectedly set."
The elliptical conditional in this scenario highlights the importance of understanding *why* a flag is unexpectedly not disabled. 'If not' prompts David to investigate the root cause of the unusual state before taking corrective action. Simply disabling the flag without investigation could mask an underlying problem.
10 / 16
A PR description reads: "This change implements a new rate limiter. If so, ensure the API documentation is updated to reflect the new limits."
The elliptical conditional here is used to direct attention to a specific follow-up action. 'If so' signals that the change has been implemented, prompting the reviewer to check for documentation updates. This avoids simply stating 'ensure…', which lacks urgency and a clear direction.
11 / 16
David: "The feature flag is currently enabled. If not, revert to the previous version and investigate why the flag was unexpectedly set."
The elliptical conditional in this scenario highlights the importance of understanding *why* a flag is unexpectedly not disabled. 'If not' prompts David to investigate the root cause of the unusual state before taking corrective action. Simply disabling the flag without investigation could mask an underlying problem.
12 / 16
A developer is reviewing a pull request that updates the configuration for a new feature. The PR includes a comment: 'If so, ensure the API documentation reflects these changes.' What does 'if so' replace in this context?
'If so' replaces a statement confirming that a particular action (updating the API documentation) has already been completed. It's an elliptical conditional signaling that the preceding condition – the configuration update – is true and therefore the subsequent step should be taken. Option A is incorrect because it doesn't reflect the context of the PR review.
13 / 16
A support engineer receives a ticket: 'The user reports intermittent connectivity issues. If not, escalate to network engineering.' What is the purpose of 'if not' in this message?
'If not' introduces an alternative action – escalating to network engineering – in case the initial troubleshooting steps fail to resolve the intermittent connectivity issues. It's a conditional statement that directs action based on whether a specific condition (successful initial troubleshooting) is met; this is a classic elliptical conditional.
14 / 16
Which of the following sentences correctly uses an elliptical conditional to avoid redundancy?
The elliptical conditional 'if the server is down' implicitly refers to restarting it. Repeating 'if the server is down' adds unnecessary words and doesn't change the meaning. Option A is a simple statement; Options B & D are also redundant.
15 / 16
In a technical report describing a bug fix, which phrase is more precise than 'if not' when referring to a feature flag that was previously enabled?
'If not' is too informal. 'If the flag isn't active' clearly states the condition and specifies the required action: reverting to the original state. This offers clarity and avoids ambiguity about the feature flag's prior status.
16 / 16
A developer writes a checklist item: 'Does this PR introduce any new security vulnerabilities? If so, run a full penetration test.' What does the elliptical conditional achieve in this context?
The elliptical conditional 'If so' acts as a trigger – it signals that a specific action (running a full penetration test) should be taken *only if* a new vulnerability is identified. This streamlines the process and avoids unnecessary testing when no vulnerabilities exist.
What will I practise in "Elliptical If So / If Not in Technical English — Grammar Exercise"?
Practise the elliptical conditionals if so and if not for compact follow-up branches in runbooks, checklists, and Slack threads. 5 exercises.
How many exercises are in this module?
This module has 16 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.