In this guide
Approval and recording are separate checkpoints
A leave request is about a plan. A leave record is about the absence being accounted for through the applicable process. They should agree when the plan occurs as expected, but one does not automatically prove the other. The public MyTime guidance allows departments to use different leave-request methods while still requiring leave used to be recorded. Follow the instructions for your own appointment and department. This article offers a reconciliation habit, not a description of every private system workflow or a decision about leave eligibility.
Build a three-part note
Use three headings: requested, occurred, recorded. Under requested, keep the approved dates and any relevant response. Under occurred, note whether the actual absence matched the plan. Under recorded, note the official record or confirmation you are authorized to review. Leave an unresolved question when those accounts differ. The model avoids a common reasoning shortcut: assuming that a calendar invitation, supervisor email, or approved request has necessarily completed every recordkeeping step. It also avoids assuming that a changed plan should be silently erased.
Worked example: a planned day changes
Consider a hypothetical employee who obtains approval for a full day away but later agrees with the department to change that plan. The employee does not simply rely on the original approval or choose a leave code from memory. They record the revised arrangement in the occurred section and ask what entry is appropriate under the department's instructions. The useful question is whether the official record reflects the revised event. The example does not determine how partial days, work performed, or a particular leave balance should be treated.
If a discrepancy appears later, the employee can provide the original plan, the confirmed change, and the relevant date without sharing why the leave was needed. That separation matters. An operational question about dates often does not require medical or other personal detail. The employee asks the responsible contact which secure documentation is necessary if further evidence is needed. They keep the request narrow enough that the answer can identify the next step rather than reopening every aspect of their benefit situation.
Read the policy population first
Rule 5-301A addresses vacation leave for University employees other than Hospitals and Clinics staff. Rule R5-200B applies specifically to Hospitals and Clinics staff and carries a February 13, 2026 effective date. Those scope statements are a warning against borrowing a colleague's leave answer from a different appointment. Neither the word health in a unit's name nor a shared campus location settles the applicable rule. Ask for your appointment's scope before using detailed provisions or discussing a possible transfer between units.
Close with confirmation rather than a guessed balance
A satisfactory outcome is confirmation that the applicable record matches the actual event, with any remaining balance question directed to the responsible office. Do not calculate future accrual, payout, or eligibility from this checklist. Keep the current policy links and department instructions beside the note so later changes can be checked. Sources were reviewed October 1, 2026. That review does not change the policies' effective dates, and it does not make the examples University instructions. The method simply keeps plan, event, and record from being confused.
Continue reading: Employment Verification: Decide What Must Be Verified Before Sharing, Campus and Healthcare Jobs: Read the Scope Before the Label, Temporary, Part-Time, or Research Work: Ask About the Shape of the Appointment.