Woman speaking on the phone in an office with a laptop and paperwork on her desk.

How Should Churches Manage Technology When Their IT Person Leaves?

by | Nov 20, 2026

When a church’s IT employee, volunteer, or outside technology contact leaves, leadership should complete a structured technology transition within the first 30 days. The immediate priorities are to secure administrative accounts, recover passwords and documentation, verify backups, identify critical systems, and establish clear responsibility for ongoing support.
For a church with 15 to 30 employees and 25 to 50 managed devices, losing one person who controls technology can create significant operational risk.
A five-step transition framework helps protect the ministry from disruption while establishing a more reliable long-term IT environment.


1. Identify Who Controls the Church’s Technology

The first step in the 5-Step IT Transition Framework

Churches frequently depend on one individual who understands their technology environment.
That individual might be:

  • A full-time employee.
  • A part-time administrator.
  • A church member who volunteers technical support.
  • An outside contractor.
  • A former employee who continues helping occasionally.

This arrangement may work for years.
The problem becomes apparent when that individual retires, relocates, changes employment, or becomes unavailable.
Leadership may suddenly discover that nobody knows who manages the internet connection, controls Microsoft 365, maintains the firewall, or receives important technology notifications.

Create a technology responsibility inventory

Within the first five business days, identify who controls:

Technology SystemInformation to Confirm
Internet serviceProvider, account owner, support contact
Firewall and networkingAdministrative access, configuration backups
Microsoft 365Global administrators, licensing, billing
Computers and serversAdministrative credentials, management tools
Church management softwareSystem owner, vendor, user permissions
Accounting systemsAdministrative access, backup procedures
Backup systemsBackup owner, recovery procedures
Website and domainsRegistrar, DNS access, renewal information
Security systemsMonitoring responsibilities, alert recipients

Do not assume that access to a system means the church owns or controls the underlying account.
For example, a volunteer may have registered the church’s domain using a personal email address.
That creates a dependency that should be resolved before the volunteer becomes unavailable.

Warning signs

Leadership should investigate when:

  • Only one person knows the administrator passwords.
  • Important accounts use personal email addresses.
  • Technology documentation is missing.
  • Nobody knows whether backups are working.
  • Equipment ownership is unclear.
  • Vendor contracts are stored in personal accounts.

A church should retain institutional control of its systems regardless of who provides technical assistance.


2. Secure Administrative Accounts and Remove Unnecessary Access

Step two: Establish account ownership

The second priority is protecting the church’s technology environment from accidental or unauthorized access.
This does not mean assuming the departing individual has bad intentions.
It means following a consistent security process whenever responsibilities change.
A transition checklist should include:

  • Confirm church-controlled administrative accounts.
  • Review Microsoft 365 administrator permissions.
  • Change credentials that were shared.
  • Remove access that is no longer required.
  • Review remote access tools.
  • Verify multifactor authentication.
  • Update security notification recipients.

Pay special attention to shared credentials

Some churches use one administrative password for several systems.
Others share credentials among staff, volunteers, and contractors.
Both approaches make it difficult to determine who accessed a system or when.
A better approach is to assign individual accounts wherever possible and use secure credential management for shared administrative secrets.
West Texas IT Consulting uses IT Glue documentation and secure password management as part of its managed services structure.
This helps organizations maintain reliable records without depending entirely on one employee’s memory.

Consider data protection and compliance obligations

A departing employee may have had access to donor records, payroll information, personnel files, or confidential ministry information.
The church should review applicable privacy obligations, contractual commitments, and internal policies when removing access.
Certain systems may also have specific audit or security requirements.
Documenting access changes supports regulatory compliance readiness where applicable, but it does not automatically establish compliance.
A related issue arises when an employee changes positions rather than leaving entirely. A documented employee offboarding and access management process helps prevent former responsibilities from turning into unnecessary system permissions.


3. Verify Backups and Critical System Recovery

Step three: Confirm that the church can recover

Many organizations assume their data is protected because someone installed backup software.
That assumption should be tested.
A successful backup notification does not necessarily prove that the church can restore the information it needs.
Within the first 10 business days, leadership should determine:

  • Which systems are backed up?
  • How often do backups run?
  • Where is backup data stored?
  • Who receives failure notifications?
  • Has a restore been tested?
  • How long might recovery take?
  • What happens if the church’s building is inaccessible?

Prioritize critical ministry systems

Not every system has the same recovery priority.
Consider a church preparing for Sunday services.
A failed guest kiosk may be inconvenient.
A failed internet connection supporting live streaming, online giving, and cloud applications could affect several ministry activities simultaneously.
Church leadership should identify its most important systems and assign realistic recovery priorities.

Network CategoryTypical Use
AdministrativeStaff computers and business applications
Ministry operationsApproved ministry devices
ProductionAudiovisual and streaming systems
Guest accessVisitors and public internet access
Building systemsCameras, access control, and connected facilities equipment

