Frameworks, templates & guides
The Temple's shared library of frameworks, templates, and safe-use guidance for AI in sacred community operations.
Framework
SACRED+R Prompt Card
The seven-part framework for building safer, clearer, more useful prompts for Temple work.
- S — Sacred Purpose: What purpose does this serve?
- A — Audience: Who is this for?
- C — Context: What is happening?
- R — Reform / Temple Voice: What tone should it use?
- E — Evidence: What approved source material?
- D — Data Discipline: What must not be included?
- +R — Review Responsibility: Who must review before use?
Governance
Green / Yellow / Red AI Use Guide
The Temple's traffic-light guide for what AI can support, what needs close review, and what is restricted.
- Green — Routine, low-sensitive drafting or organization. Normal human review.
- Yellow — Member-facing, donor-facing, family/youth, financial, reputational, or lifecycle-adjacent. Close review required.
- Red — Clergy care, sensitive member support, HR/legal, crisis statements, unredacted member/donor/youth data, unreviewed liturgy, eulogies, or clergy voice used as-is. Avoid or require explicit leadership/clergy approval.
Human Review Checklist
The public, sensitive, financial, reputational, lifecycle, and clergy-care checkpoints every draft needs before use.
Communications
Temple Voice Checklist
Warm, clear, inclusive, Reform Jewish, community-centered — a quick check before any draft goes out.
Sacred Use
Temple AI Covenant
AI may draft. Humans discern. Our shared covenant for AI use in sacred community.
- Kavod / Dignity: protect the dignity of members, families, staff, students, donors, guests, and volunteers.
- Emet / Accuracy: verify facts, dates, names, links, sources, and claims.
- Sod / Confidentiality: protect sensitive member, donor, youth, family, clergy-care, lifecycle, HR, legal, financial, and internal information.
- Chochmah / Wisdom: use AI as a tool, not an authority.
- Kehillah / Community: AI should help Temple staff serve people better, not make communication colder.
- Human Review: public, sensitive, financial, reputational, lifecycle, clergy-care, or spiritual-support content requires human review.
- Clergy Discernment: AI does not replace rabbinic, cantorial, clergy, or human judgment.
Sacred Use, Torah & Teaching Guidance
What AI can support in Torah, sermons, and teaching — and what remains for clergy authorship.
- Green — Brainstorm metaphors, organize notes, create discussion questions, summarize approved source text, draft educational handouts, create discussion guides for adult learning or Torah study.
- Yellow — Sermon research support, d'var Torah outline support, adult learning guide, holiday explanation, teaching support, lifecycle-adjacent educational material.
- Red — Unreviewed liturgy, clergy care responses, sensitive member support, eulogies, crisis prayers or crisis statements, clergy voice used as-is, spiritual-support language used directly without clergy authorship/review.
Collaboration
Teams Communication Covenant
A shared agreement on when to use chat, channels, email, meetings, files, and follow-up notes.
Templates
Meeting Recap Template
Decisions, open questions, action items, owners, deadlines, and items needing leadership review.
SOP Template
Purpose, owner, systems used, step-by-step, common mistakes, review cycle, escalation.
Event Launch Kit Template
Website blurb, confirmation, reminder, volunteer instructions, internal checklist, thank-you.
Board Summary Template
Themes, decisions, action items, open questions, risks, and items requiring executive session.
Workflows
ShulCloud-Adjacent Workflow Guide
How to use AI as workflow support around ShulCloud without altering or overriding the system of record.
Reference
Prompt Playbook PDF
The full Temple Emanuel prompt playbook, organized by role and workflow.
Current State vs Future State: Copilot Chat and Microsoft 365 Copilot
What we can do today with Copilot Chat, and what deeper Microsoft 365 Copilot will unlock later.
- Current State — Copilot Chat; manual use with Word, Excel, PowerPoint, Outlook, Teams; copy/paste workflows; file upload where allowed; prompting, drafting, summarizing, organizing.
- Future State — Deeper Microsoft 365 Copilot in-app capabilities; meeting intelligence; broader work-data grounding; advanced Teams, Outlook, SharePoint, Word, Excel, and PowerPoint integration; agent workflows.
- Note — Do not claim the organization has full Microsoft 365 Copilot capabilities unless leadership has enabled a Full Microsoft 365 Copilot License.
Assessment
Capstone Rubric
How Week 6 capstone workflows are reviewed — clarity, safety, reuse potential, and role fit.