Worked examples — Variable oxidation states — reasons
This page is the practice ground for Variable oxidation states — reasons. The parent gave you the reasons; here we run those reasons through every kind of case you can be asked. Before we start, one promise: nothing below uses a symbol you have not met. If a new number or word appears, it is defined the moment it appears.
The scenario matrix
Every exam question about variable OS is really one of these case classes. We will hit each cell.
| # | Case class | What makes it tricky | Example that covers it |
|---|---|---|---|
| C1 | Lowest possible OS (, lose only ) | why it's so common | Ex 1 (Fe → +2) |
| C2 | One step up () | is the extra -electron cheap? | Ex 2 (Fe → +3) |
| C3 | Maximum OS = all valence e⁻ | uses every electron | Ex 3 (Mn → +7) |
| C4 | Degenerate / dead end (only ONE OS) | filled shell, no variation | Ex 4 (Zn) |
| C5 | The "group-number ceiling" breaks | theoretical vs realised max | Ex 5 (Fe vs group 8) |
| C6 | Sign of decides existence (Born–Haber balance) | must compute, not guess | Ex 6 (numeric energy check) |
| C7 | Partner-atom limit (O/F allow high OS, I⁻ forbids it) | redox self-destruct | Ex 7 (MnI₇ does not exist) |
| C8 | Real-world word problem | assign OS from a formula | Ex 8 (rust / KMnO₄ titration) |
| C9 | Exam twist (find OS in a weird ion) | mixed anions, peroxide trap | Ex 9 (, ) |
Read the matrix as a checklist. When you can do all nine, you can do the whole topic.

