Fix a Time Card Entry Without Losing the Punch

A volunteer swears she left at 4:00, but the record shows 4:47 because she forgot to tap out. A line cook clocked in twice and now has two open entries. A tutor's start time reads 2:00 PM when the session began at 3:00. These are the corrections you make every pay period, and every one of them is a chance to either clean up the record or quietly corrupt it.

The goal is a fix you can defend later. When someone questions the hours on a grant report or a paycheck, you want to point to what changed, why, and what the record showed before. Here is how to do that in order.

Before you touch anything, confirm what actually happened

Do not edit on a hunch. Get the real time first. Ask the worker, check a second source, or look at the surrounding entries. A cook who clocked in at 5:02 PM was almost certainly there for the dinner rush, so a stray 5:02 AM punch is a typo, not a night shift.

Write the correct time down before you open the record. If you are converting from a paper sign-in sheet or a memory like "about a quarter after three," round to the minute you can actually justify. When the numbers get messy, a time card calculator keeps you from fat-fingering the math on total hours.

Decide the reason in one short phrase now: "forgot to clock out," "wrong AM/PM," "duplicate entry," "clocked in on the wrong day." You will attach that reason to the edit so the change explains itself six weeks from now.

Read the existing entry so you know what you are changing

Open the worker's entry in the dashboard and note both the recorded clock-in and clock-out before you change a thing. Two situations look similar but need different handling.

If the entry is still open (no clock-out at all), the system may have already handled it. Kangaroo Clock uses auto-close for forgotten clock-outs: a stale open entry is closed at its start time plus a set cutoff, never at the current moment. That means a shift someone forgot to end does not silently run for fourteen hours and inflate the report. You are correcting an already-capped number down or up to the real time, not rescuing a runaway clock.

If the entry is closed but wrong, you are adjusting a start time, an end time, or both. Note the original values in your reason text so the before-state survives even after the field changes.

Make the edit and record why

Now change the field. Set the clock-in or clock-out time to the value you confirmed in step one. Times are stored in UTC and shown in your local time, so enter the local time you and the worker agree on and let the system handle the conversion. You do not need to do timezone math in your head.

Keep the edit surgical. If only the end time is wrong, change only the end time. Leaving the correct start time untouched means half the entry still carries its original punch, which is exactly the trustworthiness you want.

Attach the reason phrase you decided earlier. "Forgot to clock out, worker confirms 4:00 PM" is worth ten seconds now and saves an argument later. The point of a correction is not to hide the mistake. It is to show the record was reviewed by a person who knew what happened.

When there is no punch to edit at all

Sometimes a worker never clocked in. There is nothing to correct because nothing exists. In that case you create the entry from scratch. The steps for that are laid out in the guide on how to clock someone in or out manually, including how to set both ends of a shift for someone who was there but never tapped their name. Use that path for a missing entry, and use the editing path above for an entry that exists but holds the wrong number.

Handle duplicates and overlaps deliberately

Double punches are the messiest case. A worker taps the kiosk, thinks it did not register, and taps again, leaving two entries an hour apart. Do not just delete one at random.

Look at both. Keep the entry with the correct start time and remove the accidental one, or merge them by editing one to span the real shift and deleting the other. Decide which single block of time the worker actually worked, then make the record say exactly that. Note "removed duplicate clock-in at 6:04 PM" so the missing entry is accounted for rather than mysteriously gone.

Overlapping entries across roles need the same care. If someone worked the front desk and then covered a tutoring slot, those are two entries, not one. Use tags on the time entries to keep them separated by program so your filtered report still reads cleanly.

Verify the corrected total before you close out

After every edit, look at the day's total for that worker and sanity-check it. A four-hour volunteer shift should read close to four hours. If a single edit swung the total by six hours, you probably fixed the wrong field or entered AM for PM.

When you are ready to hand numbers to payroll or a grant officer, pull the CSV export. The column schema is stable and never breaks, so your corrections land in the same fields every time, including the distinct-worker count for headcount reporting. Open the file and scan the rows you touched. The times you set should be the times you see.

A repeatable habit, not a one-off scramble

Run the same loop every close: confirm the real time, note the original, edit only the wrong field, write the reason, verify the total. Do it the same way each period and corrections stop being a source of doubt. They become the part of the process that makes the whole report believable.

If you are still tracking punches on paper and retyping them, you are creating the very errors this loop exists to catch. You can start a free workspace and have workers clock in with no login or app, then keep the small number of edits you do make clean and traceable.