How to handle timed speed sections

Read the question — it changes

Each family asks many different questions of the same picture: which target appears (∅ — none — is a real possibility), which never appears, how many, which symbol is the intruder, where the first target sits; a count, the busiest or emptiest line, the symbol appearing exactly N times; decode, encode, total the digits, find the mis-decoded position, or decode across a key change. Answering the question you expected instead of the one asked is the fastest way to lose a point.

Symbol search: exact match or it doesn't count

The fillers are chosen to look like the targets — ▲ against ▼, ● against ◐, ★ against ✦. Accept a hit only on an exact outline match: a look-alike sits in almost every row, and counting it is how a tally runs high.

Cancellation: one pass, small subtotals

Sweep row by row and bank a subtotal per row — a re-scan is the big time leak. Asked for the cells that are NOT the target? Count the targets and subtract. Asked which line has most or fewest? Count each line; never judge by looks. Asked which symbol is absent? Cross each symbol off at first sighting; the uncrossed one is the answer.

Coding: hold the key steady

Almost every coding error is an off-by-one lookup — the key entry next to the right one. When a token feels doubtful, re-check that single entry; never restart the row. Asked where a digit's symbol sits, look the digit up ONCE and scan for that symbol. Given a mid-row key change, apply it only from the stated position, never from the start.

The strategy

1. Fix the targets or key in mind before the row.
2. One sweep, left to right — re-reading is the main cost.
3. Exact matches only; a look-alike never counts.
4. Doubtful? Re-check one cell or key entry — never restart.

Common traps

• Answering the number you counted instead of the number asked (the complement question).
• Counting a target's look-alike twin as a hit.
• A key change ignored — or applied from the start of the row.