501c3 Bylaws Requirements: A Drafting Checklist for Counsel

The 501(c)(3) bylaws requirements a nonprofit must meet are state corporate law requirements, not IRS requirements. Bylaws are the internal operating rules of a nonprofit corporation, and state nonprofit corporation statutes generally require a corporation to adopt them. Those statutes leave most of the content to the drafter: board size, officer duties, meeting notice, quorum and the procedure for amending the bylaws are the items bylaws customarily set, and the statute supplies a default for several of them that applies when the bylaws are silent. Federal tax law does not require specific language in the bylaws of most organizations. The exempt-purpose clause and the dissolution clause the IRS organizational test requires belong in the articles of incorporation, unless the bylaws are themselves the organizing document.

This guide sets out the 501(c)(3) bylaws requirements in the order a drafter meets them. It covers whether the IRS requires bylaws at all, which document carries which provision, what the bylaws should contain, and what to keep out of them. It then turns to committees and indemnification, the filing rules, what follows a breach, how requirements vary by state, and the mistakes that stall a Form 1023. It is written for counsel doing the drafting, most often at law firms handling formation work.

[cta-1]

Key takeaways

• The 501(c)(3) bylaws requirements that bind a nonprofit come from the nonprofit corporation statute of its state of incorporation. Federal tax law imposes no bylaws-language requirement on most organizations.
• The exempt-purpose and dissolution provisions are organizing-document requirements. Putting them in the bylaws of a corporation that has articles does not satisfy the organizational test, and that misplacement is a common reason an otherwise complete Form 1023 stalls.
• A conflict of interest policy is not required for exemption. The IRS encourages one, publishes a sample and asks about it on Form 990, which makes it a strong practice rather than a bylaws requirement.
• A nonprofit does not have to have bylaws to satisfy the IRS, but an applicant filing Form 1023 has to upload the bylaws it has adopted.

Does the IRS require bylaws for a 501(c)(3)?

The IRS does not require a 501(c)(3) organization to have bylaws, but it does require a Form 1023 applicant to submit the bylaws it has already adopted. Those are two different questions.

Adoption is a state law question

The IRS guidance on exempt organization bylaws is unambiguous on the federal position: “Federal tax law does not require specific language in the bylaws of most organizations. State law may require nonprofit corporations to have bylaws, however.” Whether a given organization must adopt bylaws at all is therefore answered by its state of incorporation, not by the Internal Revenue Code.

Submission is a federal requirement

The Instructions for Form 1023 are equally direct: “You must upload a copy of your organizing document and any amendments to it along with a copy of your bylaws, if adopted. The other listed documents are not required.” The same instructions list “Bylaws or other rules of operation and amendments (if adopted)” among the required uploads.

What the two rules mean together

Read together, the rule is narrow, because submission attaches only once bylaws exist:

• An organization that has adopted bylaws and leaves them out of the application has filed an incomplete Form 1023.
• An organization that has adopted none has nothing to upload, and a corporation in that position has usually missed a state requirement rather than found a shortcut.

The streamlined Form 1023-EZ accepts no attachments, so the question does not arise on that form.

The difference between 501(c)(3) bylaws and articles of incorporation

The difference between 501(c)(3) bylaws and articles of incorporation is which document the state and the IRS each look to: the articles create the corporation and carry the provisions the IRS organizational test requires, while the bylaws govern how the corporation operates and are not filed with the state. The 501(c)(3) articles of incorporation requirements carry the provisions federal tax law requires inside a state-filed document, and the bylaws carry the governance rules state law leaves to the drafter.

What the organizational test requires, and the cost of getting it wrong

The provisions in question are specific and short, and there are only two of them, which is part of why a drafter can carry them in the wrong document for years without noticing. The IRS sets both out in its guidance on the organizational test under section 501(c)(3): “the organizing documents must limit the organization’s purposes to exempt purposes,” and an organization’s assets “must be permanently dedicated to an exempt purpose,” with the organizing documents containing a provision for their distribution for an exempt purpose on dissolution.

