º£½ÇÉçÇø

Where We Are Today

The Workday Student project has completed major system configurations and is wrapping up the current phase of end-to-end testing. Additional testing will continue through go-live as the team refines the system and prepares the campus for launch.

The project team is also advancing readiness by developing training resources and quick reference guides to support future users.

Our next major milestone is a student experience testing event on October 21, 2026. Student participation will play an important role in helping us validate key processes and gather feedback before launch. During this event, students will have the opportunity to explore activities such as viewing academic information, planning and registering for classes, and navigating important milestones in their academic journey through Workday.

Interested in helping shape the future student experience? Students can sign up to participate using the registration form here: .

Configuration Complete, Momentum Building Toward Testing

The Workday Student project has reached an exciting milestone—final system configuration is wrapping up, and the campus is now building momentum toward system testing beginning in June. Behind the scenes, teams across º£½ÇÉçÇø have been designing, configuring, and validating Workday Student with a shared focus on what matters most: reducing friction, improving clarity, and creating a more seamless experience for students, faculty, and staff.

Project team members are especially energized by what’s coming next. From streamlined self‑service processes that replace paper forms, to automated integrations that reduce manual work, to clearer, more accurate student data that supports better decision‑making, Workday Student is already showing its potential to better support students. Teams are also excited about new capabilities like real‑time prorated financial aid eligibility, improved degree planning and advising tools, robust reporting and analytics, and onboarding and journey features that help connect with students proactively throughout their academic experience.

As we prepare for End‑to‑End testing this summer, these configurations will be put into practice through real‑world scenarios that reflect the full student lifecycle. Testing is not just about validating the system—it’s about learning, refining, and ensuring Workday Student is ready to support º£½ÇÉçÇø’s phased transition beginning in early 2027.

Learn more about where we are in the most recent .

Change Freeze for Non-Essential Banner Updates

·¡´Ú´Ú±ð³¦³Ù¾±±¹±ð December 15, 2025 t³ó°ù´Ç³Ü²µ³ó March 1, 2028, Metropolitan State University of Denver will implement a change freeze on non-essential updates to Banner, our current student information system. During this period, changes involving new functionality, business process configurations, or data structure adjustments will be paused unless they are required for system stability, security, or compliance.

Why This Matters

The change freeze is an important step in the transition from Banner to Workday Student. By focusing resources on implementation, we reduce complexity in a system that is being retired and ensure a smooth migration to the new environment.

Impacts of the Freeze

Below are examples of changes that will now be restricted.

• New Data Fields or Codes
  • Adding a new student attribute or cohort (e.g., a new type of residency status or scholarship flag).
  • Creating new fields for reporting or compliance tracking.
• Business Process Changes
  • Modifying existing Banner workflows (e.g., Change of Grades or how approvals route).
  • Adding new steps to existing processes for departmental needs.
  • Modifying academic or other policies that require a customization in Banner.
• New Software Integrations
  • Connecting Banner to a new third-party tool (e.g., advising software, scheduling platform).
  • Automating data feeds between Banner and departmental systems.
• Custom Reports or Extracts
  • Building new Banner reports for analytics or other needs.
  • Adding new data points to existing extracts for external vendors.
• Configuration Updates
  • Changing security roles or permissions.
  • Updating validation tables or dropdown options.

What’s Still Allowed

• Mandated changes (e.g., state or federal compliance updates)
• Critical fixes (e.g., resolving errors that impact operations)
• Security patches