Executive brief

This document is an internal reference describing the digital platform now in operation at the Caleb University Distance Learning Centre (CUDLC). It is intended for the Director, Registrar, Bursar, Examinations Officer, Deans, and ICT leadership.

The platform is now in production at version 1.11.0 and serves the full operational cycle of the Centre — from prospective student enquiry through application, admission, academic records, learning, fees, results, and graduation.

The purpose of this document is fourfold: (1) to give management a single reference for what the platform does, (2) to make explicit the operational and reporting capabilities available to leadership, (3) to set out the risks and controls that have been put in place, and (4) to outline the roadmap for upcoming versions so that planning conversations can be held in advance.

At a glance

What the platform does for the Centre

• Receives applications online from prospective students at any time, processing UTME, Direct Entry, and Postgraduate routes.
• Generates admission letters automatically from a template controlled by the Director's office.
• Holds the complete academic record of every student — registration, course enrolment, continuous assessment, examination scores, computed CGPA, transcript-ready output.
• Delivers learning content to enrolled students through topic-organised courses with materials, assignments, quizzes, and forum discussion.
• Bills, collects, and reconciles fees through Paystack and Flutterwave, with downloadable receipts.
• Allows lecturers to grade submissions either online or offline through the dedicated Lecturer Desk app, with automatic synchronisation when connectivity returns.
• Maintains the public-facing website at caleb.university, including news, programme catalogue, and contact information.
• Sends branded outbound email through Microsoft 365 with templated bulk and transactional messages.
• Provides administrative dashboards and reports for the Director, Registrar, Bursar, and Examinations Officer.

What has been built

A walkthrough of the major surfaces of the platform, showing each from the user's perspective.

1. The public website at caleb.university

The Centre's public website is part of the same platform that runs admissions and academics — not a separate WordPress build. This means: when a programme is added, it appears on the website automatically; when an announcement is posted, it shows in both the public news section and in students' portals; when the website is updated, the same admin team that manages everything else handles it.

The site editor uses a block-based page builder. New pages can be created without involving the ICT team for routine content updates. The homepage itself uses a flexible block layout — hero, statistics, featured programmes, news block, and call-to-action — that can be reordered or extended as the Centre's priorities evolve.

2. The admissions module

Online admissions is among the most consequential features for the Centre. It moves the entire admission cycle online while preserving full administrative control.

What an applicant does

A prospective student visits caleb.university, clicks "Apply Now", and walks through six steps: personal details, education history, programme choice, document upload, application fee payment via Paystack or Flutterwave, and final review. Their progress saves automatically — they can pause and return on any device. Applications can be submitted from anywhere in Nigeria; there is no need to travel to Imota for the form.

What the admissions officer does

Pending applications appear in the admin dashboard, filterable by programme, JAMB score, payment status, and document completeness. Each application opens to a single review screen where the officer sees the applicant's data, downloads their uploaded documents, and decides: approve, reject, or request more information.

Letter generation

Approving an application triggers a chain that until recently was three days of work: a matriculation number is reserved according to the Centre's numbering rules, an admission letter is generated from the official template using the applicant's data, and the letter is delivered three ways simultaneously — emailed to the applicant, made available for download in their portal, and archived in the platform with a permanent reference.

The letter template is editable by the Director's office (under Admissions → Templates) without any technical involvement. Letterhead, body paragraphs, signature block, and programme-specific clauses can all be adjusted. Every letter generated is logged with timestamp, user, and recipient so that any letter can be located in seconds — even years later.

3. The administrative dashboard

The dashboard surfaces the operational state of the Centre at a glance: active student count, applications awaiting decision, fees collected, and current system health. Below the cards are the enrolment-by-programme breakdown, recent activity feed, and the queue of applications awaiting the Director's review.

Role-based access

Each member of the Centre's administrative team has an account with permissions matched to their role. The Director sees everything; the Registrar sees academic and student records; the Bursar sees fees and reconciliation; the Examinations Officer sees results processing; faculty officers see their faculty's data only. New roles can be created and permissions adjusted without code changes.

Audit logging

Every administrative action is recorded. Who approved which application, when, and from which IP address. Who changed which student's programme. Who recomputed which course's results. The audit trail is append-only — it cannot be edited from inside the application — and is a key control for senate enquiries and external audits.

4. The student portal

