Determinant evaluation
Every square matrix hides a single number that tells you a great deal about it — whether the matrix can be inverted, whether a system of linear equations has a unique solution, even the scaling factor of the transformation it represents. That number is the determinant, and evaluating it is a core ISC Class 12 skill: expanding a or array of numbers into one value using minors and cofactors. Done by brute-force expansion, a determinant needs three minors, six multiplications, and a sign pattern that trips up careless students. But determinants obey a set of algebraic properties — swap rows and the sign flips, add a multiple of one row to another and nothing changes — that let you manufacture zeros first and expand almost for free afterwards. This article builds the expansion formula, proves why the row-operation trick is legal, and works a full example both the slow way and the fast way, so you can recognise which approach an exam question is rewarding.
A determinant is evaluated by cofactor expansion along any row or column, and the row/column operation leaves its value unchanged, so simplifying with zeros before expanding is almost always faster than expanding raw.
The core idea
The case is the building block. For a matrix, the determinant is the product of the leading diagonal minus the product of the other diagonal:
where: are the matrix entries in row-then-column order. Every expansion reduces to several of these.
The case expands along a row or column using cofactors. The cofactor of entry is , where is the minor left after deleting row and column . Expanding along the first row,
where: each bracketed array is the minor obtained by striking out the row and column of the entry it multiplies, and the alternating signs are exactly the cofactor signs for the first row (, ). The same formula works along any row or any column — a smart choice of row or column (one with a zero already in it) cuts the arithmetic down immediately.
Five properties do most of the work in exam problems.
- Interchanging two rows (or columns) changes the sign of the determinant.
- If two rows (or columns) are identical or proportional, the determinant is zero.
- Scaling every entry of one row (or column) by scales the determinant by ; scaling the whole matrix by scales the determinant by , so .
- Adding a scalar multiple of one row (or column) to another leaves the determinant unchanged — written . This is the main simplification tool.
- , and for square matrices of the same order.
The sign grid below is worth memorising cold, since a plus/minus slip on the middle cofactor is the single most common arithmetic error in this topic.
Why row operations do not change the determinant
The claim leaves a determinant unchanged is used constantly, but it is worth proving rather than trusting blindly, since seeing why it holds is what stops students from misapplying it to operations that also scale a row, which is a genuinely different and value-changing move.
Step 1. Take a general determinant and expand it along the row that will be modified, say row 2, using the cofactor formula: , where are the cofactors built from rows 1 and 3 only — they do not involve row 2 at all.
Step 2. Apply , so the new row 2 entries become . Expand the new determinant along this same row: , using the same cofactors , because those cofactors are built only from rows 1 and 3, which have not changed.
Step 3. Expand the brackets and regroup: . The first bracket is exactly from Step 1. The second bracket, , is row 1's entries multiplied by row 2's cofactors — this is the expansion of a determinant with row 1 repeated in both row 1 and row 2, which is zero by the identical-rows property.
Step 4. So . The operation genuinely leaves the determinant unchanged, and the proof shows exactly why: it only works because the row being added is a different, untouched row, and the row being changed is not simultaneously being scaled. If instead you write , the row-2 part is scaled by first, and the determinant scales by that factor before the zero-sum cancellation applies — which is precisely the trap flagged below.
Worked example
Evaluate first by direct cofactor expansion along the first row, then re-derive the same value using row operations to confirm both methods agree.
Step 1 — direct expansion, find the three minors.
Step 2 — apply cofactor signs and combine with row-1 entries.
So direct expansion gives .
Step 3 — now simplify with row operations instead. Apply and to create zeros in the first column (these are legal by the proof above, since row 1 is untouched and unscaled):
Step 4 — expand the new determinant along the now-mostly-zero first column.
Both routes agree: the determinant is . Direct expansion needed six multiplications across three minors; the row-operation route needed two operations to create zeros but then only a single minor to finish — the trade-off worth recognising in an exam.
Common traps
- Forgetting the alternating sign pattern when expanding — a plus/minus slip on the middle term is the single most common arithmetic error.
- Writing a row operation like and forgetting this scales the determinant by as well as combining rows — only pure operations , with no scaling of itself, leave the determinant unchanged.
- Mixing row and column operations mid-calculation — pick one style and stay consistent within a single simplification.
- Assuming — this is false in general; determinants are not additive over matrix addition.
Ask the tutor: ask the AI tutor for a fresh determinant and try spotting the fastest row or column operation before you expand.
Why does row operation R sub i to R sub i plus k R sub j leave the determinant unchanged, but scaling a row by k does not
Adding a multiple of another row splits, by linearity of the cofactor expansion, into the original determinant plus a second determinant that has two proportional rows — and that second piece is always zero, so nothing actually changes. Scaling a row is a genuinely different operation: it multiplies every cofactor term in that row's expansion by k, so the whole determinant scales by k. The two operations look similar on paper but only the additive one is "free."
Is it always faster to use row operations instead of direct cofactor expansion
Not always. Row operations pay off when you can spot a multiplier that produces a whole-number zero quickly, especially when a row or column already starts with a 1. If the entries are awkward and no clean multiplier is visible, direct expansion along whichever row or column already has the most zeros is often just as fast and less error-prone, since you avoid an extra layer of arithmetic.
How do I decide which row or column to expand along when none of them have zeros
Expand along whichever row or column has the smallest or simplest numbers, since that minimises the size of the products you compute, and consider doing one quick row operation first to manufacture a zero before committing to full expansion. There is no rule that you must use row 1 — the formula works identically along any row or column, so choose for convenience.