Good topic. Tasking FRAGOs.

I have seen organizations that issue Weekly (WTF/O) and Daily (DTF/O) tasking FRAGOs or Orders. As with most things, the decisive point of success was implementation not the mere existence of the document. So, what are some of the keys tips for successful implementation?

In no particular order [ha! see what I did there?]:

– create a web-based tasking tracker with the S3 POC(s) as the sole edit rights. When a task status changes, the tasked unit contacts the S3 shop to inform them of the update and the task is updated as applicable. Completed tasks are “archived” as complete and removed from the tracker. This document also hyperlinks to the digital archive of the relevant FRAGOs. Columns identify the tasked unit, task title, and suspense. This document is reviewed at the relevant battle rhythm meetings for task completion (past suspense, 5, 10, 15, 30 days out, whatever works)

– hyperlink the “friendly forces” in paragraph 2 of the WTF/DTF to take units directly to their section of “tasks to subordinate units.” Do I want to know everything happening in the BN? Sure I do. But, my time is limited. So, take me straight to my piece of the elephant where I can start chewing.

– suspenses published in the WTF/DTF with less than a ## (I say 14) day suspense are telephonic CCIR to Company CDRs and 1SGs from reps in the S3 shop. It goes like this, “Yo, fam… check it. WTF hits on Wednesday COB and it’s gonna hit hard this week. We got a late notice 5 and 50 tasking from DIV for THIS FRIDAY. Sorry ’bout your luck. We tried to duck, dip, dodge, dive this one, but it was a no-go. Just a heads up.”

– publish consistently! Please for the love of Lasagna, publish consistently. If you actually want people to read it, it needs to go out at the same time and day so it can fit into their routine.

Hope this helps!

~Jeff

BOLC Topic Lead