Scheduling in five minutes instead of tens of hours

In 2021, Eco Wash's operations manager was spending tens of hours every week building staff schedules by hand. With more than 30 employees, seven-day operations, and a tangle of rules around shift distribution, rest days, and team composition, Excel wasn't cutting it anymore. Mistakes slipped into the schedules. They needed room to grow.

The real challenge

This wasn't about replacing a spreadsheet with software. It was about encoding how their business actually worked, and doing it in a way that could flex when things changed.

Eco Wash ran a laundry operation with three employee groups: women, men, and drivers. They needed at least 18 people on the floor daily, with minimum driver coverage. Certain days required more heavy lifting. Everyone needed at least one weekend off per month. No one worked more than five consecutive days. And then there were the edge cases, like people who shared transportation and needed aligned schedules.

Getting the rule prioritization right was the crux of it. When rules conflict, and they always do, the system needed to know what mattered most. Eco Wash knew which rules were hard boundaries and which could bend. The work was getting that out of their heads and into an order the system applied.

What it did

The manager logged into a web portal to view current schedules and generate new ones. Employees could check their assignments. Generated schedules could be adjusted manually if needed, then exported as Excel or PDF.

We considered building it so Eco Wash could change the rules themselves, without a developer. We decided against it. The rules weren't going to change often enough to justify the complexity and cost. So Eco Wash didn't pay for something it would hardly use.

What changed

Their manager got those tens of hours a week back. Fewer errors meant fewer fires to put out, and with scheduling off their plate they could focus on what actually mattered: hiring more people and scaling the operation.

From 2021 to 2024 the system ran without a single bug, and without needing a new feature. Security updates went out, and the application did what it was built to do. That's what good software should do: solve the problem and then get out of the way.