Yes. You can check whether an AI assistant calculates a ratio correctly by giving it a small dataset, calculating the answer independently, and comparing the results. A correct answer on one dataset does not prove the assistant will always be accurate, but it gives you a practical starting point for deciding whether its output deserves further review.
Start with sales per labor hour: total sales divided by total paid labor hours. The test below checks arithmetic on numbers you provide. It does not check whether an assistant can find the right figures in a sales report or connect to your systems.
Build a fictional shift dataset
The following numbers are hypothetical. Each row represents a separate two-hour period in one restaurant shift. Sales belong to the period in which they occurred; labor hours are the combined paid hours of everyone working during that period. For example, three employees each working two paid hours produce six labor hours.
| Shift period | Sales | Paid labor hours | Sales per labor hour |
|---|---|---|---|
| 11 a.m.–1 p.m. | $420 | 6 | $70.00 |
| 1–3 p.m. | $360 | 5 | $72.00 |
| 3–5 p.m. | $300 | 4 | $75.00 |
| 5–7 p.m. | $240 | 3 | $80.00 |
| Total shift | $1,320 | 18 | $73.33 |
The last row is the answer to check. Add the four sales amounts and the four labor-hour amounts first. The period ratios help you inspect individual rows, but the total shift ratio is not their simple average because the periods have different numbers of labor hours.
For this exercise, sales mean sales after discounts and before taxes and tips. Paid labor hours include paid idle time and exclude unpaid breaks. The dataset contains no refunds or other adjustments. Use the same definitions in every prompt; otherwise, you may be testing interpretation rather than arithmetic.
This is a sales-to-hours ratio, not a profit or labor-cost calculation. Sales are not cash collected, and labor hours are not wages. Fixed costs, variable costs such as wages and ingredients, and exception costs such as refunds are excluded from the calculation. Do not use the result to estimate profit or an all-in operating cost.
Calculate the answer before asking the assistant
Keep an independent answer key outside the assistant's conversation. A calculator or spreadsheet is enough for this small test. Work through the totals and then divide:
- Sales: $420 + $360 + $300 + $240 = $1,320.
- Paid labor hours: 6 + 5 + 4 + 3 = 18 hours.
- Sales per labor hour: $1,320 ÷ 18 = $73.333....
- Rounded to the nearest cent: $73.33 per paid labor hour.
The unit matters. An answer of 73.33 without a label leaves the manager to guess what it represents. An answer in hours per dollar is a different ratio, even if the assistant uses the same inputs. Ask for dollars per paid labor hour and two decimal places so the expected output is unambiguous.
A common error is to average the four period ratios equally. That gives $74.25, not the shift result of $73.33. The first period accounts for six labor hours while the last accounts for only three, so they should not have equal weight in the shift calculation. Dividing total sales by total hours handles that weighting.
Another error is rounding too early. For this worksheet, add the original inputs, divide once, and round the final result. If an assistant displays more decimal places in its working, that is fine as long as its final two-decimal answer is correct. A small display difference is different from using the wrong denominator or omitting a row.
Before using real figures, agree on how your team defines sales and paid hours. A guide to comparing labor hours with sales by shift can help frame that separate reporting decision. This exercise deliberately supplies the inputs so you can isolate the calculation.
Ask equivalent questions and inspect the work
Give the assistant the four period rows, the definitions, and the rounding rule. Do not give it the answer key. Ask each version in a fresh conversation, with the same dataset included each time. That reduces the chance that a previous answer simply carries over into the next response.
- Direct: “Using these four periods, calculate total sales divided by total paid labor hours. Show both totals and round dollars per hour to two decimal places.”
- Manager's wording: “How many dollars in sales did this shift produce for each paid labor hour? Show your calculation and round to cents.”
- Task wording: “Combine all four periods into one shift. What is the shift's sales-per-paid-labor-hour ratio? Include the units and two-decimal result.”
All three requests should produce the same $1,320 sales total, 18-hour denominator, and $73.33-per-hour result. Compare the totals as well as the final figure. A correct-looking number is less reassuring if the assistant cannot show which rows it included or gives an explanation that contradicts its answer.
Then run a separate missing-data check. Remove the labor hours from one row and ask for the shift ratio. The acceptable response is to say that the complete shift ratio cannot be calculated from the information provided and ask for the missing hours. It may calculate a clearly labeled partial ratio, but that is not the answer for the whole shift. It should not invent the missing value.
Keep the checks simulated: enter only fictional data and do not connect the exercise to a live service workflow. No real payment, guest message, or courier dispatch is needed. If you later run a live service pilot, plan it separately with staff oversight and explicit controls; a successful simulation does not establish that a live workflow is ready.
Set pass rules and decide what happens next
Record the prompt, the exact inputs, the assistant's answer, and your verdict for each attempt. Save the answer key alongside the record. This makes it easier to compare a revised prompt or another assistant without relying on memory.
For the complete-data prompts, mark a pass only when all of these are true:
- The assistant includes all four rows and reports $1,320 in sales and 18 paid labor hours.
- It divides total sales by total hours and returns $73.33 per paid labor hour, rounded to two decimal places.
- Its explanation agrees with the calculation and does not present the result as profit, labor cost, or a percentage.
Mark a fail if any total, operation, final rounded value, or unit is wrong or missing. For the missing-data check, mark a fail if it supplies an invented hour figure or presents a partial calculation as the complete shift result. If the assistant gives the right number but no working, ask it to show the calculation; record the initial response separately rather than silently replacing it.
Use the pattern of failures to decide what to do. If the assistant consistently misses a row, try a clearer table and retest from a fresh conversation. If it cannot handle the missing-data check, do not rely on it to flag incomplete inputs. If it passes, move to additional fictional cases with different totals and a denominator that is not zero. For a zero-hour case, it should explain that division by zero cannot produce a valid ratio, not return a fabricated result.
Human review still belongs between an answer and an operating decision. A manager considering a schedule change should check the source figures, definitions, staffing needs, and context for the shift. One ratio alone does not show whether service was slow, whether employees were training, or whether the sales mix changed. Ask the assistant to show its work; do not let it make the staffing decision by itself.
When you are ready to look beyond a standalone calculation, list where sales and labor figures would come from and who will verify them. Compare those requirements with Fleksa's restaurant management software, and confirm current availability before choosing a workflow. Also review the restaurant POS system and ask about relevant integrations and data access; do not assume an AI calculation or a particular export is included.
Frequently asked questions
Does a correct answer prove the assistant is accurate?
No. It proves only that the assistant answered that particular test correctly. Repeat the exercise with other fictional inputs, including missing values, before deciding how much review its work needs.
Should I average each period's sales-per-hour ratio?
Not as a simple average when periods have different labor hours. Add the sales and labor hours separately, then divide total sales by total hours to get the shift ratio.
Can I use this ratio to calculate labor cost percentage?
No. Sales per labor hour uses hours, not labor dollars. A labor cost percentage needs a defined labor-cost amount and a consistent sales figure, followed by a separate calculation.
