This post is offered as general nonprofit governance guidance, not legal advice. Bylaws are legal documents, and organizations should have final language reviewed by qualified legal counsel familiar with their state's nonprofit corporation law before adoption.
Most nonprofit leaders know their bylaws exist. Fewer than most have read them recently. And a meaningful number would discover, if they looked closely, that the document governing their organization's structure and operations describes an organization that no longer quite exists: one that mails things instead of emailing them, holds meetings in ways that predate video conferencing, or references committees that quietly dissolved years ago.
This is not unusual. It is, in fact, one of the most common governance gaps in the nonprofit sector. And while it is worth taking seriously, it is also worth understanding accurately. Because the appropriate level of concern depends considerably on what kind of mismatch exists and what the organization chooses to do about it.
What Bylaws Are Actually For
Before examining what happens when bylaws fall out of alignment with operations, it helps to be clear about what bylaws are supposed to do.
Bylaws are the foundational governance document of a nonprofit corporation. They establish the basic structure of the organization: how the board is composed, how officers are selected and what their responsibilities are, how meetings are conducted, how decisions are made, and how the bylaws themselves can be changed. They are the rules by which the organization governs itself, and they carry legal weight in the event of a dispute, an audit, a regulatory inquiry, or a leadership transition, the bylaws are the document that establishes what the organization is supposed to do and how.
That legal weight is exactly why misalignment matters. An organization that routinely operates in ways that contradict its bylaws is, technically, in violation of its own governing document. Depending on the nature and severity of the discrepancy, that can create exposure to IRS scrutiny, to state regulatory questions, to challenges from members or disgruntled former board members, or simply to the kind of organizational confusion that surfaces at the worst possible moment.
But not all misalignments are equally serious, and the appropriate response varies accordingly.
The Spectrum of Misalignment
At one end of the spectrum are administrative anachronisms. These are provisions that describe how things used to be done before practices evolved. A bylaw that requires mailing membership dues rates when the organization now posts them on its website. A provision about physical notice requirements that predates email. References to committee structures that have been reorganized. These discrepancies are real, and they should be updated, but they rarely create acute legal risk. They are the organizational equivalent of a policy manual that has not kept pace with how work actually gets done.
At the other end of the spectrum are structural misalignments. Misalignments are provisions that describe decision-making authority, officer responsibilities, membership rights, or board composition in ways that do not reflect how the organization actually operates. These are more serious. If the bylaws say the board must approve a certain category of expenditure and the organization has been routinely approving those expenditures without board involvement, that is a governance problem. If the bylaws describe membership voting rights that are not being honored, that creates potential legal exposure. If officer roles are described in ways that conflict with how authority is actually exercised, that ambiguity can become a liability during a leadership dispute or transition.
Most organizations with aging bylaws have some of both. The task is to distinguish between them and prioritize accordingly.
When Bylaws and Operations Drift Apart
Bylaws fall out of alignment with operations for understandable reasons. Organizations evolve. Technology changes how they communicate and meet. Programs grow or contract. Governance structures that made sense at founding become awkward as the organization matures. And bylaw amendments require formal board action, a threshold that creates friction and often leads to informal adaptation rather than official revision.
The problem is that informal adaptation, repeated over time, produces an organization that is governing itself by custom rather than by its own rules. Custom is fine when everyone agrees and nothing goes wrong. It becomes a serious vulnerability when leadership turns over, when a dispute arises, or when an outside party: a regulator, an auditor, a major funder conducting due diligence, looks closely at how the organization is actually governed.
The appropriate response to this drift is a bylaws review and amendment process: deliberate, board-led, and grounded in a clear understanding of what the organization actually does and how it actually makes decisions. This is not a legal exercise dressed up as governance. It is a governance exercise that benefits from legal input.
The Role of Legal Counsel and Its Limits
Nonprofit organizations should absolutely involve qualified legal counsel in a bylaws revision process. An attorney with nonprofit experience can identify provisions that create legal exposure, flag language that conflicts with state nonprofit corporation law, and ensure that the document is legally sound. That input is valuable and worth seeking.
What legal counsel is not positioned to provide, and should not be expected to provide, is organizational judgment. An attorney reviewing bylaws for legal sufficiency is not reviewing them for operational fit. A legally compliant document that describes an organization the board does not recognize, that references roles that do not exist, structures that do not apply, or authorities that conflict with how decisions are actually made, is not a good set of bylaws. It is a legally defensible document that governs a fictional organization.
The distinction matters because organizations sometimes receive bylaw revisions from counsel that represent a significant departure from the document they submitted, and feel pressure to adopt those revisions because they came from an attorney. Legal review is advisory. The board retains the authority and the responsibility to decide what its governing document says, and to ensure that what it says reflects how the organization actually intends to operate.
A productive working relationship with legal counsel on a bylaws revision looks like this: the organization provides a clear picture of its structure, its decision-making practices, and the specific provisions it wants to update or add. Counsel reviews for legal compliance and flags issues. The organization and counsel work together to produce a document that is both legally sound and operationally accurate. The final product should be recognizable to the people who run the organization, not a template adapted from another organization's governance structure.
What a Good Bylaws Revision Process Looks Like
For organizations undertaking a bylaws review, a few principles tend to produce better outcomes.
Start with operations, not the document. Before revising a single provision, it is worth mapping how the organization actually functions: how the board is composed and how members are selected, how officers are chosen and what they do, how decisions are made and at what levels, how meetings are conducted, how members (if any) participate in governance. The bylaws should describe that reality accurately, which means understanding the reality first.
Distinguish between what should change and what should be updated. Some provisions describe practices that have evolved and simply need to reflect current reality. Others describe practices that may be worth reconsidering during the revision process. A bylaws review is an opportunity to examine governance structure thoughtfully, not just to update administrative language.
Involve the full board. Bylaws govern the board as much as they govern the organization. A revision process that is driven entirely by the executive director or a single board officer, without meaningful board engagement, tends to produce a document that lacks the buy-in necessary for genuine implementation. The board should understand and endorse what the bylaws say, not simply ratify a document they have not carefully reviewed.
Amend deliberately and document the process. Most bylaws specify how they can be amended, typically requiring notice in advance of a vote and approval by a supermajority of the board. Following that process carefully, and documenting it in board minutes, is important. An amendment adopted without following the amendment procedure specified in the bylaws is itself a governance problem.
Plan for future maintenance. A bylaws revision that produces a clean, accurate, operationally grounded document is valuable only if the organization develops a practice of keeping it current. A periodic review, every three to five years, or whenever significant operational changes occur, prevents the drift that makes major revisions necessary in the first place.
Should You Be Worried?
Bylaws that do not match operations are a problem worth fixing. But the urgency and the approach depend on the nature of the misalignment. Administrative anachronisms warrant correction. Structural misalignments warrant prompt attention. And a revision process that produces a legally polished document the organization does not recognize is not an improvement over the document it replaced.
The goal of a bylaws revision is not legal compliance in the abstract. It is a governing document that accurately describes a real organization, that the board understands and endorses, and that can actually guide the organization's decisions when guidance is needed. That document is worth the time it takes to get right.
Nonprofit Snapshot publishes perspectives from across the nonprofit sector. Views expressed are for informational purposes only and do not constitute legal advice. Organizations should consult qualified legal counsel regarding their specific governance circumstances.