In this article
A role transition can look complete because the replacement has a desk, a checklist and a calendar invitation. Academic work may still be stranded if the person lacks the approved access for the actual task. At the same time, the departing employee may retain capabilities that no longer match their responsibilities. Continuity requires attention to both sides of the handoff.
This article offers a preparation framework for department managers and academic staff. It does not submit an access request, grant a role or troubleshoot a particular account. The University of Utah’s current security-authorization process determines what is required. No one should share a login, password, Duo approval or session to make the transition appear finished.
Inventory responsibilities before permissions Start with the work the new role must perform. Use concrete tasks: support a particular advising program, handle a defined scheduling responsibility or assist with an authorized class function. A list of old menu names is less useful because it can preserve access that was accumulated for reasons no longer relevant.
For each task, identify the academic scope, the approving role and the expected duration. Is the responsibility permanent, temporary or a short absence arrangement? The answer helps the designated authority evaluate the request. The department should not assume that the broadest possible role is the safest way to avoid future delays.
Also distinguish training from authorization. A person can understand a workflow without being approved to use it, and can receive technical access without having enough task-specific preparation. A handoff plan should make both needs visible rather than treating either one as proof that the other is complete.
Use the current official route The Registrar’s Security Access Forms page, reviewed October 15, 2026, says FERPA certification must precede access to specified authorization forms. It distinguishes student-record, degree-audit and e-grading authorization, and separately links change and deletion processes. The page showed an October 13, 2026 update, making it a better starting point than an old locally saved form.
Use that current official resource to identify the applicable process and contact. A public article cannot determine which security role a particular employee should receive. If the unit is unsure, describe the bounded job to the responsible university team and ask which authorization route applies.
Avoid requesting access by copying another employee’s entire configuration. Their role may include work unrelated to the replacement’s responsibilities. A task-based request is easier to justify, review and later remove. It also gives the new employee a clearer understanding of why each capability exists.
Build a handoff that points to authorized sources The departing employee should identify the current status of open work and where its official records live. The handoff should not be a personal archive exported into a new location. Use approved systems and avoid multiplying student-record copies merely to make the transition feel comprehensive.
For each open task, record what is established, what remains unresolved, the next responsible role and the relevant deadline. If a decision is pending, identify who may make it. The replacement should not have to infer authority from the fact that a task appears on their list.
Use fictional examples for practice when real records are unnecessary. A training exercise can teach how to recognize a missing term or an unclear completion state without exposing an actual student’s circumstances. If real case work is necessary, it should occur only within the approved role and handling requirements.
Verify the new responsibility without borrowing access A transition check should establish that the authorized employee can perform the required task through the official process. It should not use another person’s credentials as a temporary test. If access is pending, record that status honestly and route time-sensitive work to an already authorized role through the approved arrangement.
Distinguish a successful sign-in from successful authorization for a task. A person may reach CIS while lacking the specific academic capability needed. Conversely, a visible function may not justify using unrelated records. The handoff’s test should be scoped to the actual approved responsibility.
Do not promise a processing time based on a past experience. The official team controls the request’s handling. The department can plan a responsible temporary ownership arrangement and communicate the dependency without claiming that a new role will be ready by a time nobody has confirmed.
Close the old role deliberately Access removal is part of continuity, not an optional cleanup after the important work. The unit should know which responsibilities ended and use the official change or deletion process as appropriate. Do not assume that a departure, transfer or new job title automatically resolves every permission question.
Likewise, consider local copies and shared workspaces. A former role may still appear in a group, a document permission or a distribution list. The relevant owner should review those arrangements under university policy. This article does not prescribe a universal deletion rule, because different records and systems have different requirements.
Keep the completion evidence specific. “Handoff finished” should mean more than a meeting occurred. It should establish the new ownership, the approved route for remaining work and the status of old access. If one part is pending, leave that part visible with a responsible person and a next check.
A fictional transition before a busy term An invented department replaces a coordinator shortly before a period of heavy academic work. The initial plan is to hand over a personal folder and ask the new employee to use the outgoing coordinator’s workstation if access is delayed. The manager recognizes that this plan confuses continuity with impersonation.
The revised plan lists the actual responsibilities and submits the appropriate official requests. An already authorized colleague retains temporary ownership of urgent tasks through the approved arrangement. The new employee receives training with fictional examples and a handoff pointing to approved records. No credential or live session is shared.
As the new role becomes available, the department verifies the required task scope. The old role’s removal is tracked through its proper process. Open questions remain attached to named owners instead of disappearing into the transition meeting’s notes. The department has not eliminated every delay, but it has prevented delay from becoming a reason to ignore authority.
Review the handoff as a service After the transition, ask what the replacement had to reconstruct. Were public source links current? Did the task list distinguish decisions from routine steps? Was the backup arrangement clear? Did a supposedly complete item still depend on an unavailable person? These questions improve the next handoff without blaming the individual who inherited the gaps.
Keep the improved guide small enough to maintain. A task description, authoritative source and clear completion test can be more useful than dozens of screenshots that age quickly. Where a live system changes, refer to current official instructions rather than preserving an obsolete imitation of the interface.
A good handoff transfers responsibility in a way the institution can recognize and the employee can understand. It keeps access proportional to the work, gives unresolved tasks an owner and marks the endpoint of the old role. The login is only a means of reaching that authorized work; it is never the thing one employee should hand to another.