Rethinking the Registrar: A Statewide Shared-Services Model for Public Higher Education

By Whitney Merinar, Ed.S., Registrar, and Jim Temple, Director of Graduate Studies, West Liberty University

For decades, public universities have operated registrar offices in much the same way. Each institution maintains its own registrar, staff, processes, technology responsibilities, records operations, and administrative infrastructure. That structure made sense when universities functioned more independently, and academic records were largely campus-based. Higher education no longer operates that way.

Public university systems are facing financial pressure, changing enrollment patterns, increasing regulatory requirements, rising technology costs, and persistent staffing challenges. Students also expect faster and more seamless service. Yet institutions within the same state system often continue to perform essentially the same registrar functions separately.

That raises a basic question: Does every public university within a state system need a completely independent registrar operation?

A statewide shared-services model could reduce administrative duplication, improve data quality, strengthen compliance, provide greater staffing depth, and improve student service without removing registrar expertise from individual campuses.

A Different Organizational Model

Rather than maintaining a separate registrar infrastructure at every institution, a state university system could establish a System Registrar’s Office led by a State or System University Registrar. Individual campuses would retain an Associate or Assistant Registrar as the senior registrar professional on campus. That person would understand the institution’s curriculum, faculty, students, policies, and culture and serve as the primary connection between the university and the system operation. The distinction matters.

The goal would not be to eliminate the campus registrar function. It would be to separate work that benefits from being close to the institution from work that does not need to be duplicated at every campus. A System Registrar’s Office could handle transcript processing, enrollment and degree verification, systemwide reporting, records-retention standards, FERPA guidance, technology administration, data standards, training, common forms and workflows, and selected high-volume records processing.

Campus registrar leaders would remain responsible for work requiring institutional knowledge and relationships: faculty support, policy interpretation, curriculum implementation, commencement, unusual student cases, academic calendars, and communication with campus leadership. The system office would provide scale, infrastructure, specialized expertise, and processing capacity. Campus registrars would provide context, judgment, relationships, and institutional knowledge.

The Financial Argument

Cost is an obvious consideration. Consider a state system with ten universities. Under the traditional model, each university may maintain staff responsible for transcripts, verifications, degree audits, reporting, technology, records processing, compliance, and related functions.

That creates ten versions of many of the same processes.

Centralization would not eliminate the need for people doing registrar work. It could, however, reduce duplication and allow employees to specialize. A centralized records team could handle routine transactions. Compliance specialists could support FERPA and records-retention requirements. A technology team could support the student information system, degree-audit platform, electronic forms, and integrations. Reporting specialists could coordinate recurring state and federal requirements.

The savings could extend beyond personnel. Systems may also be able to reduce duplicated software contracts, consulting expenses, training, technology support, document-management systems, and vendor relationships.

The objective should not simply be fewer employees. It should be making better use of limited higher-education resources.

Greater Capacity Through Specialization

Capacity may be as important as cost. Many registrar offices, particularly at smaller institutions, operate with very small staffs. A retirement, resignation, illness, or extended vacancy can quickly become an operational problem. In some cases, critical knowledge about a process resides with one employee.

A statewide operation provides depth. Instead of one employee at one university being the only person who understands a particular process, a system could maintain teams of specialists serving multiple campuses. Work could also be redistributed during peak periods. If one university faces an unusually heavy graduation cycle, system resources could be shifted temporarily rather than relying entirely on already stretched campus staff. The registrar operation becomes less dependent on individual employees and more dependent on sustainable processes.

Standardization Without Eliminating Institutional Identity

A reasonable concern about centralization is that it could force every university to operate the same way. It should not. Universities have different missions, curricula, governance structures, calendars, student populations, and traditions. A research university does not necessarily need to administer every academic process in the same way as a regional institution.

A successful statewide model must therefore distinguish between standardization and uniformity.

Standardization makes sense in areas such as data definitions, security, records retention, common technology, compliance, reporting, documentation, training, and routine transactions.

Institutional autonomy should remain where differences matter academically: curriculum, faculty governance, academic policy, exceptions, commencement, academic calendars where appropriate, and institution-specific student support.

