What happens if I forget to clock in?
A forgotten clock-in leaves that day incomplete. No start means no duration, so the day produces no hours figure until the missing time is supplied through a correction request that somebody with approval rights reviews. Nothing fills the gap automatically, and nothing guesses a time on your behalf.
The incomplete day is the small part of the problem. What it does downstream is the large part.
Every figure built on that record inherits the hole. Hours for the week. The attendance percentage. The department total somebody presents on Friday. One missing morning quietly wrong-foots all of them, and none of them announce it.
This is also why nothing autocorrects. A system that invents a plausible start time produces records nobody can rely on afterwards, including the honest ones.
So the missing time arrives by request instead. Somebody states what happened, somebody else agrees, and the change keeps its before and after values in the audit trail.
Forgetting is also more common than most teams plan for. A device fails. A phone dies. Somebody walks past the terminal while on a call. A browser tab never opened. Any process treating these as rare will handle them badly, because they are not rare at all.
Volume is the useful signal. One person raising a request most weeks is a question about that person. A whole floor raising them is a question about where the hardware sits, or whether the browser card is switched on for that team.
A day where you were genuinely absent needs no correction. Forgetting to clock in and not being there produce similar-looking gaps, so say which one it was rather than leaving a reviewer to infer it.
Raise the correction the same morning while the actual time is still a memory rather than a reconstruction. Requests raised at month end are somebody's best guess and everyone involved knows it.
Related questions
Will the system assume I was absent?
The record shows an incomplete day rather than an absence. Those are different states, and rounding the first into the second would punish a hardware failure as though it were a choice.
Does a forgotten clock-in affect my hours?
Until it is corrected, yes. That day contributes no working hours at all, so any weekly total reads low by roughly a full shift.
How far back can a correction reach?
There is no fixed limit in the product. Whether an old correction is accepted is a judgement for whoever reviews the queue, and older ones are weaker evidence.