A student's home screen presents the four things they care about most: what they owe, what is due this week, where they left off in coursework, and what their lecturers have posted. The remainder of their portal — courses, fees, grades, profile, downloads — is one click away.

The portal works equally well in a desktop browser and on a mobile phone. We test it specifically on the devices and networks Nigerian students actually use. For students with chronically poor connectivity, the optional Student Desk Windows app provides offline access to course materials and assignment drafting.

5. The Learning Management System

Each course is structured around topics. Each topic carries materials — lecture videos, readings, slide decks, practice exercises — plus optional quizzes, assignments, and forum threads. Students work through topics in sequence; the system unlocks the next topic when prerequisites are met or when the academic calendar reaches the scheduled date.

What lecturers can do

• Upload materials in PDF, Word, PowerPoint, video, or audio format.
• Create assignments with instructions, file attachments, due dates, and late penalty rules.
• Build quizzes mixing multiple choice, true/false, fill-in-the-blank, and free-text items.
• Open forums where students can ask questions and earn participation marks.
• Post course-wide announcements that appear in students' portals and inboxes simultaneously.
• See which students have engaged with which materials, assignments, and quizzes.

What students can do

• Access materials online or download them for offline reading.
• Submit assignments through the portal or through the Student Desk app.
• Take quizzes with auto-graded feedback for objective questions.
• Track their own progress through the topic structure.
• Participate in course forums and ask questions of their lecturers.

6. Fees, payments, and reconciliation

Fee collection at Caleb DLC runs entirely through the platform. The Bursary office has end-to-end visibility from when a student is invoiced through to the moment a payment lands — and the reconciliation that used to consume staff time has been substantially automated.

From a student's perspective

Each student sees their itemised invoice with every component visible — school fees, library, ICT, examinations, lab fees, development levy, NHIA. They see what has been paid (with downloadable receipts) and what remains due. Payment is one click via Paystack or Flutterwave: card, bank transfer, USSD, or QR code. The receipt is generated immediately and stored in their portal.

From the Bursary's perspective

Every successful payment is matched against the student's record automatically. The webhook from the gateway carries the platform reference, the student's identifier, the amount, and the gateway's own transaction ID. The Bursary sees a daily reconciliation report showing total expected, total received, outstanding by programme, by level, and by student. Exception handling for failed transactions and partial payments is built into the workflow.

Instalment plans

The Centre's instalment policy is configured in the platform — first instalment due at registration, subsequent instalments at scheduled dates. Late payment surcharges apply automatically. Every student's fees page shows their personal instalment schedule clearly so disputes about what was due when do not arise.

7. Results processing and academic records

Results processing has been one of the highest-value parts of the platform for the Centre. The Examinations Officer can pull a course up by session and semester, see the complete class list with all scores, identify anomalies (missing CA, ungraded scripts, candidates at risk), and produce senate-ready output without leaving the platform.

Cycle

1. Continuous assessment scores accumulate during the semester as lecturers grade quizzes and assignments through the LMS or the Lecturer Desk app.
2. Examination scores are entered at the end of semester, either through the web admin or through the Lecturer Desk and synchronised.
3. The system computes totals and grades against the Centre's rules — the Nigerian 5.00 grading scale with grades A through F and corresponding CGPA points.
4. The Examinations Officer reviews class statistics — average, pass rate, distribution of grades — and either publishes or sends back for correction.
5. On publication, students see their results and CGPA updates in their portal; an email notification is sent at the same time.

Senate-ready outputs

At any point the system produces formal class lists with grades, programme-level result summaries, lists of students with carry-overs, lists of candidates eligible for graduation, and the senate result sheets used at result-presentation meetings. These outputs match the conventions of Nigerian university senate reporting and are ready for printing or PDF distribution.

8. The Lecturer Desk app

Among the platform's features, the Lecturer Desk app has had a disproportionate effect on the day-to-day life of the Centre's academic staff. It is a Windows desktop application — distinct from the web portal — designed specifically for the focused work of grading.

Why it exists

Lecturers told us, in plain terms, that grading inside a browser tab in their office between meetings was painful. The browser wanted to refresh; the network dropped at the wrong moments; other distractions were one tab away. The Lecturer Desk app exists to give them a single-purpose environment, with offline capability, where they can work through a queue of scripts in a sustained sitting.

