Time Clock Change Approvals: A Policy Template for 2026

A time clock change approval policy is a short written rule that says who may request a change to a recorded punch, who approves it, what gets documented, and how fast it happens. The best version keeps the original punch, records a reason, gets the employee’s acknowledgment, and never lets an edit reduce hours below what was actually worked. Below is how to build one for a small U.S. business, with a template you can adapt today.

TL;DR

• Employers may correct time records, but never cut recorded hours below the time actually worked, even if the employee agrees.
• Keep the original punch, add the correction as a new entry, and log who changed it, when, and why.
• Make approval a two-way process: the employee requests or confirms, a manager approves, and both are on record.
• Set a deadline before payroll closes, and keep the records for the periods the DOL and IRS require.
• Write the policy once, post it, and apply it the same way to every employee.

Table of Contents

• Why a written approval policy matters
• What counts as a time clock change
• What the law lets you change, and what it does not
• The five parts of a good approval policy
• A policy template you can adapt
• How long to keep the records
• Common mistakes to avoid
• Our perspective on change approvals
• Setting this up in your time clock
• Rolling out the policy to your team
• FAQ
• Sources

Why a written approval policy matters

Most time disputes do not start with someone lying. They start with a forgotten punch, a shift that ran late, or a manager who fixed a number on Friday afternoon and did not tell anyone. Without a rule, each of those becomes an argument about who remembers what.

The legal stakes are real even for a five-person shop. Under the Fair Labor Standards Act, employers are not required to use time clocks, but if they do, they must keep complete and accurate records of hours worked for nonexempt employees. The responsibility stays with the employer even when supervisors track time or employees record their own. The law does not prescribe a form, but the record has to show all hours worked and wages paid.

A change approval policy is how you prove that your records are accurate after someone has touched them. It also keeps your payroll honest. Our guide on payroll errors from manual timesheets covers what happens when edits are made informally, and why accurate timesheets reduce disputes covers the people side.

What counts as a time clock change

Define the term in the policy, or people will argue about it. A change is any edit, addition, or deletion to a recorded punch after the fact. In practice, that covers:

• Missed punch: the employee forgot to clock in, out, or back from a break.
• Wrong punch: the employee clocked in on the wrong job, location, or shift.
• Early or late punch: the employee punched in before the scheduled start, or stayed past close without clocking out.
• Break corrections: a meal break was skipped, shortened, or interrupted by work.
• System errors: a device was offline, a battery died, or the app failed to sync.
• Leave adjustments: an employee was sick or on approved time off, and the record needs a matching entry.

Separate these from normal punches. A normal punch needs no approval. A change always does. If you want a deeper treatment of the most common case, see our missed punch policy guide and the shorter definition of a missed punch policy.

What the law lets you change, and what it does not

Two rules sit under every approval policy.

You may correct records. According to SHRM’s guidance, employers have the authority to change or correct time records so they reflect hours actually worked, for example when an employee forgets a punch or is out sick.

You may not shave hours. The same guidance says employers may never reduce recorded hours below the amount actually worked to avoid overtime, even if the employee consents. Put that sentence in your policy in plain words. It protects you from a well-meaning manager who “cleans up” a 41-hour week into a 40-hour one.

That second rule matters most in restaurants and construction, where long days and tight margins create pressure to trim. Our pages on restaurant overtime rules and FLSA overtime rules explain where owners get caught.

Rounding and automatic deductions are changes too

A rule that silently adjusts time is still an adjustment. Rounding is lawful when it is fair and neutral. SHRM’s summary of California court decisions says automated policies must not consistently result in a failure to pay employees for time actually worked over a period of time. If your rounding always favors the business, treat that as a problem to fix before an employee raises it. Our FLSA time rounding guide goes through the details.

Auto-deducted meal breaks need the same care. SHRM suggests giving workers a way to cancel the deduction when they work through a meal. That cancellation is itself a change request, so your policy should route it through the same approval path.

The five parts of a good approval policy

1. Who can request a change

Let the employee request a change for their own time. Let a manager request one when they see an error the employee has not noticed. Do not let anyone approve a change to their own time. In a small shop where the owner is also the manager, a second person such as a bookkeeper or lead can serve as the check, or the owner can approve and log a reason for review at payroll close.

