When Scale Changes the Problem: rethinking PGR management in universities
5th October 2026
Universities have not ignored the complexity of postgraduate research management. Quite the opposite. Many have invested substantial time, money and institutional knowledge in solving it.
What is interesting is how differently they have solved the same underlying problem.
Some institutions have assembled the PGR journey across several systems, combining student records, researcher development, progression, document services and locally managed processes.
Others have built dedicated PGR systems around their own institutional requirements.
A third approach has been to progressively extend the enterprise student record system until it performs increasingly specialist PGR functions.
All three approaches can work. That is precisely why we believe the strategic question has changed. It is no longer simply:
Can our current approach manage PGR?
It is:
What must the university continually spend — in money, people, integration, development, administration, reconciliation and user attention — to keep it working?
System of record is not the same as system of process
One of the most important distinctions explored in our new white paper is between the system of record and the system of process.
A system of record answers a governance question:
Where is the authoritative institutional record of a particular fact held?
A system of process answers a different question:
Where is the specialist activity that creates or changes that fact best managed?
And for postgraduate research, we believe there is a third consideration:
PGR domain intelligence — what does that change mean to the rest of the candidature, and what should happen next?
These responsibilities can exist in the same system, but they do not have to.
A student record system can remain authoritative for core institutional data without necessarily being the best place to perform every specialist process that creates or changes that data.
This distinction matters because PGR management is not simply a collection of workflows.
An interruption, extension, study-mode change or examination outcome does not just move a form from one person to another. It can change dates, future obligations, progression requirements, reporting, supervision and what different participants should see next.
Anyone can provide a workflow. The challenge is understanding what that workflow means to the rest of the candidature.
Or, put another way:
Records tell you what is true. Process manages what is happening. Domain intelligence understands what it means.
When people become the integration layer
There is also a human cost to fragmented architecture.
When the PGR journey spans multiple systems, researchers learn which system they need for which task. Supervisors navigate different interfaces. Administrators explain hand-offs, reconcile records and resolve exceptions.
At that point, the user becomes part of the integration.
Universities will always need skilled professional staff to interpret policy, exercise judgement, support researchers and supervisors, and manage genuine exceptions.
But their expertise is less well used moving information between systems, maintaining spreadsheets, reconciling records or remembering how complex technical processes fit together.
The objective is not fewer people.
It is enabling university people to spend more of their time managing and improving the doctoral process rather than managing the machinery underneath it.
The architecture becomes the user experience
This matters increasingly because expectations have changed.
Researchers and academics routinely encounter sophisticated digital banking, travel, retail and government services that hide considerable back-end complexity.
Those expectations do not disappear when somebody enters a university.
A technically defensible architecture can therefore still produce a poor PGR experience if its complexity is repeatedly exposed to the people using it.
For a large research-intensive university, seemingly small friction is multiplied across thousands of researchers, supervisors, examiners and administrators.
The market has moved on
None of this means universities made poor technology decisions. They solved a genuinely difficult problem with the technology and choices available to them. But specialist PGR platforms have matured.
The opportunity now is to reconsider the boundary between what the university genuinely needs to own and what a mature specialist platform can absorb.
The student record can remain the system of record.
A specialist PGR platform can become the system of process.
And the domain knowledge within that platform can provide the PGR lifecycle intelligence that understands what should happen next.
System of record. System of process. PGR domain intelligence.
Our latest white paper, When Scale Changes the Problem, explores what that distinction means for universities — and asks a deceptively simple question:
You solved a genuinely difficult problem. Do you still need to solve it yourself?
Read the full white paper: When Scale Changes the Problem.