Can't award a scout's rank because of a wrong date on a requirement that I can't change

@AaronDorn @AndyDuong

September 25, 2025 Scoutbook Plus Updates

I am having the same problem with a scout - BSA # 132428972. I cannot put in his Life Rank date because of a date hang–up in requirement #3. It seems to be picking up the date of a merit badge he earned after Life. I tried to back all merit badges earned after Life but it didn’t work. He is turning 18 soon and I need to get this fixed. YIS, Christine

@ChristineAylor - have you looked at this

September 25, 2025 Scoutbook Plus Updates

@Stephen_Hornak For my Scout, the final completion date for his Life rank was blank. Just now I added an incorrect BOR date and completion date and saved. I then removed the BOR date and completion date, and saved again, but the merit badges for requirement 3 did not reset. The issue persists.

can you please advise on next steps? Thanks for your help.

@AaronDorn- did you follow the steps AND note as posted in the change log?

@Stephen_Hornak Yes. All of the Scout’s non-Eagle required Merit Badges are already entered with completion dates earlier than the Eagle-required badges. Per the instructions and note, the badges listed for Life requirement #3 should have recalculated when I added the Life BOR and rank completion dates and then deleted those completion dates. The recalculation did not occur.

I am still having the same issue with a Star Rank. I am unable to enter BOR date because Req 3 has later date. All non-Eagle Merit Badges for Star Rank have an earlier date than the Eagle Merit Badges and non of the Merit Badge dates match the date of completion for Req 3. It appears to be pulling in from Eagle Merit Badges not required for Star Rank. I followed the steps and note on the change log and had no success. I also tried removing the information related to the Eagle Merit Badge I think it is pulling from but that also didn’t work.

@GwenPerry, this is the same scout cited in your original post above, correct? Trying to make sure so the SUAC can provide the correct info to the developers for further investigation. Also, which MB did you try backing out that didn’t trigger the reset? I don’t know if it’s particularly relevant, but figured it was worth asking whole getting confirmation on the scout.

Yes, it’s for the same scout noted above. I backed out all Eagle earned Merit Badges completed after the Star Rank completion date I’m trying to input. I was unable to delete the Scoutmaster Conference date on Star Rank to try and get it to retrigger the reset. I received an error saying the prior rank was not earned. (For this scout First Class had been completed and awarded some time ago.) It seems like Star Rank is pulling in information from Life Rank.

Specifically, Star Rank Req 3 is pulling in the completion date for the most recently completed Eagle Merit Badge which happened to be Citizenship in the Community.

1 Like

I’m having the exact same issue. (Scout ID# 130697360) the merit badges shown in scoutbook plus do not match the scouts advancement record, I understand it is pulling the most recent merit badges, I also understand that I can not change that date. Point is the badges were changed by the system. I can’t make it go back to what it was, this prevents leadership from putting the correct dates into the system. The old system did the same thing, it just let us set the date and it pulled the merit badges. My question is why is the advancement report that I printed four hours ago different from what scoutbook plus shows? (yes, I mean the advancement report has completely different merit badges listed.) This has me confused.

Same problem…it says Req. 3 for Life was approved by me, but where? It’s just the merit badges. Scout ID 13793699

Here is a snapshot of Scoutbook Plus where I am stuck (same scout as referenced above). This scout finished the last merit badge shown in Req 3 on 6/21/2024. The 7/19/2025 was pulling in from a different merit badge, however, all the merit badges earned after 6/21/2024 were backed out, left incomplete for several days without a change. I also backed out the last merit badge entered here and reentered it. I have since reentered the later finished merit badges and the 7/19/25 date has not changed. When I hover over the Approved portion during these adjustments it changed according to whatever I was doing at the time, but the automatically pulled in date did not. If I can provide more info to help get this fixed, please let me know.

@GwenPerry

This is a known issue.

Watch Scoutbook - Scoutbook Plus Change Log - Scouting Forums for an announcement of a fix.

It will soon affect the scout’s Eagle Application, as it impacts the 6-month active requirement.

@EdwinSnyder

The developers are aware of the issue. Once fixed you will be able to enter the correct date for Life.

Thank you, This is actually an issue entering the completion of Star rank for my scout.

Here is my take on this because I had the same problem. There is a problem in how Scoutbook plus populates the Merit badges for Life and Star. Instead of just entering the required number of Eagle badges and then pulling from the optional merit badge population, it pulls all of the Eagle required badges and then fills in the gaps from optional. Not a functional problem unless you haven’t entered rank completion before they earn their next Eagle required Merit Badge.

To reset the system, you need to void the requirement - which means removing enough Eagle Required badges to invalid completion of the requirement. The easiest way to do that is to write down the dates earned, and remove one requirement from the most recently earned Eagle Required badges until they don’t have enough to fulfill the requirement anymore and it switches to In Progress as it’s status. Then add that one badge back in with the correct date, complete the rank, then add in the remaining Eagle Required badges.

This worked for one of my scouts with this issue and I have floated my request to have the logic reworked through our Council, but more voices may get this looked at more quickly. I did look at the change log and it says an issue was fixed on October 1, but I had to do the trick described above on Oct 11 after fighting with it for weeks. I was sent an issue resolution description around October 1, but it wasn’t this problem - it was another one.

3 Likes

That’s great investigation and work-around data, @SaraPecak. Thanks for digging into it and sharing with the rest of the class!

1 Like

@SaraPecak- bravo….excellent work