Difference between revisions of "Brevity"
(Created page with "I have been advised that my radio use can be too wordy sometimes. To help cut down on your transmission time, please try to:[list] [*]use very short, simple code words (min...") |
|||
| Line 1: | Line 1: | ||
I have been advised that my radio use can be too wordy sometimes. | I have been advised that my radio use can be too wordy sometimes. | ||
| − | To help cut down on your transmission time, please try to: | + | To help cut down on your transmission time, please try to: |
| − | + | * use very short, simple code words (minimum syllables) | |
| − | + | * if necessary, drop the clarifying words (eg. "this is") | |
| − | + | * know your message before you press your PTT button (message pads for planning complex messages can help greatly) | |
Apparently, in some circumstances, prowords like "affirmative" and "negative" can be too long. While in other circumstances they can be needed to ensure clarity. Establishing abbreviated versions of longer messages with your teammates can reduce the time it takes you to transmit. Practice together, as confused or garbled messages can be worse. | Apparently, in some circumstances, prowords like "affirmative" and "negative" can be too long. While in other circumstances they can be needed to ensure clarity. Establishing abbreviated versions of longer messages with your teammates can reduce the time it takes you to transmit. Practice together, as confused or garbled messages can be worse. | ||
| − | The more instinctive the 7-line format is, the more naturally you will use it in a game. Practice your formats: | + | The more instinctive the 7-line format is, the more naturally you will use it in a game. Practice your formats: |
| − | + | === Short Format === | |
| − | + | <blockquote>Dizzy. Whiskey. Return to Base. Over.</blockquote> | |
| − | + | # Receiver ("hey, so-and-so") | |
| − | + | # Sender ("it's me") | |
| − | + | # Content ("enemies are between us and base, go back to base") | |
| − | + | # Close ("over to you") | |
| − | + | === Long Format === | |
| − | + | <blockquote>Whiskey. Dizzy. Relay to Optix. Flash. Engaging 6 enemy at Rosebud. Do not Answer. Out. <blockquote> | |
| − | + | # Receiver | |
| − | + | # Sender | |
| − | + | # Transmit Instruction ("pass this on to the boss and the squad on the other flank") | |
| − | + | # Priority ("this is really urgent") | |
| − | + | # Content | |
| + | # Final Instruction ("more to follow") | ||
| + | # Close | ||
Revision as of 08:04, 23 January 2013
I have been advised that my radio use can be too wordy sometimes.
To help cut down on your transmission time, please try to:
- use very short, simple code words (minimum syllables)
- if necessary, drop the clarifying words (eg. "this is")
- know your message before you press your PTT button (message pads for planning complex messages can help greatly)
Apparently, in some circumstances, prowords like "affirmative" and "negative" can be too long. While in other circumstances they can be needed to ensure clarity. Establishing abbreviated versions of longer messages with your teammates can reduce the time it takes you to transmit. Practice together, as confused or garbled messages can be worse.
The more instinctive the 7-line format is, the more naturally you will use it in a game. Practice your formats:
Short Format
Dizzy. Whiskey. Return to Base. Over.
# Receiver ("hey, so-and-so")
# Sender ("it's me")
# Content ("enemies are between us and base, go back to base")
# Close ("over to you")
Long Format
Whiskey. Dizzy. Relay to Optix. Flash. Engaging 6 enemy at Rosebud. Do not Answer. Out.
# Receiver # Sender # Transmit Instruction ("pass this on to the boss and the squad on the other flank") # Priority ("this is really urgent") # Content # Final Instruction ("more to follow") # Close
