Elders and technology decisions
Bring tool choices into shared wisdom. Do not hide recurring fees in a communications budget line nobody watches.
Why do tool choices belong with elders?
Software shapes who gets followed up, who can export member lists, and which stories stay private. That is not a gadget preference. It is care of the flock (Acts 20:28). When only one staff member signs a three-year giving contract, the church learns about it when the invoice doubles.
Elders do not need to become product managers. They need enough sight to protect people, money, and continuity. A database permission is a pastoral care decision. A texting tool policy is a privacy decision. A renewal date is a stewardship decision. Leaving all three to an exhausted staffer is not trust. It is neglect with polite language.
What do elders need to see?
A one-page brief is enough: what problem the tool solves this quarter, monthly cost plus processing fees, who owns admin access, who can export people data, and how you will cancel if it fails. If the brief cannot fit on a page, the decision is not ready.
The page should answer these questions in plain words:
- Who can export the full people list tonight?
- What is the cancel path and the data-export path?
- Which pastoral notes live in this system versus a locked care file?
- What happens to access when a staff member resigns?
- What Monday job gets better in the next ninety days?
If staff cannot answer those questions, the church is not buying a tool. It is buying fog. Fog is how fees renew themselves.
What does shared wisdom look like on Monday?
Put renewals on the calendar ninety days out. Require two signatures for any tool that holds counseling notes or full member exports. Refuse “temporary” admin rights that never expire. Ask one quiet question in the meeting: if this vendor disappeared next month, what pastoral work would break first?
Shared wisdom also means refusing booth energy as a substitute for diligence. Elders nearly approve bad contracts when the demo was friendly and the packet is thin. Postpone one meeting if needed. Ask for the Monday owner name in writing. Vote on the page, not on a memory of a conference aisle.
Keep the software demo short unless a vote depends on it. Elders can learn a screen in five minutes. They cannot recover a careless three-year clause as quickly.
Costs elders should insist on seeing
Sticker price is the least interesting number. Ask for processing fees on giving. Ask for SMS overages. Ask for admin hours per week. Ask whether a “free” platform needs paid hosting or a specialist. Ask what happens to the budget if attendance dips and the contract does not.
Put tools that touch money or member data on a visible line, not buried inside “communications” or “miscellaneous.” Hidden lines create December surprises and quiet resentment between staff and board.
Care implications, not only IT
Who follows up first-time guests if this tool is adopted? Who watches replies on the shared inbox? Who may see benevolence attachments? Who can message youth directly? Technology decisions fail pastorally when elders approve a feature list and nobody names the human load.
A tool that requires ten unpaid evenings from one volunteer is not a bargain. A tool that centralizes exports without a permission review is not “simple.” A tool that only one person understands is a future crisis with a login screen.
A yearly rhythm that prevents fog
Put a short technology review on the elder calendar once a year, ideally before major renewals. The review is not a product fair. It is a care and stewardship meeting with four outcomes: keep, cut, replace, or document better.
Bring last year’s total software and processing spend. Bring the owner list. Bring one story of a kept promise (a guest who heard back) and one story of a break (a cancel that missed a household). Numbers without stories become abstractions. Stories without numbers become anecdotes that cannot guide a vote.
Between annual reviews, staff can still buy small tools inside a budget envelope. The annual rhythm exists so the envelope does not quietly become a second budget nobody watches. It also gives new elders a plain map of what the church depends on.
When staff and elders disagree
Sometimes staff want a tool elders fear. Sometimes elders want a platform staff cannot maintain. Name the disagreement without contempt. Ask what Monday job is at stake. Ask what happens if you wait ninety days. Ask what success would look like in measurable pastoral terms: reply time, schedule coverage, or export control.
A delayed decision with clear criteria is often wiser than a forced yes. A forced yes with no owner is how churches pay for shelves of unused logins. Shared wisdom includes the courage to say not yet.
One practice for this month
Pick one tool decision this quarter and require a one-page brief: weekly job, owner, cost, and cancel path. Put the next renewal ninety days out on the elder calendar. Review who currently has full export rights and remove leftovers from old roles.
If an elder can only quote the booth demo, postpone the vote one meeting. Shared wisdom is slower than a swipe of a card. It is also how churches avoid paying for fog.
Document the cancel path before you need it
Before renewal, have a staffer show where cancel lives and how data exports. Save a short screenshot packet in the church Drive. Future you will not remember the booth conversation. Future elders will thank you for a boring folder that still works.
Common questions
Do elders need to approve every small app?
No. Set a threshold. Low-cost tools with no people export and no counseling data can sit with staff inside a budget envelope. Tools that hold member data, gifts, or care notes need elder sight.
What if only one staff member understands the stack?
That is a risk finding, not a reason to stop asking questions. Require documentation, a backup admin, and a cancel/export test before the next renewal. Single-person knowledge is a pastoral continuity problem.
How do we disagree without stalling the church?
Ask for a ninety-day pilot with success criteria written in advance: owner hours, guest response time, or cancel reach. Review the criteria, then keep or cut. Open-ended trials without criteria become permanent by inertia.
The Monday digest
One short Monday email with a complete how-to for churches your size: named tools, ordered steps, and real cost. Reply anytime. A person reads it. Unsubscribe in one click.
Almost in. Check your email and confirm before we send the Monday how-to.