1. Starting a request
A student selects a service, reviews its current details, signs in, supplies the requested information, reviews the submission and creates a request. The request reference is used to track the work afterward.
If a service is paused, a new request should not be accepted for that service until it is made available again.
2. Requirements and documents
Service requirements shown on the service page and request wizard are the starting checklist. The team can request additional information when genuinely needed for the work.
Supporting documents must be uploaded to the correct request. File presence does not by itself mean the content has been verified.
3. Processing and status
The request workflow uses Draft, Awaiting Documents, Awaiting Payment, Submitted, Processing, Action Required, Completed, Cancelled and Refunded statuses. Status changes and other meaningful activity appear on the request page.
Where a service contains processing information, treat it as guidance unless the service explicitly states a guaranteed commitment. Student E-page does not invent an estimated completion date.
4. When the student must act
If the request needs more information, the student should open the request, read the latest team message, and provide the requested details or documents. The request remains in its saved status until the team updates it.
Quotes and payment records remain auditable separately. A successful provider verification can clear an Awaiting Payment status, but it does not by itself mean the service work is completed.
5. What counts as completed delivery
When processing is finished, the request can be marked Completed. If the work produces a file, an authorised admin can upload it as a Completed Document. The student can then download it from the request and from My Documents.
Some support work may concern an external portal action and may not produce a downloadable document. Completion therefore refers to the request work recorded by Student E-page, not a guarantee of an institution’s independent decision.
6. Completed and cancelled requests
Completed and cancelled requests are closed under the current workflow. Students cannot add new messages or supporting files to a closed request. Existing history and available files remain viewable according to access rules.
If new work is needed after closure, start the appropriate new request instead of reopening old work implicitly.
7. Third-party portals and institution rules
JAMB, examination bodies, universities, polytechnics and other institutions control their own portals, deadlines, eligibility rules and final outcomes. Student E-page can support a process but cannot override those systems.
For admission information, follow the official source linked from the published school, update or deadline page whenever available.