Currently we write templates based on an average week and we make a template for each schedule we have in the system.
What happens if this Tuesday is national holiday and we expect to do three times the sales we normally do? We have to go recreate or modify templates to cover that.
I think there is a good chance that if we based templates on projected sales for a daypart, for example a $2300 Lunch, we could use that template all over the place. I would guess if you cross referenced the day parts with the sales ranges that you would see very definite patterns in the sales flow.
If templates were built this way, then instead of appling a whole week at once, you could drag and drop the template built for a $2300 lunch to all the days that are in that sales range.
I find that with the current set up, I don't spend enough time looking at where the sales fall in the day. My forecast of a $6500 saturday may be very accurate, but if we happened to do $4k at lunch instead of dinner, odds are good that we were understaffed at lunch and over staffed at night. If our forecasting was focused on dayparts then we match the labor levels to each daypart, I think we would end up with better customer service in the end because we would be more prepared each shift.
We would also save money on situations like the lunch I mentioned above. When we are over staffed on a shift because the sales fell in a different day part, we wasted money on labor we didn't need.
Please sign in to leave a comment.