JAMB CAPS Login — The Central Admissions Processing System Portal Architecture

JAMB's annual cycle has four operational stages. Registration runs from late January through late February. Examination sits across two weeks in April. Result release follows within weeks of the last examination paper. After the result is out, the cycle moves into its fourth stage — admission — and the operational locus for everything that happens in that stage is the Central Admissions Processing System.

CAPS is not a peripheral surface. It is the post-result admission infrastructure that every Nigerian tertiary institution (university, polytechnic, monotechnic, college of education, innovation enterprise institution) uses to upload admission offers, that every UTME and Direct Entry candidate uses to read the admission position and to accept or reject offers, and that JAMB itself uses to approve the institution-side uploads and to apply the framework's admission rules. Without CAPS there is no operational admission process; the platform is the framework's connective tissue between the three actors.

This article is the cluster's secondary architectural anchor (parallel to the JAMB registration walkthrough which is the cluster's primary procedural anchor). It names the CAPS framework, walks the three operative surfaces (the information page, the login subdomain, the eFacility dashboard route), names the credentials each surface reads, and points the candidate to the action articles for the CAPS-side decisions (accept, reject, modification).

This article is a cycle-evergreen reference. The candidate consults the CAPS architecture reference at three different points in the cycle: pre-result (planning the CAPS-side admission cycle before the result is out), result-time and through admission (the operational stage where the dashboard returns the status and the Accept-or-Reject decision is taken), and post-cycle (where regularization or correction routes also surface through CAPS-adjacent eFacility menus).

As at publication of this article on 28 May 2026, CAPS is fully operational for the 2026 cycle. The 2026 UTME result was released in phased batches from 17 April 2026; institutions began uploading admission offers in the weeks that followed. The institution-side admission completion deadlines, set at the 2026 Policy Meeting on 11 May 2026, run through to 31 December 2026 for the latest tier (monotechnics and colleges of education). Candidates currently inside the cycle are reading CAPS for current admission activity; candidates planning for the 2027 cycle read this article for the framework that will apply in their cycle too — the architecture is stable cycle to cycle even where individual policy figures shift.

The article remains operative across the cycle. CTAs route to the action articles that match the candidate's CAPS state at the time of reading.

Four overlapping readers. The 2026 UTME candidate whose result is out and who is logging into CAPS for the first time and wants the framework reference before the action. The Direct Entry candidate at the same point in the DE cycle, reading the same CAPS architecture. The parent or guardian of an under-18 candidate, handling the CAPS check on the candidate's behalf and wanting the architectural reference before the operative login. The candidate from a previous cycle re-entering through change-of-course, change-of-institution or post-cycle regularization, returning to CAPS or to CAPS-adjacent eFacility surfaces for the modification-side or correction-side work.

CAPS sits at the operational pivot of the three-actor architecture. JAMB operates the platform; the tertiary institution makes the substantive admission decision and uploads it; the candidate reads the state and clicks the action. The architecture this article anchors:

The CAPS framework specifically — the two surfaces, the eFacility dashboard route, the five-state taxonomy, the JAMB Act and Regulations basis — in one read:

CAPS is reachable through three surfaces. The surfaces are commonly confused because they share the JAMB domain root and overlap in CAPS-side function; this section disambiguates.

Three operational notes on the surface architecture:

• The two login routes (caps.jamb.gov.ng direct and the eFacility dashboard) read the same CAPS database. A candidate who accepts an offer via the eFacility route will see the same Admission Accepted state if they then log in via the direct CAPS subdomain. The candidate may use either route as preferred.
• The CAPS information page is the canonical JAMB-side source for CAPS framework changes. JAMB publishes resolutions of the annual Policy Meeting on the page (the four-week per-offer grace period for 2026 was announced via the Policy Meeting and propagated to this page); third-party education-news sites typically report on the same source.
• Look-alike domains targeting JAMB candidates are a recurring fraud pattern — variants such as caps-jamb.com or jamb-caps.org or caps.jamb.com.ng are not JAMB surfaces. The verified surfaces are jamb.gov.ng (corporate), jamb.gov.ng/caps (information page), caps.jamb.gov.ng (login subdomain) and efacility.jamb.gov.ng (candidate dashboard). Confirm the URL bar before entering credentials.

CAPS authentication is layered on two distinct candidate-set credentials. The two are commonly confused because both are JAMB-side and both are set by the candidate; the surfaces they apply to and the recovery routes differ.

The JAMB password is the credential the candidate set at JAMB registration and uses (alongside the registered email address) to log into the eFacility portal at efacility.jamb.gov.ng. The eFacility portal is the candidate's broader self-service surface — result check, registration slip print, profile edit, and CAPS access via the dashboard. JAMB password reset runs through the eFacility password-reset link (delivered by email to the registered address) or through the SMS-based reset where eFacility offers the option; the JAMB password reset walkthrough covers the route.