Actual recovery times depend on equipment, backup design, service scope, and the nature of the failure.

Understand backup versus disaster recovery

Device backups and cloud backups are important, but they do not automatically provide a complete business continuity solution.
West Texas IT Consulting offers Business Continuity and Disaster Recovery (BCDR) as an optional service.
Churches that decline a recommended recovery solution should understand and acknowledge the associated operational risks.
This distinction becomes particularly important during severe weather, utility interruptions, and extended building closures.
Churches evaluating their long-term support needs can use a managed services fit assessment to determine whether a proactive IT partnership is the right approach.


4. Establish a Documented Support and Technology Management Process

Step four: Replace individual knowledge with organizational processes

A church does not necessarily need to hire another full-time IT employee when its existing technology contact leaves.
It does, however, need a reliable support model.
That model should define:

  • Who staff members contact when something fails.
  • Who monitors computers and servers.
  • Who manages software updates.
  • Who responds to security alerts.
  • Who approves technology purchases.
  • Who maintains documentation.
  • Who coordinates outside vendors.
  • Who reviews recurring problems.

Without these responsibilities, the church can quickly return to the same dependency it was trying to eliminate.

How proactive managed services work

West Texas IT Consulting operates through Managed Services Agreements rather than traditional break-fix support.
Its managed services structure includes a $40 per managed endpoint per month fee, together with a security package and a tiered technology fee.
The managed services fee supports:

  • Datto RMM monitoring and patching.
  • Proactive alerts and remediation.
  • IT Glue documentation.
  • Secure password management.
  • Unlimited Help Desk support.
  • Coordinated remote and onsite support when warranted.

Unlimited Help Desk support does not mean unlimited onsite labor.
Some onsite hours may be included depending on agreement size, while additional onsite work or major projects may be scoped separately.

Why technology alignment matters

Technology alignment goes beyond answering support tickets.
It means establishing standards for devices, security settings, documentation, software, and network infrastructure.
A church that replaces one departing volunteer with another volunteer may still have the same underlying weaknesses.
A church that establishes documented technology standards becomes less dependent on any single person.
A structured vendor and contractor access management process also helps churches maintain control when outside technology partners change.


5. Build a 30-Day Technology Transition Plan

Step five: Move from emergency response to long-term stability

The final step is turning the transition into an opportunity to improve reliability.
A practical 30-day plan looks like this:

TimeframePrimary Actions
Days 1-5Identify systems, accounts, vendors, and administrative access
Days 6-10Secure credentials, review permissions, and verify backups
Days 11-15Document equipment, network configuration, and support responsibilities
Days 16-20Review monitoring, patching, security tools, and recurring problems
Days 21-30Establish technology standards, priorities, and a management roadmap

Some environments will require more time, particularly when documentation is missing or ownership is disputed.
The goal is not to rebuild every system in 30 days.
The goal is to establish control, reduce immediate risk, and identify the work needed for a stable environment.


Hypothetical example: A Midland church loses its longtime IT volunteer

Consider a Midland church with:

  • 22 employees.
  • 35 managed computers and servers.
  • One main facility.
  • Microsoft 365.
  • Cloud-based church management software.
  • A volunteer who has managed technology for eight years.

The volunteer announces that they will be relocating in three weeks.
The church discovers that several administrative accounts use the volunteer’s personal email address.
There is also no current network diagram, and nobody has verified the backup process.
A structured transition would prioritize recovering administrative control, documenting the environment, reviewing security access, and testing data recovery.
The expected outcome is a church-owned technology environment with clearer responsibilities and less dependence on one individual.
This is an illustrative scenario, not a claim about an actual WTITC client.


Final transition checklist

Before considering the transition complete, confirm:

  • The church controls its administrative accounts.
  • Shared passwords have been reviewed.
  • Former access has been removed where appropriate.
  • Critical vendors and contracts are documented.
  • Backups have been verified.
  • Monitoring and patching responsibilities are assigned.
  • Staff know how to request support.
  • A technology improvement plan exists.


How West Texas IT Consulting can help

Churches in Midland, Odessa, and surrounding West Texas communities can benefit from replacing undocumented technology dependencies with consistent management processes.
West Texas IT Consulting focuses on proactive support, security, documentation, and technology alignment.
A properly secured managed IT environment is commonly budgeted at approximately $125 to $175 per endpoint per month, although actual pricing depends on device count, security requirements, user protections, the tiered technology fee, and other service needs.
For churches facing an IT leadership transition, the most important first step is establishing control of their existing environment.
Explore a managed services model that replaces individual technology dependencies with proactive support, secure documentation, and long-term technology alignment.

You May Also Like:

Ready to Talk About Your IT?

If you’re running a company or organization in the Permian Basin and want IT that actually understands your environment, we’d be happy to talk!