In this article
A time entry can exist without being the final payroll record. That is why the words saved, submitted, approved, and paid should not be treated as synonyms. Each describes a different kind of progress, and a question about one stage can be misdirected if the employee names another.
The University of Utah's Introducing MyTime introduction outlines an employee submission, manager review, and payroll sign-off sequence. It also says the transition to MyTime did not itself change payroll deadlines. That gives employees a useful framework: the system where time appears is part of a process, and an entry's presence is only one observation about that process.
The first question is what the status means
Suppose a fictional employee, Casey, enters a shift and sees it in the timecard. Casey can now say the entry is displayed. Casey cannot yet conclude that the correct position was selected, that a required reviewer approved it, or that the entry was included in the statement being examined. Those may all be true, but they require their own evidence.
This is not a reason to distrust every screen. It is a reason to use precise language. When you ask for help, describe the label the system displays rather than translating it into “everything is complete.” A staff member supporting the process can then explain the meaning of that label and identify the next owner.
If no clear status is visible, say so. Do not create a new time entry merely to make the first one feel more certain. A duplicate can make reconciliation harder. Ask how to verify the existing entry and which correction route is appropriate for your department.
Separate the employee deadline from downstream processing
A payroll calendar may contain dates for several audiences. The Payroll Schedule and Deadlines page distinguishes process deadlines, hourly calendars, and ePAF deadlines. An employee looking at the page needs to know which action a particular date governs. A department may also communicate an earlier local deadline so that someone has time to review the submission.
The practical question is therefore not simply “What is the deadline?” It is “What do I need to submit, to whom, for which period, and by what time?” If your department gives an instruction that you do not understand, ask promptly. Do not assume the last date visible on a public calendar is the employee's safe last moment to act.
For a fictional example, imagine a local review date on Monday and a later payroll processing date. Missing Monday might leave less time to resolve an error even though the later date has not passed. The example is about sequencing, not the University's actual calendar. Use the current official calendar and department instructions for real decisions.
A leave request and a leave entry are different evidence
An employee can have permission to take time away and still need to ensure that the time is recorded through the appropriate process. A calendar invitation, a manager's email, and a timekeeping entry do different jobs. The approval of the absence does not automatically explain how a payroll system represents the hours.
Before a planned absence, clarify both questions: how the department approves the absence and how the time should be entered. Keep the method specific to your employee population. A faculty process, a campus staff process, and a Hospitals and Clinics process should not be assumed identical because each involves a day away from work.
If a balance later looks unexpected, compare the requested absence, the recorded usage, and the balance's date. Do not immediately change a category to make the arithmetic match. Ask what the entry should represent. A tidy total is not useful if it was produced by the wrong classification.
When a manager is away, find the authorized path
A missing reviewer creates a process problem, not permission for an employee to act as that reviewer. The MyTime introduction describes manager delegation as a supported capability. Employees should use the department's actual instructions to identify who is authorized to review a timecard when the usual person is unavailable.
Send a short question that identifies the period and the pending stage. Avoid forwarding a complete record to a broad group in the hope that someone can approve it. A department administrator or payroll contact can often identify the appropriate person without exposing the underlying details to everyone on a team.
There is also a difference between asking who owns the approval and asking for an exception. If a deadline is close, state the timing and ask what can still be done. Do not claim that payroll has promised an expedited payment or special check unless the responsible office has actually confirmed that arrangement.
A correction needs an owner and an expected sign
The most useful correction conversation ends with three facts: who will make the correction, which record will change, and how the employee can recognize it. “We will look at it” may be a reasonable first response, but it does not yet define the outcome. A follow-up can politely ask for the next step without assuming the result.
In a fictional example, Casey learns that a shift was assigned to the wrong position. The correction may concern the time entry, an employment record, a later payroll adjustment, or more than one of these. The publication cannot know the appropriate route. Casey's task is to preserve the explanation and check the record that the responsible office identifies.
Keep the original observation available in your own permitted records. Record the date of the response and the described change. If a later statement still raises a concern, that small history lets the office continue the investigation rather than restart from an ambiguous account of what happened.
Build a short end-of-period review
An end-of-period review does not need to become a full audit. Read the period label, check that the intended position is represented, look for obvious missing or duplicated entries, and identify the status the system currently shows. Use your department's process for submitting or correcting the record.
The purpose is to notice a specific issue while there may still be time to ask about it. It is not to approve your own pay or calculate legal entitlement. If the screen is unclear, preserve the question and seek official help. Do not let an informal checklist delay reporting a genuine concern.
A good timekeeping habit is less about memorizing every button and more about recognizing the handoffs. The employee supplies or verifies the entry. An authorized reviewer handles the next stage. Payroll produces a record that can be read and, when necessary, questioned. Keeping those stages distinct makes both ordinary periods and unusual corrections easier to discuss.
Sources and reading limits
Public sources reviewed October 15, 2026. These links support the specific University context above; the comparison methods and hypothetical examples are original editorial work. No authenticated system was tested. Policies and interfaces can change. Individual pay, benefits, tax and employment decisions require the appropriate official or qualified advice.