Plan Your Project
School Website Development
Parents need reliable admissions information, term notices, and a way to contact the school. A public school website should serve that need without exposing student records. Secure staff and parent workflows belong in a separate portal or ERP scope.
Make the admissions process understandable
Publish the application steps, age/class eligibility approved by the school, important dates, and a contact for questions. A prospectus download can help, but key instructions should also appear on the page. Avoid suggesting that submitting an enquiry guarantees admission.
- Show which academic year the information applies to.
- Name a staff owner for admissions updates.
- Collect only the details needed for an initial enquiry.
Choose an update workflow the school can maintain
A notices section is useful only when staff can keep it current. Agree editing roles, approval checks, document naming, and archiving. Make PDFs searchable and accessible where possible; do not upload scans of every notice as the only version.
The website planning checklist includes ownership and update decisions that also apply to school publishing.
Keep public content separate from student records
Photos, student details, and downloadable records need school approval and appropriate permissions. Public pages should not contain attendance, marks, contact lists, or private documents. Login protection, roles, and audit requirements belong in the school ERP proposal.
Pilot the admissions and notice workflows
We confirm public page scope, build a preview with approved content, and test the enquiry with the responsible staff member. If a CMS is included, staff practise publishing and correcting a notice before handover. ERP or payment links are tested separately from the public content.
Pricing and Scope
A public information website can use the published website packages where its page and CMS requirements fit. Admissions portals, fee payments, and ERP integrations are custom application scopes. Document migration, staff training, and hosting are confirmed in the proposal.
Questions Before You Start
Does a school website include an ERP?
No. A public website and a role-based system for attendance, fees, or student records solve different problems. They can be connected after each scope is defined.
Can staff post notices without a developer?
Yes when a CMS and staff training are included in the agreed package. The proposal specifies roles and the publishing workflow.