A volunteer cannot access the supporter database before an appeal. A staff member is working from an ageing laptop that no longer receives updates. Trustees are being asked to approve a new system without a clear view of costs, risks or benefits. These are the situations a charity technology planning guide should prevent. Good planning gives your charity technology that supports its mission, rather than creating another drain on limited time and funds.

For charities, the right technology is rarely about having the newest tools. It is about helping people communicate, protect sensitive information, deliver services reliably and make the most of every pound. The best plan is practical enough to guide day-to-day decisions, but flexible enough to accommodate changing funding, staffing and community needs.

Start with the charity’s work, not the equipment

A technology plan should begin with how your organisation operates. Before discussing cloud platforms, devices or cyber security products, look at the work your people need to do. Consider staff, volunteers, trustees, beneficiaries and external partners. Each group may need different access, support and safeguards.

Ask straightforward questions. Where does work slow down? Which systems would cause a serious problem if they stopped working for a day? What information do you hold about donors, service users and staff? How do people work when they are away from the office? The answers reveal where technology is getting in the way of the charity’s aims.

For example, a small community charity may be able to work effectively with shared cloud files, secure email and a dependable phone system. A larger organisation delivering services to vulnerable people may need clearer case-management processes, tighter access controls and stronger device management. Neither approach is automatically better. The right level of technology depends on the sensitivity of your data, the way services are delivered and the consequences of disruption.

It also helps to speak to people beyond the leadership team. The person processing donations, the volunteer co-ordinator and the colleague who prepares trustee reports will often spot issues that are not visible in a software renewal spreadsheet. Technology planning works best when it reflects real working practices, including the workarounds people have quietly adopted.

Build a clear picture of what you already have

Many charities have accumulated systems over time. One platform was introduced for fundraising, another for finance, and several different file-sharing methods emerged when remote working became necessary. There may be useful tools in place, but no single record of who owns them, what they cost or whether they are still needed.

Create a simple inventory covering your devices, software subscriptions, cloud services, internet connection, phones, backups and key suppliers. Include renewal dates, licence numbers, named system owners and the location of important data. This need not be a complicated technical document. It needs to be accurate enough for a manager or trustee to understand the charity’s commitments and risks.

Pay particular attention to accounts created in individual employees’ names. If a member of staff leaves and is the only administrator for a fundraising platform, social media account or cloud storage area, access can become difficult at exactly the wrong moment. Administrative access should be controlled and documented, with more than one appropriate person able to manage critical services.

This review often identifies easy savings. Duplicate subscriptions, unused licences and unsupported devices can be addressed quickly. It may also expose harder decisions, such as whether a familiar but outdated system is still worth maintaining. Familiarity has value, especially when volunteers need simple processes, but it should not override security, supportability or the cost of repeated problems.

Set priorities in your charity technology planning guide

A long wish list is not a plan. Priorities should be tied to risk, operational impact and the charity’s objectives over the next 12 to 36 months. A charity planning a major fundraising campaign, opening a new site or expanding its services will have different needs from one focused on stabilising core operations.

A useful approach is to group work into three horizons. First, fix urgent weaknesses: unsupported software, poor passwords, missing backups, unreliable connectivity or systems with no clear owner. Next, improve everyday efficiency through better collaboration, device replacement and simpler processes. Finally, consider larger projects such as a new donor database, automation or business intelligence reporting.

The order matters. There is little value in introducing automation if staff cannot reliably access shared files, or in moving data to a new platform without deciding who should see it. A sound plan protects the foundations before adding complexity.

When deciding what comes first, test each proposal against a few practical measures:

• Does it reduce a meaningful risk to people, data or service delivery?
• Will it save staff or volunteer time often enough to justify the cost?
• Is there a clear owner who can make decisions and support adoption?
• Can it work with the systems the charity genuinely needs to keep?
• What happens if the project is delayed for six months?

Trustees do not need a technical lecture to make good decisions. They need a plain-English explanation of the problem, the options, the total cost and the likely consequence of doing nothing. This makes approvals more confident and helps avoid buying technology in response to the loudest complaint.

Treat cyber security and continuity as core services

Charities are trusted with personal information, financial records and often highly sensitive details about the people they support. That makes them a target for phishing, account takeover and ransomware. Smaller organisations are not exempt simply because they have fewer staff. Attackers often look for organisations that lack dedicated internal IT resources.

Security planning should focus on sensible layers rather than a single product. Strong, unique passwords with multi-factor authentication, managed updates, secure devices, appropriate access permissions and staff awareness training all play a part. So do backups that are checked regularly. A backup is only useful if the charity can restore the right data within a timescale that keeps services running.

Think through realistic disruption scenarios. If your main email system is unavailable, how will staff communicate? If a laptop is stolen, what data could be exposed? If the office loses internet access, can essential calls be handled elsewhere? If a key employee is on leave, can someone else access the systems needed to process payroll or donations?

These questions can feel uncomfortable, but they lead to proportionate preparation. Not every charity needs expensive duplication of every service. Most do need documented procedures, tested backups and somebody accountable for keeping security measures current.

Make funding and free licences work harder

Technology grants and charity software entitlements can make a genuine difference, but they should support a plan rather than dictate it. A free licence is not free if it creates training demands, integration problems or future costs that the charity cannot sustain. Equally, charities should not pay commercial rates for tools when suitable not-for-profit pricing or donated services are available.

Before applying for funding, define the outcome in plain terms. It may be reducing the time spent compiling reports, allowing secure hybrid working, improving donor communications or protecting beneficiary records. Then calculate the full cost of ownership: implementation, data migration, training, support, devices and ongoing subscriptions. Grant applications are stronger when they show how technology will improve services and remain manageable after the funding period ends.

Be cautious about large, one-off changes if your team has limited capacity. A phased rollout can cost slightly more to manage, but it allows people to learn, exposes problems earlier and reduces disruption. For a charity with a busy seasonal calendar, timing matters as much as the technology itself. Avoid replacing core systems just before a major event, year-end reporting period or fundraising appeal where possible.

Put ownership, training and review dates in place

The most carefully chosen system will disappoint if no one owns it. Assign a named business owner for every important platform. They do not need to be technical. Their role is to understand how the system supports the charity, approve access, raise problems and make sure processes remain fit for purpose.

Training deserves the same attention as purchasing. Short, role-specific sessions are usually more effective than a single demonstration for everyone. New starters and volunteers need a clear introduction to the tools they use, as well as basic guidance on phishing, password safety and handling personal data. Written instructions should be simple, current and easy to find.

Review the plan at least annually, and after a significant incident, staffing change or strategic shift. Check progress against the priorities you set, update the asset list and renew your view of risk. This turns technology planning from a document that sits in a folder into a working part of good charity governance.

For charities across Sussex, an experienced IT partner can bring useful structure where there is no internal technology team, or provide extra capacity for an existing one. My Tech Team can help translate technical choices into practical actions, from assessing current systems and cyber risks to planning secure, cost-conscious improvements. The aim is straightforward: your people should be able to focus on the cause, confident that their technology is working for them rather than against them.