The CAPS Profile password is the credential the candidate set at first CAPS login and uses (alongside the JAMB Registration Number) to log into the CAPS login subdomain at caps.jamb.gov.ng. The CAPS Profile is the candidate's CAPS-only surface — admission state read, Accept and Reject buttons, CAPS notifications. CAPS Profile password reset runs through the password-reset link on the caps.jamb.gov.ng login page (delivered by email to the registered address).

The two passwords may be set to the same string for convenience (candidates often do this), but the systems treat them as distinct. A change to the JAMB password at eFacility does not propagate to the CAPS Profile password and vice versa. A candidate who has reset the JAMB password and finds the CAPS Profile login still failing should reset the CAPS Profile password separately at the CAPS login surface.

The JAMB Registration Number itself is not a candidate-set credential — it is the persistent identifier issued at the CBT centre after biometric capture and used at every CAPS surface alongside the CAPS Profile password. The JAMB profile code reference walks the four candidate-side identifiers (profile code, e-PIN, Registration Number, NIN) and disambiguates the Registration Number specifically.

A CAPS login surfaces the candidate's admission state from a finite five-state taxonomy. The state determines what the candidate can do next; the surface is the same for every candidate and every cycle but the state varies cycle-by-cycle and candidate-by-candidate.

The five states and the action enabled per state:

The state-by-state procedural detail — what each state means, how to interpret it, what the candidate-side action is, what triggers the next transition — is walked in full at the admission status check walkthrough, which is the procedural companion to this architectural article. Read the two together: the architectural reference here for the framework; the procedural walkthrough there for the action.

Two cross-cutting notes that apply across all five states:

• Some institutions surface variant dashboard labels (Admission in Progress, Recommended, Welcome, Not Admitted) that map to the five-state taxonomy without being identical to the state names. The taxonomy is operational; the labels are presentational. The five states cover every candidate position.
• The state-transition cadence is institution-driven, not JAMB-driven. JAMB approves institution uploads and operates the platform; the institution decides when to upload, in what order, against what cut-off. A candidate at Not Yet Admitted may stay there for weeks while the institution completes post-UTME screening; a candidate at Admission Offered must act within four weeks of the offer being approved on CAPS.

CAPS is not a freestanding platform. The framework that authorises and shapes it sits in the JAMB Act and the JAMB Regulations, and the cycle-specific operational figures are set at the annual JAMB Policy Meeting.

The statutory and policy basis:

What the framework specifically authorises CAPS to do:

• Admission processing. The JAMB Act gives JAMB the statutory function of coordinating the admission of candidates to all Nigerian tertiary institutions. CAPS is the operational platform through which that coordination runs.
• Approval of institution uploads. JAMB's role on CAPS is approval-side, not allocation-side — the institution selects which candidates to offer; JAMB approves the institution's upload against the JAMB-set minimum cut-off mark and the UTME Brochure's course-by-course requirements; the candidate sees the approved offer on the CAPS Profile.
• Refusal-to-accept sanction administration. The JAMB Regulations authorise JAMB to apply sanctions to candidates who fail to act on admission offers within the cycle's framework; the 2026 Policy Meeting on 11 May 2026 set the operational four-week per-offer grace period and the refusal-to-accept sanction for inaction. CAPS records the candidate's CAPS-side action (or inaction) and surfaces the resulting status.
• Modification routes (change of course, change of institution). The JAMB Regulations authorise modification within a JAMB-defined window per cycle; the operational routes run through eFacility (not directly through CAPS) but the CAPS-side state record reflects the modification's effect.
• Regularization of admissions not routed through the standard sequence. The framework authorises JAMB to regularise admissions for candidates whose institution-side admission was substantively granted without going through the standard JAMB registration-and-CAPS cycle. The route runs through eFacility (not CAPS itself); the JAMB regularization reference covers the procedure.

The annual Policy Meeting sets the cycle-specific operational figures. For the 2026 cycle the Policy Meeting on 11 May 2026 set the JAMB minimum cut-off marks (150 universities, 100 polytechnics, 150 colleges of nursing, 100 colleges of education), the four-week per-offer acceptance grace period, the institution-side admission completion deadlines (31 October 2026 for public universities, 30 November 2026 for private universities and polytechnics, 31 December 2026 for monotechnics and colleges of education), and the refusal-to-accept sanction. Cycle-by-cycle changes are possible; confirm the current resolution at jamb.gov.ng/caps before relying on the operational figures.

A successful CAPS login surfaces the candidate's current admission state and exposes the actions enabled by that state. Five operational pathways follow from a CAPS login depending on the state read.

