Survivalist Forum banner

OPSEC and written plans

2645 Views 11 Replies 11 Participants Last post by  Gankom
So I'm getting together some written emergency plans to have at the house, in each car, BOB, and even in my wifes various purses. She isn't super interested in this whole thing (she's supportive and pays some attention, but I know if the SHTF she may not remember as much as I'd like) so I would like to have written plans available for her and the kids.

These plans would include things like meetup locations, routes, BOL's, contingencies, etc. I am a bit worried about these plans being written down though and then available to unscrupulous persons who may stumble across them if one of the written plans got left behind.

When I was in the army we used to have OPSEC plans in place for when a vehicle needed to be abandoned. (Stack any sensitive materials, radios, computers, documents, maps on the front seat and drop an incendiary grenade on them as run away. Or as happened during the battle of Baghdad, have the AF drop a JDAMS on a disabled tank) I don't think that covers every situation though.

I'm just curious if anyone else worries about this and if so what are your solutions to OPSEC for written plans?
  • Like
Reactions: 3
1 - 1 of 12 Posts
We have most of our information written down. We're not super worried about anything be comprimised. For the most part the only written plans with anything that could be considered sensitive are kept at the BOL which has people in it 24/7. I cant really think of any information about our plans or preps thats written down that we can't afford to lose.

The one exeption would be members personal information. Wallets, passports, etc. For the most part, alot of that info is being carried everywhere anyways, but its a risk that needs to be taken. I'd rather be prepared, and know everyone else is all set, that risk disaster because someone forgot something.
  • Like
Reactions: 1
1 - 1 of 12 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.