What's Broken in Scout Advancement Software Right Now

If you've tried exporting your troop's advancement data recently and gotten back a file full of garbled HTML tags, stray line breaks splitting entries across broken rows, or a CSV that opens looking nothing like a spreadsheet — you're not doing anything wrong. These are real, ongoing bugs, reported repeatedly on BSA's own official Scoutbook support forums, where staff have confirmed several of them as known issues still waiting on fixes. Here's a running list of what's actually going on right now.

A lot of this traces back to one root cause: Scouting America is mid-migration from Legacy Scoutbook to a newer system called Scoutbook Plus, and that migration is happening in pieces, over years, not all at once. The forums' own posted notice explains it plainly — positions, permissions, and features are being moved over gradually to match what's registered in my.Scouting, and until that's fully finished, some rough edges are expected. That context doesn't fix anything for you today, but it does explain why so many of these issues keep surfacing in clusters instead of getting resolved once and for all.

Report Builder wraps data in HTML markup instead of plain text

Scoutbook's newer Report Builder tool has been wrapping advancement statuses in raw HTML markup instead of plain text — so a cell that should just say "Approved" comes through as a chunk of link code instead. This has been formally reported and acknowledged by Scoutbook's own User Advisory Council as a known, currently unresolved issue.

Advancement exports contain stray line-break characters

Separately, the standard advancement export has been inserting stray line-break characters inside entries, which breaks the file the moment you try to import it anywhere else — a clean export can silently turn into a corrupted mess mid-row.

Rosters showing contradictory registration status

Some units have reported a Scout showing as "Current" on one unit's roster and "Needs to Register" on another for the same Scout — a real data-consistency problem that makes it hard to trust what the roster is telling you at a glance.

Leader notification emails silently stop arriving

A number of leaders have reported no longer receiving Scoutbook's notification emails at all, with no clear cause and no warning that it happened — meaning approvals, messages, or updates can pile up unnoticed unless someone happens to check manually.

Service logs and pending activities disappearing from view

Separately reported on the same official forums: service hours that were previously logged and approved disappearing from a Scout's record entirely, and activities sitting in an "awaiting approval" state simply not showing up for the leader who's supposed to approve them. Both mean real, completed work can effectively vanish from view even though it technically still happened.

The pattern underneath all of these bugs

Once you look at enough of these reports together, a pattern shows up: almost every current issue traces back to a seam somewhere in the Legacy Scoutbook to Scoutbook Plus migration — a feature that exists fully in one system and only partially in the other, or a data field that's supposed to sync between them but doesn't always. That's not an excuse for the bugs, but it does mean the smart move is treating anything mid-migration with a little extra suspicion, and double-checking outputs rather than assuming a report is correct just because the tool produced it.

How to actually report a bug so it gets looked at

A surprising number of real, valid bug reports never make it anywhere useful because they get posted as a one-line comment buried in a large forum thread. If you hit something broken, the official Scoutbook support forum is the right first stop, but it's worth doing it properly: include the exact steps that reproduce it, a screenshot if you can, and what browser or device you were using. Volunteer moderators and BSA's own Scoutbook team do monitor these forums, and specific, reproducible reports get triaged far faster than vague "this isn't working" posts. If you're a registered leader, your council's Scoutbook support contact (often listed on your council's own website) is a second path worth trying for anything urgent, like something blocking an upcoming court of honor.

It's also worth checking whether an issue is already known before reporting it fresh — the User Advisory Council's own posted list of acknowledged issues is a good first stop, since a bug that's already confirmed doesn't need a new thread, just a "me too" on the existing one, which actually helps prioritization more than a duplicate report does.

What's actually gotten better, to be fair

It's worth being fair here rather than only listing complaints: some real improvements have shipped over the course of this migration, even if the process as a whole has been rocky. Internet Advancement 2.0's mobile experience is a genuine step up from what existed before it, and several sync issues that were widely reported in earlier phases of the migration have since been resolved. The honest takeaway isn't "this software is permanently broken" — it's "this software is mid-transition, and mid-transition software needs to be double-checked more than finished software does."

Building a workaround culture in your troop

Beyond any single bug, the most resilient troops treat Scoutbook's occasional breakage as a known operating condition rather than a surprise every time. That means keeping a backup export on hand before any big event that depends on accurate records (a court of honor, a summer camp roster), having more than one adult who knows how to pull a report so it's never a single point of failure, and building in a habit of spot-checking anything Scoutbook exports against what you know to be true before trusting it fully. None of that fixes the underlying bugs, but it means a bad export catches you mid-week instead of the night before it actually matters.

How to work around this today

Skip Report Builder for now and use the plain advancement export under the Reports section instead — it's a cleaner, older export path that isn't affected by the same HTML-markup bug. If a file looks corrupted, open it in a plain text editor first (not Excel) to see exactly what's in it before deciding whether it's usable. And if leader emails have gone quiet, check the platform directly on a regular schedule rather than assuming you'd be notified.

The part that's actually the bigger problem

Even when every export works perfectly, none of this was ever built to answer the one question that actually matters — what does a Scout still need? A clean CSV full of rows and columns still isn't a roadmap. That's the gap scoutpath.tech fills — upload the same report and it turns into a real dashboard: what's done, what's left, and what to work on next, tagged by urgency.

It's completely free. Try it at scoutpath.tech.