Miran Posted on May 30 Building a Cover Flow for Missed Shifts # webdev # saas # product # buildinpublic I started working on the cover flow for missed shifts, and it became more interesting than I expected. At first, I treated it like a simple status change. Someone cannot make a shift. They tap a button. The shift becomes available for someone else. That was the clean version in my head. But once I tried to turn it into an actual product flow, I realized there are a few small decisions hiding inside that button. It is not really a cancelled shift This was the first thing I had to separate. If a staff member says they cannot make it, the job itself is not gone. The client still expects someone to show up. The time is still on the schedule. The owner still needs someone assigned to it. So I did not want to treat it like a cancellation. It is more like: This shift still exists, but the current person is no longer covering it. That sounds small, but it changes the whole flow. The shift is not confirmed anymore. It is not completed. It is not cancelled. It needs cover. That one state became the center of the feature. The owner needs to see the problem quickly Once a shift needs cover, the owner should not have to dig through the full schedule to find it. That is something I keep noticing while building this MVP. A tool can technically show all the information and still fail at the important part. If something needs attention, it should be hard to miss. So the owner view should probably not start with the question: What shifts exist? A better question is: Which shifts need a decision right now? A missed shift should move into a visible place. Not hidden inside a calendar. Not treated like a normal upcoming shift. Not buried under confirmed jobs. It needs to stand out because someone still has to solve it. The staff side should stay simple The staff side is different. A staff member should not need to understand the whole scheduling system. They just need a clear action.
LIVE