• Accept the offer. The Accept button surfaces against an Admission Offered state and commits the candidate to the institution-course pair. The how to accept admission on JAMB CAPS walkthrough walks the click, the downstream institution-side onboarding sequence and the irreversibility rule.
• Reject the offer. The Reject button surfaces against the same Admission Offered state and releases the offer back to the institution's pool. The how to reject admission on JAMB CAPS walkthrough walks the click, the modification routes that open, and the distinction between a deliberate Reject (no sanction) and a lapsed offer (refusal-to-accept sanction).
• Monitor the status. Where the state is Not Yet Admitted or Awaiting Institution Decision, the candidate-side action is patience — no CAPS button is enabled. The how to check admission status walkthrough covers the diagnostic for a stagnant state and the candidate-side recovery checks.
• Modify (change of course or institution). Modification runs through the eFacility portal at efacility.jamb.gov.ng (not directly through the CAPS subdomain). The change of course walkthrough and the change of institution walkthrough cover the routes. The CAPS state reflects the modification's effect once the modification is processed.
• Regularise a prior-cycle admission. Regularization is a JAMB-side correction for candidates whose institution-side admission was granted in a prior cycle without standard JAMB registration. The route runs through eFacility (Late Application / Regularization menu); the JAMB regularization reference walks the procedure.

The CAPS login is the entry point; the action is determined by the state CAPS returns and by the candidate's decision against that state. The five action-articles linked above are the cluster's procedural companions to this architectural reference.

Four issues surface most often around the CAPS login itself (separate from the post-login state and action issues).

• Login fails with the right credentials. Confirm the URL bar — caps.jamb.gov.ng for the direct subdomain, efacility.jamb.gov.ng for the eFacility route. Look-alike domains return generic errors. Confirm the credentials match the surface — the CAPS Profile password (for caps.jamb.gov.ng) is distinct from the JAMB password (for eFacility). If forgotten, the password-reset link on the respective login surface emails a reset link to the registered address.
• Login succeeds but the dashboard shows Welcome with no admission status. Two common causes. One: the UTME or DE result has not yet been released for the cycle; pre-result the dashboard returns no admission status. Two: the result is out and no institution has uploaded an offer yet; the state is operationally Not Yet Admitted. Confirm the result has been released and watch the dashboard for institution-side activity.
• Login succeeds but the Accept and Reject buttons do not surface against an Admission Offered state. Causes are browser-side (cache or script-blocking), session-side (session timeout), or state-side (an offer at Admission in Progress rather than fully Admission Offered). Clear the browser cache, log out and back in, try a different browser, and wait a few hours where the state reads Admission in Progress. The SMS ACCEPT/REJECT shortcode to 55019 or 66019 is the alternative channel that does not depend on the dashboard.
• The CAPS login subdomain does not load at all (browser-side timeout, connection refused). The surface is JAMB-side and occasionally goes down during high-traffic windows (immediately after result release, around Policy Meeting announcements). The eFacility route via the dashboard is the alternative; the [JAMB profile code not received walkthrough](/jamb/jamb-profile-code-not-received/) covers the broader candidate-side diagnostic where the JAMB infrastructure as a whole is intermittently slow.

A candidate stuck on any of the above has two escalation surfaces. The eFacility candidate-help link opens a ticket against the registered profile. The JAMB state office in the candidate's state of registration handles in-person reviews — bring the JAMB Registration Number, a CAPS dashboard screenshot (where any state has loaded), and a written enquiry naming the institution and course.

CAPS sits at the architectural centre of the post-result admission cluster. The references that bear on the framework and the actions:

• How to check admission status on JAMB CAPS — the procedural companion walking the five-state taxonomy in detail.
• How to accept admission on JAMB CAPS — the Accept click and the institution-side onboarding it triggers.
• How to reject admission on JAMB CAPS — the Reject click and the modification routes it opens.
• JAMB cut-off mark reference — the institution-tier cut-off landscape that shapes the offers CAPS surfaces.
• JAMB change of course walkthrough and JAMB change of institution walkthrough — the modification routes that run through eFacility but reflect on the CAPS state.
• JAMB regularization reference — the post-cycle correction route for admissions not routed through standard CAPS.
• JAMB password reset walkthrough — the credential recovery route for both the JAMB password and the CAPS Profile password.
• JAMB profile code reference — the four candidate-side identifiers, including the JAMB Registration Number that CAPS reads.
• Admission letter reference — the post-acceptance document the tertiary institution issues, downstream of a CAPS Accept click.

The CAPS surfaces named in this article (jamb.gov.ng/caps, caps.jamb.gov.ng, efacility.jamb.gov.ng) were re-confirmed live as at 28 May 2026. The four-week per-offer grace period and the institution-side completion deadlines reflect the 2026 JAMB Policy Meeting resolutions of 11 May 2026 as reported by Legit.ng, Businessday, Punch Newspapers, Premium Times and Naija News. Confirm the current operational figures at jamb.gov.ng/caps before relying on them for the next cycle.