Agree on the split before closing the check
A table may ask to split by person, by item, by seat, or into an uneven set of amounts. The request is easiest to resolve before payment begins. Confirm the plan aloud, repeat any items that are shared, and clarify who is paying for an appetizer, bottle, or dessert. A short confirmation now can prevent a longer correction after cards have been run.
Teach one default sequence so staff do not improvise under pressure. For example: confirm the requested split, assign shared items, show or read back the resulting totals, then collect payment. The exact steps depend on the restaurant and its tools. The table-service workflow page is a useful prompt for considering how table, order, and closeout handoffs fit together.
Keep shared items visible
Shared dishes and drinks are common sources of disagreement. Decide whether the server asks the table to assign each shared item, divides it evenly when guests request that, or calls a manager when the plan is unclear. Never assume that a shared item belongs to the person who ordered it. The check should reflect the guests' decision, not an internal guess.
When a party changes its mind, restate the new plan before editing the check. Keep a clear path to correct an item assignment, and make sure a payment already collected is not charged again. The POS buyer's guide includes evaluation questions about split checks, adjustments, and auditability.
Prepare for payment exceptions
A declined card, a guest leaving early, a gratuity question, or a disputed charge can interrupt the sequence. Define which cases a server may resolve and when a manager should step in. Staff should know how to pause a check, confirm what has already been paid, and protect guest privacy while handling a sensitive payment conversation.
If the restaurant has a policy for deposits, large parties, or automatic gratuity, make sure it is communicated before the meal and applied consistently. Train staff on how the policy appears on the check. The FAQ page is the public source for current Freedom POS product information; it should not be mistaken for a restaurant's own payment-policy guidance.
Use corrections as coaching, not blame
Review voids, re-opened checks, and payment corrections to find where instructions or screen flow may be unclear. Look for patterns by shift or service type, not just by employee. A high correction count may point to a confusing menu, a training gap, or a process that asks staff to make decisions too late.
Run short practice scenarios before a weekend or event. Include an even split, an item-based split, a shared appetizer, and a guest who changes the plan. The pricing overview can help frame the total cost of training and support when evaluating systems, while the platform page helps organize questions about how different roles share an operating view.
- Confirm the split plan before collecting payment.
- Make shared items and already-paid amounts explicit.
- Set clear manager escalation rules for exceptions.
After practice, ask a server to explain the sequence back in their own words. If the explanation differs from the written steps, adjust the training card before a live shift. Keep examples short enough to rehearse during pre-service. The goal is not to eliminate every unusual request; it is to help employees pause, confirm the guest's preference, and reach a manager when the next step is unclear.