Tip-Out by Role: Kill the Back-of-Napkin Math at Close

The problem this kills

It's close. The dining room is dark, the drawer is counted, and now someone is hunched over a notepad doing tip-out math: this server did $2,400 in sales, so the bar gets a percent of that, the bussers get a percent, the food runner gets a cut — and wait, two bussers worked tonight and one left early, so how do we split their share? Multiply that by every server on the floor, get it wrong, and you've got a tense conversation, an under-tipped support team, or a payroll number nobody trusts.

The math isn't hard, but it's fiddly, it's done tired, and it changes every shift depending on who worked and how long. The result is inconsistency: different managers tip out differently, there's no record of how a night was split, and the support staff just have to trust the napkin. You don't need a payroll consultant to fix this, and you don't need to be a developer — you can build the calculator yourself in an afternoon.

What you'll build

A simple internal web tool for closing out a shift. You enter (or import) each server's sales and tips for the shift and check off who worked which support role and for how many hours. The tool applies your tip-out percentages — and because tip-out is usually a percent of sales, not just tips, the base is configurable per role. It pools each role's contributions, splits the pool by hours among everyone who worked that role, and nets out what each server owes and each support person is owed. It shows the manager a clear tip-out matrix — who pays whom, how much, and what each person walks with. The manager reviews, adjusts if a night was unusual, and clicks Approve. Only then does the tool lock the shift, produce a payroll/cash-out CSV, and email the tip-out sheet to whoever needs it.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your restaurant — which support roles you tip out, whether each is a percent of sales or of tips, your exact percentages, how you split a role's pool when several people worked it, your typical and busy-night server counts, and your messy edge cases (the server who only worked half the night, the salaried bartender, the comped table) — and then it tailors the calculation, the data model, and every later step to your answers. This is not a generic template: the agent reads a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through entering a shift, the tip-out math, the hours-based pool split, the manager review-and-approve matrix, the payroll CSV export, and the emailed tip-out sheet — each step with a ready-to-copy prompt. There's also a fallback so you can build and use the whole thing today by importing a sales CSV, with no integration to your POS required.

The governance it includes (this is the point)

Money is changing hands, so this ships with the controls a real operation needs: login so only your managers and shift leads can use it, row-level security so each location only ever sees its own shifts, a complete audit trail of who entered, edited, and approved each tip-out and when, a hard manager-approval gate so nothing is finalized or sent to payroll until a person signs off, and duplicate guards keyed on server + shift so the same shift can't be tipped out twice. The math is shown line by line, so the split is never a mystery to the staff who are paid by it.

Who it's for

Restaurant managers and shift leads who run a tip-out structure and want it consistent, fair, and on the record instead of on a napkin. If you can explain how your house splits the tip-out today, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your first shift's tip-out matrix add up the same afternoon.