Level 5 — Advanced · Technical & Conceptual Reading
Lesson 67: Advanced Reading of Definitions, Rules, Exceptions & "If and Only If"
How to read conditional language by its logical direction rather than its words alone — telling 'if' (a sufficient condition) apart from 'only if' (a necessary one) and 'if and only if' (both at once), and converting a dense policy paragraph into its full logical structure.
Learning Objectives
By the end of this lesson, you should be able to:
- Distinguish 'if' (a sufficient condition) from 'only if' (a necessary condition) from 'if and only if' (both directions at once), reading each as a distinct logical direction rather than interchangeable phrasing
- Separate necessary conditions from sufficient ones, recognising that a stated requirement — must, necessary, prerequisite — does not by itself guarantee an outcome
- Read 'only' precisely for what it restricts based on its placement in a sentence, and apply quantifier logic — all/not all/none, every/any, either/neither/both, at least one/at most one/exactly one
- Distinguish real, hypothetical, and counterfactual conditionals, and read 'even if,' 'whether or not,' and 'regardless of' as concessive structures where the outcome holds despite a condition
- Convert a dense, condition-heavy policy or specification paragraph into an explicit logical structure — main rule, necessary conditions, exceptions, and scope — rather than reading it only sentence by sentence
Introduction
Lesson 61 first introduced necessary and sufficient conditions, "only if," "if and only if," "except," and "unless" as boundary markers between concepts. Today's lesson returns to that same territory deliberately — not to repeat it, but to go a full level deeper, treating conditional language as a formal logical system in its own right, with a direction that can be traced precisely through even the densest technical documentation, software requirements, laws, policies, contracts, manuals, and system specifications.
The core goal of this lesson is a single habit: never let "if X, then Y," "X only if Y," and "X if and only if Y" blur together. They look almost identical on the page. They are not the same claim.
Condition Is Not the Same as Definition
Describing what something is versus describing when something may happen
A valid invoice contains all required information is a definition or characterization — it says what a valid invoice looks like. An invoice can be approved if all required information is available is a condition — it says when approval becomes possible. The first answers "what is X?"; the second answers "when can Y happen?" Keeping these two kinds of sentence apart matters, because they answer genuinely different questions even when they share vocabulary.
"If" — The Basic Conditional
A direction: condition, then outcome
Structure: If X, Y — meaning X happening leads to Y happening or becoming possible. If the payment is verified, the invoice can be finalized.
Payment verified
↓
Invoice can be finalized
Notice the direction: X → Y.
"If X, Y" Does Not Mean X Is the Only Cause
A plain 'if' claim leaves other paths to the same outcome wide open
If the payment is verified, the invoice can be finalized does not automatically mean only if the payment is verified can the invoice be finalized. Some other condition might also make finalization possible. A plain "if X, Y" generally states that X is a sufficient condition for Y — not that X is the only route to Y.
Necessary Versus Sufficient, Reapplied to Conditional Logic
Connecting back to Lesson 61 — now built into full sentence-direction reading
A necessary condition must hold for an outcome to occur: payment verification is necessary for finalizing the invoice means without verification, finalization cannot happen — No X → No Y. A sufficient condition guarantees the outcome on its own: verification is sufficient to allow finalization means verification alone satisfies what's required — X → Y. Today's lesson builds directly on top of that distinction, mapping it onto specific sentence patterns you'll meet constantly in technical and legal English.
"Only If" — Marking a Necessary Condition
The single most commonly misread pattern in this entire lesson
X only if Y means: for X to happen, Y is required — X → Y, where Y is the necessary condition. An invoice can be finalized only if the payment has been verified.
Invoice finalized
↓
Payment verified
The clause following "only if" is the necessary condition — not, as a fast reader might assume, an optional detail.
"If" Versus "Only If"
Two sentences that look almost identical, with opposite logical direction
A. An invoice can be finalized if the payment is verified reads: payment verified → finalization can happen. B. An invoice can be finalized only if the payment is verified reads: finalization → payment must have been verified. These two sentences share nearly every word and still make different logical claims — "if" alone states a sufficient condition; "only if" states a necessary one.
"If and Only If" — Both Directions at Once
The strongest conditional relationship in this lesson — connecting back to Lesson 61
X if and only if Y claims both X → Y and Y → X. A transaction is considered complete if and only if payment has been verified and the receipt has been generated. Direction one: complete → payment verified
- receipt generated. Direction two: payment verified + receipt generated → complete. Together, the two named conditions don't just accompany completeness — they define it exactly.
"Iff" in Technical Writing
A common shorthand in mathematics, computer science, and formal specifications
The process is valid iff all required checks pass. "Iff" is simply shorthand for "if and only if" — a two-directional condition, written compactly. Expect it in mathematics, logic, and precise technical specifications especially.
"Provided That" and "As Long As," Reapplied
Connecting back to Lesson 64 — the same conditional-permission phrases, read for direction here
The system can operate automatically provided that valid data is available — X can happen, provided Y holds. This reads close to "only if" in most contexts, but isn't guaranteed to carry the exact same strict logical equivalence in every case — read it in context rather than assuming a fixed formula. Users may access the system as long as their accounts remain active attaches an ongoing condition (account active) to an ongoing outcome (access) — not a one-time check, but a condition that must continue to hold.
"Unless," Read for Logical Structure
Connecting back to Lesson 61 and Lesson 64 — now converted into an explicit mental form
The system will not generate the report unless the required data is available. Convert this directly into an equivalent conditional: if required data is not available → no report. Compare with a plain "if": the system generates the report if the data is available states data available → report generation. The system does not generate the report unless the data is available states data unavailable → no report — a genuinely stronger restriction than the plain "if" version, even though both sentences describe a similar-sounding situation.
"Without" and "In the Absence Of"
Two ways of marking a necessary condition through its absence
The invoice cannot be finalized without payment verification — payment verification functions as a necessary condition, phrased negatively. In the absence of valid documentation, the application will not be processed is a more formal equivalent of the same structure: no valid documentation → no processing.
"Subject To," Reapplied
Connecting back to Lesson 64 — the same conditional-approval phrase, here in policy and technical writing
Access is granted subject to security approval — access granted, but under the condition of security approval.
Access
↓
subject to
↓
Security approval
Extremely common across policy, legal, and technical English.
"Dependent On" and "Contingent On"
Two dependency phrases, with slightly different strength
System performance is dependent on network availability names an important dependency — though "dependent on" doesn't always carry the strict logical force of "only if"; it can describe a causal or influencing relationship instead. The agreement is contingent on regulatory approval is generally a stronger dependency signal: without regulatory approval, the agreement typically cannot proceed or stand, though the exact strength still depends on context.
"Necessary" Requires Caution
Connecting back to Lesson 61 — necessary is never automatically sufficient
Training is necessary for successful implementation means training's absence likely blocks — or seriously hampers — successful implementation, depending on context. It does not mean training by itself guarantees success. Suppose implementation also needs adequate infrastructure, good data, management support, and proper configuration:
Training
+
Infrastructure
+
Data quality
+
Management support
↓
Successful implementation
Training alone may not be sufficient — necessary ≠ sufficient, worth restating every time this pattern appears.
"Sufficient" and "Required"
Two more requirement-strength words, each worth checking against context
A valid authorization token is sufficient to access the service means the token alone satisfies this particular requirement — though a real-world system might layer additional conditions on top, so exact context still matters. A password is required to access the system states necessity plainly. Related strong-requirement signals: required, necessary, mandatory, essential, must, prerequisite, condition, prerequisite for.
"Prerequisite"
A necessary condition with a built-in sense of order
Training is a prerequisite for system access means the training requirement must be satisfied before access becomes available.
Training
↓
Access eligibility
↓
System access
A prerequisite is generally a condition that must be met first, in sequence — not just any necessary condition, but one with a timeline attached.
"Eligible" Versus "Authorized"
Qualifying for something is not the same as having been granted it
Eligible means someone has met the requirements and therefore qualifies: employees who have completed the training are eligible for system access. Authorized means a proper authority has formally granted permission: only authorized employees may access the system. A person can be eligible while still not yet being authorized — meeting the requirements is not automatically the same as having received formal approval.
"Only" and Its Placement
The same word, moved to a different spot, restricts a completely different part of the sentence
Only trained employees may access the system — only modifies "trained employees": untrained employees may not access it at all. Trained employees may only access the system during working hours — here "only" modifies "access… during working hours": they may access it, but restricted to working hours. Trained employees may access only the reporting system — here "only" modifies "the reporting system": no other systems. Every time "only" appears, ask explicitly: what exactly does it limit here?
"Not Only… But Also"
Here, 'only' builds addition, not restriction
The system not only reduces costs but also improves accuracy. This pattern names two benefits together — reduces costs, improves accuracy — rather than restricting anything. Don't let the presence of "only" trigger a restriction reading here; the "not only… but also" frame does the opposite job.
Quantifier Logic: All, Not All, None, Every, Any
Connecting back to Lesson 65's quantifier hierarchy — now applied to rules and requirements
All users completed the training = 100%. Not all users completed the training means at least one did not — genuinely different from none of the users completed the training (zero users). Scope differences here matter enormously: "not all" leaves room for most users having completed it; it never means "nobody." Every employee must complete the training and all employees must complete the training are close in most contexts, though "every" more often frames the requirement as applying to each individual member, one by one. Any employee may request access means any employee at all, without restriction — but in a negative frame, employees without authorization cannot access any restricted system, "any" instead means "even one" — translating "any" the same way in every context is a common and easy mistake.
Either, Neither, Both
Three words for exactly how many of two options apply
Either option can be selected — one of the two, either will do. Neither option is suitable — both are ruled out: A = false, B = false. Both systems require regular maintenance — the statement applies to A and B together, not to one or the other.
At Least One, At Most One, Exactly One
Three precise quantity bounds, easy to blur together
At least one administrator must approve the request sets a minimum: one, two, three — any number at or above one satisfies it. At most one administrator may approve the request sets a maximum: zero or one — not the same as "exactly one." Exactly one administrator must approve the request combines both bounds at once: at least one, and at most one — one, and only one.
Exception Logic: Except and Except When
Connecting back to Lesson 61 — reapplied directly to policy rules
All requests must be reviewed except those submitted automatically by the system. Main rule: all requests → review. Exception: automatically submitted requests.
ALL REQUESTS
↓
REVIEW
↑
EXCEPT
↑
Automatic submissions
The system runs automatically except when manual intervention is required shows an exception condition that changes the entire process's behaviour, not just a minor carve-out at the edge of the rule.
"Otherwise" and "Failing That"
Two ways of naming what happens if a condition is not met
Submit the form before Friday; otherwise, the request may be delayed. "Otherwise" functions as "if not": if you don't submit before Friday → delay may occur. Submit the documents by Monday, failing that, the application will be rejected is a more formal way of naming the same kind of alternative consequence.
"Where Applicable" and "Where Necessary"
Connecting back to Lesson 64 — scope qualifiers, not universal requirements
Additional documentation must be provided where applicable — only where relevant, not in every single case. Additional checks should be performed where necessary — only where actually needed. Both phrases scope a requirement down from "always" to "sometimes, depending on the situation."
"To the Extent That" and "Insofar As"
Connecting back to Lesson 61 — the same degree-qualifying phrases, applied to a rule's effectiveness
The policy is effective to the extent that employees follow it consistently ties effectiveness to a degree, not a flat yes/no — effectiveness scales with how consistently the policy is actually followed. The policy is effective insofar as it improves compliance scopes the effectiveness claim to one specific respect: compliance improvement, not every possible benefit a policy might have.
"Only If" Versus "If Only"
Same three words, rearranged, completely different function
The system works only if the network is available states a necessary condition, exactly as this lesson has built throughout. If only the network were more reliable! is something else entirely — a wish or regret, not a conditional claim at all. Word order here isn't decorative; it changes the sentence's entire grammatical function.
Three Kinds of "If": Real, Hypothetical, Counterfactual
Conditional sentences don't all describe the same relationship to reality
Real condition: if the server is unavailable, the system displays an error — a straightforward, ordinary conditional. Hypothetical: if the server were unavailable, the system would display an error — imagining a possible, not-yet-realised situation. Counterfactual past: if the server had been unavailable, the system would have displayed an error — imagining an alternative past that did not actually happen. All three share a similar shape; their relationship to what is real, possible, or already-decided is not the same at all.
Counterfactual Logic
Reasoning about a past that did not happen
If the organization had invested earlier, it might have avoided the current capacity problem. This means a problem exists now, and the author is imagining an alternative past — earlier investment — that might have prevented it. Note "might have avoided," not "would definitely have avoided": even inside a counterfactual, the author is still hedging, not claiming certainty about an imagined alternate history.
"Even If"
A concessive condition — the outcome holds regardless
Even if demand increases, the system should remain operational.
Normal condition → system works
Demand increases → system STILL works
"Even if" concedes that the condition might occur, while insisting the outcome doesn't change either way — a genuinely different logical move from a plain "if," which ties the outcome to the condition rather than declaring it independent of it.
"Whether or Not" and "Regardless Of"
Making two possibilities irrelevant to the outcome
The system will be upgraded whether or not demand increases makes both possibilities — demand increasing or not — irrelevant to the outcome: the upgrade happens either way. The policy applies regardless of department universalises the policy's scope: whatever the department, the policy applies. The system must be backed up regularly regardless of whether it is currently in use combines both ideas — current usage status simply doesn't change the backup requirement.
A Full Advanced Example
Necessary conditions, an explicit insufficiency warning, sequencing, and a controlled exception
Access to the production environment is granted only if the employee has completed the required security training and has been explicitly authorized by a system administrator. Completion of the training alone is not sufficient to grant access. Employees may request authorization once the training has been completed, provided that their role requires production access. Temporary access may be granted in exceptional circumstances, but such access must be documented and approved by a senior administrator.
Main rule: access is granted only if two conditions both hold — security training completed, and explicit administrator authorization. Necessary conditions: both training and authorization are required. Negative clarification: "completion of the training alone is not sufficient" — training ✔ but authorization ✘ still means access ✘. Permission to request: once training is complete, authorization may be requested. Additional condition on that request: "provided that their role requires production access." Exception: temporary access, in exceptional circumstances. Exception controls: documentation, plus senior administrator approval.
PRODUCTION ACCESS
↓
ONLY IF
↓
Training completed
+
Administrator authorization
↓
ACCESS GRANTED
Training alone
↓
NOT SUFFICIENT
Training completed
↓
May request authorization
↓
IF role requires production access
EXCEPTION
↓
Exceptional circumstances
↓
Temporary access
↓
Documentation
+
Senior approval
Converting a dense paragraph like this into an explicit logical structure — rather than reading it sentence by sentence — is exactly what makes technical and policy documentation tractable.
A Reading Algorithm for Condition-Heavy Text
Twelve questions for any rule, specification, or policy passage
A Master Logic Map
Nine conditional structures, each with its own direction
The Most Important Distinctions From This Lesson
Nine pairs worth keeping permanently separate
If: X → Y. Only if: X → Y, where Y is necessary. If and only if: X ↔ Y. Necessary: Y's absence blocks X. Sufficient: Y's presence guarantees X's condition is met. Must: obligation or necessity. May: permission or possibility. Must not: prohibition. Need not: no requirement. Except: a case excluded from the general rule. Unless: if not.
Vocabulary in Context
prerequisitenounformal
a necessary condition that must be satisfied before something else becomes possible, carrying a built-in sense of sequence (পূর্বশর্ত)
Often with a prerequisite for, essential prerequisite, prerequisite of
“A safety induction is a prerequisite for entering the yard.”
contingent onadjective phraseformal
dependent on a specified condition, typically a strong dependency signal in formal or business writing (শর্তসাপেক্ষ)
Often with be contingent on, entirely contingent on, contingent on approval
“The loan is contingent on the terminal passing its safety audit.”
counterfactual conditionalnoun phrasetechnical
a conditional sentence that imagines an alternative past that did not actually happen (বাস্তবতা-বিরোধী শর্তবাক্য)
Often with a counterfactual conditional, form a counterfactual conditional, counterfactual conditional about
“'If the alarm had sounded, the collision would have been avoided' is a counterfactual conditional.”
biconditionalnoun / adjectivetechnical
a relationship holding in both directions at once, expressed by 'if and only if' or 'iff' (দ্বিমুখী শর্তসম্পর্ক)
Often with a biconditional, state a biconditional, biconditional relationship
“'The gate opens if and only if the booking is valid' is a biconditional: it works in both directions.”
concessive conditionalnoun phrasetechnical
a conditional built with 'even if,' where the stated outcome holds regardless of whether the condition occurs (ছাড়যুক্ত শর্তবাক্য)
Often with a concessive conditional, form a concessive conditional, use of a concessive conditional
“'Even if prices fall, the project will proceed' is a concessive conditional.”
eligibilitynounformal
the state of having met the requirements to qualify for something, distinct from having formally received it (যোগ্যতা)
Often with eligibility criteria, check eligibility, determine eligibility
“Eligibility for the rebate depends on the vessel's annual call count.”
exactly onequantifier phraseneutral
a quantity bound combining 'at least one' and 'at most one' — one, and only one (ঠিক একটি)
Often with exactly one, require exactly one, exactly one of
“Each application must have exactly one authorised signatory.”
scope restrictionnoun phrasetechnical
the specific part of a sentence a limiting word like 'only' actually narrows, which can shift depending on its placement (পরিধি সীমাবদ্ধতা)
Often with a scope restriction, apply a scope restriction, scope restriction of
“'Only managers may approve refunds' places a scope restriction on who approves, not on what is refunded.”
Guided Reading Practice
Read this passage once, straight through. Then identify its necessary conditions, its insufficiency warning (if any), what "only" restricts, and its exception, before checking your reading against the notes that follow.
A refund is issued only if the returned item is unused, in its original packaging, and received within 30 days of the original purchase. Meeting the packaging and condition requirements alone does not guarantee a refund if the 30-day window has passed. Customers may request an exception in cases of manufacturing defects, provided that supporting evidence is submitted at the time of the request. Approved exceptions are processed only by a senior support representative, not by standard support staff.
Main rule: a refund is issued only if three conditions all hold — unused, original packaging, received within 30 days. Necessary conditions: all three, not any one alone. Insufficiency warning: meeting the packaging and condition requirements does not guarantee a refund if the time window has passed — echoing this lesson's "training alone is not sufficient" pattern exactly. Exception: manufacturing defects, with its own condition attached — supporting evidence submitted at the time of request. "Only" restriction: "processed only by a senior support representative" restricts who may process an approved exception, not whether the exception itself is valid — a distinct use of "only" from the main refund rule earlier in the passage.
Golden Rule
Golden Rule
Never read conditional language only by translating the words — read the direction of the relationship: "if" means the outcome follows from the condition, "only if" means the condition is required for the outcome, "if and only if" means both directions hold, "unless" means if not, and "except" means the general rule has an excluded case.
Lesson Summary
This lesson took the necessary/sufficient distinction Lesson 61 introduced and built it into a full system for reading conditional language by direction rather than by surface wording. You learned to tell "if" (a sufficient condition, one possible path to an outcome) apart from "only if" (a necessary condition, required for the outcome) and "if and only if" (both directions at once, defining the outcome exactly). You practised reading "only" for exactly what it restricts based on where it sits in a sentence, applied quantifier logic — all, not all, none, every, any, either, neither, both, at least one, at most one, exactly one — and distinguished real, hypothetical, and counterfactual conditionals. You worked through "even if," "whether or not," and "regardless of" as concessive structures where an outcome holds despite a condition, and converted a dense policy paragraph into an explicit logical map: main rule, necessary conditions, an insufficiency warning, sequencing, and a controlled exception.
Why this deserved a second, deeper pass after Lesson 61
Lesson 61 taught you to notice these logical markers as boundary signals between concepts. This lesson trained you to trace their exact direction through an entire paragraph, converting scattered conditional sentences into one connected logical structure — the skill that turns dense technical documentation, contracts, and specifications from intimidating into genuinely readable.
Practice: Test What You've Learned
Work through every question yourself before checking anything.
Before you start
For every sentence below, state the exact logical direction (if, only if, if and only if, unless, or except) explicitly, and diagram it the way this lesson diagrammed "payment verified → invoice finalized" — a vague "this is a condition" is not yet a complete answer.
Part A — If, Only If, and If and Only If
- A claim is approved if the supporting documents are complete. Diagram this sentence's logical direction, and explain why it does not rule out other possible paths to approval.
Show answer
Diagram: documents complete leads down to claim approved, a plain condition-to-outcome direction. It does not rule out other paths because a plain "if" states that the condition is sufficient, one route to the outcome, not that it is the only route — some other condition could also lead to approval. - A claim is approved only if the supporting documents are complete. Diagram this sentence's logical direction, and contrast it with question 1.
Show answer
Diagram: claim approved leads down to documents complete, meaning approval requires complete documents as a necessary condition. This reverses question 1's direction: there, complete documents were one sufficient path to approval among possibly others; here, complete documents are a requirement that any approval must satisfy, with no approval possible without them. - A shipment is classified as hazardous if and only if it contains a listed restricted substance. Explain both directions this sentence commits to.
Show answer
Direction one: if the shipment is classified as hazardous, then it contains a listed restricted substance. Direction two: if the shipment contains a listed restricted substance, then it is classified as hazardous. Together, containing the substance is both necessary and sufficient for the hazardous classification — the two define each other exactly.
Part B — Necessary, Sufficient, and Prerequisite Language
- Completing the certification exam is necessary to become a licensed inspector, but it is not, by itself, sufficient. Identify what this sentence explicitly denies, and propose one additional requirement that might also be needed.
Show answer
It explicitly denies that passing the exam alone guarantees licensure — the exam is required but does not, on its own, complete the requirements. An additional requirement might be a set number of supervised field-inspection hours, or a clean background check, either of which could be needed alongside the exam before licensure is granted. - A verified email address is a prerequisite for account activation. Explain what sequencing "prerequisite" adds beyond a plain necessary condition.
Show answer
"Prerequisite" adds an order: the email must be verified first, before activation can even be attempted, not merely alongside it at some point. A plain necessary condition only says activation cannot happen without verification; "prerequisite" additionally places verification earlier in a defined sequence. - Employees who pass the assessment are eligible for promotion, though final promotion decisions are made by department heads. Explain the difference between "eligible" and "authorized" in this sentence.
Show answer
Passing the assessment makes an employee eligible, meaning they have met the requirement that qualifies them for consideration. Being authorized, the actual grant of the promotion, is a separate act reserved for department heads, so eligibility opens the door without guaranteeing anyone walks through it.
Part C — Only, Quantifiers, and Exceptions
- Only senior engineers may approve production deployments. State exactly what "only" restricts here.
Show answer
"Only" restricts who may approve production deployments — it narrows the eligible approvers to senior engineers, meaning anyone who is not a senior engineer may not approve any production deployment at all. - Senior engineers may approve only emergency deployments outside business hours. State exactly what "only" restricts here, and explain how it differs from question 7.
Show answer
Here "only" restricts what may be approved outside business hours — senior engineers may approve emergency deployments then, and nothing else. This differs from question 7, where "only" restricted who could approve; here the same word restricts the category of deployment being approved, not the identity of the approver. - All packages must be inspected except those under a pre-cleared trusted-shipper program. Identify the main rule and the exception.
Show answer
The main rule is that all packages must be inspected. The exception removes packages under a pre-cleared trusted-shipper program from that requirement, so those specific packages need not be inspected.
Part D — Concessive and Counterfactual Conditionals
- Even if the vendor misses the delivery deadline, the launch date will not change. Explain why this is a concessive conditional rather than a plain "if" statement.
Show answer
A plain "if" would tie the outcome to the condition, saying the launch date changes depending on whether the deadline is missed. "Even if" instead concedes that missing the deadline might happen while insisting the launch date stays fixed regardless, declaring the outcome independent of the condition rather than dependent on it. - If the team had tested the update on a staging server, the outage might have been prevented. Identify what kind of conditional this is, and explain what it does and does not claim about the past.
Show answer
This is a counterfactual past conditional, imagining an alternative past, testing on a staging server, that did not actually happen. It claims only that prevention was a possibility under that imagined alternative, signalled by "might have"; it does not claim the outage would definitely have been avoided. - The audit will proceed regardless of whether the department has completed its self-assessment. Explain what this sentence makes irrelevant to the outcome.
Show answer
It makes the completion status of the department's self-assessment irrelevant to the outcome — whether that self-assessment is finished or not, the audit proceeds either way.
Part E — Full Passage Analysis
Return to this lesson's guided reading passage about refund policy.
- State the refund policy's three necessary conditions in your own words.
Show answer
The returned item must be unused, it must be in its original packaging, and it must be received within 30 days of the original purchase. - Identify the sentence that functions as an insufficiency warning, and explain what it denies.
Show answer
The sentence "Meeting the packaging and condition requirements alone does not guarantee a refund if the 30-day window has passed" is the insufficiency warning. It denies that satisfying two of the three requirements is enough on its own — all three conditions, including the time window, must hold together. - Identify the passage's exception and the condition attached to requesting it.
Show answer
The exception is for manufacturing defects. The condition attached is that supporting evidence must be submitted at the time the exception is requested. - Explain the two different things "only" restricts across this passage — once in the main rule, once in the exception-processing sentence.
Show answer
In the main rule, "only if" restricts the conditions under which a refund is issued at all — the three named requirements. In the exception-processing sentence, "only by a senior support representative" restricts who may process an approved exception, a restriction on personnel rather than on whether the exception itself is valid.
Next: Lesson 68 — Advanced Reading of Exceptions, Conditions, Limitations & Edge Cases: how to reconstruct a dense rule paragraph as one connected flowchart, and tell a genuine exception apart from a limitation, a precaution, or a parallel alternative.