As far as I know, there is no “official” definition of what’s acceptable and what’s not for logging activities. The practice we adhere to is:
- Only official unit or other activities conducted “under the auspices of the BSA” are logged, either at the pack or troop level, since these
- Service activities approved by the unit leader or their designee may also be logged, even if not conducted specifically under the auspices of the BSA
Item 1 is done that way since camping and hiking nights/miles, whether at the pack or troop level, may be counted for some of the national outdoor awards as long as they are conducted “under the auspices of the BSA”.
Item 2 is somewhat more flexible, in that (as far as I know) there is no equivalent award for hours of service, and whether or not hours of service are “counted” for rank purposes is based on the unit leader approval.
For not-yet-implemented logging like cycling miles, stock riding miles, paddling/sailing miles, etc, I anticipate that we will treat those somewhere between Item 1 and Item 2, since those could count toward outdoor awards if conducted “under the auspices”, but can count toward things like merit badges, even if conducted individually (e.g. Cycling MB), at least when conducted once the scout is in Scouts BSA. There are still some logistical items to be addressed.
With regard to “flexibility” derived from the COVID quarantine issues, those variances have been handled as being “under the auspices of the BSA” to the extent that the activities comply with the variances authorized by nationals. Does that word soup make sense? I rewrote it a couple of times, and this was the best I could come up with.
I don’t have a moral objection to logging all activities (unit, subunit, and individual) in all categories. However, it can lead to confusion down the road when trying to review/approve activities. For example, at present, there is no way to mark an activity entry as “Not Approved”, to edit it to make the entry approvable (e.g. wrong information entered), nor to delete it.
The ability to mark something “Not Approved” and have it disappear from the Needs Approval list would be helpful, since it would indicate to the scout/parent that the entry has been reviewed and rejected for some reason (having an optional “Explanation” dialog box would be great), and would eliminate the visual “congestion” that will tend to build up as increaing numbers of activities are added. The ability to edit/correct an entry made by a scout, parent, or other leader would allow the reviewing “authority” (e.g. unit leader) to correct a date or data error in the entry (e.g. 100 nights instead of 10 nights, etc). The ability to delete an entry would be helpful since that would allow for removal of duplicate entries, as distinguished from entries that are “Not Approved” for some reason but are not duplicates. This could be relevant in situations where, for example, two sets of entries were created for the same event, a “group” event by a leader and an “individual” event by the scout/parent. That would allow consolidation of the data under a single event for clearer record keeping.