Scope

Every contractor did not sign the waiver.

Two people can hear that sentence in the same meeting and leave with incompatible beliefs. One hears nobody signed and starts drafting a stop-work notice. The other hears not everybody signed and goes looking for the two stragglers. Neither of them has misread a word. The sentence genuinely has both readings, and English supplied no signal about which was meant.

What differs is scope — which operator is evaluated inside the other. Take every contractor first and negation applies once per contractor: for each one, that contractor did not sign. Take negation first and it applies to the whole quantified claim: it is not the case that every contractor signed. One string, two structures, and until the structure is fixed the sentence is not a premise anyone can use.

Operators and reach

An operator takes some content and changes how it contributes to the whole. Quantifiers — every, some, no, most, exactly two — say how many members of a set satisfy a condition. Negation flips truth. Modals such as must and may evaluate a claim against a range of alternatives. Only excludes alternatives. Conditionals sort material into an antecedent or a consequent.

The scope of an operator is the material it governs. Put two operators in one sentence and you usually get two nestings, which I will write like this:

every > not: for every contractor, that contractor did not sign.
not > every: it is not the case that every contractor signed.

Read the notation as order of interpretation, not order of words. English leans toward surface order, but intonation, lexical choice, plausibility, and syntax all push against that lean, producing inverse scope, where an expression appearing later is interpreted more widely.

The working rule is unglamorous and effective: when a sentence carries more than one operator, enumerate the nestings before relying on it. Different nestings can reverse an obligation, shift a duty from one party to another, or turn a single shared object into many separate ones. Those are not shades of emphasis. They are different claims about the world.

Two quantifiers

Every analyst reviewed a report.

every > a: for each analyst, there is some report that analyst reviewed. The reports may all be different.
a > every: there is one particular report that every analyst reviewed.

The entailment runs one way only. If a single report was read by all of them, the distributed reading is automatically satisfied. Go the other direction and it fails: three analysts reading three different reports make the first reading true and the second false. So the wide-indefinite reading is the strictly stronger claim, and it is the one people quietly assume when they are reasoning about consistency of review.

Indefinites take wide scope unusually easily. “A technician inspected every unit” most naturally describes one technician working through all the units, yet in the right context it describes a possibly different technician per unit. English will not tell you which. Your rewrite has to: the same report, a possibly different technician, or the fully explicit “each analyst reviewed at least one report; the reports need not be the same.” Three extra words buy a determinate meaning.

Distributive and collective readings

Multiplicity has a second source that is easy to mistake for scope. A predicate can apply to members of a group one at a time or to the group as a unit:

“The inspectors lifted the panel” — each of them lifted it, or they lifted it together, and the difference may be the entire safety question.
“Two departments spent $1 million” — a million each, or a million between them.
“The team surrounded the building” — collective only. No individual member surrounded anything.

A number stated without a per what is not yet a specification. “Users may submit two references” sets either a two-reference allowance for each user or a total cap of two across all users. Common sense favors the first; a system will eventually implement exactly one, and it may not be the one you meant. Write “each user may submit up to two references” or “at most two references may be submitted in total,” and the question never reaches the implementer.

Negation against quantifiers

Four forms that look like variants of one another, and are not.

“Not every test passed.” Negation is outside every. At least one test failed; the rest may all have passed. This is the weakest of the four.

“No test passed.” No bundles quantification and negation together: there is no test that passed. That is compatible with every test failing, but also with tests being skipped or never completing, unless the available outcomes have been restricted to pass and fail.

“Some test did not pass.” At least one non-passing test exists. In classical two-valued quantifier logic this is equivalent to “not every test passed,” and both come out false if there were no tests at all — a vacuously true every has no counterexample to report. The some version puts the counterexample in the foreground and is much harder to misread in operational prose.

“All tests did not pass.” Avoidably unstable. Some readers take all wide and hear none passed; others take negation wide and hear not all passed. There is no defensible reason to write this sentence. Use “no test passed” or “at least one test failed,” depending on which you mean.

Negation also cares about where it attaches inside the clause:

“Maya deliberately did not respond” — a deliberate omission.
“Maya did not deliberately respond” — denies deliberateness, leaves an accidental response wide open.
“The service is not always available” — there are gaps.
“The service is always not available” — there is nothing but gaps.

Nothing changed but the position of the negative, and in each pair the two sentences can differ in truth value.

Modals and scope

A supervisor must approve every refund.

Three structures compete here:

One particular supervisor is required to approve all refunds — a personal duty on an identified person.
For each refund, some supervisor or other must approve it, and the supervisor may vary.
The organization must arrange supervisory approval, with no personal duty falling on any individual supervisor at all.

These have different consequences the first time a supervisor is on leave. The sentence never settles whether the same person is required across refunds; “every refund requires approval by at least one supervisor, and the approving supervisor may vary” does, in one line.

