Hate that you learned it the hard way on that maple, but glad the cuts look better now.

The part that gets me is you actually did the work to prove it. Two weeks, 23 lost changes, that's not a guess, that's data. And that's the thing nobody wants to deal with, because if the problem is the terminal or the printer or whatever the wifi is doing, then there's no one to yell at. Yelling at the kitchen is easy. Fixing a bad connection at table 6 means calling somebody, waiting on hold, maybe buying new hardware, and who's gonna do that mid-dinner rush. So instead the server vents at the pass and the cook just eats it. I'd take your count to whoever runs the place and ask them to check the terminal logs against those 23 tickets, because once a manager sees the gaps on paper it stops being a kitchen problem and starts being a repair bill. Until then, that second copy you're printing is the only thing keeping the line from getting blamed for stuff the computer did.