# Guide Structure

# Governance and Documentation Levels

# Overview of Governance and Documentation Levels

Our church operates with a multi-layered governance system that ensures clarity, accountability, and consistency in how our community is organized and managed. This system reflects the various levels of decision-making and responsibility within the church, providing a structured yet flexible framework for how we operate. Each layer plays a distinct role in guiding our actions and aligning them with our shared values and mission.

<table class="min-w-full" data-end="1635" data-start="152" id="bkmrk-layer-authority-doma" style="width: 100%; height: 262.766px;"><thead data-end="361" data-start="152"><tr data-end="361" data-start="152" style="height: 29.7969px;"><th data-end="181" data-start="152" style="width: 22.4526%; height: 29.7969px;">**Layer**</th><th data-end="226" data-start="181" style="width: 21.6035%; height: 29.7969px;">**Authority**</th><th data-end="303" data-start="226" style="width: 30.293%; height: 29.7969px;">**Domain**</th><th data-end="361" data-start="303" style="width: 25.532%; height: 29.7969px;">**Accountability**</th></tr></thead><tbody data-end="1635" data-start="571"><tr data-end="780" data-start="571" style="height: 46.5938px;"><td class="" data-end="599" data-start="571" style="width: 22.4526%; height: 46.5938px;">[**Bylaws**](https://211134-bookstack.peaknetworks.cloud/books/foothills-bylaws/page/bylaws-of-foothills-unitarian-church)</td><td class="" data-end="644" data-start="599" style="width: 21.6035%; height: 46.5938px;">Congregation vote</td><td class="min-w-[calc(var(--thread-content-max-width)/3)]" data-end="721" data-start="644" style="width: 30.293%; height: 46.5938px;">Foundational governance structure and core principles</td><td class="" data-end="780" data-start="721" style="width: 25.532%; height: 46.5938px;">Entire congregation</td></tr><tr data-end="989" data-start="781" style="height: 46.5938px;"><td class="" data-end="809" data-start="781" style="width: 22.4526%; height: 46.5938px;">**Policy**</td><td class="" data-end="854" data-start="809" style="width: 21.6035%; height: 46.5938px;">Board of Trustees</td><td class="min-w-[calc(var(--thread-content-max-width)/3)]" data-end="931" data-start="854" style="width: 30.293%; height: 46.5938px;">Mission, vision, executive boundaries, board process</td><td class="" data-end="989" data-start="931" style="width: 25.532%; height: 46.5938px;">Board to the congregation, Board to the bylaws.</td></tr><tr data-end="1202" data-start="990" style="height: 46.5938px;"><td class="" data-end="1020" data-start="990" style="width: 22.4526%; height: 46.5938px;">**Organizational Guidance**</td><td class="" data-end="1066" data-start="1020" style="width: 21.6035%; height: 46.5938px;">Executive-Team or designated staff lead</td><td class="min-w-[calc(var(--thread-content-max-width)/3)]" data-end="1143" data-start="1066" style="width: 30.293%; height: 46.5938px;">Ministry-wide strategic interpretations of policy</td><td class="" data-end="1202" data-start="1143" style="width: 25.532%; height: 46.5938px;">Executive-Team to the Board</td></tr><tr data-end="1426" data-start="1203" style="height: 46.5938px;"><td class="" data-end="1246" data-start="1203" style="width: 22.4526%; height: 46.5938px;">**Standard Operating Procedures (SOPs)**</td><td class="" data-end="1291" data-start="1246" style="width: 21.6035%; height: 46.5938px;">Staff or designated teams</td><td class="min-w-[calc(var(--thread-content-max-width)/3)]" data-end="1368" data-start="1291" style="width: 30.293%; height: 46.5938px;">Day-to-day operational consistency and implementation</td><td class="" data-end="1426" data-start="1368" style="width: 25.532%; height: 46.5938px;">Staff to Executive-Team</td></tr><tr data-end="1635" data-start="1427" style="height: 46.5938px;"><td class="" data-end="1455" data-start="1427" style="width: 22.4526%; height: 46.5938px;">**How To**</td><td class="" data-end="1500" data-start="1455" style="width: 21.6035%; height: 46.5938px;">Staff or designated teams</td><td class="min-w-[calc(var(--thread-content-max-width)/3)]" data-end="1577" data-start="1500" style="width: 30.293%; height: 46.5938px;">Practical, congregant-facing instructions for specific tasks</td><td class="min-w-[calc(var(--thread-content-max-width)/3)]" data-end="1635" data-start="1577" style="width: 25.532%; height: 46.5938px;">Staff to congregants and ministries they support</td></tr></tbody></table>

---

### **Bylaws  


**Purpose:** The Bylaws are the foundational governing documents of our church. They establish the core principles and structures that define how our community is organized and how it operates.

**Authority:** The Bylaws are set and can only be amended by a vote of the entire congregation, ensuring that the most fundamental rules and principles are reflective of the collective will of the community.

---

### **Policy**

**Purpose:** Board policies define the **mission-driven boundaries and priorities** within which the church operates. Rooted in policy based governance as directed by Foothills bylaws, these policies guide both the **Ministry** and the **Board** by articulating:

- **Vision/Ends**: The outcomes the church exists to achieve—what difference we seek to make, for whom, and at what cost.
- **Executive Directions:** Requirements for the execution of ministry
- **Executive Limitations**: Boundaries around the methods and means that staff may not use in pursuit of those Ends.
- **Board Process**: How the Board governs itself to act with integrity, accountability, and vision.

These policies live in the **Board of Trustees Policy Book** and form the operational between the Board and the Executive-Team.

**Authority:** Policies are established by the Board of Trustees through a voting process, reflecting the board's role in providing strategic oversight and ensuring that the church operates in a manner consistent with its mission and values.

---

### **Organizational Guidance** 

**Authority:** Executive-Team , or designated staff lead

**Purpose**: Organizational Guidance provides ministry-wide frameworks that interpret and operationalize board-level policy. More flexible than policy and more strategic than procedures, these documents offer consistent direction for how staff and ministries live out policies across varied contexts.

They answer:

- *What does this policy mean in practice? Ie. How is the executive team interpreting the board policy?*
- *How do we stay aligned as we adapt and evolve?*

*[Template for Organizational Guidance](https://211134-bookstack.peaknetworks.cloud/books/guide-structure/page/organizational-guidance-template).*

<p class="callout info">**A Handbook** is a curated collection of Organizational Guidances focused on a specific area of church life or ministry. While each individual guidance document may stand on its own, grouping them into a handbook provides clarity, cohesion, and ease of reference for teams and ministries navigating complex or evolving domains.</p>

---

### **Standard Operating Procedures** 

**Purpose:** Procedures are practical, step-by-step instructions that help staff to enact the Organizational Guidance and daily operations. They are designed to ensure that specific tasks and processes are carried out effectively and consistently across the church.  
**Authority:** Developed and maintained by staff or designated teams.

---

### **How To**

**Purpose**: How To guides are practical, congregant-facing step-by-step instructions to enacting specific tasks and actions from the perspective of someone outside the system. These documents are written in an accessible manner for the audience that is expected to use them.  
**Authority**: Developed and maintained by staff or designated teams, these guides provide the necessary detail to support the procedures, ensuring that actions are completed in alignment with church policies and values.

<table border="1" id="bkmrk-shelves-books-descri" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 50.0596%;"></col><col style="width: 50.0596%;"></col></colgroup><thead><tr><td>**Shelves**

</td><td>**Books**

</td></tr></thead><tbody><tr><td>1\. Governance

</td><td>- Bylaws
- Board Policy
- Board Procedure 
    - Board Handbook
- Governance Archive

</td></tr><tr><td>2\. Organizational Guidance

</td><td>- Personnel / Employee
- Financial
- Membership
- Groups &amp; Teams
- Care &amp; Support
- Children and Youth
- Database and Records
- Building and
- Facilities
- Church Events
- Communication
- Legal

</td></tr><tr><td>3\. Standard Operating Procedures

</td><td>- Worship
- Rites of Passage
- Metrics
- Event Reservations and Promotion
- Caring
- Church Center
- Shared Ministry Covenanting

</td></tr><tr><td>4\. How To's

</td><td>- Using Foothills Technology

</td></tr><tr><td>Specific Use Case Shelves (Ie. Group Leaders)

</td><td>  
</td></tr></tbody></table>

# Documentation Templates

# Organizational Guidance Template

*A concise and clear title that stands alone and makes sense out of context.*

---

## 1. Purpose

**Why this guidance exists.**

State the spirit of the guidance — what it seeks to clarify, support, or achieve.  
Be values-forward. Highlight how it aligns with our mission, values, or policies.

---

## 2. Organizational Guidance

**The full content of the guidance.**

- Use clear, actionable language.
- If guidance involves steps or expectations, list them in bullet or numbered format.
- If external or internal documents are referenced, link them directly.
- If clarification or definitions are needed, include them in-line or link to a glossary.

---

## 3. Related Content

### Bylaws and Policies

*This guidance interprets or implements the following:*

- [Bylaw Article X - Membership Definition](#bkmrk-previous-version-%5Bda)
- [Board Policy - Safety and Inclusion](#bkmrk-previous-version-%5Bda)

### Organizational Guidances &amp; SOPs

*This guidance is related to or informs the following documents:*

- [Organizational Guidance - Behavior Covenants](#bkmrk-previous-version-%5Bda)
- [SOP - Incident Response Protocol](#bkmrk-previous-version-%5Bda)

<details id="bkmrk-previous-version-%5Bda"><summary>Previous Version \[Date\]</summary>

Content of Previous Version of Guidance

</details>