Publication 557 closes the question for a corporation that has articles. It states that the requirement that purposes and powers be limited by the articles of organization “isn’t satisfied if the limit is contained only in the bylaws or other rules or regulations,” and that bylaws alone are not organizing documents. A corporation whose purpose limitation appears in its bylaws and nowhere else has not met the test, however carefully the bylaws are drafted.

The unincorporated association exception

The exception is the unincorporated association, which has no articles. For it, the Form 1023 instructions provide that bylaws may be considered an organizing document only if they include the required elements, and Publication 557 describes the same condition as being properly structured, with a name, a purpose, signatures and intent to form an organization. Where the bylaws are the organizing document, they must carry the purpose and dissolution provisions.

Which document carries which provision

What 501(c)(3) bylaws need to include

What 501(c)(3) bylaws need to include is set by the state nonprofit corporation statute plus the provisions common practice has settled on, not by a federal checklist. Every item below is a decision the drafter is making rather than a clause being copied.

• Board of directors: the number of directors or a range, how they are elected, length of term, any renewal limit, how vacancies are filled, and how a director is removed.
• Officers and duties: which offices exist, what each one may sign and authorize, how officers are appointed and removed, and whether one person may hold two offices.
• Meetings: frequency, who may call a special meeting, notice period and method, quorum, and the vote required for ordinary business.
• Remote participation: whether directors may attend by telephone or video, addressed explicitly, since a statute that permits it often does so only where the bylaws do not prohibit it.
• Membership: whether the corporation has voting members at all, and if it does, their classes, admission, voting rights and removal.
• Committees: which committees exist or may be created, which may exercise board authority, which may only advise, and who appoints them.
• Indemnification: the scope of indemnification for directors and officers, whether defense costs are advanced, and the conditions on which an advance is repaid.
• Amendment procedure: who may amend the bylaws and by what vote. This provision governs every later correction to the document.
• Fiscal year: the accounting period the organization will use, which has to match what it enters on its exemption application.
• Records: which records the corporation keeps and who may inspect them, which the statute often addresses and the bylaws can tighten.

Two items that do not belong in the bylaws

Two items that commonly appear on lists like this do not belong on it. The exempt-purpose and dissolution clauses are articles provisions, and the IRS illustrates the point in its sample organizing documents for a public charity. A conflict of interest policy is a separate board-adopted policy.

Sample 501c3 bylaws template: the nine-article outline

A sample 501c3 bylaws template usually runs to nine articles, and the sample outline below is the order most nonprofit corporations follow. No federal template exists, so any sample is a starting structure rather than approved language. Treat any such template as a drafting outline rather than a form to adopt, because each article carries at least one decision that depends on the state of incorporation.

• Article I: Name and offices. Legal name, principal office, registered office.
• Article II: Purposes. A statement of purposes, cross-referring to the articles rather than restating the operative limitation.
• Article III: Board of directors. Number, qualifications, election, terms, removal, vacancies, powers.
• Article IV: Officers. Positions, appointment, duties, terms, removal.
• Article V: Membership. Classes and voting rights, or an express statement that the corporation has no members.
• Article VI: Meetings. Regular and special meetings, notice, quorum, voting, remote participation, action without a meeting.
• Article VII: Committees. Standing and ad hoc committees, which may exercise board authority, appointment and composition.
• Article VIII: Indemnification. Scope, advancement of expenses, insurance.
• Article IX: Financial administration and amendments. Fiscal year, financial reporting and records, and the amendment procedure.

Dissolution is often drafted as a tenth article. For a corporation with articles of incorporation it belongs in the articles instead, which is why the outline above stops at nine.

What should not be included in nonprofit bylaws

What should not be included in nonprofit bylaws is anything that will need to change faster than the bylaws can be amended. Bylaws typically require notice and a supermajority to amend, so every operational detail written into them converts a routine management decision into a formal governance action. The quick test is whether the board would be comfortable needing an amendment to change the item.

On that test, the following belong in board-adopted policies:

