How We Built a Scheduling System That Saved 8 Hours a Week

The starting point was not dramatic. It was a spreadsheet. Multiple tabs. Volunteer names, shifts, notes, cancellations, confirmations, and a whole lot of color-coding. It worked, technically, the way a house of cards works technically.

The staff spent 5-8 hours every week keeping the schedule alive. That is a huge tax on a small team, especially when the mission is caring for animals rather than managing rows in a spreadsheet.

▶ The first version

We did what good builders do: start small. A Google Sheets script handled the most repetitive parts of the scheduling workflow. It generated assignments and sent notifications automatically. Immediate relief. Fast feedback. Low risk.

That first version proved the concept. Once the workflow was stable, we knew it was worth turning into a proper product.

▶ The full platform

Next came the React frontend, the Express API, and a PostgreSQL database hosted on Railway. The result was a real scheduling platform with volunteer management, shift scheduling, public schedule viewing, and assignment tracking.

This mattered because the system was no longer a tool for the staff alone. It became infrastructure for the organization.

▶ The result

Manual coordination disappeared. Staff time came back. Volunteers had a clearer experience. Most importantly, the shelter could focus on the mission instead of the mechanics.

That is the pattern every small business should pay attention to: if a workflow hurts enough, it is probably not a workflow problem. It is a software problem.