---
schema_version: "1.0.0"
id: "ddf-church-blueprint:en:chapter-32"
work_id: "urn:systemstheology:book:ddf-church-blueprint:chapter:chapter-32"
book_id: "ddf-church-blueprint"
chapter_id: "30-what-meetings-are-for"
chapter_slug: "chapter-32"
title: "30. What Meetings Are For"
book_title: "DDF Church Blueprint"
language: "en"
source_language: "en"
translation_status: "source"
authors: ["Systems Theology"]
editorial_owner: "Systems Theology"
editors: []
review_status: "not_specified"
reviewers: []
content_version: "content-ec60c0b84de6"
content_hash_sha256: "ec60c0b84de629d630a948c6a9c485a3d062e1122c507b45fc1738160cf0c264"
published_at: "2026-07-15T21:14:45.000Z"
modified_at: "2026-07-15T23:50:19.254Z"
canonical_url: "https://systemstheology.com/library/ddf-church-blueprint/chapter-32/"
markdown_url: "https://systemstheology.com/research/books/ddf-church-blueprint/en/chapter-32.md"
license: "All rights reserved; research use subject to the Use Policy"
license_url: "https://systemstheology.com/use-policy/"
correction_url: "https://systemstheology.com/library/ddf-church-blueprint/chapter-32/#chapter-comments"
---

# 30. What Meetings Are For

<a id="30-what-meetings-are-for"></a>

Meetings do not become faithful because they open with prayer. Prayer places the room before God; the room must still define claims, hear relevant people, manage power, decide clearly, and finish the work.

<a id="four-meeting-types"></a>

## Four Meeting Types

Mark which kind of work the room is doing:

- Worship and discernment: Scripture, prayer, confession, listening, and theological judgment.
- Decision: a defined question, authority, evidence, options, conflicts, burden, decision, and record.
- Coordination: owners report, dependencies are resolved, and next actions are assigned.
- Care or case review: protected information, bounded roles, supervision, safety, and next care action.

A governing meeting can include all four, but the agenda should mark the transition. A prayerful reflection should not silently become a decision that bypasses notice or authority. A care detail should not enter ordinary minutes.

<a id="an-agenda-that-ends-in-decisions"></a>

## An Agenda That Ends in Decisions

Send enough information in advance. Name the decision owner, decision maker, deadline, recommendation, alternatives, source and claim types, affected people, cost, risk, conflicts, and revision trigger. At the meeting, begin by asking whether anyone has a conflict or material missing information.

Before closing, state the decision in one sentence. Name the owner, due date, communication, record, and review. If no decision was made, say whether the matter is waiting, delegated, rejected, or removed. "We had a good conversation" is not an operating state.

<a id="records-have-different-purposes"></a>

## Records Have Different Purposes

Classify records rather than placing everything in one drive:

- governing and legal records;
- doctrine, teaching, liturgy, and sacramental registers;
- finance, donor, payroll, contract, and asset records;
- membership and ordinary contact records;
- pastoral-care records;
- child, safeguarding, complaint, discipline, and allegation records;
- personnel and volunteer records;
- communications, media, consent, and data-system records.

For each class, state owner, location, access, retention, destruction, backup, legal hold, correction, transfer, and breach path. "Forever" and "until we run out of storage" are not retention rules. Some ecclesial records may be permanent; some pastoral detail should not be.

<a id="write-down-what-was-promised"></a>

## Write Down What Was Promised

Track material promises made to members, donors, staff, survivors, neighbors, landlords, partners, and public authorities. Record the exact promise, owner, date, evidence of completion, and communication. Institutions often fail not because no plan existed but because pain moved out of the room and the promise lost an owner.

Review overdue promises without reputation management. If the church cannot keep one, tell affected people before they discover the failure.

Before you move on. Meeting charters, decision-agenda and minutes templates, records classification and retention schedule, action log, and promise register.