Policy isn't paperwork
Governance documents are an operating system, not an archive
A word is dead
When it is said,
Some say.
I say it just
Begins to live
That day.
—Emily Dickinson (source)
Nonprofit governing boards have a legal responsibility to demonstrate care, loyalty, and obedience. All three require shared context, not just good intentions. And yet the policy documents intended to shape and support that context (bylaws, conflict of interest policies, whistleblower policies, committee charters, investment policies, and so on) are often densely written, poorly maintained, and referenced only in emergencies – crisis, dispute, audit, leadership transition, legal threat.
But what would it look like if these policies were present and alive throughout board discovery, discussion, and decision-making? How might they serve more as an operating environment and less like an in-case-of-emergency kit locked behind glass?
Such a living and dynamic practice requires policy documents that are easy to access, clearly written, annotated when necessary, responsibly updated with changes tracked, and rich with context. In short, not a scattered file system of PDFs and Word documents of questionable provenance, but a library developed and maintained for collective sense-making and as a source of truth.
That may sound like a tall order and a workload nightmare. But one field – software development – has spent decades working through this challenge. We might as well benefit from their hard work.
Consider the connections. Software development is not only about writing instructions for machines. It is also about helping groups of humans maintain shared information over time: what changed, who changed it, why it changed, what alternatives were considered, and which version currently governs.
Good practice in software development includes principles that could benefit nonprofit governance documents. Among them:
A single source of truth: No scattered copies. No questionable quasi-duplicates.
Clear, readable text: Plain text files in natural language for simplicity, cross-platform utility, and durability.
Trackable changes: Persistent evidence of what changed, who changed it, when, and ideally why.
Recorded decision rationale: Clear details about the issue, the options explored, the trade-offs and risks, and the justification for the option chosen.
A review-and-approval path: Coherent and consistent rules for who can suggest, review, and approve changes.
Nonprofit boards could adopt many of these goals without becoming software developers. But if a new system would help, software development already has mature tools and practices for this exact work.
This isn’t an obscure and abstract idea. Open-source foundations and civic organizations already maintain bylaws, governance policies, and chapter constitutions in public repositories, where changes can be tracked and compared over time. The Commonhaus Foundation and NumFOCUS, for example, both maintain governance documents through version-control systems, as do many software communities.
As an added bonus, clear, well-structured, and well-annotated governing documents can help make a nonprofit more transparent to the communities it serves. And as generative AI systems increasingly support decision-making in the nonprofit arts, these libraries can provide context and constraint. With a clear and current policy library, AI can help board members ask better questions against a reliable source, and remind them of compliance requirements.
Policy isn’t paperwork. It is one essential way a board captures and recalls what it has promised, what it has learned, what it may do, and what it must not do. Treated as a dormant archive, policy waits for trouble. Treated as an active and evolving operating environment, policy can help boards govern with more care, more loyalty, and more obedience to the purposes they are charged to serve.
From the ArtsManaged Field Guide
Function of the Week: Governance
Governance involves structuring, sustaining, and overseeing the organization's purposes, resources, and goals (often through boards or trustees).
Framework of the Week: Planning Organizing Leading Controlling (POLC)
Traditional management theory describes four core functions of management in any industry: planning, organizing, leading, and controlling.
Photo by Wesley Tingey on Unsplash