PhDs

PhD admissions software for complex doctoral journeys

PhD applicants rarely move through a simple admissions funnel. They may start with a research idea, a supervisor conversation, a funded project, an international enquiry, or a doctoral school pathway. Full Fabric helps institutions manage the full doctoral journey from first enquiry to application, proposal collection, academic review, offer, enrolment, student record, and reporting.

Full Fabric supports the operational layer around doctoral recruitment and admissions. It is not a research management system, supervision platform, LMS, or thesis submission tool.

Explore the platform →
Trusted by IT and leadership teams at 65+ institutions
Top business schools, universities, and conservatoires across Europe and beyond.
…and more

The operating model

PhD programmes need a different operating model

Doctoral recruitment works differently from undergraduate admissions, masters admissions, short courses, and executive education. There are often fewer applicants, but each one carries far more complexity: a research proposal, supervisor fit context, references and transcripts, eligibility checks, funding context, and academic review across several people. Data tends to sit across CRM, application forms, spreadsheets, supervisor emails, document inboxes, research systems, finance, and a student record system, which makes the full doctoral journey hard to see.

01.

Fewer applicants, higher complexity

A doctoral programme may attract fewer applicants than a large taught course, yet each application involves a proposal, references, eligibility, and review. Volume is lower, but the work per applicant is much greater.

02.

Research fit and supervisor capacity

Research area alignment and supervisor availability matter as much as formal eligibility. Admissions teams need to see research alignment and supervisor capacity context alongside the applicant, not in a separate inbox.

03.

Proposals, documents, and eligibility

Research proposals, transcripts, references, and qualification checks all feed the decision. When they arrive through different channels, the applicant record is scattered before review even begins.

04.

Many routes and reviewers in

Applicants enter through advertised projects, self-proposed topics, doctoral schools, departments, funded routes, or open enquiries. Review may need supervisor, department, school, doctoral college, or central admissions input.

05.

Funding context and offer conditions

Funded projects, studentships, and departmental funding routes shape whether an offer can be made, on what conditions, and to what timeline. Funding context needs to sit next to the applicant, not apart from it.

06.

Doctoral visibility and governance

Leadership needs visibility by department, research area, project, supervisor, funding route, offer, acceptance, and enrolment. Fragmented systems turn that into slow, manual reconciliation.

Non-linear by design

PhD admissions is not a simple funnel

A clean funnel assumes one application, one decision, and one straight line to enrolment. Real doctoral journeys rarely move that way. An applicant might respond to an advertised project, submit an expression of interest, apply, interview, and wait on a funding decision. Another proposes their own topic, opens a supervisor conversation, refines a proposal, then applies. An international enquiry may run through eligibility checks and proposal review against time-sensitive visa-related milestones, and a doctoral school pathway may route through department review and supervisor input before a central decision. Some applicants defer to a future intake and return later.

When systems are fragmented, that path is hard to follow. CRM sees the enquiry, the application portal sees the form, supervisors see emails, proposals, and documents, reviewers see decisions, funding teams hold funding context, and the student record system sees enrolment. Reporting teams then reconstruct the journey by hand, and doctoral schools or departments lack a live view of applicant and offer-holder status.

A connected applicant-to-researcher journey keeps the whole path visible: many routes in, several reviewers, and one shared history the institution can see and act on.

Illustrative interface. Actual routes and stages are configured to match each institution's doctoral programmes and admissions process.

The platform layer

A connected platform for PhD recruitment and admissions

Full Fabric is the operational layer around doctoral recruitment, admissions, and enrolment. It is not an LMS and does not deliver course content, and it is not a research management, supervision, or thesis submission system. Rather than replacing every surrounding tool, it can consolidate key workflows or connect with systems an institution already uses, so the journey stays continuous from first enquiry to enrolled researcher.

Relationship management Application management Online portal Enrolment Student records Dashboards AI Integrations
CRM and researcher relationships
Enquiries, sources and campaigns, research and project interest, segmentation, and follow-up.
Applications and portal
Programme-specific and project-specific application forms through an applicant portal.
Research proposal collection
Collect proposals and supporting material against the applicant record, ready for review.
Documents and eligibility
Transcripts, references, and qualification checks collected and tracked in one place.
Supervisor and academic review
Route applications for review with proposal and documents attached; capture decisions and conditions.
Offers and enrolment
Offer conditions, offer-holder communication, and enrolment steps into the student record.
Student records (SIS)
A continuous record from enquiry to enrolled researcher, held in one place over time.
AI, integrations, governance
Automation, natural-language questions, connectors, role-based access, and audit.

