Confidential: Internal Workshop Use Only
Implementation Evaluation Workshop
FREF Postgraduate Bursary Programme
Thursday 13 March 2026 | 10:00 to 12:30 | Working Session (Hybrid)
173
Students Supported
150
Programme Target
3
University Partners
~R95m
Funds Managed (2025)
01: Overview
Workshop Agenda
A focused two-hour working session. Come prepared: the session moves fast and there is no time for context-setting from scratch.
Session Purpose
- Build a shared understanding of what worked and what needs to change
- Prioritise the 7 recommendations: actionable in 30 days vs what needs planning
- Assign named owners for each priority action
- Agree a 30-day action plan and check-in rhythm
By End of Session
10:0015 min
Welcome & Context Setting
Overview of the evaluation. One-page summary walk-through. Session ground rules.
Shared context established
10:1530 min
Team Reflections: What Resonates, What's Missing
Student Advancement ~10 min |
M&E ~10 min |
Leadership / Finance ~10 min
Team perspectives captured
10:4510 min
Break
10:5535 min
Recommendation Review & Prioritisation
Walk through all 7 recommendations. Group decides: DO NOW / PLAN / PARK
Prioritised recommendation list
11:3035 min
Action Planning: Owners, Timelines, Quick Wins
For every DO NOW and PLAN item: who owns it? What's the first concrete action? By when?
Action plan with named owners and deadlines
12:0515 min
Wrap-Up & Closing
Read back priorities, confirm commitments, close. Buffer to 12:30.
Aligned team with clear commitments
12:2010 min
Buffer
Pre-Read Checklist
- Review the one-page evaluation summary. Know the 7 findings before you arrive.
- Come with your team's top 3 learnings from the 2025 cycle. What would you do differently?
- Think about which recommendations matter most to your function and what can realistically be done in 30 days.
- Note any additional recommendations or concerns not captured in the evaluation report.
- Be ready to name an owner (not a team, but a person) for at least one recommendation your function can lead on.
02: Overview
What Worked
The 2025 pilot was a genuine proof of concept. Name these strengths explicitly before turning to what needs to improve. They are real achievements.
Programme model validated
The integrated financial and wraparound support model was operationally viable across three universities and 173 students in its first full implementation cycle. This is a meaningful achievement.
Financial controls are robust
Disbursements were structured, auditable, and multi-layered. The finance team expressed high confidence that funds were not disbursed incorrectly. Controls are strong enough to withstand donor scrutiny. 4.2.3
Strong adaptive management
The team consistently responded to emerging challenges: accommodation escalations, provider gaps, underspend reallocation. Effective problem-solving under pressure, throughout. 4.1.5
Student impact was real and material
Students consistently described the programme as life-changing. Tuition clearance, device provision, and academic support enabled continued study that would otherwise have been impossible. 4.5.3
SOPs being formalised
Disbursement flows, refunds, and reallocations are being documented. A communications plan and earlier recruitment shifts are underway. The 2025 pressures are informing structural responses, not just informal reflection. 4.1.7
University relationships are strong
Across all three institutions, Feenix was viewed as a responsive and cooperative partner. Fee clearance worked. Dedicated contacts enabled fast response when payments were confirmed. 4.4.1
Device provision exceeded expectations
Students described laptop provision as a major academic enabler. One student noted it was of higher quality than devices used by peers in technically demanding programmes. 4.5.3
Exceeded the 150-student target
173 students supported vs the 150 target. Underspend on tuition was intelligently reallocated to clear historical debt and support an additional short-term cohort, with donor approval.
01 -- Student Advancement & Bursary
Findings: Student Advancement
Cohort instability, recruitment complexity, and accommodation pressure were the defining operational challenges of the 2025 cycle.
Cohort Instability
"Confirmation" was not a clean milestone. It was a prolonged, ongoing phase. 4.1.1
Expected
Students sign agreements, cohort confirmed, disbursement begins. A once-off intake process with a clear milestone.
Reality
Significant drop-off even after agreements were signed. Cohort stability only became clear much later, forcing continuous recruitment, verification, and replenishment. 5.1
Buffer list was essential
Maintaining a buffer list and treating recruitment as ongoing, not discrete, became necessary. Informed by historical data on attrition and ineligibility patterns.
Competing bursaries created opt-out risk
Students withdrew after signing when offered direct cash disbursements by competing programmes. The bursary model (clearing institutional debt) is less immediately visible to students: a structural vulnerability at intake. 4.2.1
Recruitment Complexity
High volumes, narrow eligibility
Application volumes were high, but strict eligibility criteria significantly narrowed the qualifying pool. Extensive screening, verification, and replacement was required throughout the cycle. 4.2.1
Postgrads needed more engagement than assumed
Initial assumptions: postgraduate cohorts would require minimal engagement. The opposite was true. Students actively sought communication, reassurance, and visibility. Monthly check-ins, academic monitoring, and escalation management were all required at scale.
Double-dipping required active verification
Ongoing verification revealed students with overlapping funding arrangements, necessitating further recruitment and cohort adjustments. This added to an already intensive administrative load.
Key insight
Postgraduate funding environments are fluid, not fixed. Recruitment is not a phase that ends: it is an ongoing programme function that requires dedicated capacity and systems. 4.1.1
Accommodation & Capacity
Accommodation payments created relationship strain
Where off-campus accommodation charges were not reflected on university statements, payments were delayed. Students became anxious and relationships became strained, requiring direct landlord engagement. 4.2.1
Timeline misalignment with institutions
Accommodation operates on separate administrative timelines from tuition clearance. Early, coordinated confirmation is required but was not consistently available. 4.4.2
Capacity was consistently stretched
The scale and intensity of recruitment, administration, engagement, and coordination exceeded initial capacity assumptions. Required extended working hours and cross-team support at peak periods. 4.1.4
Structural response
Capacity pressure acted as a catalyst. The organisation began separating bursary administration from student support functions, adding resourcing and restructuring. Reactively, not proactively.
02 -- Systems & Finance
Findings: Systems & Finance
Disbursement was a structured strength, but university bottlenecks, manual verification loads, and a 3x scale-up created significant operational strain.
Disbursement: A Structured Strength
Multi-layer disbursement process
Updated fee statements verified before each disbursement. Detailed debt analysis separating historical from current-year charges. Multi-stage approval: internal finance plus trustee oversight. Payments released within 1 to 2 days once approvals complete.
Systems as integrity control
Systems was not just automating a pipeline: it was actively protecting programme integrity through reconciliation and filtering. This is essential, and it worked. 4.2.2
Fee statements: the critical bottleneck
University responsiveness in providing updated fee statements was the most consistent constraint. Statement turnaround times could consume most of a month. Disbursement preparation had to start early just to absorb this lag. 4.1.2
Manual analysis creates operational risk
Pre-disbursement verification required intensive manual work: separating historical vs current debt, differentiating tuition from accommodation, removing non-qualifying charges. Necessary, but time-consuming and sensitive during peak periods. 4.1.3
R28m to R95m: A Step-Change in Complexity
Systems not ready for this scale
Accounting infrastructure and reporting workflows had not fully matured. Finance staff relied on manual processes and spreadsheets: "too manual and too risky" at scale. 4.2.3
Early role clarity issues
Unclear ownership around reconciliation inputs and approval sequencing caused payment delays. Not system failure, but process ambiguity at handover points. 4.2.3
Improvements underway
New accounting provider with nonprofit expertise being onboarded. Finance roles being restructured. Internal system integration and automation being invested in. The direction is right, but the work is not done.
Without strengthening, expansion means risk
Leadership recognised clearly: future programme expansion without system strengthening would introduce significant operational risk. The finance function is performing under current conditions, but headroom is limited. 4.2.3
03 -- Service Providers
Findings: Service Providers
Providers were capable and willing to adapt. The problem was not provider capability: it was programme integration and activation. 4.3.4
Tutoring provider adapted to postgrad needs
Demonstrated flexibility in sourcing specialised academic support, including niche tutors for uncommon fields like Entomology. Developing live dashboards for real-time student engagement tracking. 4.3.1
Mental health partner had structured delivery
Described structured monitoring processes and emphasised reliance on clear cohort information and early engagement. When properly activated and given updated data, they delivered. 4.3.1
Uptake was consistently low
Services were not consistently or proactively communicated to students. Limited awareness meant students who most needed support were often not engaging with it. 4.3.2
Generic models did not fit postgrad needs
Students perceived tutoring as "generic" or "automated." Mental health support timing did not align with moments of acute need. The relevance gap reduced uptake, not provider disengagement. 6.3
Provider Perspective
Confident in delivery processes and responsiveness when engaged. Believe they are delivering what the programme needs. Waiting for activation and updated data from Feenix.
Internal Team Perspective
Dissatisfied with uptake and overall impact. Mental health engagement and sustained tutoring utilisation both fell short. Students are not getting the value the programme intended. 4.3.3
Root Cause
The gap stems from integration factors: timing of student onboarding into support services, clarity of communication to students, feedback loops between providers and programme teams, and the evolving and unstable nature of the cohort. Services were technically operational, but their value depended on coordination, activation, and communication processes that extended beyond providers themselves. 4.3.3
04 -- Universities
Findings: Universities
Strong relationships and effective fee clearance, but accommodation timing and fragmented communication created ongoing operational pressure.
Mutual responsiveness
University stakeholders described relationships characterised by effective communication and quick response. Where long-standing relationships existed, dedicated contacts allowed Feenix-funded students to be prioritised quickly. 4.4.1
Fee clearance worked
Where funding commitments were sufficient to clear debt, registration proceeded without difficulty. Institutions facilitated registration and worked collaboratively to resolve barriers. 4.4.2
Accommodation on separate timelines
Tuition payments were received and processed. But accommodation funding often did not align with institutional allocation cycles. Students were funded but still faced housing uncertainty. 4.4.2
Fragmented communication
Multiple Feenix team members communicating with the same institution created uncertainty about whether requests had been addressed. Particularly challenging where staff managed multiple funding streams simultaneously. 4.4.3
Limited visibility into full funding
Universities knew about tuition contributions but had limited visibility into stipends, accommodation, or book allowances paid directly to students. Created risk of duplicating awards and required reversals. 4.4.4
University suggestion
Route all funding components through institutional financial systems. This would improve oversight, reduce adjustments, and allow universities to manage student accounts more predictably. 4.4.4
05 -- Students
Findings: Students
Funding confirmation equals stability. Coordination and timing shaped how effective the programme felt in practice, not just the existence of support. 4.5.1
Tuition funding was highly enabling
Students could register and continue their studies. Described as life-changing: removing the fundamental financial barrier to postgraduate participation. 4.5.1
Academic resource vouchers helped
Offset study-related costs and reinforced the importance of wraparound financial support beyond tuition alone. Consistently valued and utilised by students.
Device provision exceeded expectations
Laptop provision was consistently described as a major academic enabler. In one case, the device provided was of higher quality than devices used by peers in technically demanding programmes. 4.5.3
Tutoring helped where it landed
Students who engaged with tutoring reported positive academic and confidence benefits. The support, when accessed, worked. The problem was awareness, access, and relevance. 4.5.2
Accommodation uncertainty despite funding
Confirmation timelines did not align with institutional cycles. Students were funded but faced periods of housing uncertainty, which directly affected stability and wellbeing. 4.5.1
Mental health responsiveness gap
One student described receiving mental health support several days after requesting help, by which point the immediate crisis had passed. Availability alone is not sufficient: timeliness and proactive engagement are critical. 4.5.2
Coordinated Delivery Is the Product
Students confirmed what all stakeholders described: where support was timely and clearly coordinated, it enabled stable academic progression. Where timing or communication was unclear, students experienced avoidable uncertainty despite strong programme design.
06: Analysis
Process Map: Ideal vs Reality
Where design intent and operational experience diverge, and what that means for scale. The programme demonstrated strong governance and operational commitment. To support future scale, the documented process must evolve to reflect lived adaptations, feedback loops, and volatility management mechanisms.
1
Student Confirmation & Cohort Stabilisation
Ideal
Confirmation equals signed agreement equals cohort locked. Proceed to disbursement.
Reality
Provisional commitment. Ongoing opt-outs. Buffer list essential. Cohort only stable once registrations finalise. 5.1
2
Disbursement Preparation & Debt Verification
Ideal
Structured window: request statements, verify, approve, pay, confirm with universities.
Reality
University response times bottlenecked the whole chain. Manual debt analysis was extensive. Accommodation charges not on statements caused further delays. Controls strong, but process was heavy. 5.2
3
Resource Distribution & Wraparound Support
Ideal
Structured referrals to academic, financial literacy, and mental health providers. Monitoring through surveys and reporting cycles.
Reality
Service uptake varied significantly. Mental health perceived as impersonal and slow. Tutoring misaligned with postgrad needs. Feedback loops not embedded. Monitoring improved during cycle, but reactively. 4.3.2
4
Capacity & Internal Coordination
Ideal
Roles clearly defined across recruitment, systems, bursary management, and financial control.
Reality
Recruitment required more effort than anticipated. Strict eligibility plus high-touch communications created sustained pressure on a small team. Workload intensity not reflected in documented design. 4.1.4
5
Risk Management & Scalability
Ideal
Risk register anticipates drop-offs and academic progression risks. Programme maintains governance integrity and manages contingencies effectively.
Reality
Accommodation volatility, opt-outs, service provider misalignment, and university responsiveness were more prominent than anticipated. Escalation loops not formally embedded. Resilient, but exposed. 5.5
07: Analysis
Risk Areas
Five systemic risks surfaced by the 2025 implementation cycle. Each requires deliberate structural response, not just awareness.
Risk A
Cohort Volatility and Replacement Management
The cohort was never truly "locked" after confirmation. Post-agreement opt-outs, competing bursaries, and eligibility failures created ongoing recruitment cycles. Without a formal stabilisation window, this will repeat at greater scale. 5.1
Risk B
University Administration Dependency
Escalation loops and contingency disbursement mechanisms are not formally embedded in the process. If university systems are slow, disbursement delays cascade directly to student stability. The programme is resilient but exposed. 5.5
Risk C
Accommodation Payment Timing
Accommodation operates on different institutional timelines from tuition clearance. Students were funded but still faced housing uncertainty. This is a structural timing risk, not a funding risk, and must be addressed through formal university agreements. 4.4.2
Risk D
Service Provider Activation Dependency
Key personnel carry high interaction and coordination loads with capacity already stretched. As the programme scales, delivery effectiveness will be impacted unless capacity is strengthened alongside system maturity. Services exist, but only deliver when activated, communicated, and integrated correctly. 4.1.4
Risk E
Historical Debt and Certificate Risk (45%)
The intended outcome is "debt-free graduation." However, in previous cohorts, 45% of students were still unable to obtain their certificates due to outstanding fees. The process map must demonstrate that course-correction mechanisms can detect and address this risk early enough, or acknowledge it as a systemic delivery failure requiring structural resolution. This is the clearest gap between programme intent and student outcome. 5.5
08: Recommendations
Seven Recommendations
Moving from resilience to institutional maturity. The 2025 pilot was a stress test for the FREF model. These recommendations distil the underlying lessons. For each, the workshop will decide: DO NOW | PLAN | PARK
R1
Managed Cohort Stabilisation Model SA
R2
Scalable Operating Model Leadership
R3
Integrated Service Provider Model SA M&E
R4
Standardised Financial Coordination Finance
R5
Institutional Diplomacy with Universities Leadership SA
R6
Student Experience Lifecycle SA
R7
Operational Maturity Transition All Teams
09: Recommendations
R1 to R7: In Detail
Each recommendation includes the underlying problem, the proposed response, and a discussion prompt for the workshop.
R1
Managed Cohort Stabilisation Model
The Problem
The programme was designed for a fixed intake moment, but postgraduate funding is inherently unstable. Continuous shifts in eligibility, funding overlaps, and late withdrawals created a prolonged "stabilisation phase" that cascaded into delayed disbursements and reverse administration processes throughout the cycle. 6.1
The Recommendation
Shift to a Managed Cohort Stabilisation Model. Introduce a formal "Stabilisation Window" (Feb to March) with controlled replacement protocols and staged support activation. The cohort is only "locked" once university registrations finalise. This enables year-on-year cohort comparisons and predictable planning. 4.1.1
Workshop Discussion Prompt
What does a formal "Stabilisation Window" look like in practice? What triggers move the cohort from "provisional" to "locked"? What processes need to change upstream: recruitment, communications, systems -- to make this work?
R2
Scalable Operating Model
The Problem
The operational intensity, spanning 173 students and multiple high-touch interventions, exceeded the capacity of the original delivery model. Success was maintained through individual effort rather than systemic design, sometimes prioritising administrative survival over proactive student engagement. 6.2
The Recommendation
Formalise a Scalable Operating Model with clear separation between financial administration, student engagement, and provider oversight. Define caseload ratios for student-facing roles to ensure sustainability as the programme scales. Design the model so it works without heroics. 4.1.4
Workshop Discussion Prompt
What is a sustainable caseload ratio for student-facing staff? Where does the current model break first as student numbers increase? What role boundaries need to be drawn, and hardened, to prevent cross-team bleed?
R3
Integrated Service Provider Model
The Problem
Service providers operated adjacent to, rather than within, the programme ecosystem. Low utilisation was driven by a "relevance gap": students perceived text-based support to be "generic" or "automated," while academic tutoring was often too generalist for postgraduate research. 6.3
The Recommendation
Pivot to an Integrated Service Provider Model. Reposition providers as partners through mandatory "human-first" onboarding (voice or video call). Align academic support with postgraduate research milestones. For mental health: real-time cohort data sharing is essential to prevent providers operating on outdated student lists. 4.3.4
Workshop Discussion Prompt
What would "human-first" onboarding look like operationally -- who facilitates it, when, at what cost? What data do providers need from us, and how often? What performance thresholds would trigger a provider review or termination?
R4
Standardised Financial Coordination
The Problem
Financial friction in early 2025 was not a system failure: it was a result of unclear ownership around reconciliation inputs and approval sequencing. Without a finalised student list, Finance was forced into reactive, manual spreadsheet management -- described internally as "too manual and too risky" at scale. 6.4
The Recommendation
Establish a hard "Data Lockdown" for student records at a defined point in the cycle. Implement formal reconciliation checkpoints between Programme and Finance teams. Shift Finance from manually tracking invoices to well-defined high-level oversight, with automated dashboards replacing spreadsheets. 4.2.3
Workshop Discussion Prompt
When should "Data Lockdown" happen -- what's the trigger and who calls it? What does the handover between Programme and Finance look like in a structured model? What would an automated financial dashboard need to show to replace manual tracking?
R5
Institutional Diplomacy with Universities
The Problem
Universities are critical partners, but their internal cycles for housing and billing often conflict with bursary timelines. The "manual tax" paid by the internal team to resolve accommodation blocks is not sustainable at scale. Universities also had limited visibility into students' full funding package. 6.5
The Recommendation
Formalise MOUs with university Development Offices (leveraging the proposed UJ blueprint) to trigger "Advance Allowance" protocols. Students receive housing and food support in February, ahead of the standard March/April billing reconciliation. Integrate Feenix funding data into institutional systems where possible. 4.4.4
Workshop Discussion Prompt
What does the UJ MOU blueprint look like? What would each university need to agree to for this to work? How do we build institutional trust to the point where they will share funding visibility with us, and vice versa?
R6
Student Experience Lifecycle
The Problem
While the programme provided life-changing value, students highlighted a "responsiveness gap" during early-cycle crises. The lack of a clear, unified escalation pathway meant students often felt uncertain about where to turn when administrative delays affected their living conditions. 6.6
The Recommendation
Implement a Milestone-Based Student Journey Map. Define clear escalation pathways and contact protocols. Shift the student experience from a series of administrative tasks to a proactive lifecycle, particularly in situations that may compromise student security around registration, accommodation, or graduation. 4.5.2
Workshop Discussion Prompt
What are the key lifecycle milestones we need to map? What does a "crisis escalation pathway" look like -- who is the student's first point of contact, and what's the SLA for response? What proactive check-ins should be built into the standard cycle?
R7
Operational Maturity Transition
The Problem
The 2025 cycle successfully validated the bursary model through adaptive resilience. However, the organisation has reached a threshold where "firefighting" must be replaced by stable, repeatable systems to ensure long-term viability. Future expansion without further system strengthening would introduce significant operational risk. 6.7
The Recommendation
Institutionalise Operational Learning. Transition from adaptive implementation to a structured operating framework. This includes centralised governance, automated financial dashboards, and a formalised provider integration framework. The goal: predictability and sustained effectiveness without relying on heroics. 4.1.7
Workshop Discussion Prompt
What does "operational maturity" look like for Feenix in 12 months? What are the top three systems investments that would have the highest leverage? How do we ensure the institutional learning from 2025 is captured and applied, not just remembered?
10: Recommendations
Team Focus Areas
Each team brings a different lens. These cards frame your preparation for the workshop.
Student Advancement
"How do we move from reactive engagement to proactive lifecycle management?"
R1 Cohort Stabilisation
R3 Service Integration
R5 Universities
R6 Journey Map
Key report sections: §4.2.1 Student Advancement, §4.3 Service Providers, §4.5 Students, §5.1 to 5.3
Monitoring & Evaluation
"What data do we need to catch problems before they escalate?"
R3 Service Integration
R7 Operational Maturity
Key report sections: §3.5 M&E Framework, §4.3 Service Providers, §5.5 Risk Areas, Risk E (verification gaps)
Leadership / Governance / Finance
"What structural changes are needed to scale without relying on heroics?"
R2 Operating Model
R4 Financial Coordination
R5 Universities
R7 Maturity Transition
Key report sections: §4.2.3 Finance, §4.4 Universities, §5.4 to 5.5, R28m to R95m growth context
Four Questions Every Team Should Answer
- What was the single biggest operational pain point in 2025 for your function?
- Which of the 7 recommendations would have the highest impact if implemented in the next 30 days?
- What would you need to make that happen, and what's standing in the way?
- What's one thing the evaluation missed or got wrong about your team's experience?
11: Recommendations
Prioritisation Framework
For each recommendation, the group will decide together. One classification per recommendation. Go through all 7 first (quick vote), then revisit contested ones.
DO NOW
Within 30 days
Actionable immediately. Owner identified. No significant dependencies or approvals required. First step can happen this week.
PLAN
This programme cycle
Important, but needs scoping, resources, or stakeholder alignment first. Build it into the 2026 planning process. Assign a lead to develop the plan.
PARK
Revisit later
Out of scope for now: either not feasible, dependent on other changes first, or lower priority. Document the decision and the reason.
Action Planning Rule
Every action needs one person's name, not a team name. Shared accountability equals no accountability. Time is limited: park the debate, not the item.
12: Reference
Report Addendum
Click any reference to read the full excerpt from the evaluation report, organised by chapter.
Section 4.1 -- Implementation Experience
§4.1.1
Confirmation and Cohort Stability Was Not a Single Moment
→
§4.1.2
University Processes Were a Critical Dependency and a Repeated Source of Delay
→
§4.1.3
Disbursement Was Operationally Robust, but Required Heavy Manual Analysis
→
§4.1.4
Internal Capacity Constraints Shaped Responsiveness and Triggered Structural Strengthening
→
§4.1.5
Underspend Became a Strategic Lever, but Also Signals Forecasting Issues
→
§4.1.7
Implementation Learning Is Already Being Institutionalised Through SOPs
→
Section 4.2 -- Functional Teams
§4.2.1
Student Advancement Team and Bursary Management
→
§4.2.2
Systems Function: Strengths and Constraints
→
§4.2.3
Finance Function: Scale-Up and Operational Strain
→
Section 4.3 -- Service Providers
§4.3.1
Service Providers Demonstrated Responsiveness and Willingness to Adapt
→
§4.3.2
Service Effectiveness Constrained by Uptake, Communication, and Integration
→
§4.3.3
A Perception Gap Between Provider Confidence and Internal Programme Satisfaction
→
§4.3.4
Capable Partners Operating Within an Activation-Dependent System
→
Section 4.4 -- Universities
§4.4.1
Strong Operational Relationships and Responsive Coordination with Universities
→
§4.4.2
Effective Fee Clearance, but Accommodation Remained a Persistent Pressure
→
§4.4.3
Fragmented Communication and Timing Constraints
→
§4.4.4
Limited Institutional Visibility Into Full Student Support Package
→
Section 4.5 -- Students
§4.5.1
Funding Confirmation and Accommodation Coordination Directly Affected Student Stability
→
§4.5.2
Academic and Mental Health Support Valued, but Responsiveness Affected Usability
→
§4.5.3
Device Provision Was Highly Valued and Exceeded Expectations
→
Section 5 -- Process Map Analysis
§5.1
Process Map: Student Confirmation and Cohort Stabilisation
→
§5.2
Process Map: Disbursement Preparation and Debt Verification
→
§5.5
Risk Areas Identified: Management and Scalability
→
Section 6 -- Strategic Recommendations
§6.1
Managing the Fluid Intake Environment
→
§6.2
Aligning Capacity with Structural Load
→
§6.3
Integration of Service Delivery Partners
→
§6.4
Streamlining Financial Ownership and Inputs
→
§6.5
Solving the Timing Misalignment with Universities
→
§6.6
Strengthening the Student Experience Lifecycle
→
§6.7
Transitioning to Operational Maturity
→