TL;DR / Summary: Tap code is learnable in one evening because the grid is only five by five. Learn the two numbers behind each letter, practise with short words, then send one real message before bed — that sequence is enough for basic fluency.
The structure in one paragraph
Letters sit in a five-by-five grid: rows and columns numbered one to five. A letter is two numbers — row first, then column. A is one-one, B is one-two, E is one-five, F is two-one.
Tap the row count, pause, then tap the column count. Two knocks, a gap, one knock means row two, column one, which is F.
That is the whole system. Everything after this is practice and a small amount of vocabulary.
The first ten minutes
Write the grid out by hand. Writing it does more than reading it, because the hand remembers positions the eye skips.
Then tap your own name letter by letter, slowly, without looking at the grid. Look only to check. Most people can do this within five minutes.
A learning sequence
- Minutes 1–5: write the grid, tap your name
- Minutes 5–15: tap five three-letter words from memory
- Minutes 15–30: send and receive with a partner, one word each
- Minutes 30–45: send a six-word sentence, no grid
- Minutes 45–60: receive a sentence you have not seen
An hour is realistic for basic competence. Fluency takes longer, but competence is enough for the game.
Partner practice that actually works
Sit where you cannot see each other’s hands or notes. That removes the temptation to read the answer instead of the taps.
Agree a rhythm before starting: tap firmly, pause a beat between numbers, pause longer between letters. Rhythm is the hardest part to standardise and the main source of confusion.
Most “wrong” decodes are rhythm errors, not memory errors.
Start with words you both already know — colours, animals, days. Guessing from context hides mistakes early and builds confidence.
The commonly confused pairs
B and G share a column; C and H share one too. A single miscounted tap turns one into the other, and the resulting word is often still pronounceable, which hides the error.
Read back the decoded word before continuing. When the word makes no sense, stop at the previous letter rather than pushing on.
Double letters are another trap because the same pair is tapped twice with almost no gap. Use a clear pause between them.
Getting faster
Speed comes from chunking, not from tapping faster. Learn the common letters as pairs — the vowels and the first column — so you recognise them as single units.
Practise short words rather than long ones. Twenty three-letter words build more fluency than one long sentence.
Time yourself once a week. Improvement is slow and visible, which keeps practice interesting.
Using it somewhere real
The code is most fun when it has a purpose: a note passed in a lecture, a message across a noisy room, a puzzle in a game. Give it a use and the practice becomes play.
Keep messages short and harmless. The code is not secure, and anything you would not write on a postcard should not be tapped across a room.
If a message fails, resend the whole word rather than the missing letter. Partial resends produce more confusion than they save.
For the grid and the letter-by-letter reference, the tap code chart is worth printing once. Use it for the first evening, then put it away — the point is to stop needing it.
Finish the evening by sending one message you actually care about. That is the step that turns an exercise into a skill.
What to do on the second evening
The first session builds recognition. The second should build speed, and speed comes from sending full words rather than individual letters.
Set a target: ten words in two minutes, with no more than one error. That is achievable for most pairs and creates a visible improvement.
Then introduce a small complication: numbers, or a word with a repeated letter. Both are where the rhythm breaks first.
Fluency is measured in words per minute, not in letters remembered.
Swap roles halfway. Receiving is harder than sending, and most pairs discover one of them is much stronger in each direction.
Finish with a message neither of you chose, taken from a book. Improvised content is the real test of reading.
Common rhythm mistakes
The pause between the row and the column is the hardest thing to standardise. Agree a fixed count, one beat, and use it every time.
Between letters, use a longer gap, roughly three beats. Without it, two short pairs merge into an unrecognisable sequence.
Rhythm is the syntax of tap code. Get it wrong and the letters vanish.
If a partner keeps misreading, tap their name slowly and let them compare. A known word calibrates rhythm faster than any explanation.


