# Before payroll: a timecard check in plain words

*Use cases · Mays Team · October 13, 2026*

![Mays cover card: Before payroll: a timecard check in plain words — Missing clock-outs, edits and overtime, before they reach payroll](https://mays-uploads.s3.us-east-2.amazonaws.com/site/blog__timecard-check-before-payroll-ai__cover.b6303e652b.png)

Payroll day is when timecard problems get expensive. A clock-out that never happened turns a six-hour shift into a nineteen-hour one. A punch edited last week, without a note, raises a question nobody can answer. A break that ended early may matter under your state's rules. The usual check is a slow scroll through the punch grid, person by person, looking for the odd ones out.

With Mays connected to your AI app, you ask for the odd ones out directly.

*Part of our series* [*Run your restaurant with your AI*](https://www.mays.app/blog/your-ai-already-knows-your-restaurant-let-it-run-mays)*: one real situation per post, with the words you type and what happens in Mays. The prompts and results are illustrative examples.*

## What the manager types

The pay period at Harbor Lane Café's Riverside location runs September 16 to 30. The day before closing it, Maya L. asks:

> *"Check Riverside's timecards from Sept 16 to 30 before payroll. List missing clock-outs, auto clock-outs, punches a manager edited or added by hand, short breaks, and anyone in overtime. Also anyone who went more than an hour over their shift."*

## What the AI does in Mays

It reads Riverside's timecards for those days: the same data as the punch grid on the **Time Clock** page, for the locations you manage. Every punch comes back with:

- **clock-in and clock-out,** on the location's clock, and the hours worked;
- **breaks,** each one marked paid or unpaid, meal or rest, and **short** if it ended before its required length;
- **the shift it belongs to,** with the scheduled hours and the **variance** (worked minus scheduled), minutes **late** and an **early clock-out**;
- **overtime hours** on that punch, under the pay-period rules;
- flags for an **auto clock-out** (Mays closed the punch; the time is a cutoff, not when they left), a **missing clock-out**, and a punch with **no matching shift**;
- **how it was made:** phone, kiosk, added by a manager, or imported;
- **the edit trail Mays keeps:** who last edited the punch and when it last changed.

Plus totals for the range: punches, people, hours, overtime hours, and how many were edited, auto-closed or missing a clock-out. One question covers up to 31 days, so a biweekly or semimonthly period fits. You can narrow it to one person: *"Show Jordan R.'s punches this period."*

Wages appear only if you can see pay in Mays and included pay when you connected. Otherwise hours only, and the AI is told never to estimate the rest.

## What you see

The AI sorts the list into what needs a look, for example (illustrative):

> *"15 days, 9 people, 412.5 hours, 6.0 overtime hours. 1 missing clock-out: Jordan R., Sept 23, clocked in 6:28 am. 2 auto clock-outs, both on Sept 26 at the nightly cutoff. 3 punches added or edited by a manager, last edited by Maya L. 1 short break: Sept 19, 22 minutes of a 30-minute meal break. Jordan R. ran 1 h 20 m over the Sept 27 shift."*

## Fix it where it lives

The AI reads timecards; it doesn't change them. You fix punches in Mays, on the **Time Clock** page, where every edit is recorded, then approve and close the period as usual (see [Timesheets and pay periods](https://www.mays.app/help/time-clock/timesheets-and-pay-periods)).

What the chat gives you is the list to work through, and the questions to ask before you fix anything. An auto clock-out means the real end time is unknown; ask the person. A punch with no matching shift may be a pickup someone forgot to add to the schedule. And if your team fills in a paper correction form, our [missed punch and time card correction form](https://www.mays.app/blog/missed-punch-time-card-correction-form) shows what it should hold.

## What it replaces

| Before | With Mays connected to your AI |
| --- | --- |
| Scroll the punch grid person by person | The exceptions, listed |
| Export to a spreadsheet to sort by hours | Totals and variances in the answer |
| Ask around about who edited what | Who last edited each punch, and when |
| Find the nineteen-hour shift after payroll | Missing clock-outs before you close |

## Who can ask

Anyone who can view the schedule in Mays, for their own locations. It's read-only, so no actions setting is needed. Pay needs pay access in Mays and a connection that includes pay.

## What Mays doesn't do here

- **It doesn't keep earlier values of an edited punch.** It records who last edited it and when, not what it said before.
- **It doesn't edit or approve punches from the chat.** That's on the Time Clock page.
- **It isn't legal advice.** Whether a short break or overtime triggers a premium depends on your state; Mays applies the rules set for each location (see [Labor & compliance (per location)](https://www.mays.app/help/time-clock/labor-compliance)).
- **Long lists are capped.** One answer lists up to 100 punches, and the totals stay exact. Ask for one person or fewer days to see the rest.

## Try it before your next close

1. Connect Mays to ChatGPT, Claude or Grok from [mays.app/ai](https://www.mays.app/ai) ([ChatGPT](https://www.mays.app/ai/chatgpt), [Claude](https://www.mays.app/ai/claude), [Grok](https://www.mays.app/ai/grok)). [Connect Mays to ChatGPT, Claude or Grok](https://www.mays.app/help/ai-automation/connect-mays-to-chatgpt-or-claude) explains the pay box.
2. Ask for the period's exceptions.
3. Fix them on the Time Clock, then close the period.

[**Try Mays free for 30 days**](https://go.mays.app/register?utm_source=blog&utm_medium=ai_use_case&utm_campaign=timecard-check-before-payroll-ai), with no credit card, and connect it to the AI you already use.

## Related help articles

- AI & automation: [Connect Mays to ChatGPT, Claude or Grok](https://www.mays.app/help/ai-automation/connect-mays-to-chatgpt-or-claude) — Connect Mays to ChatGPT, Claude or Grok and ask about your locations from there — schedules, timecards, attendance, approvals, checklists, temperatures, stock, sales by day or hour, orders and product mix, labor targets, a suggested schedule for next week, inventory items and what to order — and, if your admin allows it, let it make changes you confirm, like adding a shift, approving time off, adding inventory items, uploading vendor invoices and knowledge-base documents, writing knowledge-base articles or sending a purchase order — or set up a whole new store in one go. Exactly the access you have in Mays. Disconnect any time.
- Time clock: [Timesheets and pay periods](https://www.mays.app/help/time-clock/timesheets-and-pay-periods) — Review every punch in a pay period on the Time Clock page — fix, add or delete punches, approve them, check warnings and hours, then close the period for payroll.
- Time clock: [Exporting payroll (CSV and Gusto)](https://www.mays.app/help/time-clock/payroll-export-and-gusto) — Download a pay period's hours as a Standard CSV or a Gusto timesheet, and add your Gusto employee IDs so the Gusto file imports cleanly.
- Time clock: [Labor & compliance (per location)](https://www.mays.app/help/time-clock/labor-compliance) — Where: Locations & Users → Locations → a location → Scheduling tab → Labor & compliance card.
- Time clock: [Taking breaks](https://www.mays.app/help/time-clock/taking-breaks) — Start and end breaks in the Mays app, pick the right break, see when one is due, and answer the break question when you clock out.

Canonical: https://www.mays.app/blog/timecard-check-before-payroll-ai