When Should I Write 'Because' Instead of 'If' Inside a Proof?

Halfway through writing a direct proof, you reach for a connective word. "Because n is even, n = 2k" or "if n is even, n = 2k" — both sound okay aloud. But inside a proof, these two words mean very different things, and choosing the wrong one can quietly turn a valid argument into an invalid one.

The rule in two words: "because" gives a reason for a statement you are asserting as true right now; "if" introduces a hypothesis you are not yet asserting — you are only exploring what would follow supposing it held. Pick the word that matches which of these you are doing.

The two connectives, side by side

Think of each line in a proof as a claim being asserted as true at that moment. The next line then builds on it. Everything you write is either:

An assertion — "this is true now, given what I have established so far." The word you use to justify it is because, since, as, or by (as in "by definition," "by the Pythagorean theorem").
A hypothetical — "suppose for a moment that this holds, and watch what happens." The word that introduces it is if, suppose, assume, or let.

Assertions stay on the table for the rest of the proof. Hypotheticals are conditional — the lines that depend on them only hold within the scope of the "if," and the conclusion you reach under a hypothetical is itself a conditional statement, not an unconditional one.

Why the distinction matters: a direct proof of "if P then Q" opens with a hypothetical ("assume P" — you are not asserting P is unconditionally true), then proceeds with assertions ("because P, we have R_1"; "since R_1 and the definition of divisibility, we have R_2"). If you write "if" where you mean "because," your reader cannot tell whether you are advancing the argument or opening a new hypothetical — and if the rest of the proof treats a hypothetical line as a firm fact, the whole argument collapses.

A miniature example of each

Correct use of "because":

Assume n is even. Because n is even, by definition n = 2k for some integer k. Then n^2 = (2k)^2 = 4k^2 = 2(2k^2). Because 2k^2 is an integer, n^2 is even.

Every "because" justifies a firm assertion. The hypothesis "n is even" was already introduced at the start by "Assume"; subsequent lines simply draw consequences from what is now on the table.

Correct use of "if":

If n is even, then n = 2k for some integer k, so n^2 = 4k^2 is even. If n is odd, then n = 2k + 1, so n^2 = 4k^2 + 4k + 1 is odd. In either case, n^2 has the same parity as n.

Here "if" opens a case. Neither case is asserted — the reader knows that one of them holds, but not which. The proof runs through both conditionally, then combines the two conditional conclusions.

Misuse (broken proof):

Assume n is even. If n = 2k for some integer k, then n^2 = 4k^2 is even.

This says "supposing n = 2k, then n^2 is even." But the step "supposing n = 2k" is not an unconditional move from the hypothesis "n is even" — it is a second layer of hypothetical. The reader does not know whether the rest of the proof is building on "n is even" or on "n is even and also n = 2k." The right word is because (the definition forces n = 2k, so the step is an assertion, not a conditional).

The flow view

A *because*-chain extends the firm part of the proof — every box is an assertion that stays on the table. An *if*-chain opens a conditional scope — the boxes inside the dashed section are only conditionally true, and any conclusion reached inside is itself conditional.

A useful test: can the line be removed if what came before is false?

To check whether a line should be introduced with "because" or "if," ask: can I assert this line unconditionally, given what I have already established?

If yes → it is an assertion. Use because, since, as, or by.
If no — it is a new supposition that does not follow from what is already on the table → it is a hypothetical. Use if, suppose, assume, or let.

Applied to the broken example: "n = 2k for some integer k" does follow unconditionally from "n is even" (that is exactly the definition of even). So it is an assertion, and the right word is because. Writing "if" made it look like an extra layer of supposition — logically spurious, and also confusing to read.

When you genuinely need "if" inside a proof

"If" is not forbidden inside a proof — it is essential in three situations.

Case analysis. "If n is even, then...; if n is odd, then..." — you are handling each case conditionally, then combining the conditional conclusions.
Proving an implication as a lemma mid-proof. If your larger proof requires a helper claim of the form "if A then B," you may open a sub-hypothetical: "if A, then... so B." Everything inside that sub-block is conditional on A; once you close it, you have established the implication and can now use it as an assertion.
Setting up a proof by contradiction or contrapositive. The opening move is a hypothetical: "suppose n is not odd; then n is even, so..." The whole proof lives inside that supposition until the contradiction appears.

Outside these situations, "if" inside a proof is usually a symptom — either you meant "because," or you are opening a hypothetical without realising it.

The short summary

Because / since / as / by → the line is a firm assertion that follows from what is already established.
If / suppose / assume / let → the line opens a hypothetical scope, and everything derived inside is conditional.
To choose between them, ask: can I assert this unconditionally right now?
"If" is legitimate for case analysis, sub-lemmas, and contradiction setups — and suspect everywhere else.

The payoff is a proof your reader can follow without guessing which lines are firm and which are provisional. That is half of what good proof writing actually does.