The one tool we reuse: the OS-balance rule
Standard partner values we will lean on: oxygen is , fluorine is , hydrogen is (with normal partners). We flag the exceptions (peroxide) when they bite in Ex 9.
Worked examples
Ex 1 — Case C1: the lowest, most common state
Forecast: guess which two electrons leave first — the pair or two of the ? Write your guess before reading.
- Identify the outermost electrons. Fe has two electrons sitting outside the . Why this step? The electrons removed first are the ones highest in energy / furthest out. Once we know which they are, we know the cheapest ionisation.
- Remove the two electrons. This gives , configuration . Why this step? Removing the pair only needs the first two ionisation enthalpies (), which are small for a d-metal (parent's "gradual rise"). See Ionisation Enthalpy of Transition Metals.
- Check the compound . Oxygen is . Rule: . ✓
Verify: , the neutral molecule. Units: a charge count, dimensionless. The state matches the electrons we removed. ✔ (See Stability of +2 and +3 states (Fe, Mn).)
Ex 2 — Case C2: one cheap step up
Forecast: what does the change give the ion? (Hint: think "half-filled".)
- Remove one more electron from . , i.e. . Why this step? Reaching costs the third ionisation enthalpy . We must check it is still "repayable".
- Notice the reward: is half-filled. A half-filled shell is extra stable, so for Fe is not as brutal as it would otherwise be. Why this step? The parent's rule says an OS exists when the ionisation cost is repaid by lattice/hydration energy. Landing on a stable lowers the effective cost — that is the "payback".
- Confirm from . Two Fe, three O: . ✓
Verify: . Neutral. ✔ Both and are real → iron varies its OS, exactly the topic's claim.
Ex 3 — Case C3: maximum OS uses every valence electron
Forecast: how many electrons can Mn possibly give away? Count before reading.
- Count valence electrons. gives 2, gives 5, total . Why this step? The theoretical maximum OS equals the number of electrons — every one that can be engaged in bonding.
- Why all 7 are reachable for Mn. All five electrons are unpaired (one per orbital), so each is accessible without first breaking a pair. Hence max OS . Why this step? Unpaired, accessible electrons are the ones a strong partner like O can pull into bonding — this is why Mn is the peak of the series.
- Confirm from . Charge ; four O at : . ✓
Verify: . ✔ Matches the ion's charge. This is the single most-asked value in the chapter.
Ex 4 — Case C4: the degenerate case (only one OS)
Forecast: how many electrons are easy to remove from Zn?
- Remove the pair. , configuration . Why this step? Same first move as every d-metal: the loose electrons go first.
- Try to go further — you can't cheaply. The next electron would come from the completely filled, very stable . That costs a huge that no lattice/hydration energy can repay. Why this step? This is the degenerate/dead-end cell: a filled shell behaves like the s-block's locked basement — the jump is too big, so the OS is frozen at .
- Conclusion. Max OS , and there is no lower positive stable state, so Zn has a single OS.
Verify: In : . ✔ Consistent, and no with higher Zn OS exists — matching " filled → no variation".
Ex 5 — Case C5: the group-number ceiling breaks
Forecast: will the rule that worked for Sc–Mn keep working? Guess yes/no.
- State the naive prediction. Group theoretical max (give away all 8 valence electrons of ). Why this step? We must write the tempting wrong answer to see where it fails.
- Add the physics that Sc–Mn didn't need. Past Mn the effective nuclear charge rises (more protons, similar shielding), pulling the electrons in tightly and forcing pairing. See Effective Nuclear Charge & Shielding. Why this step? Tightly held, paired -electrons have very high ionisation enthalpies — the cost of the top states can no longer be repaid.
- Result. Fe reaches only in special oxo-anions (ferrate ) and commonly stops at . The realised max is below the group number.
Verify (ferrate ): . ✔ So is the true ceiling, not — the group number is only an upper bound. (This is the exact "mistake" the parent flagged.)
Ex 6 — Case C6: sign of decides existence (numeric)
Forecast: just eyeballing, is the big negative enough to beat the ionisation cost? Guess sign.
- Write the Born–Haber sum (parent's formula, all terms explicit): Why this step? An OS is "stable/occurs" precisely when the whole cycle releases energy — this equation is the existence test. See Born–Haber Cycle & Lattice Energy.
- Plug numbers. Why this step? Each term is a physical step; adding them tells us the net energy cost/release.
- Add. .
Verify: → the state is stable: the lattice energy overpays the ionisation. Units consistent ( throughout). ✔ This is the quantitative version of "does this OS exist?".
Ex 7 — Case C7: the partner-atom limit (why some compounds can't exist)
Forecast: which atom can survive being bonded to a very electron-hungry metal — O or I? Guess.
- Confirm the OS both would demand. In : . In a would-be : . Same OS. Why this step? Shows the difference is not the number — it's the partner.
- Ask who donates the electrons. A metal is fiercely electron-greedy. Iodide is large and holds its electron loosely, so it is easily oxidised to . Oxide is small and holds tightly, so it is not. Why this step? If the anion is oxidised, the metal is reduced back to a lower OS — the high-OS iodide destroys itself.
- The self-destruct reaction (schematic). Any "" would instantly become a lower-OS iodide plus . So only low-OS iodides (e.g. ) are seen, while high OS lives in oxides/fluorides.
Verify: OS arithmetic checks: ; . ✔ High OS with O ✔, only low OS with I ✔ — exactly the parent's "O/F push high, I⁻ keeps it low". (See Acidic vs Basic character of Oxides across OS — is acidic.)
Ex 8 — Case C8: real-world word problem
Forecast: you already met both numbers in earlier examples — predict them, then confirm here in a "real" context.
- Rust. : . Why this step? Rust is iron that has been oxidised by air — its everyday appearance is literally the state from Ex 2.
- Permanganate — strip the spectator. In , K is , so the rest must carry : it is the permanganate ion of Ex 3. Why this step? Splitting off the counter-ion turns a real reagent into the ion whose OS we already solved.
- Mn OS. .
Verify: (a) ✔. (b) for neutral ✔. The strong purple oxidiser owes its power to Mn being at its maximum — real-world variable OS at work.
Ex 9 — Case C9: the exam twist (peroxide trap)
Forecast: if you naively use O everywhere in , you get an impossible OS. Guess what nonsense value that gives, then see the fix.
- (a) Dichromate. . Why this step? The clean case first — sets your expectation that Cr's high state is .
- (b) The naive (wrong) attempt on . If all 5 O were : . Impossible (Cr has only 6 valence electrons). Why this step? Seeing the absurd tells you an assumption is broken — some oxygens are not ordinary oxide.
- (b) The fix — peroxide oxygens. has one ordinary O () and two peroxide units (each , i.e. two O at ). Total negative . Then . Why this step? Reassigning the peroxide oxygens recovers a sensible , consistent with dichromate — the twist tests whether you spot the oxidation-state exception.
Verify: (a) ✔ (matches the ion charge). (b) ✔ (neutral, with two peroxide ). Both give Cr , its stable maximum.
Recall Quick self-test across all nine cells
Assign the metal OS, then name the case class: ::: (C1) ::: (C2) ::: (C3) ::: , only state (C4) ::: , ceiling below group 8 (C5) vs ::: exists, iodide self-destructs (C7) ::: using peroxide oxygens (C9)
Connections
- Variable oxidation states — reasons (parent)
- d-Block Overview
- Ionisation Enthalpy of Transition Metals
- Born–Haber Cycle & Lattice Energy
- Stability of +2 and +3 states (Fe, Mn)
- Acidic vs Basic character of Oxides across OS
- Effective Nuclear Charge & Shielding