Short answer: After a contest, the log shows what happened but not why. A few quick marks made during the contest give you the why: a note when a band changed, when the noise rose, when a doubtful QSO was logged, when you took a break and when something went wrong. Keep the system simple, with one key or one line per event, and use the notes next to your hourly statistics in the review.
What the log does not tell you
A contest log is a precise record of QSOs: time, frequency, call and exchange. From it you can calculate rates, count multipliers and see the hours of your operation. But it leaves out the reasons. Why was the rate low between two and three in the morning? Why did you change from 20 to 15 metres at that moment? Why is there a gap of forty minutes in the afternoon? Weeks later, you will not remember. The statistics show the effect, and without a note, the cause remains a guess.
Simple notes made at the time fill the gap. They cost seconds during the contest and save hours of puzzling afterwards. The article on comments and notes in contest logs and a station change notebook describe related habits, and this article extends them to the moments during the operation.
What is worth marking
You do not need to note everything. Choose a small list of events that matter for the review. Band changes, with the reason: the band was closing, the multipliers were missing, the rate fell. Changes of the antenna or the radio settings. Sudden noise or interference, with the time. Breaks and rests, with their start and end. Doubtful QSOs: a call or exchange that you were not sure of. Technical problems: a computer restart, a lost connection, a failed keyer. Changes of operator, in a multi-operator station. Conditions: a sudden opening, a fade-out, a flare. And finally, decisions: “start search for multipliers now”.
Think of each mark as an answer to a future question: “What happened here?” If a mark will not help to answer a question, it is not worth the effort.
Keep the system simple
A system that is too complicated will not survive the third hour of the contest. The simplest one is a sheet of paper and a pen next to the keyboard, with the time and a few words for each entry. Time is the key: write the UTC time, or the hour and minute that you can find in the log. Many loggers also have a function to insert a note into the log at the current time or to attach a comment to a QSO, and some can play a short marker into the audio recording. Choose whatever you can do in five seconds without looking away from the screen.
Use short codes. For example: B for band change, N for noise, D for doubtful QSO, R for rest, P for problem. Write the code, the time and perhaps two words. After the contest you can expand the codes into sentences. A short code is also easy to search for later.
Use the log’s own tools
Many contest loggers allow you to add a comment to a QSO or to a point in time. Use it for doubtful calls: type a short note such as “suffix?” in the comment field, and the doubtful QSO will be easy to find later. The Cabrillo format can carry comments in certain places, but not in the QSO lines, and the notes may not be exported, so keep your own copy. The article on comments in the Cabrillo file explains what can be put where.
If you record the contest, the recording itself is a source of marks. Note in your sheet the time of the recording that corresponds to important moments, or say a short note aloud into the microphone when something happens, if that is allowed by your setup. The article on recording audio for a log check shows how a recording and the log work together.
Review with the marks
When the contest is over, open your hourly statistics, and your marks next to them. For each hour that stands out, good or bad, look at the marks. A high rate on 20 metres from 14:00 to 15:00 with a mark “opening to Asia” tells you what happened. A low hour with a mark “noise started” tells you what you could not control. A flat hour with no mark tells you that you have not yet understood it, and it is a candidate for further thought. The articles on hour-by-hour analysis and a post-contest review routine show how to read the hourly figures.
Contest Analyzer provides full statistics, including rates, QSOs by hour and band, countries, continents, CQ and ITU zones, WPX prefixes, distance, beam heading, breaks and off time, and callsign length and structure. It also supports year-on-year comparison with your own logs. Put your marks beside the charts, and you have a complete picture.
Use the marks with the list of doubtful QSOs
The check of every callsign and every zone against official license databases and several independent reference sources produces a short list of QSOs worth a second look. Your own marks “D” for doubtful QSOs complement it. Compare the two lists: which QSOs did you mark as doubtful, and are they in the report? Which ones are in the report but you did not mark? The overlap shows where your instinct was right, and the difference shows where it was not. Both are valuable for improving your habits.
In the report you can mark QSOs as checked in your own audio recording and edit calls, zones, time and frequency. Your own marks tell you which rows to hear first. The contests page lists the supported contests.
A sample sheet
To make the idea concrete, here is how a short sheet might look after a contest, with invented entries. 1403: B, 20 to 15, Asia opening. 1520: D, suffix after weak signal, QSO at 1519. 1700: N, noise up on 40, likely a neighbour’s device. 1845: R, short rest, 20 minutes. 2010: P, computer restart, lost two minutes. 0230: D, zone not clear, QSO at 0229. 0410: R, main rest starts. 0710: B, 40 to 20, sunrise.
That is eight lines for about seventeen hours. In the review, each line has a role. The two D marks tell you to listen to those minutes first. The P mark explains a small gap in the hourly figures. The R marks explain the off time that you will see in the statistics. The B marks explain the shape of the band chart. The N mark may lead to a search for the noise source before next year. Without the sheet, each of these would be a guess. With it, you can write the explanation in a single sentence and move on to decisions.
Common mistakes with notes
The first mistake is to make the system too ambitious. A grid with ten columns will be abandoned by the first night. The second is to write notes without times, so that they cannot be matched to the log. The third is to wait until later to write a note: by then the details are gone. The fourth is to use abbreviations that you will not understand next week; keep a legend on the first line of the sheet. The fifth is to keep the notes in a place that is not with the log, so that they are lost. Put the sheet in the folder of the contest as soon as the contest ends.
There is also the mistake of treating the notes as a duty. They are a tool for you. If a note takes your attention away from a rare multiplier calling you, skip it and write it later from memory. A note that is a little late is better than a missed QSO. Over time you will find the rhythm, writing in the natural pauses: after a QSO, while a CQ is running, during a short break.
Notes for next year
The marks are also the raw material for next year’s plan. Review them once and write down the three lessons that you want to remember. For example: “20 metres opened to Asia an hour earlier than expected”, “the noise on 40 metres rose after 22:00”, “I forgot to eat until 15:00 and the rate dropped”. Put the lessons at the top of the notebook page for that contest. Next year, read them before you start planning. The article on goals for next year shows how to turn lessons into goals.
Keep your notes with your other material for that contest: the log, the corrected Cabrillo, the recording and the result. A small folder or a note for each contest builds into an archive that you will be glad to have.
Related reading
- Contest Training With Old Logs and Recordings
- Comparing the Same Contest Year on Year
- Setting Contest Goals From Last Year’s Statistics
The bottom line
A log tells you what happened, and a few marks tell you why. Choose a few events to mark, use simple codes, keep your notes next to your hourly statistics and write down three lessons for next year. The effort is small, and the review becomes much more useful.
FAQ
How many marks should I make?
Only as many as you can make without losing rate: perhaps one every half hour on average. Quality matters more than number.
Paper or computer?
Whatever you can do fastest. Paper is simple and reliable; a note field in the logger is easy to search.
Will the marks be exported in the Cabrillo file?
Usually not. Keep your own copy of the notes with the log.
What is the most useful mark?
A doubtful QSO. It tells you where to listen to your recording first.



