Ask the Registrar and IT lead to agree which student functions will move first and which systems will stay. Confirm the contracted target with Ellucian before choosing the sequence. Use the unanswered questions about records, reports and interfaces to decide what work must happen before a phase can proceed.
Confirm the change and who is responsible for it
Write the current product and deployment into the project scope. For the Banner path, confirm the contracted Ellucian Student powered by Banner target with Ellucian. An on-premises upgrade, managed hosting and a SaaS implementation are different changes; ask the vendor to state the responsibilities included in the contract.
Ask the IT lead to review the current jobs, connections and local changes with their staff owners. For each item needed in the proposed phase, request confirmation of the supported target approach. Keep unanswered product questions open rather than assuming current access will continue.
The official Ellucian modernization and Lancashire pages cited in the related readiness guide describe an incremental approach and institution-specific phasing. Use those examples to frame questions for your project, not to adopt another institution's schedule.
Choose phases from the work the institution needs
Ask functional managers which tasks must stay available during registration, billing and other critical periods. Mark the records, reports and connections each task needs. Have the project manager identify the work that must be completed and tested together.
The assessment may support changing an interface before moving Student, replacing a local job within a phase or deferring a function while another system stays in use. Ask IT and Ellucian to confirm whether each option is supported. Do not require every connection to move to Ethos before all other work.
For the chosen phase, have each staff owner agree an expected result and an approver. Schedule the tests and any conversion rehearsal around their availability. The sponsor should record why the proposed sequence is accepted and what could change it.
Agree staff tasks after the move
Ask Ellucian to confirm the release, maintenance and support arrangements for the contracted service. Have IT write down who receives notices, who checks affected interfaces and who contacts the vendor when a problem occurs. Do not assume a particular release frequency.
Ask functional managers who tests a change to registration, charges or reporting and who approves it for staff use. Record the cover needed when that person is unavailable. Determine staffing from those tasks rather than assuming one team will shrink or another will grow.
Before the phase goes live, have the project manager walk through a proposed support incident with staff. Check that the person receiving it knows where to record the issue and who makes the next decision.
Give the sponsor the open decisions
Bring the agreed phase scope, test results and unresolved questions to the sponsor. For each open item, name the person who will obtain a product answer, correct a record or approve a test.
The sponsor can approve the phase, request more work or defer the move. Record the reason and the conditions for the next review. There is no universal three-wave plan or deadline for every Banner or Student deployment.

