Lesson 5. Service Design, Archives, and Aftercare
Liturgy & the Original Talk
Canon anchors: Ch. XXIII; Ch. XXX The Laughter Archive; Year-One Gathering post-service records
Learning objectives
Build a complete service plan around one doctrinal theme.
Create accurate public archive metadata and private operational records.
Distinguish what belongs publicly on Iambe.org from confidential records.
Lesson text
A Gathering begins before the webinar opens. The leader chooses a doctrinal theme, prepares the talk, selects a Reading, creates discussion questions, plans the Offering, identifies technical roles, and considers accessibility. Afterward, the service continues as institutional memory.
The public archive should ordinarily record date, title, speaker, doctrine/theme, a concise summary, and links to any approved recording or transcript. It may include aggregate attendance. It should not automatically publish attendee names, pastoral disclosures, private chat logs, incident details, donor information, or internal financial records.
The private worship record should preserve actual attendance or attendance evidence where appropriate, leaders, service outline, unusual incidents, permissions, expenses, publication decisions, and any doctrinal correction. These records allow future leaders to know what actually occurred rather than reconstructing it years later.
Archive integrity matters. A canceled service should not be displayed as held. A planned attendance number should not become actual attendance. If a transcript is edited after delivery, the archive can say so. Religious history is strongest when the record resists embellishment.
Practice
Prepare one complete service packet: run-of-show, original talk outline or manuscript, reading, discussion prompts, jest prompt, Cup wording, Charge, public archive summary, and private post-service record form.
Reflection
Knowledge check
Name four items that should be prepared before a Gathering.
What is appropriate public archive metadata?
Why should attendee names not automatically be published?
How should a canceled service appear in the archive?