Should we have a policy update thread on ACC.
As HQAC do not seem very good at cascading updates to the coalface should we put them in ACC to update the masses who frequent here.
To start the ball rolling from SO1 CoOrd
As the result of MoD direction coupled with the findings of a recent service inquiry, the decision has been taken to issue to all ACO CFAVs a copy of the new Cadet Training Safety Precautions. The document is in the form of a defence Code of Practice. This Code of Practice provides clear information to be used by all Cadet Force Adult Volunteers (CFAVs) and other personnel who support and train the Cadet Force. The Pamphlet contains the policy and direction on cadet safety and safeguarding, guidance on the processes involved and good practice to apply and the actions to be taken in the event of an accident or incident involving members of the MOD-sponsored Cadet Forces.
This Code of Practice is to be carried at all times by adults supervising cadet training. If it is not practical to do so, because of the nature of the activity, the document is to be located with the nearest immediate form of communication e.g. mobile âphone or radio.
HQ ACO will produce the Cadet Training Safety Precautions. It will be in concertina âfablonedâ card format that folds to around 11cm by 8cm. It is thus durable, water resistant and fits easily into No2 trouser pockets. It will be pale blue and have Air Cadet Organisation in large letters on the front.
A copy will also be placed on BADER, Dii and on our WWW site. The document has a page of key telephone contacts. The permanent national numbers will be printed but local numbers will need to be added. This can be done either by permanent pen or by adding an adhesive paper label to the page. As unit COs it is your responsibility to ensure that this is done.
The CTSPs will be issued to you through your Wg HQ in early to mid January 2015. On receipt you are to ensure that every VR(T), adult SNCO and CI on your Sqn get a copy and are briefed as follows:
This Code of Practice provide clear information to be used by all Cadet Force Adult Volunteers (CFAVs) and other personnel who support and train the Cadet Force. The Pamphlet contains the policy and direction on cadet safety and safeguarding, guidance on the processes involved and good practice to apply and the actions to be taken in the event of an accident or incident involving members of the MOD-sponsored Cadet Forces (which are the Combined Cadet Force (CCF), the Sea Cadet Corps (SCC), the Army Cadet Force (ACF) and the Air Training Corps (ATC)).
This Code of Practice is to be carried at all times by adults supervising cadet training. If it is not practical to do so, because of the nature of the activity, the document is to be located with the nearest immediate form of communication e.g. mobile âphone or radio.
I think putting people policy decisions and communications on here is pretty poor regardless of the intent. Itâs very un-disciplined of people to do that, and before the usual mob start having a pop at the chain of command, remember that if you bump into an idiot in the morning, youâve probably just met an idioit. If you bump into idiots all day longâŚ
Actually Prune, I completely disagree with you. I fail to see how itâs ill-disciplined to try and improve comms between the corps, and as long as they arenât restricted or classified in any way then I fail to see the harm.
This thread idea gets a +1 from me. Weâll just have to be careful to distinguish between local policy and corps policy.
There have been numerous instances where important policy changes have been highlighted here, either to advise CFAVs of the new documents (as there had been limited or poorly co-ordinated publication), or, to advise of significant points within new documents as the changes hadnât necessarily been side-barred or considered necessary to mention - deletion of qcWHT for example. The subsequent discussions have often brought up useful background information too.
There should be standard reporting of new documentation - direct to all units. If feasible (taking into account document size, format or privacy/security caveats), the document should be attached. If attachment is feasible or not, the relevant direct e-link should be included. Finally, as with standard Service Writing, all revised documents should be side-barred to show the changes. If necessary (such as a complete re-issue), a summary of the changes should be included to raise the awareness of the revision status/contents. Oh, if any document is put on âholdâ pending revision, it is just as important to publicise.
On a bulletin board, you can see ânewâ posts - can this type of function be added to Bader so that you can easily see changes to a section, especially documentation?
Itâs how large corporations work - the ACO is bigger & more complex than many such corporations; move with the times please.
This is bloody good idea and who knows might give Cranwell a kick. There was an initiative last year called something like Direct Communications with email alerts of documents to all ATC emails sent from a central source so that if Region / Wing or someone didnât want to pass on tough ⌠what happened to that?
We also need an email system that is of a modern business standard. Business email systems now work in at least TB not MB ⌠maybe someone should tell our SLT.
I bet all of the people working at Cranwell use Hotmail, Gmail, Yahoo etc etc for their personal stuff and Corps stuff as theyâre more efficient, relatively quick and have vast capactities, compared to the donkey and cart system we have. I asked one of systems bods about using sharepoint to strore documents and email links to the document and their response was itâs easier to email the document. They said people store the documents they need to elsewhere and delete the those they donât and that people are better at admining email accounts than they were.
[quote=âMikeJenveyâ post=22199]There should be standard reporting of new documentation - direct to all units. If feasible (taking into account document size, format or privacy/security caveats), the document should be attached. If attachment is feasible or not, the relevant direct e-link should be included. Finally, as with standard Service Writing, all revised documents should be side-barred to show the changes. If necessary (such as a complete re-issue), a summary of the changes should be included to raise the awareness of the revision status/contents. Oh, if any document is put on âholdâ pending revision, it is just as important to publicise. [/quote]As Iâve said many times before, CROs would be very handy. Simply put a paragraph stating whatâs been updated and why (anything from âACP 16 - fixing of typographical errorsâ to âPAM21C - significant rewrite; the changes in brief are as followsâŚâ) and then a link to the relevant document for those viewing it online to research further.
There really isnât any reason not to - as Iâve said many times, if itâs worth updating the document then itâs worth promulgating the changes, even if theyâre very minor.
That way, once a month staff could just have a quick flick through, and - to take shooting as an example - those with no interest could ignore the section, those vaguely connected could just read the changes summary so that theyâre informed and those that need to know can read the new document and take it all in.
[quote=âglass half empty 2â post=22207]This is bloody good idea and who knows might give Cranwell a kick. There was an initiative last year called something like Direct Communications with email alerts of documents to all ATC emails sent from a central source so that if Region / Wing or someone didnât want to pass on tough ⌠what happened to that?
We also need an email system that is of a modern business standard. Business email systems now work in at least TB not MB ⌠maybe someone should tell our SLT.
I bet all of the people working at Cranwell use Hotmail, Gmail, Yahoo etc etc for their personal stuff and Corps stuff as theyâre more efficient, relatively quick and have vast capactities, compared to the donkey and cart system we have. I asked one of systems bods about using sharepoint to strore documents and email links to the document and their response was itâs easier to email the document. They said people store the documents they need to elsewhere and delete the those they donât and that people are better at admining email accounts than they were.[/quote]
To be fair, I bet their allowances are bigger. Mineâs 150Mb not the usual 40mb.
Yes they would. However, CROs would require publication & subsequent dissemination/promulgation (how - email chain?) &/or a method to e-access them. That is additional work all round.
Keep it basic - ACO sponsor updates ACTO 3333 - âHow to make Cup Cakes Safelyâ - emails central sqn distribution list with copy of document (if feasible) & including e-link. As a bonus, it would also give greater visibility to who is changing what (& when, & maybe been why!)âŚ
CROs already exist, are already posted on sharepoint and, if the right notifications are set, are already emailed with links to users. that need not change but those CROs (or a similar document) should provide a weekly or monthly digest with details of all policy changes and links to the master documents.
I agree with much above, that Policy dissemination, and awareness of amendments to documents is poorly carried out currently.
I do not agree that we should be putting such things out âin publicâ here. By all means refer to it so people can go and ask the chain of command or log on to sharepoint, but I donât think it is wise to start publishing internal documents in this way.
In this particular case, All Sqn OCs were sent the e-mail, so If you have not seen it, it is the local chain of command you need to address that with.
I suppose there is a risk that the general public will see what a shambles the organisation is and realise the levels of crap that we all need to put up with.
Yes they would. However, CROs would require publication & subsequent dissemination/promulgation (how - email chain?) &/or a method to e-access them. That is additional work all round.
Keep it basic - ACO sponsor updates ACTO 3333 - âHow to make Cup Cakes Safelyâ - emails central sqn distribution list with copy of document (if feasible) & including e-link. As a bonus, it would also give greater visibility to who is changing what (& when, & maybe been why!)âŚ[/quote]I already have 150 unread emails in my ATC inbox because I keep getting sent stuff that is absolutely nothing to do with me.
I really do NOT want an extra email every time someone updates a typo on ACP1812.
The points about posting internal things here are valid, so maybe if someone sees something that should be promulgated, why not do an all Bader all sqns email from an anonymous non Bader email to avoid a backlash. Iâm sure there would be a reaction. When the email about changes to a foreign camps form went countrywide there was a snot mail soon coming out, saying not the way to do it. But I thought it was as it exposed what I regarded as a smug attitude at HQAC.
I really do NOT want an extra email every time someone updates a typo on ACP1812.[/quote]
just as a FYI - ACP1812 was removed 12 months ago and has been superseded by ACTO 123 (Feb 14)
I suspect you may have picked out a ACP by random, and dont use 1812, but it does surprise me how many people are not aware of the change of policy document and the advantages it brought (musicians badge now only requires grade 3 rather than 5 to qualify)
I couldnât care less about band stuff so would have no particular interest in the contents of 1812, however had there been a system such as the one that I described above then I would have at least known about the change - handy if anyone asked me where to find info.
i have had a discussion against many on a well know Cadet Facebook page some of whom who claimed all sorts of qualifications, 100yrs experience and grade 99 in 14 different instruments* but yet were insistent i was wrong despite quoting the regs.
why did this happen? they were not aware of the changeâŚleaving the uneducated bowing down to peopleâs superiority because there isnt adequate notification of changes/updates/modifications to policies or orders
*i may be exaggerating to colour the story up a bit
