Short answer: A repeat request is not a failure; it is one of the most useful tools in a contest. The best requests are short and specific: ask only for the part you did not copy, send what you have so the other station knows where to start, and confirm the full callsign when you are not sure. Do not guess and do not log a QSO you are doubtful about. A good repeat costs a few seconds, and a busted call costs the QSO and sometimes more. Practise the wording until it is automatic.
Why a repeat is cheap and a guess is expensive
When you hear a callsign or an exchange only partly, you have three options. You can guess, you can ask for a repeat or you can drop the QSO. Guessing feels fastest, but it is the most expensive option in the end: if you are wrong, the QSO is lost, and in many contests a wrong callsign can also cost a penalty, depending on the rules. Dropping the QSO is safe but wastes the time you have already invested.
A repeat sits between the two. It takes a few seconds, usually less than the time you would spend later wondering if the call was right. Over a whole contest, those few seconds add up, but the corrected QSOs add up more. If you want to see what a bad copy can cost you, read about busted callsigns and about the gap between claimed and final score.
Ask for the part, not the whole
The most common mistake is to ask for everything when only a small part is missing. If you copied a callsign except the last letter, repeating the whole call wastes time for both stations and increases the chance of a new error. Say what you have and ask for the rest.
- On CW, send the part you copied followed by a question mark, for example the first characters of the call with a question mark in place of the part you missed, or send the call with a question mark and wait. Many operators use a short request such as AGN or a single question mark after the callsign.
- On SSB, say what you have and ask for the rest, for example the prefix and the first letter of the suffix, then ask for the last letters.
- For the exchange, ask only for the field you missed. If you did not hear the zone, ask for the zone, not for the whole exchange.
The principle is that the other station should know what to send. A request that tells them where you are in the copy is faster than one that makes them start over.
Use a consistent pattern
In a pileup everybody is in a hurry, and a consistent pattern helps both sides. Choose one form of the request, for the mode you use, and use it every time. When a station knows what to expect, it understands you faster. A good pattern has three parts: what you have, what is missing and an invitation to answer. Keep it short, and avoid long phrases that are not part of ordinary contest practice.
The same applies to the way you confirm. When you receive a callsign that you are not sure about, repeat it once in full and wait for a yes or the corrected version. Do not repeat it five times. One clean confirmation is enough, and the other station will correct you if needed. The article on SSB phonetics and confirming callsigns quickly covers the voice side in more detail.
CW specifics
In CW the difficulty is not hearing the signal, but separating characters that sound similar at speed. The letters that are easily confused, such as B and 6 with cut numbers, or the pairs that differ by one dot, are the ones you should ask about most. If you suspect a cut number, ask for the number written in full, or ask for the number in the form the other station used to send it.
If the other station is sending too fast, ask them to slow down. A request for a lower speed is perfectly normal, and many operators will reduce speed for a single QSO. Remember that a lower speed from you can also help, because a slower exchange is often copied correctly in the first attempt. For more on speed and accuracy see CW copying accuracy in contests and CW speed in contests.
SSB specifics
On SSB the problem is usually noise, accents and a weak or distorted signal. Use standard phonetics, because they are designed for exactly this situation, and avoid inventing your own words. If you did not understand a letter, ask for it in phonetics. If the station replies with a word you do not know, ask again; do not nod and hope.
It also helps to repeat what you copied in a rhythm that the other station can follow. Say the callsign slowly, in full phonetics, once. If it was right, the other station will answer with a short yes. If not, they will correct you. The article on confused letters on SSB lists the letters that give trouble most often.
Examples of the three situations
Three situations cover most repeat requests, and thinking about them in advance makes the wording easier. In the first, you copied the callsign but are not sure of one character. You send or say the call back as you copied it, with the doubtful character marked by a question or by the phonetic word you are unsure of. The other station answers with a short confirmation or the correct letter, and you log it. In the second, you copied only the beginning of the call because of QRM. You send what you have and a question mark, and you wait for the rest instead of calling again. In the third, you copied the callsign but missed the exchange. You send the callsign and ask for the missing field only.
In each case, resist the urge to add extra words. The other operator is probably listening to several stations at once, and every unnecessary word makes it harder to hear the part that matters. Short, regular and calm is the style that works, and it carries across modes and bands.
Help from a second operator or a logger
At a multi-operator station a second pair of ears can make a big difference. A partner who listens to the same audio and writes down the callsign independently provides a check without a single extra transmission. In a single-operator station the logger plays a similar role: a call history file or a checking function in the logger can tell you that a callsign you copied is very unlikely, so you ask for a repeat instead of logging it. Treat these hints as hints, not as truth, and keep in mind what the article about call history files says about trusting them blindly.
After the contest, a log check does the same job on a larger scale. It shows the QSOs where the callsign looks doubtful, so you can compare with your notes or a recording. That does not replace the repeat request at the right moment, but it is a good way to learn which of your copies were weak.
When to let a QSO go
Sometimes the best repeat request is none at all. If the signal is weak, the pileup is large and you have asked twice without success, you may be better off moving on. The time you spend on one stubborn QSO can be used for two or three others. This is a judgement that depends on the multiplier value, the band and the time left. A rare multiplier is worth a longer attempt, and an ordinary call on a busy band is not.
Do not log a QSO you have not completed. Logging an unfinished QSO and hoping that it counts is the surest way to a not-in-log mark. The article on causes of not-in-log QSOs explains how that happens. If you are in doubt, ask once more or leave it out, and your log stays cleaner.
Practise in training, not in the contest
A repeat request is a skill, and like any skill it improves with practice. Use old recordings or a training programme to practise: listen to a short clip, write down what you heard, and decide which part you would ask to be repeated. Record yourself asking for a repeat on SSB and listen to the recording. On CW, practise sending the short forms until they come without thinking.
After the contest, use your log to see how it went. A report of flagged callsigns shows where copying went wrong, and a pattern, such as errors in the same character or in the same band, tells you what to practise. The article on training your ear for callsigns suggests exercises between contests.
Related reading
The bottom line
A short, specific repeat request protects your log and costs a few seconds. Ask for the part you missed, use one consistent form, confirm once and move on when a QSO is not worth the time. Practise between contests, and let the log review show you which characters to work on. For details on what a log check looks at, read the FAQ.
FAQ
Is it rude to ask for a repeat in a pileup?
No. A short repeat request is part of normal contest practice. A wrong callsign costs more time for everybody.
Should I always confirm the callsign?
Confirm when you are not sure. If you copied it clearly, the exchange itself is the confirmation.
How many times can I ask?
Once or twice. If it is still unclear, decide if the QSO is worth more time, or move on.
Can a log check replace repeat requests?
No. A check helps you find errors afterwards, but asking at the time is cheaper and gives a correct QSO.
What about numbers in the exchange?
Ask only for the field you missed, and confirm cut numbers on CW if you are unsure of them.