• Staff job descriptions, reporting lines and compensation figures.
• Program rules, eligibility criteria and service delivery procedures.
• Dollar thresholds for signing authority, check signing and purchasing, which move with the budget.
• Named individuals in any role, as distinct from the office itself.
• The mechanics of conflict disclosure, recusal and annual certification.
• Gift acceptance criteria and investment or reserve policies, which the board revises as the asset base changes.
• Document retention and destruction schedules, which track regulatory guidance rather than governance.
• Committee charters and their membership lists, as distinct from the bylaws authority to create a committee at all.

Where the conflict of interest policy belongs

The conflict of interest policy is the clearest case, and the IRS treats it as exactly that. The Form 1023 instructions state that adoption of a conflict of interest policy is not required to obtain tax-exempt status, and the sample policy the IRS offers appears as an appendix to those instructions rather than as bylaws language. The bylaws can require that the board maintain a policy. The policy itself, with its disclosure forms and review cadence, sits outside them.

Committees and indemnification in nonprofit bylaws

Committees and indemnification are two of the articles a generic template most often thins out, and prospective directors ask about the second. Both are governed by the state nonprofit corporation statute, and both carry a constraint a generic template will not reflect.

Committees that may act for the board

The distinction that matters is between a committee that may exercise the authority of the board and a committee that may only advise it. Michigan is representative of how state statutes draw this line on composition: under MCL 450.2527, an executive committee must consist of one or more directors. That composition rule is what makes the finance-committee example below a real trap rather than a theoretical one: a committee that looks properly constituted on an org chart can still fail the statute if a non-director sits on it, and the board rarely discovers the defect until a transaction the committee approved is challenged.

Actions a committee cannot take

The same Michigan statute, separately, reserves certain actions to the full board regardless of what the bylaws say, under MCL 450.2528: a committee has no power to amend the bylaws, fill a board vacancy, amend the articles, or approve a merger, dissolution or sale of substantially all assets. Statutes in other states commonly draw the same line, with the specific reserved list varying by jurisdiction.

A drafter who creates a finance committee with authority to approve expenditures, then staffs it with two directors and a volunteer treasurer who is not on the board, has created a committee whose decisions may be challenged. In practice:

• Name in the bylaws the committees that may act for the board, rather than granting authority generally.
• Restrict the composition of those committees to directors in the bylaws themselves, so the constraint survives a later appointment.
• Create everything else as an advisory committee the board may appoint and staff freely.

Indemnification and advancement of defense costs

The operative question is not whether the organization will indemnify, since almost every set of bylaws says it will, but whether it will advance defense costs before the matter resolves. That is what a prospective director is weighing, and a provision that promises indemnification only after a successful outcome leaves the director funding a defense personally in the meantime. The drafting response:

• Permit advancement of defense costs against an undertaking to repay them if the director is ultimately found not to be entitled to indemnification.
• Keep the scope inside the limits the state statute sets, since a provision broader than the statute permits may be unenforceable to that extent.
• Confirm whether the organization carries directors and officers insurance, because the indemnification article and the policy need to describe the same coverage.

[cta-2]

Do nonprofit bylaws need to be signed, filed or made public?

Nonprofit bylaws do not need to be signed and are not filed with the state or the IRS as a registration, though a Form 1023 applicant uploads them and a filer of Form 990 has to describe how it makes its governing documents available.

Signature

The Form 1023 instructions put the signature question plainly: the bylaws need not be signed if they are submitted as an attachment, and Publication 557 adds that they need a signature only where they are the organizing document. Many boards sign or certify them anyway as a matter of record, which is sound practice rather than a requirement.

Filing and public availability

Filing runs on separate tracks, and they are easy to run together:

• The IRS exemption application: bylaws are uploaded with Form 1023 if adopted. They are evidence of governance, not a registration.
• The state: bylaws are generally not filed with the Secretary of State. The articles of incorporation are the filed document, and a state charities bureau may ask to see the bylaws on registration or examination.
• Public availability: Form 990 asks how the organization makes its application, its returns and its governing documents available to the public.