How it works

• A lecturer signs in once with their CUDLC credentials. The app pulls down their courses, ungraded submissions, and grading rubrics.
• They open a submission, see the student's text answer, download attached files, type a score and feedback, hit save. The grade is saved locally first — the network may drop without losing work.
• Pressing Ctrl+Enter saves and jumps to the next ungraded submission. A queue of 142 scripts can be worked through in one sustained session.
• When connectivity returns, all locally saved grades synchronise to the server. The student's portal updates and they receive an email — without further action from the lecturer.

The inbox view aggregates ungraded submissions from all of a lecturer's courses, sorted oldest first the way email is. Filter pills let them narrow to one course or one status. The badge in the sidebar shows the current ungraded count, so when it hits zero they know they are caught up.

9. Mobile and offline

The majority of student access to the portal comes from mobile phones. Every screen of the platform — public website, student portal, fees, results, course content — is designed to work on phones first. We test on the Android and iOS browsers Nigerian students actually use, on the connectivity profiles they have, and at the screen sizes they own.

For students whose connectivity does not reliably support online learning, the optional Student Desk Windows app provides downloadable course materials, offline assignment drafting, and automatic synchronisation. This was a Centre-specific design priority that has been kept central to every version of the platform.

Value delivered to the Centre

Areas where the platform measurably changes the operational picture for the Centre.

Admissions cycle compression

The admission cycle for an individual student — from form submission to admission letter in hand — has compressed from approximately seven to ten days under the previous manual process to under 48 hours during normal operations. Bottlenecks that used to consume staff hours (matching paper applications to receipts, manually drafting admission letters, reconciling JAMB scores) have been substantially eliminated.

Fee reconciliation accuracy

Reconciliation between Paystack and Flutterwave deposits and student records was the highest-leakage area in the previous workflow — payments not credited, students unable to register, recurring escalations to the Director's office. With the gateway-to-platform automation now running, payments are matched in real time and reconciliation discrepancies have effectively disappeared from the Director's queue.

Result publication speed

End-of-semester result publication, formerly a multi-week exercise involving spreadsheets, in-person meetings, and printed documents, now runs through the result computation engine. From the day examinations close to the day students see their results in their portal is an exercise of days, not weeks. The Examinations Officer's time has shifted from data entry to review — exactly the right place for it.

Lecturer time

Anecdotal but consistent feedback from the Centre's lecturers is that the Lecturer Desk app has reduced the time taken to grade a class of scripts by 30 to 40 percent compared to the previous web-based workflow. The savings come from the offline-first design (no work lost), the keyboard-driven workflow (Ctrl+Enter, no mouse needed), and the absence of a network round-trip per save.

Student satisfaction signals

• Students can pay fees from anywhere, at any time, without visiting the Centre.
• Students see their grades within hours of release rather than waiting for printed result sheets.
• Students who lose connectivity can keep studying through the desktop app.
• Students experience the same university — the same letterhead, the same tone, the same standards — across every digital touchpoint.

Internal efficiency

• The Director's daily dashboard replaces what used to be a status meeting at 8am.
• The Bursary's morning reconciliation is now a five-minute review of an automated report rather than a two-hour spreadsheet exercise.
• The Registrar's student record retrieval, formerly an in-person office visit and file pull, is a search-box query.
• The Examinations Officer can produce senate-ready result sheets without re-typing data from spreadsheets.

Why this approach was chosen

A side-by-side look at the platform alongside the global LMS leaders and the typical in-house portal that many Nigerian universities run today.

What this means for the Centre

CUDLC was the right choice because the Centre needed something that did everything a university platform should do, fitted Nigerian operational realities by default, and was supported by people we could call. Moodle would have been an LMS only — leaving admissions, fees, the public website, and admission letters to be solved separately. Canvas and Blackboard would have meant per-active-user pricing in dollars and a perpetual mismatch with Nigerian operational specifics. A new in-house build would have meant years of work and the perpetual risk of relying on whichever individuals happened to have built it.

Technical robustness

How the platform is built, hosted, secured, and protected against failure.

Architecture

The platform runs as a single, modular server application on a dedicated Linux server. All compute, memory, storage, and bandwidth on the machine are allocated exclusively to the Centre — there is no shared tenancy, no noisy-neighbour exposure, and no resource contention from other workloads. The MySQL database holds approximately 80 tables organised under a clean schema prefix. Each module — admissions, LMS, fees, results, mail — installs and uninstalls independently, so the Centre can add new capability over time without re-architecting.

