By Denise Kidd, Business Operations & Continuity Analyst, Office of the University Registrar, Tulane University
Graduation season is one of the most meaningful times of year in the registrar’s office. It’s also one of the busiest.
Even after conferral, the work isn’t quite finished. Many teams tie up loose ends, resolve exceptions, and ensure students are awarded accurately. The work is time-sensitive, highly visible, and deeply connected to the student experience.
It’s also a season when process lessons appear everywhere, which can show up as:
A repeated question from a department.
A handoff that almost worked, but not quite.
A manual step that caused avoidable rework.
A policy interpretation that needed clarity.
A communication gap that didn’t feel urgent in the moment but clearly needs attention before the next cycle.
The challenge is that graduation season is rarely the right time to stop and fix everything. When the volume and stakes are high, the immediate work has to come first. But if teams rely on memory alone, many of those valuable observations disappear before anyone has a chance to revisit them.
Two simple practices can help: an open-loop capture process during the cycle and a debrief survey after the cycle ends.
One gives the team a place to park important-but-not-urgent observations while the work is still underway. The other creates space to reflect, celebrate wins, identify opportunities for improvement, and decide what should change before the next cycle.
Together, they help registrar teams close the cycle without losing the lessons.
Creating a place for ‘important, but not right now’
During our most recent graduation cycle, our team implemented an open-loop capture system using a simple and short electronic form. The purpose was to give the team a place to park important observations that weren’t immediately actionable.
In other words: this matters, but not right now.
That distinction was important. During peak periods, every issue can start to feel urgent. But not every issue needs to interrupt the work in front of us. Some items need to be captured, protected, and reviewed when the team has more capacity to think clearly and make thoughtful changes.
The form gave us a shared place to identify those items as they surfaced. It allowed team members to quickly note process gaps, recurring questions, confusing handoffs, communication needs, or ideas for improvement without derailing the awarding work already underway.
It also reduced the risk of losing valuable insight to the pace of the season.
Pairing capture with reflection
The open-loop form was only one part of the routine. We also use a debrief survey after the cycle to help the team reflect more intentionally.
The debrief gives us space to do two things that are equally important: celebrate wins and identify opportunities for improvement.
That balance matters because post-cycle reflection shouldn’t become a list of everything that went wrong. Teams need to name what worked, which improvements paid off, and where people showed resilience under pressure. Those wins are a big part of the story, too.
At the same time, a debrief creates a structured way to ask:
What should we adjust before the next cycle?
What caused confusion?
What did we learn?
What needs a clearer owner, timeline, communication plan, or documented process?
Together, the open-loop forms and debrief survey support our continuous improvement cycle. One captures observations in real time, while the other helps the team reflect after the busiest work has passed.
Turning feedback into action
Collecting feedback is only useful if something happens with it.
After the cycle, our leadership team reviews the open-loop items and debrief responses to identify what can be improved before the next round of graduation processing. Some changes may be small: updating instructions, clarifying a communication, adjusting a checklist, or documenting a decision. Others may become larger process changes that need more discussion, coordination, or timing.
Not every issue can be fixed immediately. But capturing the issue gives it a place to live. It also allows leadership to look for patterns instead of relying only on the loudest problem or the most recent frustration.
That is where a simple routine becomes more than a form. It becomes a way of protecting institutional learning.
Questions other teams can use
For teams looking to try something similar, the process doesn’t need to be complicated. A short form, shared document, or standing debrief agenda can work. The tool matters less than the habit.
A few useful prompts include:
What issue came up repeatedly during this cycle?
What caused avoidable rework?
What question did we answer more than once?
What worked better than expected?
What should we clarify, document, or revisit before the next cycle?
What should we celebrate?
These questions help teams move from hazy recollection to practical next steps.
A small routine with a big purpose
High-volume seasons in the registrar’s office aren’t only periods to survive. They’re also some of the richest sources of process intelligence we have.
The key is creating a routine that lets the team stay focused on urgent work while still preserving the lessons that surface along the way.
An open-loop process gives those ideas a safe place to land.
A debrief gives the team space to make meaning from them.
Leadership follow-through turns them into improvements.
Graduation work will always involve complexity, deadlines, and unexpected issues. But when teams build simple habits for capturing and reviewing what they learn, each cycle becomes more than a finish line.
It becomes preparation for the next one.
share