On the third track the IRS is specific about where the question sits. Its governance guidance for 501(c)(3) organizations notes that Form 990 Part VI Section C Lines 18 and 19 ask how the organization makes its Form 1023, Form 990 and governing documents available. The consequence for a drafter is that the bylaws should be kept where the board can produce them, with the adoption date and every amendment recorded.

What happens when a 501(c)(3) does not follow its bylaws

What happens when a 501(c)(3) does not follow its bylaws is, in the first instance, a state corporate law problem rather than a federal tax one: the action taken without authority may be void or voidable, and the exposure runs to the directors who took it. Such a breach does not, for that reason alone, cost the organization its exempt status, and loss of exemption is not the ordinary consequence of a procedural lapse.

Who can act on a breach

• The board: it can ratify a defective action at a properly noticed meeting, and in most cases does.
• Voting members: where the corporation has them, they may have standing under the statute or the bylaws.
• The state attorney general: the office generally has supervisory authority over charitable organizations, which gives it the broadest standing, though its interest typically runs to asset diversion rather than a missed notice period.

What the remedy usually is

Ratification at a properly noticed meeting resolves most procedural defects. Where a transaction has already closed, the question becomes whether a third party can rely on the apparent authority of an officer, which the bylaws themselves often address; a transaction a director or officer lacked authority to approve is void or voidable rather than automatically binding.

When a federal tax consequence attaches

Federal tax exposure arises from the substance of what happened, not from the procedural breach as such. The IRS prohibits any part of a 501(c)(3) organization’s net earnings from inuring to the benefit of a private shareholder or individual, and that prohibition applies regardless of what the bylaws say about board authority. A transaction between the organization and an insider that confers an excess benefit on the insider is separately sanctionable under the excess benefit transaction rules, independent of whether the bylaws were followed. Revocation of exemption is reserved for sustained operation outside exempt purposes, not an isolated procedural lapse.

For a drafter, the lesson runs backward into the document. Most bylaws breaches are not misconduct, they are provisions the board could not realistically comply with: a quorum it cannot reach, a notice period shorter than the board can manage, or an amendment threshold no board will assemble.

How nonprofit bylaws requirements vary by state

Nonprofit bylaws requirements by state vary on a short list of dimensions, and each one has to be checked against the statute of the state of incorporation before the bylaws fix a number.

The adoption requirement

Michigan is a representative example. Under section 231 of the Michigan Nonprofit Corporation Act, the initial bylaws “shall be adopted by its incorporators, its shareholders, its members, or its board,” while the content provision is permissive, allowing the bylaws to contain “any provision for the regulation and management of the affairs of the corporation not inconsistent with law or the articles of incorporation.” That pairing, a mandatory adoption and an open content, is the shape most state statutes take.

Statutory defaults such as quorum

The second dimension is the set of defaults that apply when the bylaws say nothing, and quorum is the one that catches drafters out. The same act provides in section 523 that “a majority of the members of a board who are then in office ... constitutes a quorum for the transaction of business, unless the articles of incorporation or bylaws ... provide for a larger or smaller number.” A statute written that way means the bylaws are not supplying a missing rule, they are overriding one that already exists, so a drafter changing it should know what the default was.

Director minimums

The floor on board size is set by the state, not by the IRS, which sets none, and it is the reason a template board of one or two directors fails on formation in some states and not others. The number of directors and any range in the bylaws is checked against the statute of the state of incorporation before the document is signed.

Whether the bylaws must address membership

Several states require a nonprofit corporation to state whether it has voting members, which makes an express statement that the corporation has no members the safer default everywhere, including in states with no such requirement.

Who may amend the bylaws

Some statutes allocate the amendment power between the board and the members unless the articles reserve it, and the local convention on amendment thresholds varies by state as much as the statute does.

The method for checking a state

The sequence is the same in every jurisdiction:

• Identify the state of incorporation, which is not always the state the organization operates in.
• Read that state’s nonprofit corporation act for the mandatory items and for the defaults that apply where the bylaws are silent.
• Fill in the outline only then, so that each number in the document is a choice made against a known default.

