I do think one of the biggest challenges to transitioning to a better system would be figuring out how to synch duplicate member ID numbers - as figuring out how to synch individuals who have had multiple Council-issued id numbers is an issue now. But then, it would be a one-time fix (albeit on larger scale), now, it’s a recurrent problem (albeit for fewer individuals).
But I think some of these other new concerns would be dealt with in the change of paradigm itself. Instead of thinking how to fit the current model into newer technology, we have to change the model in its entirety, by focusing on individual membership rather than organizational charters.
That is not to say do away with the charters entirely, but to always go back to the individual Scout or Scouter registering and being registered with BSA as the fundamental operative focus.
When you get to Jan 1, and you haven’t had the requisite number of adults and youth complete the online individual renewal, your unit will cease to exist. Or what if you all pay, but you COR/IH refuses to sign their annual agreement? In both cases, what happens to the money individuals paid?
Refunds are not difficult. However, the important thing is that the Scout/ers are registered. If an org decides to stop chartering a unit, there are ways to find a new one or transfer scouts to another unit, or put them in Lone Scout status, or default to a virtual unit in the interim. To send them an auto message that this particular unit is going offline in three months and they need to find a new one, whatever. This issue shouldn’t really affect whether a Scout/er is registered, just where.
Further, you would also be asking your COR to log in multiple times for each position change instead of a single time for all of them.
I’m not sure that’s a bad thing. Important is that data is up-to-date. Positions change throughout the year, not just on an annual cycle. If that reality is not reflected in the data management system, then it is pointless to have and we rely on excel spreadsheets and shadow databases instead. CORs should be engaging at least monthly with the Key-3, so it’s no big ask to log on, click a button, and log off - and certainly less cumbersome than the recharter process for them.
The way the bsa sees it, they’ve paid for a full year of scouting. So, dropping them completely off a roster would be removing them from a service that they paid for mid-term. I think having an inactive flag that could be set would be a more likely solution to that.
Sure - they have paid to be registered with BSA for the year. But if they move in June, there is no reason they should still be showing up in the system until the following March, which is what we have now. And that’s only when it works like it is supposed to. Sometimes they linger a year beyond that!
Better that as soon as someone moves, they can be transfered out - ideally to a new unit in a new council without anything more than the click of a button, but if into some transfer limbo (or temp. Lone Scout status or whatever) while they find a new unit, that’s better than false data clogging the rolls.
This is perhaps more significant an issue with adult volunteers than Scouts. Just try getting a training chair to run a ‘trained unit leader’ report and find anything useful when 1/3 of the names that appear haven’t been anywhere in the Council/District for months. Or any other use of the data system. So much better if the data is accurate to within 24-48 hours, rather than 9-18 months.
But, I acknowledge getting from here to there, wherever it ends up being, is a lot of work that, even if it should have been done decades ago, is now facing unique and significant challenges to time and resources. I’m grateful for the moves BSA is able to make, especially toward eliminating paperwork and increasing data efficiency and accuracy.