Skip to content
EMPOBase
en

When an NGO should move from spreadsheets to operations software

By the EMPOBase team · · 4 min read

Short answer

Move from spreadsheets when the same data is typed in several places, versions conflict, approvals are lost, reports take days to assemble, or one person's absence stops the work. Before you switch, clean your data and write down your process. Then move one function or one project first, run both for a short time, and widen only when the first step works.

Key points

  • Spreadsheets are fine for small, simple work; the signs of strain are specific.
  • Software will not fix a process nobody has written down; do that first.
  • Move one function or project first and run the old and new side by side.
  • Plan who owns the setup, the training and the data after the move.

What do spreadsheets do well?

Spreadsheets are flexible, cheap and familiar. For a small team with a few projects, a good set of shared files and clear habits can work for years. They are also useful for analysis, drafting a budget, or quick calculations. Moving too early can add cost and complexity you do not need.

The question is not “are spreadsheets bad?” It is “where do they now cost us more than they save?”

It helps to count the real cost. Add up the hours staff spend each month copying data, finding the latest file, checking totals and assembling reports. Add the cost of errors found late, such as a wrong budget figure sent to a donor. Compare that with the cost of a system, plus the time to set it up and learn it. The sum, in your own context, gives a fair answer.

What are the signs that spreadsheets no longer fit?

Look for these signs. One or two may be tolerable. Several together mean it is time.

  1. Double entry. The same figure is typed into several files.
  2. Version conflicts. People ask “which file is the latest?”
  3. Reports take days. Each reporting cycle starts with collecting and reconciling files.
  4. Weak approvals. Decisions sit in email, with no clear record of who approved.
  5. No shared view. Nobody can see grants, budgets and results together.
  6. Key-person risk. One person knows how the files work, and their absence stops the work.
  7. Access problems. Everyone can edit everything, or access is too tight to be useful.
  8. Audit stress. Evidence is hard to find when donors or auditors ask.

Ask staff themselves. A short question in a team meeting, such as “What takes the most time that should not?”, often brings out the same few answers. Listen for repeated phrases like “I have to check with…”, “Which version…” and “I did that last week already”. They are signals that the same work happens twice or that records are not shared.

What should you do before switching?

Software exposes weak processes. Fix the basics first.

  1. Write down the process. Who requests, who approves, who records, who reports.
  2. Clean the data. Remove duplicates, fix names, and settle on one list of projects, donors and budget lines.
  3. Agree definitions. What counts as a beneficiary, a reached person, a completed activity?
  4. Name an owner. One person who runs the setup and answers questions.
  5. Decide what moves. Not everything has to move at once.

Keep a simple list of your records and who owns each: budgets, indicators, contracts, staff files, stock lists. For each, note where it lives now, who edits it, and who needs to read it. This map is useful whatever you choose, and it shows which records matter most to move first. Our article on organizing NGO documents can help you with the document side.

How do you move in stages?

A staged move lowers risk.

  • Pick one function or project. Choose one with a clear pain and an engaged team.
  • Run both for a short period. Keep the old files read-only as a check, but avoid typing everything twice for long.
  • Train with real work. Short sessions using your own records beat generic demos.
  • Review after one cycle. What worked, what did not, what to change.
  • Widen step by step. Add the next function or project.

Our article on planning digital change in a small NGO covers the people side in more detail.

Set a clear end date for the old files. Without one, staff keep both systems for months and trust neither. Announce the date, say which records are final in the old files, and make them read-only after that date. Keep a copy for the record, with a note on what it contains, so an auditor can still trace earlier years.

What should you watch for after the move?

Check that staff are using the system, not keeping side files. Look at who still sends spreadsheets by email and ask why. Set a date to review permissions, since people change roles. Keep a regular export of your data, so you are never locked in. Recheck your needs each year.

Where EMPOBase fits

EMPOBase is operations software that keeps programs, MEAL, finance, people, logistics and governance records in one workspace, so shared records stop living in separate files. It does not fix a process nobody has written down, and some work, such as analysis, will stay in spreadsheets. The ledger is for projects, grants and restricted funds, and is not statutory accounting. You can read about what it covers and where it stops, or ask us for a walk-through with sample data.

Questions people ask

Can an NGO keep using spreadsheets for some things?

Yes. Many keep spreadsheets for analysis and one-off tasks. The aim is to move records that many people share, such as budgets, approvals and indicator data, into one system.

How long does a move take?

It depends on size and how clean your data is. Plan weeks to months, in stages, rather than a single switch-over date.

What if staff resist the change?

Involve them early, start with a problem they feel, and train in short sessions with real data. Resistance often points to a real gap in the tool or the process.