PREVIEW · EXAMPLE DATA ONLY — no real member names, giving, or private church records
Unitarian Universalist Church of Catawba Valley · Hickory, NC · Board preview for Carl Beardsworth
What this hub is for.
A single place for board, staff, and lay leaders as UUCCV grows out of family-size patterns
(everybody knows everybody; authority around a few anchoring figures; pastor as chaplain)
toward program-size patterns (quality programs as entry points; staff + lay leadership circle;
board governs, teams do ministry; shared pastoral care).
Size theory (Rothauge / Mann, used by UUA):
Family 0–50 · Pastoral 50–150 · Program 150–350 · Corporate 350+.
Moving family → program usually means crossing the pastoral plateau first.
The hard work is not just more people — it is letting go of old decision habits and taking on
written roles, teams with charters, and systems (calendar, pledging, newcomer follow-up)
that do not depend on one person’s memory.
🌱 Transition progress Example data
Markers drawn from Alice Mann’s pastoral→program work and UUA size-transition guidance. Score is illustrative.
Overall readiness
Estimated stageLate family / early pastoral
Program markers in place4 of 10
Next focusTeam charters + newcomer pathway
View learning-team notes
System Change Index (later)
Family → Program markers
Named ministry teams — Worship, RE, Hospitality exist (still informal)
Board shifts to governance — still handles day-to-day ops
Pastor equips leaders — still carries most pastoral care personally
Written team charters — not yet
Newcomer pathway — hospitality strong; follow-up inconsistent
Shared calendar — started in Breeze
Caring / pastoral care team — not yet shared
Staff beyond minister — part-time admin / RE under discussion
Pledge & giving tracked — Breeze in use
Policies library — bylaws only; safe-congregation draft pending
📋 Board dashboard Example data
At program size, the board sets ends, guards resources, and stops running every ministry. This panel models that shift.
FY goals In progress
- ✓
Adopt size-transition learning plan
- ~
Clarify board vs. ministry-team roles
Approve RE staffing recommendation
Complete safe-congregation policy
- ✓
Keep average attendance tracking monthly
Decisions log
Oct 12Form size-transition learning team
Sep 28Approve Breeze as CMS of record
Sep 14Set FY pledge drive window (example)
Aug 31Authorize QuickBooks Online for books
Add decision
Action items 5 open
Board chair — draft ends statements for Nov meeting
Treasurer — map restricted funds to QBO classes
Membership — write 4-step newcomer follow-up
- ~
Minister — propose caring-team pilot
Secretary — collect team charters by Dec 1
🤝 Ministry teams & committees Example data
Program churches thrive on quality programs led by equipped lay + staff leaders — not by the board doing everything.
Worship Arts Active
LeaderA. Rivera (example)
Meets2nd Thu · 7pm
CharterDraft
Plans Sunday worship with minister; recruits readers, musicians, tech.
Religious Education Active
LeaderJ. Okonkwo (example)
MeetsMonthly · Sun after service
CharterNeeds update
Children & youth programs; teacher roster; curriculum choices.
Hospitality & Welcome Active
LeaderS. Nguyen (example)
MeetsAs needed
CharterDone
Greeters, coffee hour, visitor cards → Membership pathway.
Social Justice Forming
LeaderOpen
MeetsTBD
CharterNot started
Local partnerships; advocacy aligned with UU principles.
Finance Committee Active
LeaderTreasurer + 2
MeetsMonthly before board
CharterDone
Budget, pledges, restricted funds; QBO ↔ Breeze reconciliation.
Caring Team Needed
LeaderNot yet
Meets—
CharterKey gap
Shared pastoral care is a program-size hallmark. Pilot proposed.
🙋 Volunteers — recruiting & scheduling Example data
Family churches ask whoever is standing nearby. Program churches publish roles, rotate fairly, and invite gifts.
Open roles this month
| Role | Date | Status |
| Greeter | Nov 2 | Open |
| Coffee host | Nov 2 | Filled |
| RE assistant | Nov 9 | Open |
| Tech / AV | Nov 9 | Needs backup |
| Reader | Nov 16 | Open |
Post signup (later → Breeze)
Recruiting notes
- ✓
Gift survey drafted for new members (example)
Time-and-talent fair planned for January
- ~
3 people expressed interest in Caring Team
Youth volunteer pathway with RE
Connects later
Breeze scheduling / tags can drive reminders and role history once an API key is connected.
🛤️ Newcomer & membership pathway Example data
Program churches cannot rely on “someone will notice.” A clear visitor → friend → member → leader path keeps growth healthy.
1Visitor
welcome + card
2Follow-up
within 48 hrs
3Orientation
/ Path to Membership
4Member
signing + photo
5Leader
team invite
This month’s funnel
First-time visitors7 (example)
Follow-ups completed4 of 7
In Path to Membership3
New members (YTD)5
Invited into a team2
Follow-up checklist
- ✓
Welcome email / text within 48 hours
- ✓
Personal note from Hospitality
Invite to coffee with minister or member
Offer Path to Membership date
After joining: gift conversation + team match
Example newcomers (fictional)
Jordan P.Visitor · week 1
Sam & Riley L.Path class · Oct
Morgan C.Member · needs team invite
Names are placeholders. Live data would come from Breeze people records.
💰 Finance Example data
Board needs a clear picture without living in the spreadsheet. Restricted funds and pledge tracking matter more as the church grows.
QuickBooks vs budget Connects later
FY income (YTD)$84,200 / $120,000
FY expense (YTD)$79,450 / $118,000
Net (YTD)+$4,750
Reserve target3 months ops (example)
Income progress toward annual budget (example).
QuickBooks Online — connect later for live P&L, classes (funds), and board packet export.
Restricted funds
Building / capital$12,400
RE scholarship$1,850
Music / arts$920
Minister’s discretionary$640
Share the Plate (pass-through)$310
Map each fund to a QBO class / account before go-live.
Pledge & giving ↔ Breeze Connects later
Pledged (FY)$96,000 (example)
Received to date$71,200
% of pledge in74%
Last Breeze → QBO reconcileNot connected
Breeze API key — connect later to pull giving, people, and events; reconcile deposits against QuickBooks; flag mismatches for the treasurer.
👥 Staff & roles Example data
In family size the minister is chaplain. Toward program size the minister recruits, equips, and inspires a leadership circle — often with part-time staff.
Settled / called minister
Focus nowWorship + pastoral care
Growing intoEquip leaders · vision
FTEExample: ¾–full
Religious educator
StatusUnder discussion
ProposedPart-time
ReportsMinister / board ends
Admin / office
StatusVolunteer + hours
NeedsBulletin, Breeze, calendar
LaterPaid part-time
Music / worship support
StatusStipend / volunteer mix
TeamWorship Arts
GapBackup pianist (example)
📣 Communications & calendar Example data
At program size, calendaring and communicating leave the board and become coordinated church-wide work.
Upcoming (example)
Sun Nov 2Worship · Coffee hour · RE
Tue Nov 4Board packet due
Thu Nov 6Worship Arts meeting
Sun Nov 9Path to Membership class
Sat Nov 15Justice work day (example)
Sun Nov 16Board meeting after service
Connects later
Live calendar from Breeze Events (or Google Calendar) once connected.
Channels
Weekly e-newsEditor: Admin (example)
Sunday announcementsWorship lead
Website / socialNeeds owner
Emergency treeDraft with Caring Team
- ✓
One church calendar of record
Comms style guide (tone, logos, UU principles)
Photo & privacy consent on file
📁 Policies & documents Example data
Program-size life needs written agreements so newcomers and leaders are not guessing the culture.
Safety & care
- ~
Safe congregation / RE screening
Building use & keys
Disruptive behavior policy
Pastoral care confidentiality guide
Finance & ops
- ✓
Fiscal year budget
- ~
Restricted fund definitions
Expense / reimbursement policy
Document retention schedule
What’s real vs later.
Everything on this page is labeled example data for board conversation.
To make it a living hub: (1) Breeze API key for people, giving, events, and volunteer tags;
(2) QuickBooks Online connection for P&L, classes, and bank reconcile;
(3) real board goals, team leaders, and policy files;
(4) optional Google Calendar / email for reminders.
No secrets or member data are stored in this preview.