The goal is not to make universities identical. It is to stop requiring every university to independently build the administrative machinery needed to accomplish many of the same fundamental tasks.

The Technology Is Already Moving in This Direction

There is another reason this model deserves consideration. Many public higher-education systems already mandate or are moving toward common enterprise platforms across their constituent institutions. Once institutions operate within a common technological ecosystem, maintaining completely separate administrative structures and repositories becomes increasingly difficult to justify. This is already happening.

The University System of Georgia (USG) is implementing a Unified Enterprise Resource Planning initiative intended to replace separate institutional legacy applications with a common cloud-based platform. Its guiding principles state that all institutions will use the selected ERP solution and that business processes and configurations should be standardized where practical (University System of Georgia, n.d.-b).

What makes Georgia especially relevant is that standardization does not require institutions to surrender their identities. USG institutions can operate in the same Workday environment while retaining their individual missions, programs, and institution-specific information (University System of Georgia, n.d.-a).

Minnesota State offers an example even closer to registrar operations. Its NextGen initiative is moving the system toward a unified environment connecting human resources, finance, and student systems. Workday Student will replace the existing Integrated Statewide Record System and support functions that include registration, student records, grading, graduation, and transcripts. Minnesota State also identifies greater systemwide policy and process alignment as a benefit of the new environment (Minnesota State, n.d.).

The California State University system is moving along a similar path. San Diego State University describes its Common Management Systems transition as a mandatory move to enterprise systems shared across CSU universities, bringing financial, human resources, and student operations onto common platforms (San Diego State University, 2026).

These examples change the nature of the discussion. If universities within a system already operate on common enterprise platforms, the question is no longer whether technology can support shared administrative services. In many systems, that technological foundation already exists or is being built.

Enterprise systems are intended to do exactly this kind of work. Seidl and Norin (2023) describe one of the central purposes of ERP systems in higher education as bringing separate systems, tools, and processes together into a central solution that improves standardization and access to information.

That leads to a harder question: If the technology is centralized, why must every administrative process built on it remain decentralized? Take academic records. If institutions share a student information platform, common data definitions, security standards, reporting structures, and workflows, maintaining separate technology administration and records-processing structures at every campus may simply layer organizational duplication on top of technological standardization.

A central records repository becomes much more practical in that environment. Rather than maintaining multiple versions of records processes, reporting logic, integrations, documentation, and technical expertise, a system could establish an authoritative records infrastructure with common governance, retention standards, security protocols, quality controls, and reporting definitions.

None of this requires universities to surrender control over academic decisions. Institutions should determine their curricula. Faculty should govern academic programs. Universities should establish policies appropriate to their missions. But the infrastructure that records, preserves, processes, verifies, and reports those decisions does not necessarily need to be recreated at every campus. Public systems may otherwise find themselves operating centralized technology while maintaining decentralized administrative structures designed for an earlier era. That contradiction deserves attention.

Better Data and Stronger Compliance

Registrar offices maintain some of the most important information held by a university: enrollment histories, grades, degrees, academic standing, curriculum records, demographic information, and historical academic records.

When institutions maintain different definitions, procedures, coding practices, and reporting methods, inconsistencies are likely.

A System Registrar could establish common data definitions, documentation standards, records-management practices, audit procedures, and quality controls. Statewide reporting could become more reliable while individual institutions would have less need to interpret the same requirements independently.

The move toward common enterprise systems strengthens that possibility. USG identifies accurate, reliable, and timely information as one of the goals of placing institutions on a common application (University System of Georgia, n.d.-b). Minnesota State similarly points to improved analytics, consistency, and systemwide alignment as benefits of its unified platform (Minnesota State, n.d.).

Compliance expertise could also be shared. Every small registrar office should not necessarily have to independently maintain deep expertise in FERPA, records retention, enrollment reporting, accreditation requirements, NCAA-related records issues where applicable, and changing state and federal requirements. A system could maintain that expertise and make it available to every institution.

Creating a Better Student Experience

Students increasingly move between institutions. They transfer credits, take online courses, participate in consortia, stop out and return, and pursue credentials from multiple institutions. Administrative structures, however, often remain institution-centered.

