TOEIC Link Writing Modal Verb and Degree of Certainty Calibration: Saying Exactly How Sure You Are

A modal verb is the single word in a sentence that tells the reader how sure you are. "The shipment will arrive Monday," "should arrive Monday," and "might arrive Monday" describe the same event but make three completely different commitments — a certainty, a strong expectation, and a real possibility. In TOEIC Link Writing, the modal is where certainty is calibrated, and a miscalibrated modal misinforms the reader as surely as a wrong fact does: it promises something you cannot deliver, or it hedges something you are sure of, and in both cases the reader plans around the wrong level of confidence.

The reason modals get miscalibrated is that writers choose them by tone rather than by truth. "Will" feels confident and helpful, so it gets attached to forecasts that are actually uncertain; "might" and "could" feel safely cautious, so they soften statements the writer is really quite sure of. Meanwhile the obligation modals — "must," "should," "have to" — get swapped for one another as if they were interchangeable politeness levels, when they actually encode different strengths of requirement. Fixing modals means treating each one as a precise instrument for reporting certainty or obligation, and matching it to the reality rather than to the mood you want to project.

This article is the modal-calibration discipline for TOEIC Link Writing. The guide covers the certainty ladder from "will" down to "might" and what each rung commits you to, the obligation and permission modals that set expectations, the past-modal forms that express deduction and hindsight, and the proofreading pass that checks every modal against how sure you actually are.

The certainty ladder and what each rung commits you to

Certainty modals form a scale, and using one is a claim about where you sit on it. Knowing the rungs lets you pick the level you can actually defend.

"Will" and "won't" claim near-certainty. "The report will be ready by Friday" is a commitment, not a hope — it tells the reader they can plan around Friday. Reserve "will" for outcomes you are prepared to stand behind, because a reader treats it as a promise. Attaching "will" to a genuinely uncertain forecast is the most common overclaim in business writing, and it costs credibility the moment the outcome slips.

"Should" and "ought to" claim a strong expectation with a margin. "The report should be ready by Friday" says you expect Friday but are leaving room for a delay — it is confident without being a guarantee. This is the honest choice for forecasts that are likely but depend on something outside your control. The gap between "will" and "should" is exactly the gap between a promise and a well-founded expectation, and choosing the right one tells the reader how much to rely on the date.

"May," "might," and "could" claim genuine possibility. "The report might be ready by Friday" says Friday is possible but far from settled — the reader should not plan around it. These modals are correct when the outcome is truly open, and they are a disservice when used to hedge something you are actually sure of, because they push the reader toward unnecessary caution. Downgrading a certainty to a "might" out of politeness is as much a miscalibration as inflating a possibility to a "will." Calibrating this scale is a form of the stance control described in tone and register control, where the writer's degree of commitment is itself part of the message.

Adverbs fine-tune the modal but must not contradict it. "The report will definitely be ready" and "might possibly be ready" pair the adverb with the modal's level, but "will possibly" and "might definitely" fight themselves — a certainty modal with an uncertainty adverb sends two conflicting signals. Keep the adverb on the same rung as the modal, and use adverbs to sharpen the level, not to muddy it.

The obligation and permission modals that set expectations

A second family of modals is not about certainty but about requirement and allowance, and confusing their strengths sets the wrong expectation about what someone has to do.

"Must" and "have to" state a hard requirement. "All expense reports must be submitted by the fifth" leaves no room for choice — it is a rule with consequences. Reserve these for genuine obligations, because a reader treats "must" as non-negotiable. Softening a real requirement to "should" tells the reader compliance is optional when it is not, and a missed hard deadline dressed as a suggestion is a failure the writer caused.

"Should" and "ought to" state a recommendation. "You should include the vendor's reference number" advises without commanding — it is the right strength for best practices and strong suggestions that are not strictly mandatory. The line between "must" and "should" is the line between "or there are consequences" and "because it is a good idea," and picking the wrong one either over-commands or under-warns.

"Can," "may," and "could" grant permission or state ability. "You may submit the form electronically" grants an option; "you can reach the team at extension 4" states a possibility available to the reader. In formal register, "may" is the more precise permission modal and "can" leans toward ability, though "can" is widely accepted for permission in everyday business writing. Keeping requirement, recommendation, and permission distinct is part of the precision that vocabulary precision and collocation discipline applies across the whole sentence — the exact word carries the exact meaning.

The past-modal forms for deduction and hindsight

Modals combine with "have + past participle" to reason about the past, and these forms are where writers most often build a broken construction.

"Must have," "might have," and "could have" express degrees of deduction about the past. "The vendor must have shipped it already" is a confident inference; "might have shipped it" is a tentative one. These forms let you report a conclusion about something you did not witness, calibrated to how certain the evidence makes you. The structure is fixed — modal plus "have" plus past participle — and dropping the "have" ("must shipped") or using a base verb ("must have ship") breaks it.

"Should have" and "ought to have" express hindsight and unmet expectation. "The report should have been ready by Friday" says it was expected but was not — it names a gap between expectation and reality without assigning blame. This is the precise form for a post-mortem observation, and it pairs naturally with the counterfactual reasoning covered in conditional and hypothetical construction precision, where "would have" reasons about a past that did not happen.

"Would have" belongs to hypothetical past results, not to plain past events. "We would have proceeded" only makes sense as the result of an unmet past condition ("if the vendor had confirmed, we would have proceeded"), not as a stand-alone report of what happened. Using "would have" where a simple past ("we proceeded") belongs turns a fact into a phantom hypothetical, so confirm that any "would have" has a real or implied condition behind it.

The proofreading pass that checks certainty against reality

Modals reward a dedicated final read because the error is invisible at the grammar level — the sentence is well-formed but says the wrong thing about how sure you are.

Read every modal and ask whether you can defend that level of certainty. For each "will," ask if you are truly prepared to promise it; for each "might," ask if the outcome is genuinely open or whether you are just hedging. A "will" you cannot back becomes a "should"; a "might" you are actually sure of becomes a "will." This single check catches both overclaiming and over-hedging, the two failures that a well-formed sentence hides.

Check obligation modals against the real consequence. For each "must," confirm there is an actual requirement with a consequence; for each "should," confirm you meant a recommendation and not a rule. If missing the "should" item causes a real problem, it should have been a "must," and downgrading it misinformed the reader about what was mandatory.

Verify past-modal structure and hidden conditions. Confirm every past modal is "modal + have + past participle" with no dropped "have," and confirm every "would have" has a condition behind it rather than standing in for a plain past event. This structural verification is the same targeted final read prescribed in self-editing and revision protocol under time constraint, applied to the one word that carries your certainty.

Bringing it together

Modal calibration in TOEIC Link Writing is the discipline of saying exactly how sure you are, and no surer. It rests on treating the certainty ladder as a scale you choose deliberately — "will" for what you can promise, "should" for what you expect, "might" for what is genuinely open — and never trading the true level for the tone you would prefer to project. It extends to keeping obligation and permission modals distinct, so a requirement reads as a requirement and a suggestion reads as a suggestion, and to building past-modal forms correctly when you reason about what happened or should have. And it ends with a read that checks every modal against reality, asking whether you can defend the certainty you claimed. Get this right, and your reader will always know precisely how much to rely on what you have written — which is, in the end, the whole point of writing it down.