A school or college website should help prospective students and families understand programs, requirements and the next step. Zoha can build a public website with organized course information, admissions guidance and enquiry routes. Publishing responsibilities, dates and staff editing need a clear process. Teaching delivery and student administration are separate software requirements.
Updated
On this page
Follow the prospective student's questions
A visitor may need to know what a program covers, who can apply, which documents are needed and how to contact admissions. Put those answers together rather than scattering them across news items and downloadable leaflets.
Program names, entry requirements and dates should come from the institution's approved material. Assign someone to review them before each intake. A website should not leave a previous intake's information looking current because nobody owns the update.
Give each content type an owner
| Information | Publishing responsibility |
|---|---|
| Programs and courses | Academic owner confirms descriptions and requirements |
| Admissions | Admissions team checks process, dates and contact details |
| News and notices | Editor manages publication and removal |
| Fees or charges | Authorized staff approve the current statement |
| Documents | An owner checks the correct version and access |
Editing access should support those responsibilities. Staff may need to update course details without changing shared navigation, or publish a notice without altering admission requirements. Include orientation using the actual tasks the editors will perform.
An illustrative admissions journey
In a hypothetical college, a visitor compares two programs, reads the requirements and chooses an enquiry category. The request reaches admissions with enough context to respond. The confirmation states what will happen next without implying that the student has been admitted.
Test the route on a phone, including a visitor who does not know the institution's internal department names. Check document downloads, missing form fields and a program that is not taking applications. Clear wording can prevent unnecessary calls and incorrectly routed enquiries.
Keep the public website separate from teaching systems
Publishing a course description is different from delivering lessons, managing assessments or giving enrolled students private access to learning material. If those functions are required, they should have their own learning-platform scope and operating responsibilities.
The public website can explain the learning offer and guide enrolled users to the appropriate system. It should not duplicate private course records or student information just to make the homepage appear more complete. The related e-learning service covers teaching-delivery requirements separately.
Prepare for the next intake, not only launch day
- Check every program's status, entry information and current contact route.
- Test notices with start and end dates so expired content can be handled.
- Give staff a guide for images, documents and accessible headings.
- Agree who checks enquiries and how editing questions are supported.
Before handover, let the designated editor complete a representative update while another staff member checks the published result. Record ownership of domain, hosting and content access. The goal is a website the institution can keep accurate throughout an academic year.