How to Cut "Why Isn't This Counting?" Tickets in Your Advising Office

Degree audit not counting a course? Learn the root causes behind these advising tickets and the operational fixes registrars and advising offices can make.

Every advising office knows the ticket. A student sends a screenshot of their degree audit with a requirement still showing red, and underneath it a course they're sure should have filled it. Sometimes they're right, sometimes they aren't, and either way someone on your team ends up tracing the answer through the student record, an email thread, and last year's catalog.

Here's the reality: when a degree audit is not counting a course, the cause usually comes down to one of a short list of operational issues. The student may be on the wrong catalog year, an approved exception may never have been encoded, a transfer equivalency may still be unmapped, a double-counting rule may be doing exactly what it was written to do, or the audit may simply be looking at stale data. Each of those has a fix that lives upstream of the advising appointment. This guide walks through them from the office's side of the desk, for advising directors and registrars who want fewer of these tickets reaching the queue in the first place.

Tag every "not counting" ticket by root cause

You can't shrink a queue you can't see into. Before changing any process, spend a term tagging each audit question with the cause that resolved it. A simple set of tags works fine: catalog year, unrecorded exception, transfer equivalency, rule behavior, data timing, and "student misread the audit."

That last tag matters more than it looks. If a large share of your tickets end with an advisor explaining that the audit was correct all along, your problem is readability, and no amount of data cleanup will fix it. If the tickets cluster around exceptions or transfer work, the fix sits with whoever owns encoding and evaluation.

Review the tags with the registrar's office monthly. The goal is a shared picture of where the friction comes from, which makes it much easier to agree on which upstream process to repair first.

Catalog year assignments that drift

A student who changes majors, adds a minor, or returns after stopping out can end up evaluated against requirements they were never supposed to follow. The audit then reports gaps that don't exist, or misses ones that do, and the student has no way to know why.

Catalog year problems usually trace back to policy. Most offices have a written rule for whether a major change moves the student to the current catalog and whether a returning student gets to choose, but the rule often says less about who updates the record and when. If those answers live in a policy document and never make it into a workflow, assignments drift.

The operational fix is to make catalog year changes a deliberate, logged step tied to the transaction that triggers them, such as a change-of-major form, with the update made at the same moment the change is approved. It also helps to show the active catalog year prominently on the audit itself, so both students and advisors can spot a mismatch in seconds. Our student-facing guide on why a degree audit shows missing requirements covers how this looks from the student's side, and it's a useful link to send when the answer is "you're on a different catalog year."

Exceptions approved in email but never encoded

This is the cause advisors find most frustrating, because the hard part already happened. A department chair approved a substitution, the student has the email, and the audit still shows the requirement unmet. Approval and recording are often separate steps owned by separate people, and the handoff between them is where exceptions disappear.

Close that gap by treating an approval as incomplete until it's encoded. A few practical changes help:

  • Route every substitution and waiver through one intake form instead of email, so nothing is approved outside the system.
  • Make encoding part of the approval workflow, with a named owner and a target turnaround.
  • Hold the notice to the student and their advisor until the exception shows up on the audit.

That last point sets a clear expectation. Students stop filing tickets about exceptions that are approved but still in the encoding queue, because they know the audit will update and they'll hear about it when it does. For more on how exceptions move through approval, see our guide to course substitutions and waivers.

Transfer equivalencies waiting in the queue

Transfer credit generates a steady stream of "not counting" tickets, and most of them have the same shape. The course posted to the record, but it posted as a general elective because no one has mapped it to a specific equivalent yet. To the student, it looks like the credit vanished.

Two operational habits reduce this load considerably. The first is building and maintaining a shared equivalency table for courses you see repeatedly from your feeder institutions, so the same evaluation doesn't happen from scratch every term. The second is making pending status visible. If the audit labels a transfer course as "under evaluation" while it sits in electives, the student knows the review is still underway and can wait for it. It also helps to give advisors visibility into the evaluation queue, so they aren't forwarding tickets they can't answer. Our article on transfer credit evaluation goes deeper on building a sustainable process.

Double-counting rules students can't see

Some tickets come from an audit working as designed. A course that could satisfy both a major requirement and a general education requirement may only be allowed to count once, or the audit may place it where it's most efficient for the student's overall progress. Both are reasonable, and both look like errors to a student who expected the course to count in two places.

The fix here is transparency. Write your double-counting and sharing rules in plain language and make them visible near the requirements they affect. Where your audit tool allows it, show students why a course landed where it did and what else it could have satisfied.

A what-if scenario is another strong deflector. When students can test a different major, minor, or course placement themselves, many of the questions that would have become tickets get answered in the audit. Our explainer on how a degree audit decides where courses count is written for exactly this conversation.

Data sync and timing gaps

Finally, some tickets are just about timing. A grade posted this morning, a repeat course was processed yesterday, or a registration change hasn't flowed from the student information system to the audit yet. The student sees an outdated picture and assumes something is broken.

Start by documenting how often your audit refreshes from the SIS and what events trigger an update. Then put that information where students and advisors will see it, ideally with a "last updated" timestamp on the audit. Publish a short note before high-volume moments, such as the end of grading or the start of registration, explaining when audits will reflect new grades. A simple expectation set ahead of time heads off a lot of identical questions. And if your integration can fail silently, set up an alert, because a stalled sync generates tickets for every student it touches.

Fewer tickets start with a clearer audit

Every one of these fixes points in the same direction. When the audit reflects decisions as soon as they're made and explains itself in language students understand, most "why isn't this counting?" questions never get written. That frees your advisors for the conversations only they can have, the ones about what a student wants and how they'll get to graduation.

That kind of clarity doesn't happen by accident. It takes clean upstream processes and an audit built to be read by students as well as staff. If you'd like to see how Stellic's degree audit and planning tools give advisors and students an audit that explains itself, including what-if scenarios, we'd be glad to show you around.


A better path to graduation starts here

Smiling graduate student