DRAFT IBN - Proposed change to Gold Shot criteria

As far as I can see under all the required protocols, it’s one shoot = one RSD. I can’t find anything that lists a “repetitive” RSD or one that covers multiple shoots over a set period. As such, I don’t see any way (happy to be corrected) where an SPO could assist in that respect.

As it is, if other SPOs are in similar positions to ours, they are probably “multi-hatted” (OC a sqn, sector commander, OIC wg / region something else) so anything to ease their admin burden would be of benefit.

Wasn’t it SASC who initially amended the safety drill for the L144 so it could be carried with the bolt closed (to avoid rain getting into the chamber on an outdoor range?)?

I still hate giving the “ease springs” command for AIR rifle - there isn’t a spring of any kind!

1 Like

Perhaps highlight it as a safety issue - it was quite clear that SASC just did a bodged copy/paste jobs when writing the PAM.

2 Likes

Agree, raise a change request.

This is what you said… so working with your SPO to have authorisation at short notice is the easiest way to manage it.

That way you spin up the SMS app on the day when you are certain you’ll be shooting and what staff you have.

Crikey - put that in the system about 10 yrs ago! Wouldn’t it be nice if we could use flexi-plastic cord like they do in NSRA safety protocols…

If it’s not in the current change request system and pre-cursured the current TDT then it won’t have been actioned.

Nah, that’s unworkable. We have the required staff on nearly every parade evening. It’s not fair on the SPO for me to fire off a draft RSD on the day, expecting them to approve it. Then I would have to upload it, get OC approval, then finally SPO to give overall approval. A “standing” or repetitive RSD is the way ahead - clearly the activity could not go ahead if the staff requirements were not met. Yes, I could action about 100 RSDs to cover all parade night in a yr - ain’t going to happen!

Oh, bin the requirement for CFAV to be “ammo orderly” for AR; it’s the most superfluous / naff requirement ever!

3 Likes

That’s probably the issue.

Sorry, but it is possible, with discussions.

Had a request for a short notice addition to an L144 shoot to be run the following day. RSD submitted, an hour later I started to review and approved, sent back and the RCO uploaded to SMS, 2 hours later i recieved the SMS and approved. (Took longer as I was working)

Was additional to extra previously reviewed and approved.

That’s somewhat different I would suggest than a standing / repetitive RSD.

Our SPO is very flexible to requests, however, they work & considering their work / home / RAFAC workflow & loading, they generally look at a 2-3 week approval process for RSDs. I don’t have a problem with that; I plan ahead accordingly.

1 Like

Back in the day I used to raise one RASP to cover the three months of 5-6 range bookings I’d put in with the local Army Reserve Centre at a time. It was the same qualified people running the range every time in the same location.

Introduction of RAMs and RSDs created a significant uptick of LFMT admin due to its one time use, for one RCO, and the cut and paste for every new version that came out (we as an org have a real problem with not using the latest version of a form for even superficial changes). Initially RAMs seemed helpful in cutting single-event admin, then every new release made the document grow and grow into just a tabular format of a full RASP, without the benefits of a RASP. Then, we kept adding our own extra things like standard blocks of text suggested by RAFAC wing/region shooting pers (issued service hearing protection, ENI numbers on eye protection, AED locations etc.). Digital signatures have also been a more recent-ish pain for our less IT savvy people. I need a look up way I can digitally countersign RSDs when I’m reviewing docs on my phone, otherwise I currently need to be on a particular laptop I’ve set it up on.

I’m generally flexible with my planning officers if they let me know of a short notice plan provided I’m not on holiday or something, but region currently insist on events being submitted for wing approval 2 weeks in advance and approved by wing one week in advance, so they can audit things before they’ve happened. I’ve asked a couple of the regulars if they can bulk submit several RSDs for multiple dates rather than trickle feed RSDs one by one to cut down my context switching.

Two easy changes I’d like to see are:

  1. A blank RSD form for planning officers to use (i.e. not the pre-filled example we currently find in CT-R Supporting Documents). As SPO, I’m regularly returning RSDs where someone has left in the default values for things like who completed the risk assessment or the RAU telephone number.
  2. If Air Rifle LFMT could be Self-Approved by sqns after demonstrating they can complete the admin correctly. I still have to countersign an RSD anyway and do the SPO checklist.

More on topic, I’m in favour of matrix progression rather than linear progression, so having both competition or FCC as options is good with me as long as they have also achieved Silver Shot. I already mentioned this in my email feedback the first time around, but attending an FCC doesn’t demonstrate a cadet’s personal progression but accept that there’s no easy way to offer an actual instructor qualification to them for Gold level.

2 Likes

That would be very handy.

Effectively, & whilst I do check each RSD to make sure I haven’t missed anything(yes, copy / paste for a new version is a faff!), effectively, I’m only adding a different SMS reference, date of planned event, & date of range recce / reading of range orders. The last 2 will normally be my last shoot (or most recent parade evening if we haven’t shot for a while).

If it is “my” sqn range, then I know that a range recce won’t have changed anything, & range orders haven’t changed. Shooting personnel will be the same.

That’s why I would like to push for a “repetitive” RSD (& / or one that covers a set period).

I had a Scouts equivalent of RSD somewhere, don’t think it needed upward approval; much simpler.

1 Like

I think this self-approval of low level activities is what the RAFAC is missing. Time and again I have said there are certain activities which are bread and butter for a qualified staff member which should (provided the CFAV is SQEP) be self approved:
RCO - Running an AR Range at their own Squadron
AT - Running a 2 Day Expedition
First Aid - Running YFA
Etc

I am sure @Baldrick will confirm if the SCC have to out in a separate AT applications every time they get in a boat.

1 Like

I did one set of paperwork to cover me for every canoe session this summer.

1 Like

But can the SCC or ACF bulk approve air rifle shooting as you all want the RAFAC to enable?

My argument is we have trained the staff - let us get on with it. I’m not saying straight away, so a new RCO goes through the usual procedure, but by the time you have run 10 ranges you’re pretty ok with it.

2 Likes

i have to agree

if we train CFAVs to be CFAVs(!) then they should be competent at managing the SMS requirements for non SME events - day trip to an air show or aviation museum etc.

throw in an event which requires a qualification, be it shooting, AT, or otherwise then it is a case of bringing the two together…SMS event skills with an ability to know what as the SME is required for the event

and it turns out Robert is your Dad’s brother…

except it doesn’t end up that way…

There is a fine line, we see people bending/breaking rules as it is with the current system, is that because it is admin intensive and they are lazy? Would people comply more when given the responsiblity to manage this themselves?

I have a national overview of this sort of stuff and I’m afraid the truth is that the few will ruin it very quickly for the many.

I’m not really sure I’m following this argument very well.

For most non-RTL activities Sqn OC’s can approve already (it makes sense that the Activity IC isn’t also the approver).

For RTL activities it makes sense that it would require an additional set of eyes for assurance. Particularly as the Activity IC and/or Sqn OC may not be SMEs for said activity.

Tell me if I’m missing something.

Edit for clarity: I think the single RSD thing is a good idea, rather than one per shoot.