Why PGR Management Is Different

21st September 2026

At first glance, postgraduate research management can look like a collection of relatively straightforward processes.

Annual review. Progression. An interruption. An extension. A change of supervisor. Thesis submission. Examination.

Taken individually, none necessarily looks especially difficult to digitise.

The complexity appears when they interact.

A doctoral candidature is a journey, not a collection of workflows

Consider something as commonplace as an interruption of study.

Depending on an institution’s regulations, that interruption may change the researcher’s expected completion date, their next progression point, supervision requirements, funding position, engagement expectations and eventually their eligibility to submit their thesis.

Now add an extension. Or a subsequent change from full-time to part-time study. Or a change of supervisor.

And what if the university’s regulations have changed during the candidature?

Each individual process remains understandable. It is their interaction, over several years, that creates the real complexity.

A different kind of complexity

This is one of the important distinctions between postgraduate research management and other research-management systems.

A CRIS or RIMS faces complexity. It needs to create a reliable institutional picture of researchers, projects, funding, publications, impact and other scholarly activity, often bringing together information from numerous systems and sources.

PGR management has many of those same integration requirements, but introduces another dimension: the need to manage an individual’s changing state through time.

Dates, regulations, permissions, approvals, milestones and exceptions continually interact. Something that happens today can affect what should happen months or even years later.

That’s why we don’t think of PGR management simply as research workflow with students added.

It is a multi-year, regulated journey.

Flexibility alone isn’t the answer

It can be tempting to solve this complexity by making everything configurable.

But that risks transferring responsibility for understanding and maintaining the complexity from the software provider to the university.

Our experience has led us towards what we call controlled configurability.

Universities need considerable flexibility because policies, terminology and processes genuinely differ between institutions. But that flexibility can sit within a mature model of how postgraduate research actually works.

The objective isn’t to restrict what universities can do.

It’s to avoid requiring each university to become the designer of its own PGR management system.

The software should absorb the complexity

SkillsForge has spent many years learning which differences between institutions genuinely matter, which processes can sensibly be standardised, and how a change in one part of a candidature should propagate through everything that follows.

That accumulated domain knowledge matters just as much as the technology underneath it.

Because good PGR management software shouldn’t expose the complexity of doctoral administration to the people using it.

It should absorb it.