Jump to content
Perfk

Lets write a better briefing (CO´s assemble!)

Recommended Posts

Hi all,

 

It has come to my attention that not everyone reads the entirety of the briefing before they start leading a mission. 

Lets see if we can rectify that.

 

Below is the briefing from my latest Tanoa mission.

What would you change for it to be easier to read, what is redundant? what should be added?

Should i change the format completely, in that case, please provide examples to what. (note this is for BLUFOR/NATO/US forces)

 

ALBUM: http://imgur.com/a/a42o9

NEWTAB("------------- OPORD ------------")
<br/><font color='#FFA500' size='15'>Task organisation:</font>
<br/>
<br/>[-Platoon Command
<br/>
<br/>[ NATO Rifle Platoon 55 man.
<br/>
<br/>[-Platoon Commander
<br/>
<br/>[--Platoon Sergeant
<br/>
<br/>[--Platoon RATELO
<br/>
<br/>[--Platoon Medic
<br/>
<br/>[--Platoon Runner/CLS
<br/>
<br/>[
<br/>
<br/>[-3x Rifle Squads
<br/>
<br/>[-Squad Leader
<br/>
<br/>[--3x Fire Teams
<br/>
<br/>[--Fire Team Leader
<br/>
<br/>[--Automatic Rifleman
<br/>
<br/>[--Rifleman (AT4)
<br/>
<br/>[--Rifleman / Rifleman CLS / Rifleman DMR
<br/>
<br/>[
<br/>
<br/>[-1x Weapon Squad
<br/>
<br/>[-Squad Leader
<br/>
<br/>[--2x Machine gun teams
<br/>
<br/>[--Machinegunner (Zafir 7.62)
<br/>
<br/>[--Assistant Machinegunner
<br/>
<br/>[--Assistant Machinegunner
<br/>
<br/>[--2x Anti-tank teams
<br/>
<br/>[--AT Gunner (Titans)
<br/>
<br/>[--Assistant AT Gunner
<br/>		
ENDTAB;

NEWTAB("Preliminaries:")
<br/><font color='#FFA500' size='15'>Ground:</font>
<br/><img image='Tanoa.jpg' width='400' />
<br/>
<br/><font color='#FFA500' size='15'>Weather:</font>
<br/>> Overcast with low probability of rain.
<br/>
<br/><font color='#FFA500' size='15'>Light:</font>
<br/>> First Light: 0630h
<br/>> Last Light: 1830h
<br/>> Time Now: 0700h
<br/>
<br/><font color='#FFA500' size='15'>Forecast:</font>
<br/>> Weather is not expected to change.
<br/>
<br/><font color='#FFA500' size='15'>Moonstate:</font>
<br/>> n/a (daytime)
<br/>
<br/><font color='#FFA500' size='15'>Visibility:</font>
<br/>> Good (1500-2000 m).
<br/>>> OBJ DELTA is barely visible from PLD TANGO due to fog.
<br/>>> OBJ OSCAR is barely visible from OBJ DELTA and LIMA due to fog.
<br/>
ENDTAB;

NEWTAB("I. Situation:")
<br/>Paramilitary nationalists rushed over the island of Tanoa, with low restiance from the local government were they able to take every major port, airport and military bases.
<br/>The nationalists claim that its their homeland.
<br/>
<br/>NATO have deemed that the nationalists have no claim, and a taskforce is sent to the Horizon Islands.
<br/>
<br/>1st Platoon (you) will be the first wave to hit the island, in an effort to remove the nationalists and bring peace to the unstable region.
ENDTAB;

NEWTAB("A. Enemy Forces:")
<br/><font color='#FFA500' size='15'>a. Composition, Location and Capabilities:</font>
<br/>> Tuvanaka Airbase:
<br/>>> 3x Infantry platoons armed with AK assualt rifles, RPG rocket launchers, RPK or PKM machineguns.
<br/>>> 1x Mechanized Qilin section armed with miniguns.
<br/>>> 1x BTR-K (Kamysh) patrolling the airbase.
<br/>>OBJ DELTA and OBJ LIMA each have:
<br/>>> 1x Infantry squad.
<br/>>In the forrest around OBJ DELTA, LIMA and OSCAR:
<br/>>> 3x Infantry platoons armed with AK assualt rifles, RPG rocket launchers, RPK or PKM machineguns.
<br/>>> Sniper teams may be operating in the area.
<br/>
<br/><font color='#FFA500' size='15'>c. Assessment of Intentions/MLCOA:</font>
<br/>> They are not likely to have any reinforcments, and will therefore hold out against any attack. 
<br/>> MLCOA is that they hold position and defend against our advance. 
<br/>> MDCOA, use the high tree density to hide and will then use hit and run tactics to run us down.
ENDTAB;

NEWTAB("B. Friendly Forces:")
<br/><font color='#FFA500' size='15'>a. Composition and Location:</font>
<br/>> 1x infantry rifle Platoon.
<br/>> Platoon is located at the marked infantry Platoon marker south of the PLD (PL TANGO).
<br/> 
<br/><font color='#FFA500' size='15'>b. Attached or Organic Forces:</font>
<br/>> 1x Weapons platoon. (Titans and Zafir)
<br/> 
<br/><font color='#FFA500' size='15'>c. Adjacent Units:</font>
<br/>> nearest friendly forces are north 10km holding with the rest of the taskforce.
<br/>
<br/><font color='#FFA500' size='15'>d. Higher Commanders Intent:</font>
<br/>> Alpha Platoon advances and secures a vital area in order for follow up forces to setup base on the airfield.
<br/>
ENDTAB;

NEWTAB("II. Mission:")
<br/>Alpha Platoon, your force, will secure OBJ DELTA OR OBJ LIMA togeahter with OBJ OSCAR. NLT H-Hour+120m
<br/>
<br/>Alpha Platoon, your force, will secure OBJ OSCAR and either OBJ DELTA or OBJ LIMA. NLT H-Hour+120m
<br/>
<br/>Objectives:
<br/>> OBJ DELTA or OBJ LIMA - Blow up the communications tower.
<br/>> OBJ OSCAR - Secure the airbase. (clear 400 m around OBJ OSCAR marker)
<br/>
<br/>It is not COY intent for the island to be cleard. Just clear a path to the airbase, and clear that (airbase) so follow up forces can land safely.
ENDTAB;

NEWTAB("III. Execution:")
<br/><font color='#FFA500' size='15'>Intent:</font>
<br/>
<br/>> Battalion Commands intent is that our unit advances to secure OBJ OSCAR, and while doing so engages and destroys any opposition. in Coy intent is that our unit forms up, crosses the PLD, then moves west to the marked objective destorying any enemy that is located.
<br/>
<br/>
<br/><font color='#FFA500' size='15'>a. Concept of Operations</font>
<br/>
<br/>1. General Plan
<br/>> Each individual unit will organize and move to their designated FUP position behind the Platoon Line of Departure (PLD). Once each individual unit is at their designated position at the FUP, they will radio it into the platoon leader. The platoon will then advance.
<br/>
<br/>
<br/><font color='#FFA500' size='15'>b. Tasks/Missions to Manoeuvre Units:</font>
<br/>
<br/>2. Phases
<br/>> 1st Phase (PLD)...
<br/>> 2nd Phase ...
<br/>> 3rd Phase ...
<br/>> 4th Phase ...
<br/>> 5th Phase (LOA)...
<br/>
<br/>3. Schemes of Manoeuvre
<br/>> Platoon Leader will outline the general manoeuvre plan and outline which units will function as the Main Effort, Support by fire, and security. Then the platoon Leader will explain each individual units scheme of manoeuvre.
<br/>> 1'1
<br/>> 1'2
<br/>> 1'3
<br/>> 4'1
<br/>
<br/>4. Supporting Fires and Weapons
<br/>> N/A
<br/>
<br/><font color='#FFA500' size='15'>e. Coordinating Instructions:</font>
<br/>
<br/>1. Task Organization
<br/>> Where and what are boundaries.
<br/>> Where and what are the objectives.
<br/>> Where and what is the Line of departure/PLD.
<br/>> Time and direction of attack.
<br/>> Coordinating measures.
ENDTAB;

NEWTAB("IV. Service Support:")
<br/><font color='#FFA500' size='15'>a. Support Concept:</font>
<br/>
<br/>> Logistical support has been provided when leaving the Taskforce, extra ammunition, medical equipment, and explosives have been cross loaded within the platoon. Further logistical support will arrive tomorrow with the follow on forces. Until this time, there is no further logistical support in the AO.
<br/>
<br/><font color='#FFA500' size='15'>b. Materiel and Services:</font>
<br/> 
<br/>  1. Materiel and Supply:
<br/> 
<br/>> Everyone has been issued a standard comabt loadout. Everyone has been issued an IFAK for treating injuries.
<br/>
<br/>2. Transportation and Maintenance:
<br/> 
<br/>> None
<br/>
<br/>3. Allocation of Logistics
<br/>
<br/>> Assistant machinegunners and automatic riflemen will carry extra ammunition for their designated team.
<br/>
<br/><font color='#FFA500' size='15'>c. Medical Evacuation and Hospitalization:</font>
<br/>
<br/>1. Medical equipment has been allocated to each individual. Extra equipment is located with the HQ Medic.
<br/>
<br/>2. In the event of an injury or death under non-combat situations, the medic will assess the casualty and report the best plan of action to the platoon leader.
<br/>
<br/>3. In the event of a casualty under fire, the nearest unit will stabilize the casualty then radio to the platoon leader, who will then decide on the best course of action.
<br/>
<br/>
<br/><font color='#FFA500' size='15'>d. Personnel:</font>
<br/>
<br/>1. our unit is at full strength.
<br/>> 1x 5 man HQ team.
<br/>> 3x 13 man squad.
<br/>> 2x 3 man machinegun team.
<br/>> 2x 2 man Anti Tank team.
<br/>
<br/>2. Replacements are unlikely, but reorganization and tasking will occur tomorrow with the follow-on forces.
<br/>
<br/>3. Any EPWs are to be reported to the Platoon Leader, who will decide on a plan to either dispose of or transport to the nearest Battalion HQ.
<br/>
<br/><font color='#FFA500' size='15'>e. Civil-Military Cooperation:</font>
<br/>
<br/>   1. Civilians
<br/>> no non-military personnel have been spotted in the AO, and all efforts have been made to inform anyone remaining inside the town is deemed hostile.
<br/>
<br/>   2. Refugees
<br/>> In the event that the unit comes across refugees, the platoon leader and company commander will be informed, who will dispatch them with an escort out of the AO.
<br/>
ENDTAB;

NEWTAB("V. Command & Signal:")
<br/><font color='#FFA500' size='15'>Radios:</font>
<br/>> Squad Leaders, Team Leaders, PSG, and the PL possess an AN/PRC 148 Radio and AN/PRC 343 Radio.
<br/>> RTO possess an AN/PRC 117F, AN/PRC 148 and a AN/PRC 343 Radio.
<br/>> All other units carries a personal AN/PRC 343 Radio.
<br/>
<br/><font color='#FFA500' size='15'>PRR Nets:</font>
<br/>> Channel 1 - 1'1
<br/>> Channel 2 - 1'2
<br/>> Channel 3 - 1'3
<br/>> Channel 4 - 4'1 (att. weapons platoon)
<br/>> Channel 6 - 1'6
<br/>'
<br/><font color='#FFA500' size='15'>LRR Nets:</font>
<br/>> Channel 1 - PLT 1 (YOUR NET)
<br/>> Channel 2 - PLT 2
<br/>> Channel 3 - PLT 3
<br/>> Channel 4 - PLT 4
<br/>> Channel 6 - I COY
<br/>> Channel 7 - CAS
<br/>> Channel 8 - Fires
<br/>
<br/><font color='#FFA500' size='15'>Recognition Signals:</font>
<br/>
<br/>> Green Smoke = Location of friendly forces.
<br/>> Red Smoke = Location of enemy forces.
<br/>> Yellow Smoke = Wounded or requesting Aid.
<br/>> White Smoke = Concealment.
<br/>
<br/><font color='#FFA500' size='15'>Challenge and Pass:</font>
<br/>
<br/>>Challenge = HAN
<br/>>Password = SOLO
<br/>
<br/><font color='#FFA500' size='15'>Succession of Command:</font>
<br/>In descending order
<br/>
<br/>> 1'6 Platoon Leader
<br/>> 1'7 Platoon PSG
<br/>> 1'1 Squad Leader
<br/>> 1'2 Squad Leader
<br/>> 1'3 Squad Leader
<br/>> 4'1 Squad Leader
<br/>- First to get in touch with other units
ENDTAB;

NEWTAB("VI. Mission notes:")
<br/><font color='#FFA500' size='15'>RESPAWN</font>
<br/>
<br/>> None.
<br/>
<br/><font color='#FFA500' size='15'>REVIVE</font>
<br/>
<br/>> None.
<br/>
<br/><font color='#FFA500' size='15'>JIP</font>
<br/>
<br/>Blufor
<br/>> Yes. JIP players get an option to teleport to their SL when they join.
<br/>
<br/><font color='#FFA500' size='15'>END CONDITION</font>
<br/>
<br/>Victory
<br/>> OBJ OSCAR cleared. (400 m from OBJ OSCAR marker) and one of the following OBJ DELTA OR LIMA Radio Towers blown up.
<br/>
<br/>Defeat
<br/>> 75% of friendly units dead.
<br/>> Time limit of 120 min reached.
<br/>
<br/><font color='#FFA500' size='15'>USE OF ENEMY VEHICLE ASSETS</font>
<br/>
<br/>> Prohibited. Following exceptions remain when in a survival-style situation: Jeeps and other non-special vehicles can be manned and operated for tactical advantage. This includes the usage of standard weapon systems like M2/miniguns.
<br/>
<br/><font color='#FFA500' size='15'>ACE MEDICAL</font>
<br/>
<br/>> Ace Medical Surgical Kit can only be used by Doctors/Corpsman
<br/>> Ace Medical Surgical Kit can be used anywhere, as long as the patient is stable. (no bleeding/pain)
<br/>> Ace Medical Surgical Kit is not used up when used.
<br/>> Corpsman is set to be ACE Doctor.
<br/>> CLS/Runner is set to be ACE Doctor.
<br/>> Each squad have a CLS. He is set to be ACE Reqular Medic.
<br/>
<br/><font color='#FFA500' size='15'>TECHNICAL ASPECT</font>
<br/>
<br/>> On mission start give the mission a few(!) seconds to initialize!
<br/>> View Distance: 1500 (AI: 1450). 20 percent fog.
<br/>> Teams are assigned colors prestart. Alpha = RED, Bravo = BLUE, Charlie = YELLOW.
<br/>> ACRE Signal loss is turned off.
<br/>> ACRE Occlussion is turned off.
<br/>> ACRE radio interference is turned off.
<br/>
<br/><font color='#FFA500' size='15'>CREDITS</font>
<br/>
<br/>> Olsen Framework.
<br/>
<br/>  <font color='#FFA500' size='15'>Mission by Perfk</font>
<br/>
ENDTAB;

NEWTAB("Game Mastering") //This is shown for everyone
<br/> This mission is not designed for game mastering and should only be manipulated for technical, administrative or diagnostic purposes.
<br/> Please DONT go into zeus, unless you REALLY have to.
ENDTAB;
Edited by Perfk

Share this post


Link to post

I actually think your briefing is really nice, you added colors which make it easier to read, described how you've setup ace medical etc.

I think most people don't read briefings entirely because they are mostly too long and contain too many non-relative mission info making it sometimes, a pain in the ass to read. (I stopped counting the number of "command and signal" tabs I decided to not read because they show informations for like 3 companies even though it's a 20 player mission ...)

I know it gives a feel of authenticity to the thing and other people might like it, but I don't.

Share this post


Link to post

I'm playing with the idear of marking the truly important stuff like this:

 

 
.. now its just a question of finding what is truly important, and whats not :D

Share this post


Link to post

Please don't ! It might be because I am colorblind but the red is ripping my eyes out and I'm unable to read it.

Share this post


Link to post

The '>' characters to me seem unnecessary and together with lack of line breaks make it a bit harder to read. What I'd suggest is starting paragraphs without an indent at the beginning and then have empty lines between paragraphs, for example:

A. Enemy forces

(in some examples of US OPORDs you'd see weather here but it's a good idea to keep it seperate like now)

1.Strength, composition and disposition

 

a) Tuvanaka airbase (OBJ OSCAR)

3 infantry platoons composed of (known or approximate number of men in each platoon) men each defending/digging in/patrolling the area (give a more precise description of located strongpoints and patrols)

 

B) OBJ DELTA

...

 

c)OBJ LIMA

...

 

2.Capabilities 

Describe armament, used vehicles if not covered previously, reinforcement capability, support like artillery, c etc

 

3.MLCOA

 

4.MDCOA

 

In friendly forces you state the mission and intent of commanders 2 levels up and the immediate commander, so a platoon mission would state battalion commander's mission and intent, then company, then missions of adjacent units if applicable.

 

You do not have to list the player controlled forces as their TASKORG you've already included at the top (I'd suggest changing that tab's name to Tast Organization rather than OPORD, you can also include the starting position there, preferably with a hyperlink to a marker).

 

In the service support tab it would be nice to include who has any special equipment like explosives, so you don't have to go through the whole loadout index to find out, also the personnel tab in service support refers to handling of prisoners so if you don't have the enemy surrendering you can totally ommit this.

 

In the comsig I'd throw out all the nets and units not relevant to the operation so it's easier to find out what you need to know. Basically, you could write an entire OPORD with all the realistic fluff that has no application in the actual mission and highlight the important parts like you presented or, what's better to do I believe, just ommit those parts so that instead of spending 10 minutes reading the OPORD and planning and briefing for 5, the CO would read it in a few minutes and use more time planning and briefing.

Share this post


Link to post

 

I'm playing with the idear of marking the truly important stuff like this:

 

 
.. now its just a question of finding what is truly important, and whats not :biggrin:

 

 

 

I do love your briefings but i wonder if there are some informations that dont add much but "color" to the picture. In the image you posted above, what is the use of knowing the time of dawn if the operation starts after that?

Then now i suppose it's a sort of raw template, but gamewise you would like to find the information you need to crack this particular nut open, too much fluff and you may either miss vital information or alienate all those players that have slotted in non leading positions. Personally i never slot in leading slots so during briefings most of the times i bounce from my team callsign and temmates' names cos i know i wont remember it for the life of me, to the team's/squad's loadout, to the place where radio channels are written down to the mission and execution just to have a bland idea what we are supposed to do -then we go in game and i find myself at night, and i blink. 

Share this post


Link to post

The orange is good, but I don't feel the red is good for darker backgrounds. Try, green or turquoise.

Share this post


Link to post

For any briefing, remove anything that is not relevant to the mission( situation( background essay of the mission), com sig of other units that are not involved in the mission i.e 2 plt doing their own thing else where, enemy morale because lets be honest its a game first and foremost and AI are AI and player are players, noon really cares.

 

I agree 100% with what delta is saying and having to essentially skip through 3 paragraphs of text to find the information that is relevant to the mission is an eye sore and should be removed from the briefing if its not need to know.

Share this post


Link to post

I would agree with scratching the things that are really not applicable, like refugees or civlians (unless you are actually simulating that), as well

as SOIs for notional units and these other things. 

 

Otherwise it looks pretty alright.

Share this post


Link to post

Well, if you want to cut down a briefing/set of orders to the actual required information, in my experience, this is the minimum required info to conduct ops sort of properly. It largely depends on how much information you have received prior to giving/receiving this type of frago, but even with nil info (your typically start point for arma stuff), it is enough.

 

situation
enemy
SALUTE of en unit(s)

 

friendly
2up intent
1up intent
other units in area

 

mission
WHO will WHAT no later than WHEN in order to WHY

 

 

The execution paragraph, as is done in many UO missions, is uhmm ... a bit off, so it can generally be ignored. Service support is information that can be sorted out after orders, and command and signals can be sorted out after orders as it is typically "read the card"/"what we have been using".

 

To clarify, this would be the information in the briefing.

Edited by beta

Share this post


Link to post

Seems I forgot to actually save my edit. This link is a useful guideline to a US style briefing, which you can use as a baseline and cut out the irrelevant stuff.

 

OPORD

Share this post


Link to post

The minimum briefing as per SOP must contain When, Where, What, What, What (Exactly like a contact report that we don't do either) and a comsig

 

When - Time of day, Light levels, Weather goes here too

Where - Where are FF and where are EN/OBJ (Roughly)

What - What is the EN (Mech inf, ARINF etc.), their strength should be included here aswel

What - Is the EN doing (Defending, attacking etc)

What - What are you doing about it (Essentially your mission)

Comsig - Mandatory even if its "You dont have radios, use runners"

 

Service + Support - This is not mandatory but if you have any you should include it as its really annoying as a CO to find out when the mission loads you have vehicles (For extra points include the number of seats the vehicles have)

 

----- MMO Bit Ends --------

 

With the exception of the Situation General where I always write a bit of a story (Dat Immersion) all of my briefings are done with headings, this allows me to remember if I have covered all of the key points when writing the brief and also allows the CO to easily see the various points he needs to know.

Feel free to steal it (inb4 Fox is a shit mission maker and writes shit briefings)

 

On a general note very few briefings I have ever seen on the server have been difficult to understand (See Falcon + and his thesaurus fest briefs) the issue with people not reading the briefing is one of laziness, if you cant be bothered to read the briefing in full then dont slot as the CO, time and time again I have seen people ignore their OBJs because they have not bothered to read the brief and understand what their actual mission is.

 

Another point is if you are CO and you dont understand what exactly you should be doing ASK. 8/10 the mission maker will be on the server or someone who has helped test the mission will be there, maybe someone will have a different understanding than you. This is a game, your not expected to have all the answers

 

And one final point is that sometimes as a mission maker something will make complete sense to you but be gibberish to someone else (See aforementioned Falcon brief) if people bothered to give feedback to mission makers beyond "This is shit or your mission is broken for X reason" then we could adjust from there and maybe fix the issues???

 

tl;dr

Briefs arent hard to understand (most of the time) just be bother to read it

If you dont understand ASK

Give mission makers feedback and maybe briefs would be better

Share this post


Link to post

At the end of the day, the most important part of your briefing is your mission statement. If you have a solid mission statement, and the rest is literally pictures of cats, as long as the map is marked up with appropriate APP6 markers to show friendly and enemy dispositions, you can still get a plan working.

Share this post


Link to post

In the image you posted above, what is the use of knowing the time of dawn if the operation starts after that?

 

How are you supposed to know that it is after dawn at 7.00 am unless you know what time first light is?

Share this post


Link to post

For some more specific feedback for your briefing Perfk, your execution paragraph reads like a guide on how to give a platoon briefing. The execution paragraph of an operations order is where the person giving the orders details what each of the sub-units are to do to accomplish the mission statement. So, in your briefing, it would be the company commander giving tasks to the platoon commanders in order to accomplish the mission. Thus, when you are reading the execution paragraph as the platoon commander of the mission, you extract your task from it and any limitations imposed (boundaries, time, equipment, troops, etc.). Lots of the info you have in the mission paragraph should be here instead (the coy intent for example). In general, you seem to be switching between an opord written by the company commander, one written by a battalion commander, and then in some parts written by a platoon commander. I would recommend sticking with it being an opord written by the company commander, allowing the platoon commander to extract the info they need to give their own opord.

 

The mission paragraph, as I mentioned earlier, is the MOST important part of your operations order. If I was only to read the mission statement and nothing else from the entire operations order, I should still be able to know where I am supposed to go and what I am supposed to do. The mission statement needs to be clear and concise. Following the format of WHO will WHAT (mission task verb) no later than WHEN in order to WHY is a solid way of forming a good mission statement.

 

As an example, here is a mission statement for what you've got in your opord:

 

1 COY will DESTROY OBJ DELTA or LIMA and SECURE OBJ OSCAR no later than 0900 today in order to secure the airfield for follow on forces

 

 

The WHO portion of the mission statement is the unit that is conducting the mission, since you mention the company commander's intent, it is implied you are receiving orders from the company commander instead of directly from the battalion commander, even though it appears your platoon is the only unit conducting the mission.

 

The WHAT portion is the actual task and is taken from a specific list of mission task verbs, this is the pivotal words of the mission statement and is what enables you to conduct your mission with minimal information (if/when required), as it is essentially an army-wide (NATO wide often) set of standard operating procedures on how to tell subordinates what you want them to do.

 

The WHEN portion details when the mission is to be completed by, you can expand on this in the timings portion of the execution paragraph if you want certain objectives completed earlier (OBJ Delta/Lima for example).

 

The WHY portion is important as it gives context to what the mission is to accomplish in the bigger picture, so that the subordinate commander can still meet the commander's intent if/when the situation changes.

Edited by beta

Share this post


Link to post

I much prefer briefings where the entire OPORD except for execution is already done for me. If I had to read a company OPORD for a platoon mission, I'd then have to extract vital information from it, which takes time out of the 15 minutes I have to read, plan and issue orders.

 

A good briefing should provide me as much information and guidance as possible, with as few words as possible - it should be short and accurate, which will require a balance between the two.

 

Ideally I should only really have to issue the execution part to my subordinates, as they should already have a picture of the situation and task. Pretty much none of our COOPs require players to coordinate their actions with friendly AI (except artillery support). Only information relevant to the mission should be placed in the execution tab - for example fires planned by the higher HQ, any restrictions, limitations and unit boundaries intended by the mission maker, handling of civilians or prisoners.

 

A general layout of the execution tab can be placed (for example under all the relevant info, which I've talked about above), so that commanders can follow it as a framework while issuing their briefing. It would act as a sort of checklist for the CO, to ensure nothing important is forgotten in the briefing.

 

 

TL;DR - Use platoon level OPORD with only relevant information from company level execution on a platoon sized mission. Include an execution framework for the CO to base on (what you have already is pretty good). Be brief, clear and accurate.

Share this post


Link to post

If extraction of information is too complicated, then perhaps the mission briefing should simply be a pre-made operations order that the commander simply has to read and change only key information: location of ORV, location of firebase, location of attack position, etc.

 

This way, there will be negligible time required to generate orders and you can easily brief even complex missions in less than 15 minutes.

Share this post


Link to post

How are you supposed to know that it is after dawn at 7.00 am unless you know what time first light is?

 

oh.

 

well, color me dumb, that's  a fact. 

 

Still, i wonder if there isnt an easier, shorter, and more immediate way to convey the same message. or maybe it's just my lack of confidence and habit to read briefings with a strategic objective. I was used to way simpler briefings: may sound very stupid of me and i am ashamed of actually writing it down, but the very tought of having to put in relationship different lines and sections of the briefing to extract the info you need (how light visibility will be at start) looks like an artificial hurdle to me. But then again this is a hardcore a simulation as one like it to be, so i maybe it's just a matter of forming a habit of readin things and connecting them as you go down the text.

Edited by Maffa

Share this post


Link to post

oh.

 

well, color me dumb, that's  a fact. 

 

Still, i wonder if there isnt an easier, shorter, and more immediate way to convey the same message. or maybe it's just my lack of confidence and habit to read briefings with a strategic objective. I was used to way simpler briefings: may sound very stupid of me and i am ashamed of actually writing it down, but the very tought of having to put in relationship different lines and sections of the briefing to extract the info you need (how light visibility will be at start) looks like an artificial hurdle to me. But then again this is a hardcore a simulation as one like it to be, so i maybe it's just a matter of forming a habit of readin things and connecting them as you go down the text.

 

Mission SOP state that light/weather conditions should be stated in the brief

 

I have just been putting the next timing on so you can assume that if the timing is last light then you will be playing in daylight, and if the timing states first light it will be night time

Share this post


Link to post

HOLY SHIT YOU CAN PUT COLOR IN A BRIEFING!!!!  Perfk do you mind if i steal this, I really like the structure?

Share this post


Link to post

Just like Aphex, do you mind me copying your color code?  Played around with the colors for a bit and really like the one you used in your example.

 

Improvements:  Without getting into the actual content of the briefing, I think there are some ways to improve the structure by making more use of colors and fonts.  I started using colors and a bold font for not only the headlines of each sub-paragraph, but also for the individual "-", ">" and numbers at the beginning of each new line.  That might help to make it easier to read while still being able to identify new lines easily.  In the same manner, I try to keep my text font "light" and highlight important parts with a bold font.

Of course, personal taste has to be taken into account, but I personally are very happy with that kind of structure.

Share this post


Link to post

Some players may not read lengthy briefings because they are lazy.  But often it is because the briefing is not applicable to the mission.

 

COs often skim briefings cause they are under pressure to form a plan quickly.

 

SLs (PLs) may also be busy making planning or making notes on the force structure, (writing down the orbat and weapons etc) and providing preliminary actions on to subordinates.

 

I’m not suggesting that the briefing be short just pertinent.

 

Back stories should be separated out so those who are busy don’t have to wade through the text looking for the required information.  It is really important to limit the orders part of the briefing to the objectives and information that the CO and leaders need to know to accomplish the mission.  Don’t confuse the backstory with the all-important “Why” of the mission statement.  We don’t need a story to know what the intent of our mission.  Perhaps the detailed narrative could be put into a separate "tab" so the lazy players who have nothing to do can read while they wait for the CO to prepare the plan.  But clearly mark it so others don't have to waste time reading it.

 

Keep it simple.

 

  • WHO
  • What (usually involves where)
  • When
  • Why

 

WHO is so often under emphasized.  COs should confirm the comsig at the very start of their briefing.  Missions makers should be consistent throughout the mission.  The Slot-up screen should match the Loadout Screen and the Briefing (both Friendly and ComSig).  I'm told that matching the Slot-up Screen and the Load-out is finicky.
It is really helpful if all of the callsigns, comsig, orbat etc matches.  It is not infrequent that there are conflicts between the slot-up, the briefing and the comsig.  And then the CO changes it and provides a different set of callsigns and radio channels.

 

 

For any briefing, remove anything that is not relevant to the mission( situation( background essay of the mission), com sig of other units that are not involved in the mission i.e 2 plt doing their own thing else where, enemy morale because lets be honest its a game first and foremost and AI are AI and player are players, noon really cares.

 

 

I would agree with scratching the things that are really not applicable, like refugees or civlians (unless you are actually simulating that), as well

as SOIs for notional units and these other things. 

 

 

Well, if you want to cut down a briefing/set of orders to the actual required information, in my experience, this is the minimum required info to conduct ops sort of properly.

I would recommend sticking with it being an opord written by the company commander, allowing the platoon commander to extract the info they need to give their own opord.

 

The mission paragraph, as I mentioned earlier, is the MOST important part of your operations order. 

 

Share this post


Link to post

Thank you all for the amazing answers, i will do my best to work it into my oncoming missions. 

 

As for the "template with colors" use what you can, if i were forced to add credits to all the places i had "borrowed" code etc. that would make my credits tab longer than my briefing :)

I believe in a fair use for all my missions. Take what you can, just make sure you understand what goes on, as i really don't wanna hear "oh it broke, blame Perfk" :)

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...