A parent comparing schools needs clear answers before a campus visit: which learners you admit, where you are, how admissions work, and who will answer an enquiry. A website should make those tasks easy on a phone. A beautiful photograph cannot compensate for an outdated application deadline or a contact form that sends messages to an abandoned inbox.
For school website design kenya, begin with the admissions journey and the people responsible for keeping information current. Build a useful public website first, then add private portals only when the school has a clear operational need. This guide explains the content, privacy decisions, testing and handover that belong in a practical school website brief.
Start with a parent's actual questions
List the questions the admissions office answers repeatedly. Separate questions about suitability from questions about process. Suitability includes curriculum, age groups, location, day or boarding arrangements, and support available to learners. Process includes application dates, required documents, school visits, assessments and the contact person responsible for enquiries.
Give each answer a natural home. An admissions page should explain the sequence from enquiry to a decision. A learning page should describe what the school actually teaches, using approved language. A contact page should show a usable map, directions and office hours. Avoid putting essential facts inside a poster that readers must zoom into.
Use precise campus names if the institution has several branches. Parents should not have to guess whether a photograph, telephone number or fee document belongs to the campus they are considering. Where programmes differ, describe the differences explicitly instead of using one broad description that creates confusion at the interview stage.
Ask an admissions officer to review the first draft. They can identify missing details that a designer may never encounter. Their approval should cover facts and enquiry routing, while the head of school signs off the public positioning and sensitive material.
Organise admissions content before choosing a theme
A useful initial site can include home, learning, admissions, school life, news and contact pages. That is a planning suggestion, not a fixed page count. The right structure depends on the institution. A school with several curricula may need separate programme pages; a small institution may need fewer pages with stronger information.
Keep downloadable material optional where possible. Put the main application steps in readable web text, then provide a current PDF for parents who want to save or print the detail. Label documents with their purpose and applicable intake. Remove superseded versions from prominent links so parents do not apply using an old checklist.
If fees are public, explain which period and campus they cover and what is excluded. If fees are provided after an enquiry, say that clearly. Avoid a button promising an immediate fee download when it merely collects a phone number without delivering anything. Both approaches can work when the page tells the truth about the next step.
Plan content ownership alongside the structure. For each page, name a staff member who supplies updates and another person who approves publication. A news page that nobody can maintain may create more work than value. Consider a smaller announcements section with a simple review routine instead.
Make the enquiry form short and accessible
An initial enquiry usually needs a parent's name, contact method, programme of interest and message. Decide whether additional fields are necessary before requesting them. Birth certificates, identification documents and detailed learner information belong in a carefully designed admissions process, rather than an unrestricted first-contact form.
The W3C forms tutorial recommends clear labels, instructions and feedback, and explains that forms should ask for information needed for the task. Apply that guidance by giving every field a visible label and making successful submission unmistakable. Placeholder text alone should not carry the instruction.
Test errors as carefully as success. Submit an empty form, enter an invalid email address and interrupt the connection. The page should explain what needs correction without deleting the parent's message. A success notice should state what happens next, using a response timeframe the office can actually meet.
Test the complete route to staff. A submission that appears successful but never reaches the admissions team is a broken process. Confirm the inbox, responsible officer, backup recipient and handling of messages received during holidays. Use sample data for these tests and remove it afterwards.
Keep learner privacy separate from marketing ambitions
Choose photographs and stories through an approved school process. Record permissions and any restrictions before material goes online. Avoid publishing a learner's detailed timetable, private records or contact information simply because a design layout has room for them. Have the school assess its data protection duties with appropriate professional advice.
A public website and a parent portal serve different purposes. Public pages explain the institution; a private portal may contain fees, reports or learner records. Do not protect those records merely by hiding the page from the menu. Define authentication, access rules, account recovery and removal of access when a learner leaves.
For the first release, a link to an existing well-managed portal may be more sensible than building a new portal at the same time as the marketing site. Confirm who supports that portal and whether the school can export its records. Keep private accounts out of publicly indexed content and include permission checks in the test plan.
Write a clear privacy notice for enquiry handling. Explain the purpose of collecting information and where a parent can raise questions. Keep marketing subscriptions separate from an admissions enquiry. A parent asking about admission should not discover that the school has silently added them to unrelated promotional lists.
Budget around work and responsibility
Request a quote with separate lines for discovery, design, content preparation, development, hosting, domain administration, integrations and ongoing support. A price without scope is difficult to compare. Two suppliers may use the same phrase, school website, while including very different amounts of photography, copywriting and staff training.
Prepare the source material before requesting estimates: approved logo files, curriculum descriptions, campus addresses, admissions steps, staff contacts, photographs and existing portal details. Mark what is ready and what needs production. That lets a developer identify dependencies instead of assuming the school will supply everything immediately.
Treat integrations as their own work. Fee payments, automated receipts and parent accounts need testing and operational ownership. Ask how failed payments, duplicate submissions and reconciliation will be handled. Do not assume that putting an M-Pesa number on a page creates a functioning payment integration.
Agree who pays for renewals and holds the accounts. The school should know how to recover its domain, hosting and administrator access if a staff member or supplier changes. Include a handover checklist and a support contact with escalation instructions in the project agreement.
Test with real tasks before launch
Give a person unfamiliar with the site five tasks: identify the right programme, find the campus, understand admissions, send an enquiry and locate a current notice. Observe where they hesitate. This is a small usability exercise, not proof that every parent will behave identically, but it can reveal unclear labels before publication.
Use several phone sizes and an ordinary mobile connection. Check menus, document downloads, tap targets and map links. Resize long campus names and programme titles. A template demonstration using short sample headings may look tidy while the school's actual content wraps badly.
Before launch, record the approved version of essential facts. Check telephone numbers, intake dates, page titles, broken links, form delivery and image permissions. After launch, repeat the enquiry test and give the office a simple process for reporting incorrect information.
Schedule reviews around admissions and term changes. Update essential pages before producing new news stories. Accuracy in a fee document or application date matters more to a prospective parent than the number of posts on the homepage.
Frequently asked questions
Does every school need a parent portal?
No. Start with the tasks you need to support. If an existing system already manages private records, the website can provide a clear access link. Build a new portal when requirements, permissions and support arrangements are defined.
Should we publish our fees?
Choose a policy the school can maintain consistently. Public fees need a clear period and scope. If fees are supplied by the office, explain how parents request them and who responds.
Can staff update the site themselves?
Yes, if the project includes appropriate editing access, training and an approval process. Test routine updates during handover, including changing a deadline and replacing a document.
What should we send a developer first?
Send the admissions journey, page requirements, available content, portal details and responsible staff contacts. Mocky Digital's industry website services are a starting point for discussing that scope. For maintenance responsibilities after launch, review website care plans.
