As a DXer and contester I think it is instructive to listen to well managed DXpedition pileups and to CW contests. In these events speed and accuracy are essential. The minimum amount of information is sent, clearly and unambiguously. The same applies when dealing with a large number of chasers as a SOTA activator.
What is the essential information for a valid QSO?
Activator: Chaser’s callsign, your report and SOTA reference.
Chaser: Your callsign and report
That’s it. Everything else is slowing down the QSO rate and is inconsiderate when there are other chasers patiently waiting for a QSO.
A fast, efficient SOTA QSO might therefore proceed as follows:
Activator: TU G3WGV (the end of the previous QSO)
Chasers: Send full callsign once, then listen. Repeat… until
Activator: XX1XYZ 599 LD012
XX1XYZ: 599 TU
Activator: TU G3WGV
There is no need for chasers to ever send the activator’s callsign: he knows his callsign already and will quite reasonably assume that if you’re in his pileup then you are calling him!
Similarly there is no need for the activator to send his callsign as part of the exchange because the chaser already knows it. The activator should give his callsign at the end of every QSO, so chasers tuning into the pileup are not left guessing who it belongs to for more than a few seconds.
Consistency is important: use the same QSO format for every QSO, so the chasers know what to expect and when to call. As an activator you are in charge of and responsible for your pileup, so of course you are entirely at liberty to add in more information, e.g. your name, QTH, inside leg measurement and so on. In so doing you need to recognise that this is slowing down the QSO rate and may be reducing the possibility of other chasers getting their QSO in the log before you have to go QRT.
Chasers can also help to speed up the QSO rate. Never ever, under any circumstances call while the activator is working someone else or has called a partial, e.g. 3WG?, unless your callsign contains those characters. This is known as calling out of turn. It is bad manners, poor operating practice and it slows the QSO rate down considerably.
The DX Code of Conduct is an excellent, succinct guide that is as applicable to SOTA as it is to DXing.