Hosting

The platform sits on a dedicated server provisioned for the Centre at caleb.university. The decision to operate on dedicated infrastructure was deliberate: it gives the Centre predictable performance under load, full administrative control over the operating environment, and the ability to scale individual resources (CPU, RAM, storage, bandwidth) as the student body grows without re-architecting or migrating. Operationally, the server is managed through familiar tooling so that the Centre's ICT team works with the skills they already have — backups, file management, DNS, and standard Linux administration — without specialised cloud or DevOps expertise.

Resource posture

• Compute, memory, storage, and bandwidth are allocated entirely to the Centre — no shared tenancy.
• Headroom is sized for peak admission and registration periods, not just the steady-state student body.
• Resource utilisation is monitored continuously; thresholds trigger alerts well before capacity becomes a concern.
• Storage is provisioned with substantial headroom for media files, lecture videos, student submissions, and a multi-year archive.
• The MySQL database, application code, and uploaded media all live on the same machine, eliminating cross-host network latency in routine operations.

Backup strategy

• Daily database backups are produced and stored both locally on the server and offsite.
• A 30-day rolling retention policy keeps recent backups available for restoration.
• Quarterly full backups (database plus media files) are archived for long-term retention.
• Restore-from-backup is a documented one-page runbook executed by the ICT team within stated SLAs.
• Backups are encrypted at rest. The encryption key is held separately from the backup itself.

Security model

• All passwords stored as bcrypt hashes — never recoverable, only resettable.
• Role-based access control on every administrative action; no shared accounts; every action attributable to a named user.
• CSRF protection on every form submission; rate-limiting on login and password-reset endpoints; bot prevention on the application form.
• Optional two-factor authentication; recommended for the Director, Bursar, and Registrar accounts; required for any account with privileged data export.
• Microsoft 365 mail integration uses OAuth Authorization Code flow — no plaintext credentials are stored.
• Payment gateway integration uses platform-issued public keys for the front end and secret keys for webhook verification, stored in encrypted configuration.

Audit and compliance

• Every administrative action is logged with timestamp, user, IP address, and the affected record.
• The audit log is immutable from within the application — append-only — and is the basis for any senate or external audit enquiry.
• Data export endpoints exist for student data subjects, supporting NDPR compliance and any data subject access request.
• Data retention policies are configurable and applied in line with the Centre's NDPR practice and the Nigerian Data Protection Regulation.

Update and rollback

When a new platform version is released, the Centre's ICT team triggers the update from the admin panel's System & Updates section. The platform downloads the new release, takes a snapshot, runs database migrations, and deploys the new code. If anything fails during migration, the system rolls back automatically and the Centre is left running on the previous version. There is no maintenance window for routine updates.

Uptime and monitoring

• External uptime monitoring is configured and reports to the Centre's ICT lead.
• Internal health checks expose database connectivity, email delivery status, payment gateway connectivity, and disk space.
• Alerts on any of the above failing trigger immediately — through email, and optionally through Telegram for the Director's ICT lead.

Adoption and training

How staff and students learn the platform.

For administrative staff

Each administrative role — Director, Registrar, Bursar, Examinations Officer, Admissions Officer, faculty officer — has been trained through an initial hands-on session covering the workflows specific to their role. Training materials including illustrated step-by-step manuals are available in the System & Updates section of the admin panel and can be reissued on request. New staff joining the Centre are onboarded by their reporting officer using these materials, with additional sessions arranged as needed.

For lecturers

Lecturers were introduced to the LMS, the web admin, and the Lecturer Desk app through a series of cohort sessions. Most found the Lecturer Desk app immediately intuitive — its keyboard-driven workflow matches how they think about grading. The materials they uploaded for one course are easily duplicated to the next academic period; they do not start from zero each year.

For students

Students experience the platform first through the application process, which is designed to be self-explanatory. Once admitted, the welcome email points them to a brief getting-started guide in their portal. Most students need no further training; the few who do are supported through the Centre's student support function and through email.

Documentation library

The Centre has access to:

• An administrator manual covering every admin module.
• A lecturer guide covering web grading and the Lecturer Desk app.
• A student handbook covering portal use, fees payment, and the Student Desk app.
• A standard operating procedure document for the Director's office covering admission decisions, exam result publication, and senate reporting.
• Release notes and known-issues lists with each platform update.

Roadmap

Where the platform goes next, in conversation with the Centre.

The platform is on a regular release cycle. A backlog of items is maintained shaped by both observed needs and direct requests from the Centre. The Director's office is consulted on prioritisation before each major version. Below is a current sketch of items in flight or queued.

Near-term (next two minor versions)

• Refinements to the Lecturer Desk app based on accumulated feedback — additional keyboard shortcuts, improved attachment preview for large PDFs, configurable feedback templates per course.
• Expanded reporting templates for NUC submissions covering enrolment by gender, by state of origin, and by disability status, ready for the next NUC reporting cycle.
• A parents' portal — view-only access for parents and sponsors to see fees status and academic standing of their child or ward, with student opt-in.
• Bulk SMS notifications — alongside email, for students whose primary channel is SMS. Particularly useful for fees reminders and exam timetable announcements.
• Refined analytics dashboard for the Director's office — programme-level retention rates, fee collection trends over multiple sessions, application-to-admission conversion ratios.

Medium-term (next major version)

• A native mobile app for students (iOS and Android) — for now, the responsive web version handles mobile use; a native app expands offline capability and adds push notifications.
• Live virtual classroom integration — bringing scheduled live tutorials into the LMS itself rather than relying on external Zoom/Teams links pasted into announcements.
• Plagiarism check integration for assignment submissions, configurable per course.
• Library and resource management module — catalogue, loans, returns, and integration with the academic record so library obligations affect graduation clearance.
• Alumni and careers module — graduate tracking, alumni directory, and career services.

Long-term (12-24 months)

• Hostel and accommodation management for the Centre's residential programmes.
• Direct CAPS API integration with JAMB for automated UTME score retrieval, subject to JAMB's API access policy and the Centre's CAPS credentials.
• Advanced analytics with predictive elements — early-warning indicators for students at risk of carry-over, programme demand forecasting, capacity planning.
• Open data export to the Nigeria Education Repository and Databank (NERD) once the data exchange standard is published by NUC.

Operations and support

How the platform is operated, maintained, and supported day to day.

The platform is operated by the Centre's ICT function. Day-to-day administration sits with the team responsible for hosting, backups, user accounts, and routine configuration changes. Issues raised by staff and students flow through a defined channel into a single queue where they are triaged, assigned, and closed.

Support model

• A ticketing system tracks every reported issue with reference number, status, owner, and resolution.
• Documented response time SLAs based on severity — critical issues responded to within agreed hours, with progress updates until resolution.
• A clear escalation path from front-line ICT support to the Centre's ICT lead for issues that cannot be resolved at first line.
• A monthly operational review covering issue trends, upcoming releases, configuration requests, and any items needing the Director's decision.
• A quarterly roadmap conversation with the Director's office to align platform priorities with the Centre's academic calendar.

Operational responsibilities

Routine cadence

• Daily — automated backups verified; system health dashboard reviewed; new tickets triaged.
• Weekly — open ticket review; pending fee reconciliation exceptions cleared; pending applications progressed.
• Monthly — operational review meeting; reporting pack distributed to Director, Registrar, Bursar, Examinations Officer.
• Quarterly — roadmap conversation; restore drill; permission audit; documentation refresh.
• Per academic period — pre-cycle readiness check (admissions opening, exam scheduling, result publication, graduation processing).

Continuity

The platform runs on standard cPanel hosting with documented operations procedures, so the Centre is not dependent on any single individual. Backups are encrypted and held in two locations. Source-code custody arrangements protect the Centre's long-term position. Restore-from-backup, server migration, and account provisioning all have written runbooks held by the ICT team.

Risks and open items

What management should know is on the risk register and what is being done about each.

Items currently under discussion

• Whether to enable two-factor authentication compulsorily for the Bursar role this session — recommended on security grounds; awaiting Director's decision.
• Whether to extend the Student Desk Windows app to a Mac edition — useful for the small but growing share of postgraduate students on Apple hardware.
• Whether to add a warm-standby replica server for disaster-recovery purposes — recommended as the Centre grows; would shorten any worst-case recovery window from hours to minutes.