See the platform overview. Funding context, payment or deposit status, and research-system data are surfaced only where relevant to doctoral admissions.

Use cases

Built around how doctoral teams actually work

Doctoral recruitment spans research areas, projects, supervisors, funding routes, and international markets, with staged and often rolling decisions. Full Fabric is designed for the realities of running PhD admissions, not for a single neat applicant funnel.

Doctoral recruitment and CRM

Operational problem

Enquiries about research areas, advertised projects, events, and webinars arrive in different tools, so source tracking and prospective researcher nurturing are hard to run consistently.

How Full Fabric helps

Capture enquiries with source and campaign tracking, record research and project interest, segment audiences, and run follow-up against one contact record with relationship management.

What teams gain

A clear view of where prospective researchers come from and consistent nurturing that carries into the application.

Online PhD applications

Operational problem

Programmes and projects need different forms and documents, and applicants lose track of proposals and outstanding items across separate portals and inboxes.

How Full Fabric helps

Run programme-specific or project-specific forms, research proposal collection, and document collection through an online application portal, with clear status visibility for applicant and staff.

What teams gain

Cleaner applications, fewer chasing emails, and a shared view of where each application and proposal stands.

Supervisor and academic review

Operational problem

Supervisor fit, proposal review, eligibility, and academic review happen over email and shared drives, separated from the applicant record and from each other.

How Full Fabric helps

Route applications for review with the proposal and documents attached, capture supervisor and academic review context, decisions, and offer conditions, and keep everything on the same record.

What teams gain

Better-documented decisions and reviewers who see supervisor fit and applicant context without leaving the record.

Funding context and offers

Operational problem

Funded project context, studentship details, and offer conditions live apart from the applicant, so offer holders slip through the gap between decision and enrolment.

How Full Fabric helps

Hold funded project and studentship context alongside the applicant where relevant, manage offer-holder communication, offer status and conditions, and enrolment steps.

What teams gain

Fewer offer holders lost to friction and a continuous record as applicants become enrolled researchers.

International doctoral admissions

Operational problem

International applicants bring more documentation, credential checks, and time-sensitive milestones, spread across teams and markets that struggle to stay aligned.

How Full Fabric helps

Track documents and timelines against each applicant, see demand by market and region, and coordinate time-sensitive communications around visa-related milestones across teams.

What teams gain

Better-supported international applicants and clearer coordination on the timelines that decide whether an offer converts.

Doctoral reporting and visibility

Operational problem

Leadership wants demand and conversion by research area, department, and funded route, but reporting depends on exports reconciled by hand across disconnected tools.

How Full Fabric helps

Report across department, school, research area, project, supervisor, funding route, source, application, review, offer, acceptance, and enrolment from live data. See dashboards and reporting.

What teams gain

Workload, decision, and demand visibility for doctoral schools, departments, and leadership, without manual reconciliation.

Applicant-to-researcher continuity

One record, from enquiry to enrolled researcher

Doctoral admissions asks a lot of coordination across prospective researchers, supervisors, departments, doctoral schools, central admissions, funding teams, registry, and reporting. The applicant experiences one journey from enquiry to proposal, application, review, offer, and enrolment. Internally, each team needs its own view of the same person without losing the shared context.

Supervisor and academic review need to happen without losing applicant context, and proposals, references, documents, funding context, offers, and enrolment steps all need to stay connected. When the applicant becomes an enrolled doctoral researcher, the relationship should not reset. A connected applicant-to-researcher record helps teams avoid duplicate data entry and manual handoffs, so the history recruitment and admissions built up carries straight into the student record.

One continuous record means every team, from first enquiry to registry, is working from the same relationship history rather than rebuilding it at each stage.

Illustrative interface. Configured to match each institution's doctoral programmes, stages, and review workflows.

Data and reporting

See demand and conversion across doctoral programmes

Doctoral teams need reporting across department, school, programme, research area, project, supervisor, funding route, source, market, nationality, application status, review status, offer, acceptance, and enrolment. Leadership needs visibility into demand and conversion by research area, department, or funded route. Doctoral schools need applicant, offer-holder, and enrolment visibility, admissions teams need workload and decision visibility, and supervisors or departments need review and capacity context where appropriate. Funding teams may need visibility into funded routes or scholarship context where relevant.

When systems are fragmented, reporting is slow and unreliable. A connected platform helps teams move from manual reconciliation to live operational visibility. See dashboards and reporting.

Illustrative interface. Actual dashboards are configured to match each institution's doctoral programmes and reporting needs; labels shown are examples only.

AI and automation

AI that supports doctoral admissions teams, not replaces them

