Astraware Sudoku - It's a different kind of Zen

Solving Sudoku : Forcing Chains

This technique (thankfully!) is quite easy to understand, but can take quite some time to work out within a puzzle. This is a technique where having a separate copy or notepad overlay really helps, because you'll be making lots of notes!
A simple forcing chain is when you have lots of cells with just 2 candidates - and whichever value you would choose for one cell forces another cell to be just one of its two values. (It'll be clearer with an example!)

The First Choice

Take a look at this puzzle, which shows an example of a forcing chain.
It doesn't matter which value - 1 or 2 - was in the top cell (at coordinate C3,R1), they would force the value 5 into the other cell (C1,R4).

Now before starting, its worthwhile mentioning that some of these chains can be short, and sometimes they can be quite long! This example has one of each.

First of all, imagine if the top cell is a 1. This in turn would force the {14} a few cells below it to be a 4, and so on. Can you follow the chain?





So, the 1 forces the 5:




The Second Choice

Now start again, but instead of a 1, this time make the top cell a 2.
Again crossing out the values which get ruled out - you'll see its quite a long chain!

Here's what it looks like with the arrows...

The two chains have different paths starting with each of the two values for the first cell, but either one means there'll be a 5 in the second cell.
As soon as you find a situation like this, even though you don't know what the first cell will be, you definitely know the value in the second cell, so you can write it in!

Is this the same as guessing?

Not quite - what you're doing is simultaneously looking at the implications of either choice, and seeing if any other cells will turn out the same whichever your choice would be. If you were to have just guessed one, and worked from there, you would actually fill in the same result for the second cell, but depending on whether you guessed correctly or not, you might have made a whole batch of mistakes on the way.

Can this one get harder too?

What makes this method hard is that you might have to follow chains a long way, and you will have a lot of testing to do. Longer chains don't make it conceptually any harder, but they do make it more likely that you'll make mistakes along the way.

Sticking to working with just the pairs generally keeps it fairly simple, but there's nothing stopping you considering the effects of triples or other techniques as you go!


Tip: When using an overlay (tracing paper or computer overlay), here's a method which makes finding the chains a bit easier.
Pick your starting cell, and make a small u shape (a little smiley curve) underneath the first pencilmark. From there, look around, but instead of crossing out pencilmarks (otherwise it gets too messy!), when you find a value that it forces somewhere else, put the same u shape underneath the forced value. Ignore any that the first choice eliminated - you might need them later!
Carry on doing this until you can't make any more "u" forces.
Now choose the second value in your original cell - and this time put a little "n" symbol (a downturned mouth) above the second pencilmark. Like before, look at the implications and forces that this makes, continuing on until you can't find any more.
If there's a forcing chain, at some point you'll find a pencilmark with both a "u" and "n" on the same mark (in which case they'll almost join up!). When you see this its a sure sign that whichever candidate you picked for the first cell, you've found the right value for the second cell. Fill in that value, because it means you don't need to look any further!
Some people use colours to make it easier too - but it isn't essential.

NOTE! This example has an error!

A number of people have been in touch to say that they've seen an error in the example above, and most of them are right! Since you'd have to understand the concept of forcing chains to see where the error lies, this example is still somewhat valid as a learning example, even if it isn't correct. If I get time, I'll put together a different (and hopefully correct) example!

Thanks for spotting this error, and wanting to let us know, but now that we know, please don't get in touch to tell us about the error - the pages of weird numbers and brackets they get by email only scare the customer support team! Thanks!