Whoever is taking order should have each order by number (or whatever alternate system) and should be constantly communicating what's left (needed) to complete an order...before getting too far ahead...by just taking orders...posting them...waiting...packing...taking more orders.
Calling out ticket 3. This that the other. Post. Working on ticket 3. Waiting on fries. How long for fries? Ok. Ticket 3 out. Pull ticket 3. Calling out ticket 4. This that & the other. Post. Working on ticket 4. Waiting on this or ticket out. Ticket 4 out. Pull ticket 4. Ticket 6 quick ticket fries only. Post. Fries out. Pull ticket 6. Back to ticket 5. Calling out ticket 5. This that & the other. Post. Working on ticket 5. Ticket 5 out. Ticket 7. No post. Soda only. Pull ticket 7. Ticket 8...
Some system where you can hear it...(get used to it) follow it.
(develop a system to answer the call simply to verify you got it)..slow down the traffic pile ups...while keeping it move. The expeditor has to be able to make judgement call by knowing what's working (how long it will be) and should be able to navigate back & forth to get whatever they can moved out...without always waiting for the line strictly by the number.
A standard system with the same order & words so no matter who is expediting (or who you might have to teach) it's always the same...no matter who is calling.
You just have to map out you own system...outline it...and write it up.
A rack is a rack.
post edited by CCinNJ - 2012/10/07 05:14:45