One weekly report. One human decision.
Follow a made-up shop owner through a weekly sales-and-labor check. The workflow joins the two reports, flags the number that doesn’t add up, waits for the owner to decide, then writes the summary. Every number on this page is fictional sample data that lives in the page. Nothing you type is sent anywhere.
What the owner does by hand every Monday.
- Export last week’s sales from the register, one report per location.
- Export last week’s hours from the timeclock app.
- Copy both into a spreadsheet and line them up by location and day.
- Check that labor makes sense next to sales, and chase anything odd.
- Write a short summary for the managers.
Sample only. “Sample Street Café” and its locations are fictional. The register, timeclock and backup log below are sample files built into this page. No real customer records, accounts or paid services are used.
Run the workflow on sample data.
- Connect data
- Review the flag
- Weekly summary
1. Connect the sample sales and labor data
- Sample register · daily salesConnected (sample)
- Sample timeclock · hours workedConnected (sample)
| Location | Sales | Hours | Labor cost | Labor % of sales | Status |
|---|
Labor cost uses a sample wage of $17 an hour. The workflow flags any day with hours worked but no sales.
2. Review the row that needs a human
Connect the sample data first. If anything doesn’t add up, it shows here.
| Day | Register sales | Timeclock hours | Check |
|---|
3. Generate the weekly summary
The summary is written after the owner decides what to do with the flagged row.
Weekly summary · Sample Street Café
Sample data · fictional
Have a weekly report you build by hand?
On a free 30-minute call we find which part of it a workflow should do, and which decisions stay with you.