When running a Custom Roster Report, the generated CSV is missing the appropriate commas for second (and subsequent) adults/guardians of a Scout. This makes the output basically unusable without significant effort to realign data (see image).
Request custom reports be fixed to provide correct output.
The “home”, “mobile”, and “work” appended to numbers is also annoying, but not as much of a show-stopper if the necessary commas were present.
@RyanTashma not sure I understand from a CSV perceptive. is it that the Scout name is NULL for the for second parent? What is the REF# of the report?
ref: PD-20260725181336-637235-588916
NULL name for second (and subsequent) adults isn’t the biggest problem, or at least it’s easily fixed.
If you look at the raw file, it’s more obvious:
" ","YOUTH MEMBERS"
"5","K***","B***","","L***","(***) - Cascade Pacific Council 492 - Mother of - Guardian","(4**) ***-**** home","","(4**) ***-**** mobile","***@gmail.com",
,,,,"J***","(***) - Cascade Pacific Council 492 - Father of - Guardian (4**) ***-**** mobile","***@gmail.com",
Whereas the first parent has a comma separation between “Guardian” and their first phone number, and a null value with comma separation for missing numbers, the second (and subsequent) adult lacks a comma separation after “Guardian” and doesn’t have any comma separations for missing phone numbers.
This results in second (and subsequent) adults’ information not being aligned under the proper columns. Our troop has 50 Scouts, our pack has 80+. Trying to have a compact, printed report we can put on a clipboard is nearly impossible. I spent about an hour using Power Query with Gemini’s assistance to clean the data because I’m a giant nerd, but that is an awful way to run a railroad. (FWIW, appending “home”, “mobile”, and “work” to phone numbers is only helpful when you’re using PQ to clean up the data into a usable format.)
Clearly, Scoutbook knows to put commas between fields for the first adult, but is missing that for others.
Yeah it is a tough one - cause the CSV is working as designed for that report - it is when you take it for secondary use that is the issue arises - it is being discussed.
Working as designed by if you load the csv is makes sense as the NULL name is in place.
But it’s not working as CSVs are designed to, because the values aren’t separated consistently. 
@RyanTashma I will send you a direct message > look at top right Avatar to find it > it will be a green envelope > it will be a private message channel with select members of the Scoutbook User Advisory Council (SUAC)
© 2026 Boy Scouts of America - All Rights Reserved