Negation gives the modal contrast that most often causes real damage:

“You must not disclose the key.” Disclosure is prohibited — must > not.
“You do not have to disclose the key.” Disclosure is not required, and you may disclose if you like — not > must.

Must not is not not must. Read one as the other and you have converted optional conduct into forbidden conduct, or a prohibition into a free choice.

May not is worse, because it holds both readings without any signal:

prohibition: you are not permitted to disclose it.
possible absence: perhaps you will not disclose it.

Contracts use may not almost exclusively for prohibition; ordinary predictive prose uses it for uncertainty. When a reader has to guess which register they are in, write “is prohibited from” or “might not” and take the guess away.

Only and focus

Only excludes alternatives to whatever it associates with — and what it associates with is set by focus, which speech marks with stress and writing frequently does not mark at all. One clause, three claims:

“Only Dana approved the release.” Dana approved it, and no other relevant person did.
“Dana only approved the release.” Among the relevant actions, approval is what she did — she did not authorize, draft, or distribute it.
“Dana approved only the release.” She approved nothing else on the relevant list.

Moving only next to its intended target helps and does not fully solve the problem, because the set of relevant alternatives is still supplied by context. When the distinction matters, name the alternatives being excluded rather than trusting placement to carry them.

Combine only with negation and the claims separate further:

“Not only Dana objected.” At least one other person objected.
“Only Dana did not object.” Everyone relevant except Dana objected.
“Dana did not only object.” She objected and did something else besides.

Three sentences built from the same handful of words, and no two of them are paraphrases.

Numerals and hidden bounds

On a common analysis, bare numerals carry an at least core with an exactly reading supplied by context; other analyses build exactness into some uses directly. Either way, usage shifts. “I have two children” is heard as exactly two, because a speaker with three would normally have said so. “You need two signatures” usually means two are sufficient, with a third harmless.

Rules are where the gap starts costing something:

“The panel consists of three members” conventionally fixes the total at three.
“Three members may approve the motion” typically sets a threshold: three or more suffice.
“Submit two references” gets implemented as a hard cap in one system and a minimum in another, and both implementers will insist they read it correctly.

Exactly, at least, at most, no more than, one or more — when a boundary governs behavior, spend the word.

Pronouns and dependent readings

Every manager reviewed their report.

The pronoun normally covaries with the quantifier: each manager reviewed the report belonging to that manager, so there are as many reports as managers. It need not denote one group-owned document, though it can. The dependency is invisible in English because singular they and plural their are spelled the same, so nothing on the page distinguishes one report from many.

A reviewer told every author that they had made an error.

Here they can pick out the reviewer, each author individually, the authors collectively, or some other salient group — and the choice interacts with whether one reviewer or many is in play. Repeating the noun (“that the author had made an error”) reads slightly heavier and prevents a materially different attribution of blame. That is a good trade.

Scope islands

Not every logically imaginable nesting is grammatically available, which is a relief. Relative clauses, coordinate structures, and certain other constituents act as scope islands: an operator inside them resists being interpreted outside them. “A reviewer who read every report resigned” does not normally mean that for each report, a possibly different reviewer of it resigned. The indefinite is trapped inside a subject phrase whose structure limits its reach, so the natural reading is one reviewer who read everything.

Context suppresses readings too. World knowledge makes “Every student carried a backpack” strongly distributive — the communal backpack is available and absurd. But legal and technical reading cannot lean on plausibility the way conversation does, because a literal implementer or an adversarial counterparty will happily take the reading everyone else dismissed.

Three requirements, worked

“Each request must receive an approval from a manager.” Scope will not tell you what this means; it tells you what the sentence failed to say. May different requests have different managers? Is one approval a minimum or an exact count? Does a manager mean anyone holding the role at approval time, or a specific assigned manager? And who bears the duty — the requester, the system, or the managers? Four open questions in nine words.

“No user can delete every backup.” Two readings are structurally available, though the first is much more natural. On no > every, no individual user has the ability to delete all backups, which leaves each user potentially able to delete some. On the inverse every > no reading, each backup is something no user can delete. Write “no single user can delete all backups” for the first and “users cannot delete any backup” for the second; neither rewrite is ambiguous.

“The service must archive every record before a user deletes it.” The pronoun it makes deletion record-dependent, so far so good, but a user leaves the actor open and before leaves the trigger open: archive before any user could possibly delete, or before the actual deletion event? The testable version names the unit and the trigger together: “For each record, the service shall complete archival before permitting any user to execute deletion of that record.”

Scope analysis is finished when every operator has a stated reach, every quantity has a unit, and every dependency answers one question — the same one, or possibly a different one? Short of that, prose that looks precise can specify two incompatible systems at once, and the disagreement will surface long after everyone has signed.