I just mass deleted a load of SMS email notifications.
Coincidentally, I also just spammed my inbox with read receipts telling me that I deleted my own message without reading it.
Why is this a thing?
2 Likes
That’s your fault for requesting read receipts.
System has had them since the dawn of time in relation to events being submitted for approval & approved…
1 Like
Ah. I somehow forgot that. I just have a vendetta against people that request read receipts
1 Like
I’ve turned them off on WhatsApp after starting this job.
People would send me a request for something, which I’d park until I could get around to it, then get offended that I hadn’t actioned their request as soon as I’d read the message. Now they don’t know if I’ve read the message and they’ve stopped whining.
“The Galactic Empire supports flexible working practices.”
1 Like
Sorry?
What
They want all questions to reflect the naked truth.
Was that meant to be “new versions”?
So avoiding repeat questions and upvoting ones similar to what you want to ask.
1 Like
I assume they wanted to avoid ‘rude’ questions!
Definitely telling on ourselves that we haven’t watched it…
Yet (honest).
I like the video format but never have time to watch the recordings, so I just ask ChatGPT to summarise the transcript…
Summary
1. Overview
This RAFAC digital townhall covered updates on the organization’s digital strategy, current development priorities, resource constraints, and future plans.
2. Digital Strategy and Priorities
2.1. New Digital Strategy
- The overarching goal: eliminate paper-based processes, unify procedures across regions/wings, and leverage data to inform better command decisions.
- Emphasis on “education and being driven by data.”
2.2. Resource Limitations
- Currently 1 full-time paid developer and a volunteer developer team.
- The volunteer developer team recently expanded to 10 members. Two new junior civil service devs are planned.
- High-impact “hand grenade” projects (e.g., MyRAFAC, Eclipse) consumed much needed dev time over the past year.
2.3. Immediate Development Focus
- Commandant’s #1 priority: digital VA (Form 80) and 1771 to reduce admin burden for volunteers and better track the budget.
- Overhauling event management (currently in SMS) is also on the roadmap, but it’s not the immediate top priority.
3. Progress on Key Projects
3.1. Volunteer Allowances (Form 80) & 1771 Claims
- A prototype for electronic claims is nearly ready.
- Testing with a pilot unit or wing is expected soon.
- The system will automatically handle rank details, partial attendance days, etc., reducing manual checks and errors.
3.2. Safeguarding & Integrations
- Integration with safeguarding tool Eclipse. Significant dev time spent ensuring compliance.
- Westminster-CCF integration to eliminate dual data entry; future expansions will share more data with minimal user effort.
3.3. Migration Away from SMS
- SMS is outdated and will be replaced by newer portals (Admin Portal, Volunteer Portal) module by module.
- The process is slowed by limited dev capacity and the need to build new features with “jam” (value-add enhancements), not just replicate old features.
3.4. Performance & Encryption Changes
- Encryption in some areas was removed to speed up performance.
- The system is now generally faster, with fewer reliability issues.
4. Future Features and Challenges
4.1. Events & Activity Approvals
- A brand-new events system is planned, but building it right (with integrated risk assessments, etc.) takes time.
- People want easier ways to update events so cadets automatically see changes without having to “push” info multiple times.
4.2. Digital 3822A and Informed Consent
- Fully electronic cadet joining forms (3822A) and “informed consent” for activities are on the roadmap.
- The complexity lies in obtaining and storing parental consents without a parent portal (yet).
4.3. Parent Portal
- A parent portal option is acknowledged as highly desired.
- It’s on the to-do list but hasn’t reached the top of priorities yet.
4.4. Notifications & Emails
- Efforts underway to improve notification settings (e.g., letting staff choose how many automated emails they receive).
- Cadet email accounts via RAFAC might not happen; Teams and OneDrive access for cadets is under trial, but not email.
4.5. Barriers to Full Replacement of SMS
- Event management and qualifications still live in SMS.
- The user community sometimes prefers first finishing big new features (e.g., e-VA) before tackling complete SMS migration.
- Ensuring new tools significantly reduce admin overhead, not just replicate old processes, is crucial.
5. Citizen Developers & BADER Officers
5.1. Citizen Developers
- The organization has volunteers building SharePoint, Power Apps, and other solutions filling functionality gaps.
- This leads to “shadow IT” if not centrally coordinated (multiple vehicle-booking systems, etc.).
- Plans to unify these efforts so solutions can be shared and integrated, rather than duplicated region-by-region.
5.2. BADER Officers’ Role
- HQ wants BADER/IT officers to be “super users” with extended permissions.
- A “BADER Officer Conference” is planned to give them training, clarify their responsibilities, and possibly grant them more system access for better local support.
1 Like
That summary is great, I was away for the live session and haven’t had time to watch it back. I don’t think I need to now, having read that. Thanks 
@Wizzle that sort of summary would be good added under the video on the weekly brief 
just on my regular regulation scroll, the Small Arms School Corps wear Similar colour Chevrons to our No1 in their Barrack dress
and an embroidered cloth crown