For a corporation formed under the Michigan nonprofit bylaws rules that means reading sections 231 and 523 together, and the equivalent pair exists in most states.

Common mistakes in drafting 501(c)(3) bylaws

The most common mistakes in nonprofit bylaws are not omissions a checklist would catch, they are provisions that are present, correctly placed and unworkable in practice. Each of these five mistakes has a specific failure point and a specific fix a drafter can apply at the outline stage.

• The dissolution clause written into the bylaws and nowhere else: Publication 557 is explicit that the purpose limitation is not satisfied if it appears only in the bylaws, and the same logic applies to the dedication of assets. Put both provisions in the articles and let the bylaws stay silent on them.
• A fiscal year that does not match the application: the Form 1023 instructions carry an explicit tax tip: “Check your bylaws or other rules of operation for consistency with the tax year (annual accounting period) you enter here.” A mismatch is a correspondence item on an otherwise clean application.
• Quorum set as a majority of a fixed board size: a nine-director board with quorum at five cannot meet once two seats are vacant. Setting quorum as a majority of directors then in office, which is how many statutes phrase the default, keeps the board functional through turnover.
• An amendment threshold set at unanimity: unanimity is occasionally deliberate, usually inherited from a template, and it makes every later correction impossible once a single director is unreachable. A supermajority of directors in office does the intended work.
• Silence on whether the organization has voting members: silence is read against the drafter, and in states that require the bylaws to address it, it is a defect. One sentence resolves it either way.

When to review the bylaws

Bylaws also benefit from a scheduled review rather than an amendment driven by a crisis. A review every two or three years, and whenever the board’s size, officer structure or membership changes, keeps the document usable. Material changes are reported to the IRS on the annual return: the governance guidance notes that Form 990 Part VI Section A Line 4 requires organizations to report significant changes to their organizational documents since the prior Form 990 was filed, described on Schedule O.

Using an AI tool to draft 501c3 bylaws

An AI tool to draft 501c3 bylaws is useful on the checklist layer of the work, which is where the mistakes above actually live. Spellbook is an AI platform for commercial legal work that runs natively inside Microsoft Word, so the review happens in the document the bylaws are already being drafted in rather than in a separate application. Three capabilities carry most of the weight on formation work:

• The Draft feature generates and completes provisions from the surrounding document and from the firm’s own precedent, for the lawyer to review and adapt to the state of incorporation, which matters for the articles a template usually thins out, such as committees and indemnification.
• The Review feature reads a draft and surfaces missing or inconsistent provisions: a quorum stated two different ways in two articles, an officer given authority the board never delegated, a fiscal year that contradicts the application.
• Playbooks hold the firm’s own drafting standards, so the same positions apply across every nonprofit client rather than depending on which associate opened the file.

Firms doing formation work at volume generally pair this with their wider use of AI for legal drafting across the practice.

What the software does not do

Two limits of using an AI tool to draft 501c3 bylaws are worth naming. Spellbook is a commercial contract specialist. The benchmark data behind the platform covers negotiated commercial terms rather than nonprofit governance documents, so a bylaws draft is not being compared against a market standard. Nothing in the tooling resolves a state law question either: whether a three-director floor applies, or whether the bylaws must state membership status, is research the lawyer does. The software can store earlier versions of the bylaws and show what changed between board approvals, which is useful at amendment time. The lawyer still decides what the organization’s governance should be.

See how the Draft feature works in Word.

[cta-3]

Frequently asked questions

Who creates the bylaws for a 501(c)(3)?

The bylaws for a 501(c)(3) nonprofit are adopted by the incorporators or the initial board of directors during formation, and in most states the statute names who holds that power. The drafting is usually done by counsel, and the board adopts the document by resolution at its organizational meeting.

Can a nonprofit operate without bylaws?

A nonprofit corporation generally cannot operate properly without bylaws, because most state statutes require their adoption and the statute’s default rules are an incomplete substitute for a governance document. An unincorporated association has more latitude, though if it applies for exemption its bylaws are likely to be its organizing document.