How to check stitch counts in a crochet pattern before testers see it

By Ali Lehrman · October 5, 2026

Check two numbers for every round, not one. First, how many stitches the round uses up, which has to match the count of the round before it. Second, how many stitches it makes, which has to match the count you wrote at the end. Most designers only check the second. A round can end on the right number and still be written wrong, and checking only the total will never catch it.

The round that ended on the right number

One of my patterns had this line in the head:

Rnd 43: (6 dec) * 6 (6)

The count at the end is right. Six stitches is exactly where the head should close. The instruction is not. “(6 dec) * 6” is six decreases, six times. That is 36 decreases, which needs 72 stitches to work into, and the round before it only had 12.

What I meant was “(1 dec) * 6.” Twelve stitches in, six out.

And because I reused that head section, the typo came along with it into a second pattern before I caught it. That is the part worth remembering. A copied section carries its mistakes with it, and a total that looks right is the one you never look at twice.

The check: what a round uses and what it makes

Every stitch does two things. It uses up stitches from the round below, and it makes stitches in the round you are working. Most of the time those are the same number, which is why it is easy to forget they are two different things.

That last row is how I count joins in amigurumi. Some designers count them differently. It does not matter which way you go, as long as the pattern does it the same way every time.

A repeat multiplies everything inside it. “(2 sc, 1 inc) * 6” uses 3 stitches and makes 4, six times over: uses 18, makes 24.

Then for each round, two questions:

1. Does what it uses equal the count of the round before? If not, the instruction is wrong, or the previous count is.
2. Does what it makes equal the count you wrote? If not, the instruction is wrong, or the count is.

Worked example

Here is a decrease round from one of my patterns, worked after a round of 26:

Rnd 6: 5 sc, (1 dec, 2 sc) * 4, 5 sc (22)

Uses: 5, then the repeat is 2 + 2 = 4, four times is 16, then 5. That is 26, and the round before was 26. Good.

Makes: 5, then the repeat is 1 + 2 = 3, four times is 12, then 5. That is 22, and the count says 22. Good.

A harder one, with increases and decreases in the same round, after a round of 15:

Rnd 20: (1 dec, 1 sc) * 2, 1 sc, 3 inc, 5 sc (16)

Uses: the repeat is 2 + 1 = 3, twice is 6, then 1, then 3, then 5. That is 15. Good.

Makes: the repeat is 1 + 1 = 2, twice is 4, then 1, then 6, then 5. That is 16. Good.

Now the one from the top, after a round of 12:

Rnd 43: (6 dec) * 6 (6)

Uses: 6 decreases is 12, six times is 72. The round before was 12. That is where it falls apart, even though the 6 at the end is fine.

Where counts actually go wrong

Counts rarely go wrong on a plain round of sc. They go wrong in a handful of places, and these are the ones I slow down for:

• Repeats. Check the multiplier, and check what is inside the brackets. A number in the wrong place, like the 6 above, multiplies the mistake.
• Copied sections. A head, a set of legs, an arm you reuse across patterns. Check it again in the new pattern. It is not checked just because it was fine last time, and it may not have been.
• The round after an edit. Change a count on round 14 and round 15 now uses the wrong number. The edited round looks fine. The next one is the one that broke.
• Spans. “Rnd 8 – Rnd 21: 9 sc [14 Rounds] (9)” is fourteen rounds that each use 9 and make 9. Check the round before the span and the round after it. That is where a span goes wrong.
• Joining pieces. When a round works across two pieces at once, like joining the legs to start the body, its count comes from both pieces. In one of my dolls each leg ends on 20, and the joining round works 20 stitches around each leg plus a chain of 3 between them, worked on both sides, for 46. Change the legs to end on 22 and that round is wrong, even though you never touched it.
• Chains inside a round. Decide whether they count, write it down, and stick to it.

What testers will and will not catch

Testers catch a lot. A count that does not work usually shows up when someone gets to the end of the round with stitches left over, or runs out early.

But a tester catches it in their yarn, after they have worked it, and only if they notice. Some people fudge a stitch and keep going. Some assume the mistake was theirs. And a test round is not the time to find something you could have found with a pencil, because testers are not tech editors. Their time is better spent on the things you cannot see from inside your own pattern.

So the count check happens before anything leaves my hands. Here is the rest of the list I run, including photo numbers and the stitch key.

What I used to do

Honestly, I would paste my pattern into an AI chatbot and see if it could catch any errors. Often the errors it found were unfounded. But sometimes it would find actual errors.

The problem was it had nothing to reference. No crochet or knitting rules to check against first. No way to know about a stitch I had defined myself. And it obviously could not fix anything for me. So the rest of my checking was waiting to see if testers found errors.

How I do it now

I think every designer should be able to do the check above by hand. I just do not do it by hand on every round anymore.

I write my patterns in NodeStitch, and before a pattern goes out I run Pattern Review on it. It flags stitch count errors where a round’s count does not follow from the round before it, mixed count styles like (12) on one line and [12] on the next, rounds numbered out of order, and abbreviations that are not in my stitch key. It flags them. I still go read the round and decide what is wrong.

The difference from the chatbot is that it works from rules. It reads rounds in pattern mode, where each line is a numbered round, an inc uses one stitch and makes two, and chains inside a round count as stitches. If you invent a stitch, you can define how many it uses and makes in your stitch key and it counts it your way.

The catch: Pattern Review is on the paid plan, and a free account gets three tries at it. Building the pattern itself is free.

The short version

1. For every round, check what it uses against the round before.
2. Check what it makes against the count you wrote.
3. Multiply repeats out. Do not eyeball them.
4. After any edit, check the next round too.
5. Treat a copied section as new.

The total at the end of a round is the number everyone checks. The instruction in front of it is where the mistake usually is.