By Nicole Parker, Degree Works Consultant | David Kent Consulting
How academic policy and Banner data practices shape the student experience
Colleges and universities rely on Ellucian Degree Works to help students, advisors, and staff understand academic progress. The audit brings together program requirements, completed coursework, current registration, transfer credit, and student curriculum information in one place.
Because Degree Works presents the final result, it frequently receives the blame for anything that looks wrong. A requirement appears in an unexpected area. A concentration is missing. A course falls into electives. A student sees requirements from the wrong catalog year.
The audit configuration may need attention, but the source could also be the curriculum, academic policy, Banner data, or an established business practice. Degree Works sits at the point where all of those institutional decisions meet.
That makes the audit useful for more than tracking individual students. It can reveal where curriculum, data, and operational practices no longer align.
Curriculum Complexity Becomes Visible in the Degree Audit
Academic programs change over time. Departments add concentrations, electives, grade requirements, admission standards, residency rules, and special conditions. New requirements are introduced while continuing students remain under earlier catalog years.
Each change may make sense on its own. Together, those changes can produce a program that is difficult to explain and maintain.
Some programs require extensive Scribe logic because the catalog does not clearly explain how requirements interact. Others need several versions of nearly identical blocks to accommodate small differences between catalog years. Courses may qualify for multiple areas, creating competition among requirements. Students may regularly need substitutions because advising practices no longer match the approved curriculum.
Those situations deserve a broader conversation than how to revise the audit.
Curriculum committees and academic departments can use Degree Works to see how approved policies function in practice. A requirement that appears straightforward in a catalog may be difficult to apply consistently across hundreds of student records. A program structure that makes sense to those who created it may be confusing to students and advisors.
Frequent questions provide useful evidence. Students should be able to understand what they have completed and what remains. An audit that requires extensive explanation may point to unclear catalog language, inconsistent terminology, or a program structure that has accumulated too many layers.
Degree Works cannot determine the right curriculum for an institution. It can provide a practical view of how successfully that curriculum translates into an understandable academic path.
For a closer look at audit presentation and requirement logic, read Common Issues with Degree Works Audits Explained.
Ellucian Banner Data Determines the Student’s Starting Point
The curriculum defines the requirements, while Banner identifies the requirements associated with each student.
Degree, major, minor, concentration, college, level, campus, catalog term, and curriculum priority can all affect the audit. Student attributes, cohorts, course attributes, transfer information, repeat indicators, and other institutional values may also influence how coursework is evaluated.
The presence of a value does not guarantee that it is accurate or consistently maintained.
Catalog term is a strong example. Staff may view it as one field among many on the student record, but it can determine which version of the curriculum Degree Works applies. An incorrect catalog term may place a student under requirements that do not represent the institution’s intention.
Curriculum records present another challenge. A student may have multiple degrees, programs, majors, or fields of study. Old records may remain active, priorities may be inconsistent, or changes may be added without closing earlier curriculum records. The data can look understandable to an experienced Banner user while producing an unclear result in Degree Works.
Concentrations and minors create similar concerns. Some institutions track them consistently in Banner. Others maintain them in advising notes, spreadsheets, departmental systems, or informal communications. Degree Works needs a reliable Banner value to connect the student with the correct set of requirements.
The issue extends beyond student curriculum. Course attributes can determine which courses qualify for a requirement. Transfer articulation affects how external coursework reaches the audit. Repeat processing influences which attempts count. In-progress registrations shape the student’s current view of academic progress.
These Banner elements are maintained through different forms and business processes, sometimes by different offices. Clear data-entry expectations are essential because Degree Works applies the values it receives without the context an experienced employee may use to interpret them.
For more detail about the connection between the two systems, read our Accurate Banner Data: Key to Optimizing Degree Works article.
Misused and Unused Banner Fields Create Their Own Risks
Every institution develops local Banner practices. Some are intentional and well governed. Others emerged years ago to address an immediate need.
An office may use an available field to track information unrelated to its intended purpose. A department may maintain its own student list because the official record does not capture what it needs. Employees may leave certain fields blank because those values have never been required for their daily work.
These practices can continue unnoticed until the information is needed by Degree Works, reporting, advising, or another connected system.
A student attribute may help identify a population with distinct academic requirements. A course attribute may support a defined category of electives. A concentration code may connect a student with the correct curriculum. Consistent curriculum priorities may help present multiple programs more clearly.
This does not mean institutions should begin populating every available Banner field. Each field needs a defined purpose, an agreed-upon meaning, a responsible office, and a reliable maintenance process. More data does not create clarity when offices interpret it differently.
Repurposed fields create another concern. A Banner field may carry a local meaning that experienced employees recognize but connected systems do not. Reports, integrations, and degree audits interpret values according to established configurations. They do not have access to the institutional history behind a workaround.
Nonuse creates a different limitation. Information maintained in spreadsheets, advising notes, or departmental databases may never reach Degree Works. Staff members may know that a student belongs to a particular group, but the audit has no reliable way to recognize that distinction.
Banner data practices should be reviewed as institutional decisions rather than isolated data-entry habits. The review should consider how information moves across admissions, registration, advising, curriculum management, reporting, and Degree Works.
Repeated Degree Works Exceptions Point to Larger Questions
Exceptions are a necessary part of degree audit management. They document approved substitutions, waivers, and adjustments for individual students.
Patterns among those exceptions can reveal something larger.
Repeated substitutions may show that departments are recommending courses that are not included in the approved curriculum. Frequent waivers may suggest that a requirement no longer serves its original purpose. Exceptions used to address missing concentrations or incorrect catalog terms may expose gaps in Banner maintenance. Similar adjustments across many students may indicate that a one-time solution has become an unofficial policy.
These patterns connect individual student decisions with broader institutional operations.
A periodic exception review can help registrars and academic leaders identify requirements that generate recurring work. The goal is not to eliminate professional judgment or prevent appropriate flexibility. The purpose is to recognize where the institution is repeatedly solving the same problem one student at a time.
That information can support curriculum revision, policy clarification, Banner cleanup, advisor training, or a change to the Degree Works configuration. The source and scope of the pattern should guide the response.
Using Degree Works as Part of Strategic Curriculum Review
Degree Works can contribute useful evidence to program review, catalog development, data governance, and process improvement.
Institutions can begin by looking for patterns rather than isolated audit complaints:
- Programs that generate frequent questions
- Requirements that receive repeated exceptions
- Catalog language that leads to different interpretations
- Banner fields maintained inconsistently across offices
- Student populations tracked outside Banner
- Curriculum records that remain active beyond their intended use
- Audit logic that has grown increasingly complex
- Differences between approved policy and advising practice
The review should bring together the people who understand the curriculum, student record, system configuration, and advising experience. Each group sees a different part of the issue.
This broader perspective helps the institution choose the appropriate response. Some concerns belong in Scribe. Others require Banner data cleanup, clearer procedures, curriculum revision, or stronger communication among offices.
A regular system review can also help institutions identify these concerns before they become widespread. The Ellucian Degree Works Health Check: A 2026 Guide provides a practical starting point for evaluating configuration, data, security, integrations, and ongoing maintenance.
Greater Clarity Begins Upstream
Degree Works gives students and advisors a central place to review academic progress, but the quality of that experience begins long before the audit appears on the screen.
It begins with understandable curriculum, well-defined academic policies, accurate Banner records, consistent data practices, and coordinated processes.
A confusing audit creates an opportunity to examine how academic decisions are defined, recorded, communicated, and applied. The most effective solution may involve Degree Works, Banner, curriculum, policy, or a combination of those areas.
Viewed from that perspective, Degree Works can support clearer curriculum, better data practices, more consistent advising, and an academic path students can understand.
Key Takeaways
- Degree Works can expose curriculum that has become difficult to interpret, maintain, or explain, which makes the audit a practical source of evidence for curriculum review.
- Ellucian Banner fields and forms, including catalog term, curriculum records, and course and student attributes, directly influence which requirements students see and how their coursework applies.
- Unused, inconsistently maintained, or repurposed Banner data can reduce audit clarity, because Degree Works applies the values it receives without the institutional context behind them.
- Patterns in audit questions and exceptions can identify opportunities for curriculum, policy, and process improvement.
- The right response depends on the source of the pattern: some issues belong in Scribe, while others call for Banner Data cleanup, clearer procedures, or curriculum revisions.
Frequently Asked Questions: Degree Works
Ellucian Degree Works tracks a student’s program requirements alongside completed coursework, current registration, transfer credit, and the curriculum information stored in Ellucian Banner, including degree, major, minor, concentration, and catalog term. It compares those records with the requirements scribed for the student’s program and shows what is complete, in progress, and still needed. Because the audit applies whatever values Banner provides, it also reveals where curriculum records, course attributes, or student attributes are incomplete or inconsistently maintained.
The catalog year identifies which version of the academic catalog governs a student’s degree requirements. In Ellucian Banner, it is maintained as the catalog term on the student’s curriculum record, and Degree Works uses it to decide which set of requirements to apply. Continuing students often remain under earlier catalog years while new students follow updated requirements. An incorrect catalog term can place a student under requirements that do not reflect the institution’s intention, so catalog term accuracy belongs in every Banner data review.
No. A degree audit is an advising and planning tool, not a graduation certification. Degree Works reflects the requirements that have been scribed and the Banner data it receives, so its results depend on current requirement logic, accurate curriculum records, and properly documented exceptions. Final degree clearance is typically completed by the registrar’s office. When audits and final clearance frequently disagree, that gap deserves investigation as a curriculum, data, or configuration issue rather than a series of one-time errors.
No. A transcript is the official academic record of courses, grades, and credit earned. A degree audit applies that record to a specific set of program requirements to show progress toward a credential. The same academic history can produce different audits depending on the student’s major, concentration, and catalog year, which is why Degree Works results depend so heavily on the curriculum information maintained in Ellucian Banner. A Degree Works audit does not replace an official transcript.
Degree Works gives institutions evidence about how curriculum and data practices work in practice. Frequent advising questions, recurring exceptions, complex Scribe logic, and near-duplicate requirement blocks can point to unclear catalog language, outdated requirements, or inconsistent Ellucian Banner maintenance. Registrars, curriculum committees, and academic leaders can use those patterns during program review, catalog development, and data governance work to decide whether a fix belongs in Scribe, Banner, academic policy, or the curriculum itself.
About the Author
Nicole Parker, M.S., is a higher education consultant with David Kent Consulting. She has more than 15 years of experience working with Ellucian Banner Student and General and more than 10 years of registrar operations experience.
Nicole specializes in Degree Works, academic policy, curriculum management, student records, degree audit accuracy, and the functional processes connecting Banner with Degree Works. She helps colleges and universities align institutional requirements with system functionality, improve operational practices, and create clearer experiences for students, advisors, and staff.
About David Kent Consulting
David Kent Consulting helps colleges and universities strengthen Degree Works, Ellucian Banner, and the operational practices that support student success. Our consultants provide functional and technical support for assessments, implementations, upgrades, configuration, testing, data review, and process improvement.
Having served hundreds of colleges and universities, our team brings practitioner-level experience to work that connects curriculum, academic policy, student records, and degree audit accuracy.
