Level 5 — Advanced · Technical & Conceptual Reading
Lesson 66: Advanced Reading of Uncertainty, Probability, Risk & Forecasting
How to preserve an author's exact level of uncertainty instead of quietly upgrading it — telling possible from likely from certain, probability from risk, and a forecast from a guarantee, across technology, business, economics, and policy writing.
Learning Objectives
By the end of this lesson, you should be able to:
- Distinguish possibility from likelihood from certainty, reading may/might/could, likely/probable, and stacked hedges as marking genuinely different strengths of claim
- Separate risk — probability combined with impact — from plain probability, and read exposure language (at risk of, vulnerable to, susceptible to) as distinct from a claim that something has already happened
- Distinguish estimate, prediction, and forecast, and recognise that 'expected to,' 'projected to,' and 'anticipated to' name a forecast's evidentiary basis without guaranteeing its outcome
- Read conditional forecasting language — assuming that, if current trends continue, in the worst-case scenario — as scenario-dependent, and track range language (up to, at least, no more than) for its precise bound
- Preserve an author's exact level of uncertainty when restating a claim, rather than silently upgrading a possibility into a prediction, or a prediction into a fact
Introduction
Lesson 65 trained you to treat "better" as a conclusion that depends on criterion, evidence, and context. Today's lesson turns to passages where even the underlying facts are unsettled — where the author isn't claiming something is true, but weighing how likely it is, how risky it is, or what might happen next. This is the language of uncertainty, probability, risk, and forecasting, and it shows up constantly in technology, business, economics, science, weather and climate writing, project management, logistics, policy, investment, technical documentation, and research papers.
The single biggest misreading in this territory is collapsing three genuinely different claims into one: treating "possible" as though it meant "likely," and "likely" as though it meant "certain." Today's lesson builds the precision to keep all three apart.
Certainty Is a Spectrum, Not a Binary
Information doesn't only arrive as true or false
An author's confidence in a claim can sit anywhere along a spectrum:
CERTAIN
↓
very likely
↓
likely
↓
probable
↓
plausible
↓
possible
↓
unlikely
↓
very unlikely
↓
almost impossible
These words don't correspond to exact mathematical percentages — "likely" generally means "there's substantial probability," not "70% exactly." Read this spectrum as relative strength, not a lookup table.
"Possible" Is Not "Likely"
Two words often blurred together — and genuinely different in strength
The system could fail under extreme conditions states possibility: failure could occur under extreme conditions, without claiming it's expected. The system is likely to fail under extreme conditions is a stronger probability claim — the author is saying failure has a relatively high chance of happening. Possible names a possibility; likely names a real expectation. Collapsing the two erases a distinction the author almost certainly intended.
May, Might, Could: Three Possibility Modals, and Could's Extra Jobs
These three overlap, but aren't perfectly interchangeable
The change may increase costs — costs could rise. The change might increase costs — the same possibility, phrased slightly more tentatively. The change could increase costs — possibility again, but "could" carries extra baggage worth watching for. It has (at least) three distinct jobs: possibility (the delay could affect the delivery schedule), past ability (the old system could process only 100 requests per minute), and a hypothetical option (the organization could reduce costs by automating the process — here "could" names an available strategy, not a prediction). Never read "could" as a simple synonym for "might" without first checking which of these three jobs it's doing.
Probability Language, From High to Very Low
A reference scale for probability vocabulary
"Expected To" and Why Expected Is Not Guaranteed
A forecast, not an assertion
Demand is expected to increase next year gives a forecast or expectation — noticeably weaker than demand will increase, a strong prediction or assertion, and stronger than demand may increase, a plain possibility. Even so, sales are expected to rise means the available evidence or models support that expectation — not that the outcome is locked in. An unexpected event can still make the forecast wrong. Forecast ≠ fact, no matter how confidently it's phrased.
"Projected To" and Its Near-Synonyms
A cluster of forecast verbs that are related, but not perfectly identical
Revenue is projected to increase by 15% means a model or forecast estimates that increase — a future estimate, not a settled outcome. Related expressions — forecast to, projected to, estimated to, predicted to, expected to, anticipated to — cluster around the same idea, but they are not exact synonyms; each carries a slightly different connotation about the basis and confidence behind the claim.
Estimate, Prediction, and Forecast: Three Different Claims
All three involve uncertainty, but about different things
An estimate is an approximate calculation of a current or unknown quantity: the cost is estimated at $50,000. A prediction is a statement about a future outcome: the system will probably require more storage. A forecast is a future expectation built specifically on data, models, or trends: demand is forecast to increase over the next five years. Keeping these three apart matters because each one implies a different kind of basis behind the claim.
"Estimated" Carries Hidden Uncertainty
One word quietly flags that a number isn't final
The project will cost an estimated $2 million — $2 million is not necessarily the exact final cost; it's an estimate. The project cost $2 million reports an actual, historical amount. Whenever "estimated" appears next to a number, read the number as approximate, not fixed.
"Approximately," "Roughly," and "About"
Three interchangeable signals that a number is not exact
Approximately 10%, roughly 10%, and about 10% all signal the same thing: this is not an exact figure. Compare directly with exactly 10% — a genuinely different, much more precise claim.
Probability Is Not Frequency
How often something happens is a different fact from how likely it is to happen next
The system often fails states frequency — failure has happened repeatedly in the past. The system may fail states possibility — about a future occurrence, without saying how common it's been. A sentence about frequency doesn't automatically tell you the probability of the next event, and a sentence about possibility doesn't tell you how often the event has occurred before.
Degree and Frequency Hedges: Generally, Typically, Usually, Tends To
Four words that describe a tendency, never a universal rule — connecting back to Lesson 62's hedge words
The method is generally effective means effective in most cases, with room for exceptions — a genuinely different, weaker claim than the method is always effective, which is universal. The process typically takes three days names a common pattern, not a guaranteed exact duration every time. Automated systems tend to reduce processing time states a general tendency — "X tends to Y" means X has a general propensity toward Y, not that X always produces Y.
Risk Is Not the Same as Probability
Risk combines two separate factors: how likely, and how bad
Risk is generally best understood as probability × impact, not probability alone. Event A might have high probability but low impact; Event B might have low probability but catastrophic impact — the two cannot be judged the same way just because one has the higher probability number. Reading "risk" as if it meant only "chance of happening" loses half of what the word is actually doing.
Risk Vocabulary
Common risk-related phrases
Benefit and risk, named together
Automation may reduce labor costs but increase the risk of data-quality problems. Benefit: labor cost ↓. Risk: data-quality problems ↑ — a trade-off structure, exactly like Lesson 63 and Lesson 65's trade-off patterns, now applied specifically to risk.
Risk Is Not the Same as Actual Failure
A stated risk is a possibility, not an event that has happened
The system faces a risk of failure states that failure is possible — it does not say the system has failed. Compare three distinct claims directly: the system failed (an actual, completed event); the system may fail (a possibility); the system is at risk of failure (a vulnerability or exposure). All three sound related; only the first reports something that actually occurred.
"At Risk Of," "Vulnerable To," and "Susceptible To"
Three phrases naming exposure, not certainty
The project is at risk of being delayed is a warning — delay is not certain, but the project is exposed to that possibility. Small organizations are particularly vulnerable to sudden cost increases goes beyond plain probability — it names a susceptibility: the impact of sudden cost increases would likely fall harder on them. The system is susceptible to network failures means the system has a vulnerability to network failure — not that failure is guaranteed to occur.
Risk Mitigation: Risk → Mitigation → Residual Risk
A common three-stage pattern in risk-aware writing
Cloud outages can disrupt operations. Regular backups and failover systems can reduce this risk, although some downtime may remain unavoidable. Risk: cloud outages. Impact: disrupted operations. Mitigation: backups and failover systems. Remaining risk: some downtime may still occur. Notice the pattern doesn't end at "mitigation" — a careful author names what risk is left over even after the mitigation is applied.
"Reduce Risk" Is Not "Eliminate Risk"
A strength ladder for risk language — connecting back to Lesson 63
The new system reduces the risk of failure means failure's probability or impact may decrease — it does not mean failure becomes impossible. Eliminates the risk is a much stronger claim: risk completely removed. Roughly ordered by strength: eliminate → prevent → substantially reduce → mitigate → minimize — though this ordering can shift with context, so treat it as a useful default, not a fixed mathematical scale. Prevent means stop something from happening outright (the backup system prevents data loss); reduce means make it less likely or less severe (the backup system reduces the risk of data loss — loss is still possible).
Where Uncertainty Comes From
Common sources an author might cite for their own uncertainty
'Due to limited evidence' names the uncertainty's source directly
The long-term effects remain uncertain because the available data cover only a short period makes the reason for uncertainty explicit. The long-term impact remains unclear due to limited evidence does the same: conclusion uncertainty, because evidence is limited — the author is acknowledging a limitation rather than speculating past it.
"It Remains Unclear Whether…"
A powerful, deliberately open-ended uncertainty signal
It remains unclear whether the policy will improve productivity leaves both possibilities genuinely open — the author is not leaning toward either outcome, just naming the question as unresolved.
"Cannot Be Ruled Out"
A cautious way of saying 'still possible,' without predicting
A further increase in costs cannot be ruled out. This does not mean costs will increase; it means that possibility hasn't been eliminated. This is characteristically cautious academic and business language — naming what remains possible without asserting it will happen.
"There Is a Possibility That…"
A deliberately hedged way of introducing a possible outcome
There is a possibility that demand will decline states a possible outcome without predicting it — the phrasing itself signals the author is being careful not to overstate the claim.
Near-Zero Probability Language
'Very unlikely' still isn't the same claim as 'impossible'
Little chance means a low probability; no chance means zero probability — never treat these as equivalent. The system is unlikely to fail states low probability; the system cannot fail states impossibility — the two differ enormously in strength. A complete system failure is highly unlikely offers strong reassurance, but it is still not the same claim as "impossible."
Scenario Thinking
A forecast can describe several possible futures at once, not just one
Common scenario phrases: in the best-case scenario, in the worst-case scenario, under a favorable scenario, under adverse conditions, if current trends continue, assuming that…, if demand remains stable, in the event that…, depending on… If current demand continues to grow, the system may reach capacity within five years is a conditional forecast — the structure is assumption → future possibility, not an unconditional statement about the future.
"Assuming That" and "If Current Trends Continue"
Two phrases that make a forecast's hidden condition explicit
Assuming that fuel prices remain stable, transportation costs are expected to increase only slightly. The forecast — costs increase slightly — depends entirely on the stated condition: fuel prices stay stable. If current trends continue, demand could double within a decade layers uncertainty twice: the trend continuing is itself uncertain, and even given that assumption, "could double" is only a possibility, not a guarantee. Track both layers — the condition and the forecast built on top of it — separately.
Conditional Forecast: "If X, Y Is Likely"
Naming the condition keeps a prediction honest about its own dependence
If traffic continues to increase, congestion is likely to become more severe.
Traffic ↑
↓
IF trend continues
↓
Congestion likely ↑
This is not a deterministic prediction — it's a probability claim that only holds under a stated condition.
"Would" Versus "Could" in Hypothetical Forecasting
Two hypothetical forms with different implied certainty
If demand increased significantly, the existing system would become inadequate uses the structure if + past form → would + verb to analyse a hypothetical future situation, treating the consequence as following fairly directly from the condition. If demand doubled, the current infrastructure could become overloaded uses "could" instead of "would," signalling a genuine possibility within that hypothetical — noticeably less certain than "would become overloaded." Both sentences are hypothetical; "would" and "could" mark two different strengths of consequence within that hypothetical frame.
Best-Case and Worst-Case Scenarios
Naming the range of plausible outcomes, not one single prediction
A best-case scenario describes the most favourable plausible outcome under optimistic assumptions; a worst-case scenario describes the least favourable plausible outcome under adverse conditions. In the best-case scenario, the project will be completed within six months. In the worst-case scenario, major delays could extend the timeline to more than a year. This builds a genuine range — six months to more than a year — rather than one fixed prediction.
Range Language
Phrases that bound a forecast rather than pin it to one number
'Up to 20%' names a ceiling, not an average
Costs could increase by up to 20%. "Up to 20%" names the maximum projected or possible level — it does not mean the average increase is 20%. Confusing a stated ceiling with a stated average badly overstates what a range claim actually commits to.
Precise Bounds: At Least, At Most, No More Than, No Less Than
Four phrases with an exact mathematical relationship worth holding onto
At least 10 days means 10 or more. At most 10 days means 10 or fewer. No more than 10% means ≤ 10%. No less than 10% means ≥ 10%. Reading these as precise mathematical bounds, rather than vague qualifiers, makes quantitative English significantly easier to follow.
"Could Reach" and "Up To" Versus "An Average Of"
A possible ceiling is not the same claim as a typical value
Demand could reach 500,000 units by 2030 names a possible future level — not a claim that demand will be 500,000. And costs may increase by up to 30% (a maximum possible or projected increase) is a genuinely different claim from costs may increase by an average of 30% (a typical, central value) — the two are easy to blur together and mean quite different things.
Confidence and Evidence Are Separate Things
An author can sound very sure while offering very little support
The policy will definitely improve productivity is a strong, confident claim — which immediately raises the question: what evidence backs it? Preliminary evidence suggests that the policy may improve productivity stacks three separate qualifications — "preliminary evidence," "suggests," and "may" — making it a far more cautious claim. Confidence in tone and strength of evidence are two separate dimensions; a confident-sounding sentence is not automatically a well-supported one.
Hedge Stacking
Several qualifiers compounding inside a single sentence
The policy may potentially contribute to a modest reduction in costs. Unpack it piece by piece: "may" (possibility), "potentially" (possibility, again — doubled), "contribute to" (partial causation, not sole cause), "modest" (limited degree), "reduction" (the outcome itself). This is a heavily qualified claim, compressible without losing its force to: the policy might contribute somewhat to lower costs — genuine semantic compression, the same skill built in Lesson 47 and reapplied in Lesson 63.
Forecast, Prediction, and Scenario: Three Different Things
Revisiting the distinction with three matched examples
Prediction: demand will increase — a plain future claim. Forecast: demand is forecast to increase based on current trends/data/models — an evidence- or model-based projection. Scenario: if demand grows rapidly, capacity may become insufficient — a hypothetical, conditional future. All three describe something not yet known, but they differ in exactly what kind of basis or condition stands behind the claim.
"Expected," "Likely," "Intended," and "Observed": Four Layers Kept Separate
A recurring confusion this lesson exists to prevent
Demand is likely to increase is a probability judgment. Demand is expected to increase is a forecast or expectation — often carrying the weight of a model, forecast, or plan behind it, even when it sounds close to "likely" in context. Separately: the project is expected to reduce costs names a forecasted result; the project is intended to reduce costs names an intended goal; the project has reduced costs reports an observed result. These are three genuinely different claims:
INTENDED
↓
EXPECTED
↓
OBSERVED
Higher demand is anticipated next year belongs with "expected" — foreseen, but anticipated ≠ guaranteed, exactly like every forecast verb in this lesson.
"Uncertainty Remains"
A direct statement of the author's own epistemic limits
Considerable uncertainty remains regarding the long-term effects states, plainly, that substantial uncertainty persists — the author is naming the limits of what is currently known, not hedging around it.
Epistemic Versus Practical Uncertainty
Not knowing because of missing information is different from the world itself being unpredictable
Epistemic uncertainty exists because of data, information, or model limitations — we don't know because we lack the information. Practical uncertainty exists because of real-world variability — future demand, weather, human behaviour, market changes — the world itself hasn't settled yet, regardless of how much data we have. When reading an uncertain claim, check which kind of uncertainty the author is actually naming — the fix for one (gather more data) doesn't fix the other.
"Risk" Rarely States an Exact Probability
A word that names exposure, not a percentage
The project carries a significant financial risk gives no exact probability at all — it's a broad judgment that the financial downside or exposure is significant. Don't automatically translate "significant risk" into "high probability of failure" — the sentence never actually claimed that.
A Risk Matrix Mental Model
A useful, if informal, way to hold probability and impact together
IMPACT
Low High
┌────────┬────────┐
Low │ Low │ Medium │
Probability├────────┼────────┤
High │ Medium │ High │
└────────┴────────┘
This isn't a precise universal formula — treat it as a mental model for sorting risks while reading, not a rule to calculate with.
An Uncertainty Reading Algorithm
Ten questions for any forecasting or risk-heavy paragraph
Risk, Uncertainty, and Forecast Together: A First Worked Example
A shorter passage showing several of this lesson's layers at once
Although demand is expected to increase over the next five years, the scale of the increase remains uncertain. If current trends continue, capacity constraints could emerge earlier than anticipated, particularly under a high-growth scenario. However, the risk may be mitigated through phased infrastructure expansion.
Forecast: demand is expected to increase. Uncertainty: the scale remains uncertain. Conditional scenario: if current trends continue. Risk: capacity constraints. Higher-risk condition: high-growth scenario. Mitigation: phased infrastructure expansion — the whole architecture this lesson has been building, compressed into three sentences.
A Full Advanced Example
Forecast, cause, uncertainty, condition, risk, mitigation, and remaining unknown, layer by layer
The demand for automated port services is likely to increase over the next decade as operators seek to reduce processing time and improve visibility. However, the rate of adoption remains uncertain because smaller ports may lack the technical infrastructure and skilled personnel required to implement such systems. If infrastructure investment continues at its current pace, adoption could remain concentrated among larger ports. In a high-growth scenario, capacity constraints in existing digital infrastructure may become a significant risk. This risk could be mitigated through phased investment, although the long-term costs of such expansion remain difficult to estimate.
Forecast: demand is likely to increase — relatively high probability. Reason: operators seek to reduce processing time and improve visibility. Uncertainty: the rate of adoption remains uncertain. Reason for that uncertainty: smaller ports may lack infrastructure and skilled personnel. Conditional scenario: if infrastructure investment continues at its current pace. Forecast under that condition: adoption could remain concentrated among larger ports — "could" marking possibility, not certainty. High-growth scenario: named explicitly as a separate, riskier case. Risk: capacity constraints. Mitigation: phased investment. Remaining uncertainty: long-term costs remain difficult to estimate — the passage never claims to have resolved every unknown.
The Paragraph's Compressed Meaning
Compression that keeps every layer of hedged claim intact
Automation demand will probably grow, but adoption speed is uncertain. Smaller ports may face infrastructure and skills constraints. Under current investment levels, adoption may remain concentrated in larger ports. Rapid growth could create digital-capacity risks, which phased investment may reduce, although long-term costs remain uncertain. This compression preserves every original layer — probability, uncertainty, conditions, risk, mitigation, and limitation — none of it silently upgraded into a firmer claim than the original text actually made.
Ten Core Distinctions From This Lesson
Keep all ten of these pairs genuinely separate
Possible ≠ likely. Likely ≠ certain. Risk ≠ actual failure. Reduce risk ≠ eliminate risk. Forecast ≠ fact. Expected ≠ guaranteed. Intended ≠ expected. Expected ≠ observed. Scenario ≠ prediction. Uncertain ≠ permanently unknowable.
Three Master Maps
Probability Language Master Map
Risk Language Master Map
Forecasting Master Map
No need to memorise exact percentages
Treat the probability map especially as relative strength, not a lookup table of fixed numbers — the value is in ordering claims correctly against each other, not in assigning them precise percentages.
Vocabulary in Context
epistemic uncertaintynoun phrasetechnical
uncertainty that exists because of missing or limited information, rather than because the world itself is unpredictable (জ্ঞানভিত্তিক অনিশ্চয়তা)
Often with epistemic uncertainty, reduce epistemic uncertainty, source of epistemic uncertainty
“The forecast carries epistemic uncertainty because only six months of data were available.”
residual risknoun phrasetechnical
the risk that remains after mitigation measures have been applied (অবশিষ্ট ঝুঁকি)
Often with residual risk, accept the residual risk, low residual risk
“After installing fire barriers, the residual risk of a warehouse fire was rated as low.”
hedge stackingnoun phrasecourse term
the layering of several qualifying words in a single sentence, each narrowing the claim's certainty or scope further (একাধিক শর্তসংকেতের স্তরায়ন)
Often with avoid hedge stacking, a case of hedge stacking, hedge stacking in
“'It may possibly be the case that costs could rise' is hedge stacking: four qualifiers weaken one claim.”
conditional forecastnoun phrasetechnical
a prediction about the future that only holds if a stated condition or assumption is met (শর্তসাপেক্ষ পূর্বাভাস)
Often with give a conditional forecast, conditional forecast of, conditional forecast based on
“The report gives a conditional forecast: volumes will grow four percent if the canal stays open.”
vulnerabilitynounformal
a susceptibility to harm or negative impact from a particular risk, distinct from a claim that the harm has occurred (ঝুঁকিপ্রবণতা)
Often with vulnerability to, security vulnerability, expose a vulnerability
“The audit exposed a vulnerability in the port's payment system.”
risk matrixnoun phrasetechnical
an informal grid for sorting risks by combining their probability and their impact (ঝুঁকি ম্যাট্রিক্স)
Often with build a risk matrix, use a risk matrix, position on the risk matrix
“On the risk matrix, a fuel spill is rated unlikely but severe.”
worst-case scenarionoun phraseneutral
the least favourable plausible outcome under adverse assumptions, one end of a forecast's stated range (সবচেয়ে খারাপ সম্ভাব্য পরিস্থিতি)
Often with in a worst-case scenario, plan for the worst-case scenario, worst-case scenario of
“In the worst-case scenario, the terminal would lose two weeks of throughput.”
forecastnoun / verbformal
a future expectation built specifically on data, models, or trends, as distinct from a plain prediction or an estimate of a present quantity (পূর্বাভাস)
Often with economic forecast, revise the forecast, forecast for
“The forecast for the coming year predicts flat container volumes.”
Guided Reading Practice
Read this passage once, straight through. Then identify its forecast, its stated condition, its risk, its mitigation, and its remaining uncertainty, before checking your reading against the notes that follow.
Container volumes at the terminal are expected to grow moderately over the next three years, assuming regional trade patterns remain broadly stable. Should growth accelerate beyond current projections, however, yard storage capacity could become a limiting factor sooner than planned. This risk is considered manageable in the short term through temporary off-site storage arrangements, though such arrangements are unlikely to remain cost-effective if volumes continue to rise sharply over a longer period. At this stage, it remains unclear whether planned yard expansion will be completed in time to address a high-growth scenario.
Forecast: container volumes expected to grow moderately — a forecast, not a guarantee. Stated condition: assuming regional trade patterns remain broadly stable. Conditional risk: if growth accelerates beyond current projections, yard storage capacity could become limiting — "could," a possibility, not a certainty. Mitigation: temporary off-site storage, explicitly scoped as workable only "in the short term." Limitation on the mitigation: unlikely to remain cost-effective under sustained sharp growth. Remaining uncertainty: whether yard expansion will be completed in time — left explicitly, deliberately unresolved with "it remains unclear whether."
Golden Rule
Golden Rule
Advanced reading means preserving the author's uncertainty — if a text says "the system may improve efficiency," don't silently read it as "the system will improve efficiency"; read it as "the author considers improved efficiency a possibility," and hold that exact level of confidence, no more and no less, all the way through.
Lesson Summary
This lesson built the discipline of never silently upgrading an author's claim. You separated possibility from likelihood from certainty across "may," "might," "could," "likely," and "expected to," and learned that risk means probability combined with impact, not probability alone. You tracked exposure language — at risk of, vulnerable to, susceptible to — as distinct from claims that something had actually happened, and worked through the risk → mitigation → residual risk pattern. You distinguished estimate, prediction, and forecast, and kept intended, expected, and observed outcomes as three separate layers. You practised reading conditional forecasts and scenario language precisely, tracking range phrases like "up to" and "no more than" for their exact mathematical bound, and unpacked hedge-stacked sentences piece by piece without losing any of their qualifications.
The single habit this lesson protects
Every technique in this lesson defends one thing: the gap between what an author actually claimed and what a careless reader might remember them as having claimed. A possibility restated as a prediction, or a forecast restated as a fact, is a real misreading — even when every individual word was understood correctly.
Practice: Test What You've Learned
Work through every question yourself before checking anything.
Before you start
For every sentence below, name its exact certainty level, and restate it in your own words without upgrading or downgrading that certainty — "this says it might happen" is a starting point, not yet a complete answer.
Part A — Possibility, Likelihood, and Modal Verbs
- The upgrade could resolve the compatibility issue. Identify which of "could's" three functions from this lesson applies here, and explain how you know.
Show answer
This is the possibility function, parallel to "the delay could affect the delivery schedule." There is no past-tense frame that would signal past ability and no sense of naming an available strategy, so "could" simply flags resolving the issue as one possible outcome of the upgrade. - Congestion is likely to worsen during the holiday season. Restate this claim without upgrading it to a certainty.
Show answer
There is a strong chance congestion will get worse over the holidays, though it is not guaranteed to happen. "Likely" belongs near the top of the probability spectrum, well short of "certain," so any restatement must keep that room for it not to worsen. - The vendor's older platform could only support 50 concurrent users. Identify which meaning of "could" this sentence uses, and explain why it is not a claim about possibility.
Show answer
This is the past-ability meaning, describing a fixed limitation of the old platform's capacity that already existed, not something that might occur. It is not possibility because there is nothing uncertain or future about it — it reports a settled fact about what the platform was and was not capable of doing.
Part B — Risk, Exposure, and Mitigation
- Remote workers are particularly susceptible to phishing attacks. Explain what kind of claim "susceptible to" makes, and what it does not claim.
Show answer
"Susceptible to" names a vulnerability or exposure — remote workers are more likely to be harmed by phishing attempts than other groups, or harmed more severely. It does not claim that remote workers have already been phished, nor does it state an exact probability that they will be. - Diversifying suppliers reduces the risk of a single point of failure, though some exposure inevitably remains. Identify the risk, the mitigation, and the residual risk in this sentence.
Show answer
The risk is a single point of failure, relying too heavily on one supplier. The mitigation is diversifying suppliers, and the residual risk is the exposure the sentence says "inevitably remains" even after that mitigation is applied. - The merger carries considerable regulatory risk. Explain why this sentence gives no exact probability, despite sounding confident.
Show answer
"Risk" here names exposure to a potential regulatory downside, not a measured chance of it occurring, and "considerable" describes the size of that exposure rather than a probability figure. The sentence sounds confident because the judgment is stated firmly, but confidence of tone is a different dimension from strength of evidence or an actual percentage.
Part C — Estimate, Forecast, and Prediction
- The renovation is estimated to cost around $400,000. Explain what kind of uncertainty "estimated" signals here.
Show answer
"Estimated" signals that $400,000 is an approximate calculation, not a final, fixed figure — the actual cost could turn out higher or lower once the work is complete. It flags uncertainty in the number itself, distinct from any uncertainty about whether the renovation will happen at all. - Based on current enrollment trends, the university forecasts a 5% increase in applications next year. Identify what this forecast's claim is actually based on.
Show answer
The forecast is explicitly based on current enrollment trends, named directly in the sentence's opening phrase. That named evidentiary basis is what makes this a forecast rather than a plain prediction, since a forecast is specifically a future expectation built on data or trends. - The team predicts the new feature will boost user retention. Classify this as an estimate, a prediction, or a forecast, and justify your choice.
Show answer
This is a prediction: it is a plain statement about a future outcome, using "predicts" and "will," with no named data, model, or trend cited as its basis. It is not an estimate, since it concerns a future event rather than an approximate current quantity, and not a forecast, since no evidentiary basis is stated.
Part D — Conditional Forecasts and Range Language
- Assuming current staffing levels are maintained, response times should remain under two hours. Identify the condition this forecast depends on.
Show answer
The forecast depends on current staffing levels being maintained. If staffing drops below that level, the two-hour expectation is no longer supported by the stated condition. - In a worst-case scenario, a prolonged outage could cost the company up to $2 million. Explain why "up to $2 million" is not the same claim as "an average of $2 million."
Show answer
"Up to $2 million" names a ceiling, the maximum the cost could reach under the worst-case scenario, not a typical or central figure. "An average of $2 million" would describe a usual outcome around that value, which is a much stronger and different claim than naming the top of a range that most outcomes would likely fall well below. - If the pilot program succeeds, the initiative could be expanded to no more than five additional cities in its first year. State the precise mathematical bound "no more than five" expresses.
Show answer
"No more than five" means five or fewer — a maximum of five additional cities, with the actual number possibly being lower.
Part E — Full Passage Analysis
Return to this lesson's guided reading passage about container volumes and yard storage capacity.
- State the passage's forecast and the condition it depends on, in your own words.
Show answer
The forecast is that container volumes at the terminal will grow moderately over the next three years. It depends on the condition that regional trade patterns remain broadly stable, so a shift in those patterns would put the forecast itself in question. - Identify the passage's risk and its proposed mitigation, and explain the limitation placed on that mitigation.
Show answer
The risk is that yard storage capacity could become a limiting factor sooner than planned if growth accelerates beyond current projections. The proposed mitigation is temporary off-site storage arrangements, but the passage limits it explicitly: those arrangements are considered manageable only in the short term and are unlikely to stay cost-effective if volumes keep rising sharply over a longer period. - Identify the sentence that leaves a question explicitly unresolved, and explain why the author chose not to answer it.
Show answer
The final sentence, stating that it remains unclear whether planned yard expansion will be completed in time to address a high-growth scenario, leaves the question open. The author cannot answer it because the outcome genuinely has not been settled yet, an honest acknowledgment of epistemic uncertainty rather than a guess dressed up as a conclusion. - Explain why summarising this passage as "the terminal will run out of storage space" would overstate what the author actually claimed.
Show answer
The passage only says storage capacity "could become a limiting factor" and only under the condition that growth accelerates beyond current projections, plus it names a mitigation already in place. Turning that conditional, hedged possibility into a flat future certainty erases both the condition and the mitigation, which is exactly the kind of silent upgrading this lesson warns against.
Next: Lesson 67 — Advanced Reading of Definitions, Rules, Exceptions & "If and Only If": how to read conditional language by its logical direction, telling "if," "only if," and "if and only if" apart with precision.