What would dodge the inevitable politics about which is better is adding a unit level setting for whether events should appear on CP automatically or not
I expect most squadrons would choose not. Itâs awkward if something goes up on CP and cadets see it and then you have to unadvertise it and potentially remove them.
A better option might be for units to get an email notification when they are invited to something (which includes the basic event info) with buttons to say âyesâ or ânoâ to advertise.
There is the added complication that we currently have the option to customise the CP details for our unit, which you may need to do for some events.
There is a fairly sensible middle ground. Currently, staff have to go on and advertise events to cadets. This is good as it allows staff control over what their cadets see, but is a bit of an admin burden, and often events get missed and cadets donât see it.
Most people are against events being automatically pushed straight away to their cadets.
So what about a cool down system instead? Wing staff create an event, tick a âadvertise in Cadet Portalâ box, but it wonât be advertised for, say 7 days. So Sqn staff can still, if they choose, go in and stop it from going to their cadets. But if they donât do anything, then itâll auto-push after 7 days.
This doesnât increase any admin burden, as going in to stop it is the same as having to currently go in to put things onto Portal. It sort of reduces burden, as if the staff arenât worried about cadets seeing all events, they now donât need to log in and advertise them.
The problem with that is invariably sqns have to make adjustments to event details prior to publishing to CP, such as drop off and pick up times if providing transport.
We currently have a deadline date on SMS why not have an âadvertise fromâ field?
This allows events to be started as draft several months before hand and then advertised in the date the organisers want them to.
Secondly why not have the notification emails about events only be sent on the cadet portal deadline date - avoids unnecessary emails cluttering the system & reduces the micro management.
I did say that ![]()
You did.
The primary purpose of this release is to roll out the claiming of Volunteer Allowance (VA) electronically to the whole organisation.
Itâs finally happening!!

Video was really useful.
Glad that you can also switch between Primary and Supernumerary Posts.
Itâs been operational for a while, Iâm yet to use it. When Iâve tried it doesnât quite work in the way youâd want around travel time, which Iâve fedback to the team but donât know if it changed.
Itâs pretty quick and easy. Gotta make sure your SMS events are at least 4 hours long or they wonât show on the list though.
Well that was the issue. If the event itself isnât right but the travel time included takes the total time past the mandated number, you canât claim it and I think you should be able to.
Edit:
For example if i run an activity that is 3h30m long, and have a 15m each way trip to get to the activity, i think that is claimable currently on paper forms but it wonât be claimable digitally, meaning either you have to amend your sms activity to include fake hours or you have to inflate the travel time artificially to get it through, none of which are acceptable.
Sorry, I thought you meant the amount you could put for travel time. I think the last time I did it it wouldnât let you put less than 0.5 or 1 hour (canât remember which).
Unless things have changed, there is a minimum total duration for a half day / full day (4 or 8 hours) but then also within that is supposed to be a minimum training duration as well (2 or 4 hours).
Edited to add from ACP 300:
So in @pEpâs case a 3hr 30 âhalf dayâ event meets the minimum â2 hours contact timeâ
thus any travel time over the 3hrs30 and to extend the total over 4 hours meets the requirements for a 4 hour/half day criteria.
Yeah, but currently to claim VA for it youâd have to either fudge your travel time or the timings on SMS.
i am not disagreeing - i am simply adding to pEpâs case that with the policy wording shared, the activity is viable but the system does not allow it
Itâs here!
Iâve submitted my first claim and it was so much easier⌠no confusion around email subjects or combining claims to a single email and I can now really easily see what Iâve claimed.
Howâs it work before I go exploring later?
