What I learned from this module is that most advisory boards — including mine — don't have bylaws, and the reason is structural: states don't require them. Sign-in sheets and meeting minutes are what get reviewed during program approval. Bylaws aren't on the checklist, so they get deferred.
The course made the case for why that's a mistake. Bylaws are what new members read to understand what they signed up for. They're the only thing that survives leadership turnover. And they shift the board from being held together by relationships to being held together by structure.
I'm writing ours this quarter, and the approach I'm taking is to separate what should be locked from what should flex.
Locked in the bylaws: purpose statement, member qualifications, term lengths, the four-subcommittee structure, decision-making authority, and the amendment process. These are the load-bearing pieces.
Held in lighter documents underneath: subcommittee charters, meeting cadence, contribution tiers, work plans. A subcommittee chair revises their charter annually without triggering a full amendment. That lets the work breathe.
The piece I'm building in that the module doesn't quite name: an annual bylaws and charter review on the calendar. The review IS the flexibility. If you don't schedule it, the document calcifies the moment you adopt it.
How I'm applying it: bylaws drafted against a year of real operating data, subcommittee charters as separate evolving documents, and an annual review built into the IAC calendar.
