Shaping — increasing or decreasing stitches to create a sleeve taper, a raglan line, a triangular shawl, a fitted waist — is where row counting stops being a simple background task and becomes something that actively determines whether the finished piece fits or looks right. A plain rectangle can absorb a miscounted row without much visible consequence. A raglan increase happening on the wrong row throws off the whole geometry of the piece it's shaping.
The reason shaping rows are harder to track than plain rows is that they genuinely require two separate numbers held simultaneously: which row you're on (to know whether this is a shaping row or a plain row), and how many stitches are currently on the needle (to confirm the shaping has actually happened correctly so far). Most row-counting mistakes in shaped garments come from dropping one of these two numbers while focused on the other.
Why "every fourth row" instructions are a common failure point
A lot of shaping instructions follow a repeating pattern — 'decrease 1 stitch at each end every 4th row, 6 times' is a typical sleeve taper instruction. This kind of instruction requires tracking your position within the 4-row repeat, not just a raw row count. It's easy to lose track of whether you're on shaping row 1, 2, 3, or 4 of the current repeat, especially if you set the project down mid-repeat and come back later.
The safest approach is to explicitly track both numbers separately: the row count overall, and a secondary count of how many shaping repeats you've completed so far. If your row counter shows row 37 and you know shaping happens every 4th row starting from row 5, a quick check — is 37 minus 5 evenly divisible by 4 — tells you whether this is a shaping row without needing to recall anything from memory. Writing that starting-row number down at the beginning of the shaping section, rather than trying to remember it forty rows later, removes a surprising amount of the guesswork.
Using stitch count as a built-in error check
The single best tool for catching a shaping mistake before it compounds is the stitch count itself, because most shaping instructions tell you exactly how many stitches you should have at specific checkpoints — 'you should now have 54 stitches' after a set of decreases, for example. If your actual stitch count doesn't match what the pattern expects at a checkpoint, that's an immediate, unambiguous signal that something went wrong somewhere in the last stretch of rows, and it's much easier to backtrack a few rows and find the error than to discover a mismatch only at seaming time, several inches later.
This is exactly why tracking rows and stitches together, rather than just rows alone, matters more during shaping than at any other point in a project. A counter that only tracks row number tells you where you are chronologically, but says nothing about whether the shaping itself has actually happened correctly — you need both numbers side by side to catch a dropped increase or an accidental double decrease before it becomes a visible flaw in the fabric.
A habit that prevents most shaping errors
Increment your row and stitch counts at the same moment, right after finishing the row, rather than counting rows as you go and stitches only when the pattern happens to prompt a checkpoint. This keeps the two numbers permanently synchronized, so a discrepancy shows up the moment it happens rather than several rows later when it's harder to trace back to its source.
It's also worth reading one row ahead before starting it on any shaping section, specifically to confirm whether the row you're about to work is a shaping row or a plain row, rather than starting to knit and only checking the pattern partway through. A moment of confirmation before the row costs almost nothing; unpicking a misplaced decrease costs considerably more.