Doctoral admissions involves a lot of repeatable work: enquiry follow-up, proposal and document reminders, application reminders, review routing, supervisor and academic reviewer follow-up, offer-holder communication, and enrolment reminders where relevant. Full Fabric uses AI and automation to reduce that load while keeping people in control. Staff decide what runs, when, and on whose behalf.

Admissions automation handles repeatable workflows, status updates, and reminders. AI in the platform helps staff ask natural-language questions of their own data: about applicants, projects, supervisors, research areas, offers, funding context, and enrolment.

Responsible use: AI supports staff decisions and operational workflows. It does not replace academic judgement, supervisor assessment, admissions criteria, funding decisions, or applicant support. Sensitive actions stay with people.

Integrations, funding, security

Connected, governed, and built for higher education

PhD admissions rarely operates in isolation. Institutions need Full Fabric to work alongside a student information system, CRM, marketing automation, finance, research systems, document systems, identity, and BI or reporting tools. The aim is to clarify the source of truth, not to add new fragmentation. Explore the integrations ecosystem.

Funding context can matter for doctoral admissions, especially where funded projects, studentships, or departmental funding routes are involved, and payment or deposit status is surfaced only where it is relevant. Security, role-based access, auditability, and data governance matter because applicant data, research proposals, supervisor comments, academic review information, and student records may cross many teams. Compliance remains a shared responsibility between platform and institution. See security and GDPR-aligned operations and GDPR in higher education.

Role-based access across recruitment, admissions, supervisors, academic reviewers, funding teams, registry, IT, and reporting.
Audit and history so changes to applicant, proposal, review, offer, and student records can be reviewed over time.
GDPR-aligned operations built around applicant, research, and student data, with compliance as a shared responsibility.
Enterprise connectors for institutions running Salesforce, HubSpot, or Microsoft Dynamics alongside Full Fabric.

Who it is for

Built for the teams that run doctoral admissions

Full Fabric is designed for the teams that share responsibility for the doctoral journey: strategic leaders, recruitment and admissions specialists, supervisors and academic reviewers, and the people who keep the data and systems in good order.

Doctoral admissions teams

Applications, proposals, documents, review, decisions, and offers across programmes.

Postgraduate research admissions

Research-led applications, eligibility, and staged or rolling decisions.

Graduate schools and doctoral colleges

Applicant, offer-holder, and enrolment visibility across departments and routes.

Research degree administrators

Proposal, document, reference, and review coordination on one record.

Supervisors and academic reviewers

Supervisor fit, proposal review, and decisions with full applicant context.

Heads of department

Demand, capacity, and offer visibility by research area and project.

International recruitment teams

Market and region demand, documentation, and visa-sensitive timelines.

CRM and marketing teams

Source attribution, segmentation, campaigns, and prospective researcher nurturing.

Registry and student records

Enrolment continuity and a clean handoff from applicant to enrolled researcher.

Funding and scholarships teams

Funded route and studentship context alongside applicants, where relevant.

IT and integrations teams

SIS, CRM, finance, identity, and BI connections with clear ownership.

Institutional leadership

Demand, conversion, and a strategic view of the doctoral portfolio.

Implementation

An operating model design exercise, not just a software install

Building doctoral admissions on a connected platform takes planning. The institutions that get the most value treat implementation as a chance to clarify the doctoral applicant journey, lifecycle stages, entry routes, proposal and review requirements, funding context, reporting needs, and the boundary between CRM and student records.

PHASE 01Map the doctoral applicant journey
PHASE 02Define lifecycle stages, enquiry to enrolled researcher
PHASE 03Model routes: projects, self-proposed, doctoral schools, funded
PHASE 04Define proposal, document, eligibility, and review requirements
PHASE 05Design supervisor and academic review workflows
PHASE 06Model funding context and offer conditions
PHASE 07Clean applicant data and plan integrations
PHASE 08Phased rollout and governance after go-live

Decide how open PhD applications, advertised projects, doctoral schools, departments, and research areas differ in forms, documents, review, and decision ownership, and where CRM ends and student records begin. Align recruitment, doctoral admissions, supervisors, departments, doctoral schools, funding teams, registry, IT, and reporting around shared definitions and reporting requirements set early. A phased rollout by doctoral school, department, faculty, research area, project route, or intake is usually more realistic than a single switch-over.

See PhD admissions on one connected platform

See how Full Fabric helps institutions manage PhD recruitment, doctoral admissions, research proposals, supervisor and academic review, offers, enrolment, student records, reporting, automation, and applicant-to-researcher continuity in one connected platform.

Book a demo → Explore the platform →