2. Who can approve

Name roles, not people, so the policy survives turnover. A typical small-business setup:

Edits that create or remove overtime deserve a higher approval level, because they carry the most cost and the most legal risk.

3. What the request must include

Keep it short enough that people will actually fill it in. Require:

1. Employee name and date of the shift.
2. The original punch (or the fact that none exists).
3. The requested punch time.
4. A reason, chosen from a short list of reason codes, with a free-text line for anything unusual.
5. Who is requesting and when.

SHRM’s guidance recommends a clear reason code and, where edits are made, keeping the original entry and creating a new record for the change. Never overwrite. The original punch is your evidence.

4. Acknowledgment from the employee

This is the step most small businesses skip, and it is the one that pays off in a dispute. When a manager changes a record, SHRM’s background guidance is that the manager and the employee should both sign or electronically acknowledge the change. That protects you if an employee later claims a manager altered records without their knowledge.

Think of approval as a shared process, not a one-way decision. An employee who has confirmed their own corrected hours is far less likely to contest them later, and you have a record that is much easier to defend during an audit.

5. Deadlines and a lock

A policy without a deadline becomes a backlog. Pick two dates:

• Employee deadline: requests must be submitted by the end of the next workday, or before the pay period closes, whichever comes first.
• Manager deadline: all requests approved or denied before payroll is run.

After payroll closes, lock the period. Late changes then go through a separate path, usually owner approval plus a corrected paycheck, so that the exported hours always match what was paid. Staffing firms that chase weekly timesheets describe the same pattern: supervisor approvals, payroll locks, and an audit trail work together to stop endless back-and-forth.

A policy template you can adapt

Copy this into your handbook and edit the bracketed parts.

Time Record Corrections Policy

We keep accurate records of all hours worked. If a punch is missing, wrong, or incomplete, you must tell your supervisor by [end of the next workday] and submit a correction request through [the time clock app or form].

Every request must state the date, the correct time, and the reason. Your supervisor will review it by [payroll cutoff]. Changes that add overtime or affect a closed pay period also need approval from [owner or general manager].

The original punch is never deleted. Each correction is saved as a new entry showing who made it, when, and why. You will be asked to confirm any correction made to your time.

Time records will never be changed to reduce hours below the time you actually worked. If you believe your record is wrong, report it to [name or role] and it will be reviewed. No one will be disciplined for reporting a timekeeping error in good faith.

Falsifying a punch, punching in for another employee, or approving a change to your own time is a violation of this policy.

Have an employment attorney review the final text, especially if you have staff in a state with its own meal and rest break or recordkeeping rules. State requirements vary and can be stricter than federal ones.

How long to keep the records

Approval records are time records. Keep them.

The DOL’s recordkeeping fact sheet says employers must preserve payroll records for at least three years, and records on which wage computations are based, such as time cards, for two years. Separately, the IRS says to keep employment tax records for at least four years after filing the fourth-quarter return for the year. Since the periods differ, the practical answer for most small businesses is to keep the original punches, corrections, and acknowledgments for the longest period that applies to you, and check your state’s rules, which may be longer.

Year-end is when this catches up with people. If you are preparing W-2s, it helps to know about the W-2 reporting changes for 2026 before you start matching payroll totals to your timekeeping files.

Common mistakes to avoid

• Verbal approvals. “I told Dana it was fine” is not a record. Log it.
• Editing in a spreadsheet. If the only copy is the one that got changed, you have no original.
• Approving your own edits. Even honest self-approval looks bad in an audit.
• Applying the policy unevenly. If you accept late requests from favorites and reject them from others, the policy becomes evidence against you.
• Silent rounding. Automated adjustments that always land in your favor invite claims.
• No cap discussion. Some employers limit how many change requests one person can submit in a month. A cap can help spot patterns, but never use it to refuse a legitimate correction. A worker who really did work the hours must be paid for them.
• Letting requests pile up. Approving a month of changes on payroll day leads to rushed, careless decisions.

Our perspective on change approvals

