How do you write a board policy that people actually follow?

Somewhere in your board’s shared drive there is a policy that four people voted for, two people remember, and nobody has read since. It isn’t a bad policy. It’s a fine policy. It just doesn’t do anything.

Board policies rarely fail because they’re wrong. They fail because they’re unfindable, unreadable, and unowned. Fixing those three things is most of the work.

First: is this a policy, or just a decision?

Write a policy when a decision keeps re-arriving. If the board has now spent part of three meetings deciding whether to reimburse mileage, that’s a policy. Answer it once, in writing, and stop spending meeting time on it.

If the situation happened once and is unlikely to repeat — a specific building issue, a one-time grant, an unusual gift — that’s a decision. Make it, record it in the minutes, and move on. Boards that write a policy every time something surprising happens end up with a binder full of rules that describe a single Tuesday in 2019.

The test: will this question come back? If yes, write it down. If no, let the minutes carry the memory.

Bylaws are not policies

This distinction is worth getting exactly right, because boards blur it constantly and the consequences are real.

Bylaws are the organization’s structural rules — how many trustees, how they’re elected, term lengths, officer roles, quorum, notice requirements, how the bylaws themselves get amended. They interact with state nonprofit law, and they are deliberately hard to change: typically a supermajority, often notice at one meeting and a vote at the next. What your bylaws require and how they can be amended is set by your own document and your state’s law — read yours, and involve counsel for amendments.

Policies are board-adopted rules for how the organization operates within that structure. Reimbursement, gift acceptance, whistleblower protection, document retention, conflicts of interest, social media. They’re adopted by a simple motion at a regular meeting and revised the same way.

The practical consequence: put an operating rule in the bylaws and you’ve made it expensive to change, so boards quietly ignore it rather than amend it. Put a structural rule in a policy and you’ve made your governance foundation revisable by a Tuesday-night motion. When in doubt: structure goes in bylaws, operations go in policy.

What a policy people follow looks like

One page. If it’s longer, it’s a procedure manual, and procedure manuals belong to staff, not the board. The board sets the rule; staff writes the steps. A trustee should be able to read the whole thing at a stoplight.

Plain language. “Board members submit mileage within 60 days” beats “Reimbursement requests shall be submitted in a timely manner.” Shall and timely are where policies go to become unenforceable.

Who it binds. Trustees only? Trustees and staff? Volunteers? Committee members who aren’t on the board? Name them. A policy that doesn’t say who it applies to applies to whoever feels guilty.

Who enforces it. A named role — the treasurer, the board chair, the executive director. Not “the board.” A policy nobody owns is a suggestion with formatting.

What happens when it’s violated. Boards omit this because writing it feels unfriendly, and it’s the section that makes the rest credible. It needn’t be dramatic — “expenses submitted after 60 days are not reimbursed” is a complete consequence. Say what actually happens, so the enforcer isn’t improvising against a friend.

A review date, printed on the policy. “Adopted March 2026. Review by March 2029.” Now the policy has a lifespan and an appointment. Put those dates on your compliance calendar.

Pruning: a board with forty policies has zero policies

Policies accumulate. Nobody proposes deleting one, because deletion feels like saying the earlier board was wrong. So the binder grows, and past a certain size no trustee can hold its contents in mind — which means the board is now formally bound by rules it can’t recite.

Set a review cycle — every policy revisited every two or three years, a handful each year rather than all of them at once. At each review the question is simple: keep, revise, or retire? Retiring a policy is a normal, healthy motion, and it should feel that way. If a rule no longer reflects how the board operates, the choice is to fix the rule or fix the practice. Leaving the gap open is the only wrong answer.

The short list most volunteer boards genuinely need

Not forty. Something closer to this:

• Conflict of interest — with annual disclosure and a recusal procedure.
• Whistleblower — how concerns get raised and that raising them is protected.
• Document retention and destruction — what’s kept and for how long. Retention periods vary by record type and jurisdiction; get yours confirmed rather than copied.
• Gift acceptance — what the organization will and won’t take, so no one has to decide about the donated timeshare under pressure.
• Expense reimbursement — what’s reimbursable, by when, with what documentation.
• Executive compensation review — how the board sets and documents the executive’s pay.
• Financial controls — check signing thresholds, who can commit funds, who reconciles what.
• Board member expectations — attendance, giving, committee service, confidentiality.

That’s eight. Most boards need a couple more for their sector — schools, churches, and anything touching public funds carry additional obligations, and counsel can tell you which. Eight, kept current, beats thirty nobody’s opened.

The one-sentence version

A policy that people follow is one page, names who it binds and who enforces it, says what happens when it’s broken, carries its own review date, and exists because a question kept coming back.

Before your next policy goes to a vote, read it aloud to the board and ask one question: who does this bind, and who enforces it? If the room can’t answer in a sentence, the policy isn’t finished.