A statewide registrar operation could support a more portable academic record. Transfers within a system could become easier. Transcript exchange could be faster. Course information and equivalencies could be maintained more consistently. Students attending more than one system institution could interact with a common records infrastructure rather than learning entirely different processes at each campus.

Minnesota State’s implementation of Workday Student illustrates the possibilities. Its unified environment connects functions across the student lifecycle, including registration, academic progress, graduation, and transcripts (Minnesota State, n.d.). The boundaries between universities could become less administratively burdensome without becoming less academically meaningful.

What Should Remain on Campus?

Centralization should not mean removing registrar expertise from universities.

The campus Associate or Assistant Registrar would remain an important institutional leader, working directly with faculty, students, advisors, athletics, financial aid, enrollment management, academic leadership, and other campus offices.

Complex academic decisions should remain close to the institution. Faculty relationships should remain local. Policy interpretation should involve campus leadership. Students facing unusual circumstances should have access to someone who understands their university rather than only a remote service center. Technology can centralize transactions. It cannot replace institutional judgment.

A Hub-and-Spoke Model

The result would resemble a hub-and-spoke organization. At the hub would be the System Registrar and teams responsible for shared technology, records processing, compliance, reporting, data governance, training, and operational support.

At each spoke would be a campus registrar leader responsible for institutional relationships, policy implementation, complex cases, faculty support, and campus-specific needs.

The model attempts to combine the efficiency of a large organization with the responsiveness of a local one. Common enterprise platforms make this increasingly realistic. In some systems, the technological hub is already being built. The next question is how much of the administrative structure surrounding it should follow.

The Challenges Cannot Be Ignored

Institutions may resist losing perceived autonomy. Collective bargaining agreements, personnel classifications, governance structures, accreditation requirements, state law, and existing technology would all have to be considered.

Technology is particularly important. Centralizing employees while maintaining incompatible systems could simply move inefficiency from one location to another. But the reverse is also true. Implementing common technology without examining the organizations operating it can leave a system paying for integration while continuing to support unnecessary administrative duplication.

Governance would matter as well. Campus registrar professionals would need a meaningful role in system decisions. Service expectations, escalation procedures, and processes for requesting changes would have to be clear. A central records repository would also require explicit rules for ownership, access, security, retention, auditing, disaster recovery, and authority to modify records.

Most importantly, this should not become a headcount-reduction exercise primarily. If the only objective is eliminating positions, a system could simply create a distant bureaucracy that provides worse service at lower cost. The better question is: Which registrar functions gain value by being performed once for the system, and which gain value by remaining close to the campus? That question should drive the design.

An Opportunity Worth Exploring

Higher education spends considerable time discussing innovation in teaching, student success, technology, and academic programming. We should be equally willing to examine the administrative structures supporting them. The decentralized registrar model has served higher education well for decades. Longevity, however, is not by itself a reason to preserve an organizational structure.

Public university systems already exist because states recognize that institutions can gain value through coordination. Shared services simply extend that idea by asking where universities can pool expertise and resources without sacrificing institutional identity.

Registrar operations may be particularly well suited to that conversation.

Academic records are digital. Compliance obligations cross institutional boundaries. Students move among institutions. Specialized employees are difficult to replace. At the same time, public systems are investing in common enterprise technology.

Georgia, Minnesota, and California show that systemwide administrative technology is no longer hypothetical. Systems are building common platforms intended to reduce fragmentation, improve data, standardize appropriate processes, and increase efficiency.

It makes sense to ask whether the organizational structures sitting on top of those platforms should evolve as well.

A statewide registrar shared-services model would not work for every system, and not every registrar responsibility belongs at the system level. But the concept deserves serious consideration. Perhaps the registrar office of the future is neither completely centralized nor completely decentralized. Perhaps it is a network: one systemwide operation providing scale, expertise, technology, data infrastructure, and consistency, connected to experienced registrar leaders embedded at individual institutions.

The question is no longer simply whether centralization can save money. The better question is whether we can build a registrar structure that is less expensive to operate, more resilient when staffing changes occur, better at managing data and risk, able to take advantage of technology systems are already purchasing, and ultimately easier for students to navigate.

If we can, public higher education should be willing to have that conversation.