We built Kloqk for owners who do not have an HR department. Most of the owners we talk to in restaurants, retail, construction, and clinics are not worried about complicated edge cases. They are worried about the ordinary Tuesday: someone forgot to clock out, the manager fixed it from memory, and now nobody is sure what was paid.

Our view is that the best approval policy is the one that makes the right thing the easy thing. Prevention does most of the work. Photo verification at clock-in, location checks, and clear break tracking mean fewer punches need correcting in the first place, so approvals are the exception rather than a daily chore. When a correction is needed, it should leave a trail: the original, the change, the reason, and who agreed.

We also think owners should be wary of any rule that exists only to protect the business. A policy that quietly trims hours, or that makes employees fight to correct a missed punch, will cost more in disputes and turnover than it ever saves in payroll. Pay for the time worked, document the exceptions, and keep the record clean. That is both the fair approach and the defensible one.

Saad

Setting this up in your time clock

A policy is only as good as the tool that enforces it. Whichever system you use, check that it can do four things: keep the original punch beside the edit, record who changed what and when, route changes to an approver, and export hours that match the approved record.

Kloqk’s free plan covers the core of time tracking: payroll-ready timesheets, overtime and break calculations, and payroll exports, with mobile and kiosk punching for your team. Paid upgrades are optional, at $29 per month per location for Pro and $59 per month per location for Premium. See the Free, Pro, and Premium plans to compare what each includes, or look at how employee time tracking works before you commit to anything. If your crew works at job sites, the GPS time clock page explains how location checks reduce the need for after-the-fact edits.

Rolling out the policy to your team

A good policy fails if nobody knows it exists. A simple rollout works for most small teams:

1. Write it on one page. Use the template above and strip anything that does not apply to you.
2. Explain it in person. Spend five minutes at a staff meeting or shift huddle. Show a real example of a missed punch being fixed.
3. Get acknowledgments. Have each employee sign or confirm in your system that they have read it.
4. Train supervisors separately. Make sure they know they cannot cut hours, cannot approve their own edits, and must log a reason every time.
5. Review monthly. Look at the number of changes per employee and per supervisor. A cluster of edits from one person or one shift usually points to a training problem, a device problem, or something worse.

If you find a pattern of corrections that always lower hours, stop and investigate. If you find a pattern of forgotten clock-outs at closing time, fix the closing routine instead of approving the same edit every night.

FAQ

Can a manager change an employee’s time clock punches?

Yes, when the change corrects the record to show time actually worked, such as a forgotten punch. A manager may not lower recorded hours below what was worked, even with the employee’s consent. Keep the original entry, log the reason, and get the employee’s acknowledgment.

Does the employee have to approve the change?

Federal law does not spell out an employee sign-off requirement. HR guidance recommends it because it creates a shared record and protects you if the employee later says the change was made without their knowledge. Build it into your policy as a standard step.

How quickly should change requests be approved?

Before payroll runs, and ideally within one or two business days. Set the deadline in writing and apply it evenly. Requests that arrive after payroll closes should follow a separate path that ends in a corrected paycheck.

Should I limit how many change requests an employee can make?

You can track the numbers and talk with employees who submit many requests, since repeated errors may signal a training or device issue. Do not use a hard cap to deny a correction for hours that were really worked, because those hours must still be paid.

How long should I keep time clock edit records?

Keep them at least as long as the longest applicable rule. The DOL sets three years for payroll records and two for time cards, and the IRS asks for four years of employment tax records. Your state may require more, so check before you delete anything.

Sources

• DOL Fact Sheet #21: Recordkeeping Requirements under the FLSA
• SHRM: Can managers change employee timesheets?
• SHRM: Rounding and grace period policies in California
• SHRM: 3 steps to minimize risks with auto-deducted meal breaks
• IRS: Employment tax recordkeeping
• US Tech Automations: Stop weekly timesheet chasing in staffing
• TaxFormHero: W-2 changes for 2026

Recommended

• Photo Clock-In Policy: U.S. Employers Need Privacy Rules
• Managers: Four Stage Timesheet Approval Workflow That Works
• Best Time Clock Apps for Small Business in 2026