When a campus ticket crosses the service desk, an application team and a vendor, somebody still has to tell the campus what happens next. Agree on that person, the checks each team will run and what it takes to close the ticket before cutover.
Give the campus ticket an owner
Suppose a student adds a course in the SIS. The Registrar can see the enrollment, but the student still can’t open the course in the learning management system. The vendor asks for a timestamp. The integration team is checking the next scheduled transfer. The student needs to know whether they can submit tonight’s assignment.
Have the service desk assign a named incident owner. That person keeps the campus ticket current, gets a response from each team and tells the caller when to expect the next update. The SIS lead or vendor may investigate the cause. Keep the ticket and its next update with the campus owner while they do that work.
Solano Community College publishes Banner SaaS transition updates alongside directions to its service desk and offices such as Admissions & Records. Tennessee State University’s February 2026 board materials list cutover and support plans among the intended Banner SaaS readiness deliverables. Use your own campus calendar and contact list to decide who covers problems during registration, billing and other deadlines.
Confirm which team can take the next step
Ask the application lead to write the contracted product, deployment and support route on the handoff sheet. If the Student target is Ellucian Student powered by Banner, confirm that name and the services in scope. Use the agreement for your actual deployment when assigning hosting, maintenance, diagnosis and case handling. Managed hosting, an on-premises upgrade and SaaS can leave different work with the campus.
Name a primary and a backup who can open and follow vendor cases. Ellucian’s Customer Center says that access to Actionline and Cloud cases requires institutional approval. Before cutover, have both staff members confirm access with their approved accounts and find the current priority criteria and after-hours instructions. If a partner will open cases, confirm that arrangement and who at the institution can take over.
| When this happens | What to check or record | Who takes the next step |
|---|---|---|
| A student or staff member reports a problem | Record the failed task, time and time zone, affected group and deadline. Agree when the caller will hear back. | Service desk incident owner |
| An enrollment is missing from the learning system | Check the SIS enrollment and term, then compare the transfer result with the receiving enrollment. | Registrar representative and integration owner |
| An account cannot reach a service | Confirm the person’s expected access and check the sign-in or role assignment through approved support channels. | Campus identity or application support |
| A vendor case is needed | Send the approved case details. Link the case number and next update time to the campus ticket. | Authorized case owner or backup |
| A fix or workaround is ready to check | Repeat the original task with an approved test record. Have the functional office confirm the result and any remaining exceptions. | Functional reviewer and service desk incident owner |
Route the incident using the records you have
Start with the last point where staff can confirm the expected result. In the enrollment example, the Registrar confirms the course and term in the SIS. The integration owner checks when that change should transfer and whether the receiving system accepted it. If the transfer completed but the student still can’t open the course, have learning system support check access to the course. Keep each finding in the same campus ticket.
Check Ellucian Cloud Status if the symptom could involve a covered cloud service. The page reports service issues that can affect multiple production systems. If the status page doesn’t explain what your campus is seeing, continue the campus checks. Use your agreement and the actual impact and deadline to select the escalation route.
- Step 01Record the problem
Name the failed task, affected group and deadline.
- Step 02Find the last good result
Compare the SIS record, transfer and receiving result.
- Step 03Assign the next check
Send the findings to the campus team or authorized case owner.
- Step 04Verify and close
Have the functional office repeat the task before closing the ticket.
References: [5]
Set the update and closure rules
If the authorized case owner escalates, share the product and environment, when the issue started, a reproducible example and what the campus already checked. Follow the institution’s rules about sending student information or attaching logs. Record the vendor case number, the person following it and the next update time in the campus ticket.
Agree who can approve a temporary procedure. The Registrar might decide how to handle students with missing course access while the incident is open. Have the office record which students still need follow-up and when staff will review the arrangement. Use the campus ticket to track those follow-ups after the immediate problem clears.
Rehearse the handoff before cutover with the primary owner unavailable. Have the backup find the correct contact and explain what they would send and when they would update the campus. When testing recovery, have the Registrar confirm the enrollment and the receiving team confirm that the approved test student can open the course. The service desk records who checked the result and keeps any remaining exceptions assigned. When the project team hands open cases to operations, have the receiving owner accept each case and its next update.
Sources
- Banner SaaS Transition Updates — Solano Community College (accessed )
- February 2026 Board Materials, Banner SaaS Upgrade (p. 136) — Tennessee State University (accessed )
- University of Stirling Chooses Ellucian Student Powered by Banner — Ellucian (accessed )
- Customer Center — Ellucian (accessed )
- Ellucian Cloud Status — Ellucian (accessed )
Related reading
- Cloud & SaaS Migration
A strategy for migrating Ellucian Banner and Ellucian Student to SaaS
A planning guide for confirming the target, choosing migration phases and agreeing who checks student records, interfaces, reports and support.
- Integration & Ethos
Before moving to Ellucian Student: map the interfaces that must keep working
Find the jobs, files and manual uploads that connect Student to other systems. Have staff confirm who uses each transfer, when it must arrive and what must change before cutover.
- AI & Automation
Test an AI staff assistant before it answers Banner support questions
Give the assistant approved support questions and current runbooks. Have staff check its answers, source references, access limits and handoff to the right support team.
- Related service
Managed Services & Support
Functional and technical operations for Ellucian estates — from day-to-day support to release readiness.

