Welcome! This forum has a treasure trove of great info – Scouters helping Scouters! Just a heads up, though - all content, information, and opinions shared on this forum are those of the author, not the BSA.
For some reason, Scoutbook+ is showing my registration with our Pack as having expired 8/31/24, which is about when our unit started. My correct status is shown in our Boys troop and our Girls troop.
I reached out to our Scout Office and they said they can’t help troubleshoot Scoutbook.
I recognized it. The point is all those roles are expired in my.scouting. Only the Scoutmaster is active. Scoutbook plus seems to be having trouble knowing which one to base its singular date on.
Right. How do we update those expired dates? Our CC said when he adds positions to someone, it doesn’t give him a date option to set. Our Scout Office apparently also cannot see these dates, so I’m not sure how to edit them.
Our SE looked at it (we don’t currently have a registrar) and said it showed I was currently registered. She said she couldn’t see any expiration dates that I mentioned.
Well the Item that is wrong is that your SM position (expires 1/31/26) does not match up with Expire dates with your other registered positions - that end 6/30/25. All Expire dates are supposed to match for Registered positions, this might cause you issues.
Your Council can send in a National Membercare Ticket for a solution.
A couple of additional comments from what I’m seeing in your posts:
SM and MC shouldn’t be positions that can be registered simultaneously in one unit.
CC isn’t able to adjust registered positions in my.scouting (unless they are also COR or assigned by COR to COR Delegate functional role). Where is the CC adding positions?
They moved me from MC to SM a couple of nights ago.
I just checked and he is the COR/CUR Delegate, so that must be how he’s doing it. The SE said something about them using “Position Manager” (I think that’s what she called it).
There’s nothing that you or your unit can do directly about the overlapping positions, because of the 90-day grace period.
Your council may be able, as Donovan noted, to submit one or more MemberCare tickets to national to:
Correct the expiration dates to match. Without ruling this out, there’s no way to readily determine if it’s the underlying cause. That might also be why your pack positions are showing as expired (around this time of year, that might also be tied to whether or not your pack got there recharter processed in time).
National might be able to suppress the 90-day grace period for your former MC position, but I’m not even sure if that’s possible. It probably depends on exactly how it’s coded in the system, which I’m guessing will require national’s MemberCare team to engage with the developers who handle that system (who are not the same folks that SUAC can contact, who only handle the SB/SB+ system).
From what I’ve seen on these groups, it almost seems like changing registered positions for Key 3 in the online system doesn’t work very well, since there can only be one person in that role at a time. It’s not a big issue if there are multiple overlapping MCs, ASMs, DLs, ADLs or ACMs. However, since each unit gets one an only one SM/CM and only one CC, the system seems to be finicky about what happens when one person moves out and another moves in, apparently due to the grace period.
It seems like the only was this particular class of issues is going to get resolved is by council professionals agitating through their channels to national for a better solution, whether that it a two-step confirmation that the unit leader or CC is being changed in the online system by the COR/COR Delegate or whether the registrar gets a “button” to end the grace period that they can use on request from a unit (or some other idea that hasn’t popped into my head), it has to be implemented at the national level, which means council professionals will have to get behind it.