Your Bylaws Are More Important Than You Think
Most nonprofit founders treat bylaws as a box to check during formation. You need them to file your articles of incorporation. You need them for your 501(c)(3) application. So you find a template online, fill in the blanks, and move on to the work that actually feels like running a nonprofit.
Here's the problem: your bylaws aren't just a formation document. They're the operating manual your board is legally required to follow. Every board meeting, every vote, every officer election, every financial decision — your bylaws govern how those things happen. And when your bylaws are vague, outdated, or copied from a template that doesn't match your actual operations, you create problems that compound over time.
I've reviewed governance documents for organizations that have been operating for years with bylaws that contradict their actual practices. Board members who were never properly elected. Meetings that don't meet quorum because the bylaws set it too high. Amendment procedures so restrictive that fixing the bylaws themselves becomes nearly impossible.
The good news: getting your bylaws right isn't complicated. It just requires thinking through how your organization actually operates — or how you want it to operate — and putting that in writing clearly enough that any board member can pick up the document and understand the rules.
What Your Nonprofit Bylaws Must Include
Every state has slightly different requirements for what bylaws must contain, but the core elements are consistent. Here's what belongs in every set of nonprofit bylaws, and why each section matters.
Organization Name and Purpose
This sounds obvious, but it matters legally. Your bylaws should state your organization's exact legal name (matching your articles of incorporation) and your exempt purpose. The purpose statement in your bylaws should align with what you told the IRS on your Form 1023 or 1023-EZ application.
Don't copy your mission statement here. Your purpose statement is a legal description of what your organization exists to do under Section 501(c)(3). Your mission statement is a communications tool. They serve different functions.
Board of Directors
This is the most important section of your bylaws, and it's where most problems originate. You need to address:
Board size. Specify either a fixed number or a range (e.g., "no fewer than 3 and no more than 9 directors"). A range gives you flexibility to grow without amending your bylaws every time you add a board member. Most states require a minimum of one director, but three is the practical minimum for a functioning board — it allows for a president, secretary, and treasurer without one person holding multiple officer roles.
How directors are selected. Are they elected by the existing board? By members? Appointed by a specific person or organization? Spell this out clearly, including who nominates candidates and what the voting process looks like.
Term length and limits. Define how long each term lasts (two or three years is standard) and whether directors can serve consecutive terms. Term limits aren't legally required in most states, but they're a governance best practice — they prevent board stagnation and create natural opportunities to bring in fresh perspectives. A common structure is two consecutive three-year terms, after which a director must rotate off for at least one year before being eligible again.
Removal procedures. How do you remove a director who isn't fulfilling their duties, has a conflict of interest, or is actively harming the organization? Your bylaws should specify the grounds for removal, who can initiate it, and what vote is required. Without this, removing a problematic board member becomes a legal headache.
Vacancies. What happens when a director resigns, is removed, or can no longer serve? Who fills the vacancy, and does the replacement serve the remainder of the original term or start a new one? These details matter when you're trying to maintain a functional board through transitions.
Officers
Your bylaws need to define which officer positions exist, what each officer does, how they're elected, and how they can be removed. At minimum, most states require a president (or chair) and a secretary. A treasurer is strongly recommended even when not legally required.
For each officer, describe:
- Title and responsibilities. What does the president actually do? What about the secretary and treasurer? Be specific enough that someone stepping into the role knows what's expected, but not so detailed that routine changes require a bylaws amendment.
- How officers are elected. Usually the board elects officers from among its members, but your bylaws should say so explicitly.
- Term of office. Officers typically serve one-year terms, elected at the annual meeting.
- Removal. Can the board remove an officer before their term ends? Under what circumstances? What vote is required?
One common mistake: writing bylaws that require specific individuals to hold specific roles. Your bylaws should describe positions, not people. "The Treasurer shall oversee financial reporting" — not "Jane Smith shall serve as Treasurer."
Meetings
Meeting procedures might seem like administrative trivia, but they're actually a core governance safeguard. Your bylaws should cover:
Regular meetings. How often does the board meet? Monthly? Quarterly? State the minimum frequency. Most well-functioning nonprofit boards meet at least quarterly. If your bylaws say "monthly" but your board actually meets quarterly, you're technically in violation of your own governing documents every single month you skip.
Annual meeting. Most states require an annual meeting. Your bylaws should specify when it happens (e.g., "in the first quarter of each fiscal year") and what business must be conducted — typically officer elections and a review of the prior year.
Special meetings. Who can call a special meeting outside the regular schedule? Usually the president or a specified number of directors (e.g., "any two directors"). Define the notice requirements — how many days in advance, and how notice is delivered.
Notice requirements. How much advance notice is required for each type of meeting? Seven to fourteen days is typical for regular meetings. Special meetings may require less notice but should still have a minimum (48 hours is common).
Quorum. This is the minimum number of directors who must be present for the board to conduct official business. A majority of the board is the standard default, and most states will apply this if your bylaws are silent. But think carefully about your specific situation — if you have a nine-member board and set quorum at a majority (five), you need five directors to show up before you can do anything. Some organizations set quorum at one-third for large boards, but going below a majority can create legitimacy concerns.
Virtual participation. Can directors attend meetings by phone or video? Post-2020, most organizations allow this, but your bylaws need to explicitly authorize it. If your bylaws are silent on virtual attendance, you may have a legal argument that remote participants don't count toward quorum.
Voting. How are decisions made? Majority vote of those present? Majority of the entire board? Can votes happen by email or written consent outside of a meeting? Each of these should be addressed explicitly.
Conflict of Interest
The IRS asks about your conflict of interest policy on Form 1023 (Part V, Line 5), and while it's technically a separate document, your bylaws should reference it and require all directors and officers to comply. At minimum, your bylaws should:
- Require annual disclosure of potential conflicts
- Establish a procedure for managing conflicts when they arise (typically recusal from discussion and voting)
- Apply to all directors, officers, and key employees
A common mistake is having a conflict of interest policy that exists as a standalone document but isn't referenced in the bylaws. If your bylaws don't require compliance with the policy, enforcement becomes optional rather than mandatory.
Committees
If your board uses committees — and most boards of any size should — your bylaws need to authorize them. Address:
- Standing committees. These are permanent committees that exist regardless of who's on them (e.g., finance committee, governance committee). Name them in your bylaws and describe their general purpose.
- Ad hoc committees. These are temporary committees created for specific projects. Your bylaws should authorize the board to create them as needed without a bylaws amendment.
- Committee authority. Can committees make binding decisions, or only recommendations to the full board? This distinction matters. In most cases, committees should recommend and the board should decide — but your bylaws need to be clear about this.
- Composition. Can non-board members serve on committees? This is common and useful, but your bylaws should address it.
Fiscal Year
State your fiscal year. For most nonprofits, this is January 1 through December 31, but you can choose any 12-month period. Your fiscal year affects your 990 filing deadline, your annual meeting timing, and your budgeting cycle. Pick one that makes sense for your operations and stick with it.
Amendment Procedures
This is the section most founders don't think about until they need it — and by then, it's often a problem. Your amendment procedure defines how the bylaws themselves can be changed. Consider:
- Who can propose amendments? Any director? Only the governance committee? Only at annual meetings?
- What vote is required? A simple majority of the board? A two-thirds supermajority? Unanimous consent?
- What notice is required? Directors should receive the proposed amendment language in advance of the vote — not hear about it for the first time at the meeting.
The most common mistake here is setting the bar too high. If your bylaws require unanimous consent to amend, and you have even one uncooperative board member, your bylaws become effectively unamendable. A two-thirds supermajority with advance notice is a reasonable standard that protects against hasty changes while remaining practically achievable.
Dissolution
Nobody starts a nonprofit thinking about how it will end, but your bylaws need a dissolution clause. This isn't morbid — it's required. Your 501(c)(3) status depends on the IRS knowing that if your organization dissolves, its remaining assets will go to another tax-exempt purpose (not back to the founders or board members).
The standard language directs remaining assets to one or more organizations described in Section 501(c)(3) of the Internal Revenue Code. Your articles of incorporation should contain similar language, and the two documents should be consistent.
Indemnification
Your bylaws should include an indemnification provision that protects directors and officers from personal liability for actions taken in good faith on behalf of the organization. This doesn't protect against fraud or intentional misconduct, but it does protect board members who make honest decisions that don't work out.
Indemnification provisions vary by state, so this is one area where your bylaws should follow your state's specific nonprofit corporation act. The protection this offers is one reason people are willing to serve on nonprofit boards — without it, recruiting board members becomes significantly harder.
Common Bylaws Mistakes That Create Real Problems
Beyond missing sections, there are structural mistakes that cause ongoing governance headaches:
Bylaws that don't match actual practice. If your bylaws say the board meets monthly but you actually meet quarterly, you have a compliance gap. If your bylaws require a membership vote for directors but you don't actually have a membership structure, every board election is technically invalid. The fix isn't to ignore the bylaws — it's to amend them to match reality.
Overly specific provisions. Bylaws that name specific people, reference specific dollar amounts, or include operational details that change frequently need constant amending. Your bylaws should be specific enough to be useful but general enough to remain accurate as your organization evolves.
Copy-paste from the wrong template. Membership organization bylaws don't work for organizations without members. Church bylaws don't work for secular nonprofits. State-specific provisions from another state's template can create legal conflicts. Using a template is fine as a starting point, but it needs to be customized for your actual structure, state, and operations.
No review schedule. Bylaws should be reviewed at least every three to five years, or whenever your organization undergoes significant changes (new programs, new states, major growth, leadership transitions). Without a scheduled review, bylaws drift further and further from reality until a crisis forces the issue.
When to Get Professional Help
You can draft functional bylaws yourself, especially for a straightforward nonprofit with a small board. But certain situations call for professional input:
- Multi-state operations — charitable solicitation and corporate filing requirements vary by state, and your bylaws may need state-specific provisions
- Membership structures — member rights, voting, and classes of membership add significant complexity
- Existing organizations with governance problems — if your current bylaws are creating conflicts or compliance gaps, a governance review can identify what needs to change and prioritize the fixes
- Complex board structures — ex-officio members, designated seats, or weighted voting require careful drafting
For straightforward formations, Wylie Advisory's Nonprofit Startup Navigator includes bylaws drafting as part of the full formation package — we draft bylaws that match your specific structure, state requirements, and operational plans, so you're not starting from a generic template.
If your organization already exists and you're not sure whether your bylaws are adequate, a governance review is the most efficient way to find out. We assess your bylaws alongside your other governance documents, compliance status, and board practices to give you a clear picture of where you stand and what needs attention.
The Bottom Line
Your bylaws aren't a one-time formation document — they're the rules your organization lives by. Getting them right from the start saves you from governance headaches, compliance gaps, and board conflicts down the road. And if they're already wrong, the best time to fix them is before the next crisis forces the issue.
Take an hour to actually read your bylaws. Compare what they say to what your organization actually does. If there's a gap, that's your starting point.