The FM outlines our core skills, policies and guides to ensure every member stands ready for the mission ahead.
FM/BP-1284 · v1.02
Types of transactional networks
- Code
- FM/BP-1284
- Kind
- Policy
- Version
- v1.02 1yr ago
- Views
- 420
- Platforms
- As its document
- Published by
- LtCol James 6 Oct 2025
- Last material change
- v1.00 Initial Version
No words changed between v1.01 and v1.02.
v1.01
In transactional nets callsigns must first identify with one another and once ident has been completed, a series of tranmissions may take place, and then the transaction is ended with the proword "OUT".
When a transaction is taking place between two callsigns, only those callsigns can use the net, other callsigns on the net must remain silent until they hear "OUT" which indicates that the transaction is completed.
UNITAF does not use the pro-word "OVER".
If a callsign who is not part of the ongoing transaction has urgent information to send, they can use the proword "BREAK BREAK BREAK" to break into a transaction.
Once a series of transmissions in a transaction are underway, IDENT does not need to happen for each message, just at the start and end of the transaction.
The below table shows the types of nets and their usage of IDENT and transactional communication procedures.
Activity Fireteam Squad Platoon Company Direct/Special
IDENT Use names or buddy team colours Short callsigns Full callsigns Full callsigns Full callsigns
TRANSACTIONAL NO YES YES YES YES
v1.02
In transactional nets callsigns must first identify with one another and once ident has been completed, a series of tranmissions may take place, and then the transaction is ended with the proword "OUT".
When a transaction is taking place between two callsigns, only those callsigns can use the net, other callsigns on the net must remain silent until they hear "OUT" which indicates that the transaction is completed.
UNITAF does not use the pro-word "OVER".
If a callsign who is not part of the ongoing transaction has urgent information to send, they can use the proword "BREAK BREAK BREAK" to break into a transaction.
Once a series of transmissions in a transaction are underway, IDENT does not need to happen for each message, just at the start and end of the transaction.
The below table shows the types of nets and their usage of IDENT and transactional communication procedures.
Activity Fireteam Squad Platoon Company Direct/Special
IDENT Use names or buddy team colours Short callsigns Full callsigns Full callsigns Full callsigns
TRANSACTIONAL NO YES YES YES YES
In transactional nets callsigns must first identify with one another and once ident has been completed, a series of tranmissions may take place, and then the transaction is ended with the proword "OUT".
When a transaction is taking place between two callsigns, only those callsigns can use the net, other callsigns on the net must remain silent until they hear "OUT" which indicates that the transaction is completed.
UNITAF does not use the pro-word "OVER".
If a callsign who is not part of the ongoing transaction has urgent information to send, they can use the proword "BREAK BREAK BREAK" to break into a transaction.
Once a series of transmissions in a transaction are underway, IDENT does not need to happen for each message, just at the start and end of the transaction.
The below table shows the types of nets and their usage of IDENT and transactional communication procedures.
Activity Fireteam Squad Platoon Company Direct/Special
IDENT Use names or buddy team colours Short callsigns Full callsigns Full callsigns Full callsigns
TRANSACTIONAL NO YES YES YES YES
Where it appears
Lives in
FM/G165 Transactional communicationsOn role cards
On 41 role cards in 12 combat areas.
Named on
-
Acting Fireteam Leader (≤5)
Combat Leadership
-
Fireteam Leader (≤6)
Combat Leadership
-
Transactional Radio User
Specialisations
The other 38 roles read it through these cards.
By combat area
-
Core Infantry
1 of 13
-
Medical
2 of 10
-
Specialisations
1 of 2
-
Rolecard Development
1 of 11
-
Logistics
1 of 2
-
Fire Support
1 of 8
-
Remotely Piloted Systems
1 of 5
