A school website brief is a written description of what the institution needs, who the website will serve, what it must do and how the work will be reviewed. It gives management and the developer a shared starting point before design and pricing begin.
The brief does not need technical jargon. It needs accurate information, clear priorities and an honest distinction between essential work and possible future additions.
Without that foundation, two developers can quote for very different projects under the same description: “a school website”. One may mean an information website. Another may assume applications, payments and private student accounts.
1. Describe the school and the reason for the project
Include the institution’s name, location, school sections or programmes and the person coordinating the work. Explain whether this is a first website, a redesign or an extension of an existing system.
Then describe the problem you want resolved. Perhaps admission information is scattered, parents cannot find the correct contact, staff struggle to publish updates or the institution needs a consistent official source of programme information.
Keep aims specific enough to assess. “Make the entrance requirements and application route easy to find on a phone” gives the project a clearer direction than “make us look professional”. Visual quality matters, but visitors also need to complete tasks.
2. Identify the audiences and their main tasks
A school website serves people with different needs. List the important groups and what each must be able to do.
| Audience | Example task | Information or route required |
|---|---|---|
| Prospective parents | Explore a school section and arrange a visit | Programme information, location and visit-enquiry route |
| Applicants | Understand requirements and apply | Current requirements, dates and application instructions |
| Current families | Find an announcement or approved resource | Updates and clearly labelled downloads |
| Staff | Publish authorised information | Appropriate editing access and training |
| Alumni and partners | Find relevant institutional information | Useful sections and contact routes |
These are planning examples, not a mandatory set of features. A small school may need a simpler structure. A larger institution may have additional audiences or separate systems.
3. Separate the public website from private systems
State which functions are actually required. Displaying admission information, receiving an enquiry and processing a full application are separate requirements. A private dashboard introduces further decisions about accounts, permissions, records and support.
Use my guide to school website versus school management system to help management agree the boundary. For a more specialised application workflow, see planning a nursing school admission portal.
Where an existing portal works, tell the developer whether the public website should link to it, integrate with it or leave it unchanged. Do not assume an external system can be modified without checking access and capability.
4. List the pages and features in priority order
A starting page list might include the homepage, about the school, programme or school-section pages, admissions, news, resources and contact. Add other sections only where they serve a real purpose.
- Essential for launch: the information and functions needed for the agreed core tasks.
- Useful if the budget allows: improvements that add value without blocking launch.
- Future phase: features requiring further decisions, content or operational preparation.
Describe functions with a short user scenario. Instead of “include forms”, write: “A parent can request a school visit, receives confirmation and the enquiry reaches the admissions team.” That statement creates a useful testing requirement.
5. Agree who supplies and approves content
Prepare a content inventory. Identify existing text, photographs, brand assets, approved documents and information that must be written or updated. Confirm who can approve programme descriptions, fees, dates and institutional claims.
For photographs, include ownership and publication permission in the preparation process. The developer needs to know which assets can be used, not just which files are available.
Set a realistic review process. One management contact can collect feedback, resolve conflicting requests and return a consolidated decision. Agree what happens when essential content is delayed.
A practical lesson from educational website work
The NCI website project connects school information with admissions, updates and resources. It is a useful prompt for a brief: name the destinations your community needs and explain how they should connect.
A brief should still reflect your own institution. Copying another school’s menu without understanding its users can produce unnecessary sections while leaving your actual needs unresolved.
6. Record access, ownership and existing assets
List the domain, hosting and current website platform if known. Identify the authorised account owner and who can provide access securely when work begins. Do not put passwords or private applicant records in a general proposal document.
Ask the proposal to explain ownership or licensing, account handover, renewal responsibilities and the treatment of any paid themes or software. If an existing website is being replaced, include content migration and important page addresses in the scope.
7. Set the budget range and timing
A budget range helps the developer recommend a realistic first phase. State whether it should cover content preparation, photographs, portal work, hosting, training and support, or whether these need separate quotations.
List important dates and dependencies. An admissions launch deadline is useful context, but the schedule also needs room for content approval, development, testing and corrections. Ask which decisions could change the delivery date.
Prices from a different type of school may not match your scope. My nursing school website cost guide explains cost categories for that specific institutional context; request an itemised proposal for your own requirements.
8. Define testing, handover and ongoing care
Agree what management will review before launch and who signs off. Include checks for mobile layouts, links, permitted form tests, editing access, migrated content and required integrations.
State who will receive training and documentation. Ask for recurring charges, maintenance responsibilities, backup arrangements and the route for reporting problems. These belong in the proposal alongside design deliverables.
A sample school website brief you can adapt
Our school needs a public website serving prospective parents, applicants and current families. The first phase should present our school sections, approved programme information, admission requirements, announcements, resources and contact details.
The main visitor tasks are to explore a suitable programme, understand admission requirements and request information or a visit. A private student management system is outside this phase unless separately agreed.
Management will supply approved institutional information and permitted photographs. Please identify the content you need, proposed pages, development approach, mobile review process, enquiry handling, training, handover and ongoing charges.
Our proposal review should compare deliverables, exclusions, content responsibilities, milestones, ownership arrangements and support. Please explain any assumptions or dependencies that affect price and timing.
Add your actual school details, budget range and required dates before circulating it. The example is a planning starting point, not a complete contract.
Compare proposals using the same brief
Send the agreed version to each shortlisted developer. Compare what each proposal includes, where assumptions differ and how the provider will demonstrate completion. My guide to choosing the right school website developer provides further checks.
For help turning your requirements into a workable scope, explore my website consultation and website development services.
Frequently asked questions
Who should prepare the brief?
A management coordinator can lead it, with input from admissions, the staff responsible for updates and other relevant teams. A developer can help clarify requirements.
Can we request a quotation without knowing every technical detail?
Yes. Describe the users, tasks and constraints you know. Ask the developer to identify unresolved decisions and explain their effect on scope.
Should the brief include every possible future feature?
Record future ideas separately and agree a focused first phase. This helps management assess the initial cost and delivery.
Discuss your website with me
I am Lawson Godwin Hezekiah, founder of Mita School and Techmita. Tell me what your organisation needs to improve, who the website serves and what visitors should be able to do. We can agree the scope, priorities and next steps.
- WhatsApp: Send me a message on WhatsApp.
- Contact form: Send a project enquiry through my contact page.
- Email: [email protected].
- Phone: +234 703 799 7791.
Based in Uyo, Akwa Ibom State, Nigeria. Remote project arrangements can be discussed.





