I walked into a small domestic violence shelter four years ago to help them fix their intake process. The director, a woman who had been doing this work for twenty years, showed me a filing cabinet stuffed with paper forms. Each client had a folder that could be two inches thick. When a woman called asking if she could come back after leaving six months earlier, someone had to dig through those files by hand, often taking fifteen minutes just to find the right folder. The shelter served about three hundred people a year. I calculated they spent roughly four hundred hours annually just looking for information they already had. That is ten weeks of someone’s time, every year, doing nothing that helped a single person directly.
This problem is not unique to that shelter. The social sector has a data problem that most people outside it do not see. We collect mountains of information about the people we serve, but we organize it in ways that make it hard to use. When I train staff at nonprofit organizations, they tell me the same thing over and over. They spend more time entering data than using it. They fill out forms because a funder demands it, not because the information helps them do their jobs better. One caseworker I know kept a separate notebook with real notes about her clients. The official case management system, she said, was for the grant reports. The notebook was for doing the actual work. That is a systemic failure. Software should make good work easier, not harder. The most effective teams I have seen use tools designed for the kind of work they actually do. For example, one organization Lamplight us to replace a spreadsheet system that had grown so large it crashed every afternoon. The switch cut their documentation time by about a third, and staff could finally pull up a client’s full history in seconds instead of minutes. That is what good data looks like. It disappears into the background and lets you focus on people.
Why we collect data we never use
Most social service organizations track a long list of things they do not need. They log the time of every phone call, the reason for every visit, the outcome of every interaction. The data goes into a system and never comes out again in any useful form. I once worked with a youth program that required staff to enter twenty-three fields for every single contact with a young person. That included the young person’s mood, the weather, and whether transportation was provided. Nobody ever analyzed the weather data. Nobody even knew why it was there. The person who designed the form five years earlier had left, and nobody wanted to change anything because they were afraid of breaking the reporting. So the waste continued.
The direct human cost of bad data
When you add up the time lost to bad systems, you get a clear picture of services not delivered. A caseworker who spends two hours a day on data entry loses ten hours a week that could go to clients. Over a year, that is more than five hundred hours. Spread that across a team of ten workers, and you have lost five thousand hours. That is roughly three full-time positions worth of time, spent typing instead of helping. I have seen organizations burn out their best staff this way. The workers who care the most spend the extra hours doing the documentation because they know it has to happen. Then they have less energy for the people who need them.
Where the time actually goes
I have tracked dozens of social workers through their workdays. Here is what I see most often:
- Logging into three different systems to find information that should be in one place
- Manually entering the same client data into multiple forms because no system talks to another
- Generating reports by exporting data to spreadsheets and reformatting everything by hand
- Chasing down missing information because required fields force staff to guess or leave blanks
- Printing out case notes for supervisors who refuse to read them on a screen
- Rebuilding intake forms every time a funder changes a reporting requirement
What good data practices look like
I have seen a few organizations do this right. The best ones share a few habits. They collect only what they will actually use. They design forms around the needs of the caseworker, not the grant report. They let people enter information in natural language instead of forcing every observation into a dropdown menu. One program I worked with reduced their intake form from forty-seven questions to twelve. The director was terrified the funder would complain. The funder did not even notice. What did change was that staff started completing the intake during the first meeting instead of pushing it to a second appointment. That single change cut the time between first contact and service delivery by nearly two weeks.
How to fix your own system
Start with the waste. Pick one process your team does every day and time it. Just watch someone do the task and write down how long each step takes. I did this with a housing program that thought their intake took twenty minutes. It actually took forty-seven minutes on average. The team was shocked. They had been underreporting their own workload for years. Then ask the people who do the work what they would change. The people on the front line almost always know exactly what is broken. They have workarounds and hacks and secret shortcuts. Listen to them. In my experience, the fixes that stick are the ones the staff invent themselves, not the ones imposed by leadership.
Measuring what matters
The real test of a data system is not whether it produces pretty reports. It is whether the people using it can answer basic questions about their work. How many people did we see this week. Which clients are close to reaching their goals. Where are we seeing the most drop-offs in service. If your team cannot answer those questions in under a minute, your system is failing you. I have seen too many organizations spend thousands of dollars on software that generates fifty-page quarterly reports nobody reads, while the caseworkers cannot pull up a simple list of clients who missed their last appointment. That is a problem of priorities, not technology. The best tools are the ones that make the daily work easier and the quarterly reports take care of themselves.