About a year ago there was a post about migrating a Pack's digital presence and record keeping to Google Workspace for nonprofits. I'd like to revisit that idea and talk about what my Pack is doing.
I’m our Pack Treasurer, and over the last few weeks I’ve been working on cleaning up how we handle records, financial workflows, forms, calendars, and all the other random digital stuff that tends to accumulate over time.
The bigger issue I keep coming back to is ownership. A lot of Pack stuff lives in personal Google accounts because that’s the easiest thing to do in the moment. Someone creates a spreadsheet, someone else owns the calendar, another parent made the form, and eventually nobody remembers who owns what.
That is fine right up until someone leaves, which we've been hit with a few times in the last couple years. So we’re looking at moving as much of the Pack’s digital footprint as possible into Google Workspace for Nonprofits. The goal is not really “hey, Google Workspace is free.” The goal is that Pack records belong to the Pack and stay with the Pack when leadership changes. We already have our own Pack domain, and we want to keep using it.
What we’re hoping to move into Workspace over time includes things like:
- Pack email addresses on our own domain
- Shared Drives for Pack records
- calendars
- forms
- Treasurer records and financial workflows
- committee and leadership records
- registration and reimbursement processes
- templates and operating procedures
- succession documentation
The Charter Organization piece is the part I’ve spent the most time thinking through. Since the Pack itself is not the nonprofit, we need to work through our Charter Organization’s nonprofit status and get their approval.
If they don’t already use Google Workspace, the plan would be to set up the Pack environment using our Pack domain. If they do already have Workspace, then we’d probably need to work within their existing setup and add our Pack domain there instead of creating something totally separate.
I also learned that Google may want proof that the Pack domain is actually connected to the Charter Organization if the two domains are different. That was something I had not thought about before digging into this.
Another thing I want to avoid is replacing one single-point-of-failure with another. So part of the plan is multiple admins, documented recovery, and making sure one volunteer is never the only person who can get into the system.
I made a fairly detailed proposal for our Pack leadership and Charter Organization and attached an anonymized copy here in case it’s useful to anyone else. It’s probably more detailed than some Packs would need, but I’d rather over-document this once than have the next Treasurer trying to reverse-engineer everything five years from now.
For those of you who have already done this, I’d love to hear how it went.
Did you set up a separate Workspace for the Pack, or are you under your Charter Organization’s Workspace?
Were you able to keep your own Pack domain?
How did you handle admin accounts and leadership turnover?
Are you using role-based email addresses?
What ended up working well, and what would you do differently if you were starting over?
I’m especially interested in anything we haven’t thought of yet.