Discovery before design
Written scope, audience, constraints and acceptance criteria before visual work starts. You know what you are buying.
Education websites and enrolment decisions
A course is not findable when its facts live in five different documents
For Australian schools, registered training organisations, higher education and short-course providers that need learners to compare eligibility, delivery, fees and intake dates before entering the correct application system.
- Schools
- Registered training organisations
- Higher education providers
- Short-course providers
- Who this covers
- Schools, Registered training organisations, Higher education providers, Short-course providers
- Typical buyer
- A principal, registrar, marketing director or education executive signs off with admissions, course owners, accessibility and regulatory teams contributing.
- Indicative timing
- A focused provider site commonly takes 10–16 weeks; large course migrations, procurement and system integration may require 16–30+ weeks.
- Next step
- Map priorities, content owners and systems
04Who this covers
Schools, registered training organisations and higher education providers do not share one website problem
The business model determines which information changes, which system owns critical data and what a useful enquiry contains.
Schools
Parent evaluation, enrolment milestones, calendars and current-community access need distinct paths.
Registered training organisations
Course codes, delivery modes, fees and regulatory information must remain accurate and comparable.
Higher education providers
Large course catalogues, faculties, research and international pathways require governed taxonomy.
Short-course providers
Dates, prerequisites, availability and payment need a compact conversion journey.
05Buyer journey
A learner compares a future, not a page in a catalogue
Picture a regional worker looking for a part-time qualification before the February intake. They move between a Google result, course page, entry-requirement PDF and fee schedule while checking whether attendance is online, on campus or both—and whether the published dates agree.
Course discovery
The learner searches by career outcome, subject, qualification or location and needs to distinguish a course from a unit, faculty article or archived intake.
Eligibility check
They compare prerequisites, recognition pathways, language requirements, delivery mode and any provider-approved conditions that determine whether application is realistic.
Fee and date comparison
They look for current tuition, additional costs, funding context, start dates, duration and application deadlines presented from consistent sources.
Application start
The selected course and intake should carry into the application system so the learner does not have to identify the same option again.
Completion and follow-up
The provider confirms submission status and routes missing information through the admissions workflow rather than leaving applicants unsure whether anything was received.
Common friction: The common break occurs when entry requirements and fees sit on separate, contradictory pages. Structured publishing can reduce that conflict, but the website cannot set admission policy, create places in a full intake or approve course and registration claims.
06Decision path
How a education buyer moves from problem to commitment
The website earns the next step by answering suitability questions before asking someone to book, enquire, buy or trial.
| Phase | Common failure | Better path |
|---|---|---|
| Discovery | Search across faculty pages and handbook PDFs | Filter governed course records by learner-relevant facts |
| Eligibility | Interpret prose copied from an older intake | Read current structured requirements and pathway notes |
| Application | Open a generic form and choose the course again | Carry course and intake context into the supported application system |
| Honest limit | Admissions decides eligibility and intake capacity | Admissions still decides eligibility and intake capacity |
07Jobs to be done
What a education website or system has to do
An education website must let a learner compare the facts that determine a real application, while preserving the provider’s course governance and handing the selected intake into admissions without ambiguity.
- Help learners compare courses, eligibility, fees and dates.
- Move suitable applicants into the correct enrolment process.
- Maintain one governed source for course information.
- Serve parents, learners and current students without mixed navigation.
- Make essential information and forms accessible.
08Failure signals
What people notice when a education site is wrong
Education friction appears when admissions corrects web copy by email, applicants select the wrong intake, staff update the same prerequisite repeatedly and analytics loses the learner between catalogue and application systems.
- Students cannot compare courses without opening several PDFs.
- Entry requirements differ across page, handbook and form.
- Enrolment drop-off is invisible between systems.
- Staff duplicate course updates in multiple places.
- Current students overwhelm prospective-student navigation.
- Forms and documents create accessibility barriers.
09Education systems
Systems this sector commonly runs on
A supported hand-off is usually safer than recreating operational data in the website CMS.
Learning management system
- Moodle
The public website should direct authenticated learners to Moodle while keeping marketing and course-reference roles distinct.
- Canvas LMS
Canvas access and selected course touchpoints can connect without duplicating the learning environment publicly.
Student management system
- aXcelerate
RTO course and enrolment flows should use supported aXcelerate capabilities and agreed data ownership.
Education CRM
- Salesforce Education Cloud
Prospective-student journeys can route into Education Cloud when lifecycle stages and consent are defined.
Devoq does not claim confirmed delivery experience with these education platforms on this page. Each connection is treated as requirements and verified against the current account and vendor documentation.
10Compliance context
Standards and obligations that shape the build
Standards for Registered Training Organisations
Australian Skills Quality Authority
How it shapes the build: RTO course and marketing content needs provider-led review against current registration and information obligations; Devoq does not certify compliance.
Higher Education Standards Framework (Threshold Standards) 2021
Tertiary Education Quality and Standards Agency
How it shapes the build: Higher-education information governance and representations should follow provider approval under its applicable standards context.
Education Services for Overseas Students Act 2000
Australian Government Department of Education
How it shapes the build: International student information may require CRICOS and provider-approved disclosures; applicability must be confirmed by the institution.
This is general context that shapes how we build, not legal or compliance advice. Confirm your obligations with your own adviser or the relevant regulator.
11Content operations
Who updates content, how often, and with what skill
Course owners should approve academic description, outcomes, prerequisites and delivery detail. Admissions owns application dates, process and applicant communications; finance or student administration confirms fees and additional costs; marketing shapes discovery without rewriting controlled facts. A structured course record should expose those ownership boundaries instead of storing the entire proposition in one editable text field.
Intakes need effective dates and states. A future offering may be planned, open, waitlisted, closed or cancelled, while the underlying course remains current. Publishing should allow authorised teams to change an intake without duplicating the course, and should preserve an archive or redirect decision when an offering ends. The student management or catalogue source should remain authoritative for data it already owns.
Large providers also need controlled reuse across faculty, campus and international pathways. Shared requirement or fee blocks should carry source and review metadata so one approved update reaches every relevant page. Devoq can design the content model, integrations, roles and migration checks. The provider remains accountable for course accuracy, registration representations, admissions policy, accessibility governance and final approval.
12System architecture
The website routes demand; it does not replace operating systems
Clear ownership prevents the CMS becoming a stale copy of inventory, records or listing data owned elsewhere.
- Public education website
- Owns discovery content, audience routes, accessible explanation and presentation of approved course facts.
- Governed course catalogue
- Stores or receives course, delivery, fee, requirement and intake fields with source and ownership rules.
- Application system
- Carries the selected offering into a controlled process for applicant details, evidence and submission.
- Student management system
- Owns applicant progression, admissions decisions, enrolment and protected learner records.
13Education editorial
The course page should not be the fifth copy of the course
Course truth accumulates in layers
Education websites accumulate truth in layers. A course begins in a student or curriculum system, is rewritten for a handbook, summarised on a faculty page, shortened for a campaign and finally represented by options in an application form. Each version may have a legitimate purpose. The problem begins when every version becomes independently editable and nobody can say which one controls the next intake.
Learners experience that governance problem as personal uncertainty. They find a January page showing one prerequisite, a PDF showing another, and an application form using a course title they have not seen before. They cannot tell whether the fee is annual, total or indicative; whether “online” means fully remote; or whether the date belongs to the course, the intake or the application deadline. A visual redesign cannot reconcile facts that the organisation has not reconciled internally.
Naming the entities learners actually compare
The answer is not necessarily one enormous database project. It starts by naming the entities a learner actually compares: course, qualification, delivery mode, campus, intake, prerequisite, fee, application deadline and pathway. Each field needs a source and an owner. The public page then becomes a view of governed information, with explanatory content around it, rather than another uncontrolled copy.
This distinction is especially important for accessibility. A downloadable handbook can remain useful as a fixed reference, but it should not be the only way to discover essential requirements. Structured HTML gives learners better headings, zoom behaviour, screen-reader navigation and direct links to the fact they need. Accessible forms and error recovery matter just as much once the application begins.
Search visibility and Devoq’s honest limit
A governed catalogue also makes honest search content possible. Providers can answer specific questions about delivery, eligibility and intakes without creating dozens of thin pages whose facts drift apart. Search and AI visibility should follow the approved course structure, not invent certainty where the provider has not supplied it. An archived intake needs a deliberate status and next route, not silent removal that strands old search results.
Devoq’s honest limit is clear: Devoq is not an education regulator, curriculum designer or student recruitment agency, and cannot approve course claims, outcomes or registration information. We can model records, build comparison and application paths, migrate approved content and connect supported systems. Course owners, admissions teams and the provider’s authorised reviewers own the substance.
What this changes about measurement
That limit changes how success should be measured. More application starts can indicate better discovery, but they can also mean applicants reached a generic form before understanding eligibility. A useful path carries the chosen course and intake forward, makes required evidence clear, and lets the provider distinguish a completed submission from an abandoned start.
The most effective education redesign is therefore partly an information-governance project. It asks which system owns each fact, who may change it, and when the public version becomes effective. Once those decisions are explicit, design can help learners compare without opening five tabs, and help staff publish an intake without updating five copies. Until then, a cleaner interface only makes contradiction easier to read.
Education focus
The common break occurs when entry requirements and fees sit on separate, contradictory pages. Structured publishing can reduce that conflict, but the website cannot set admission policy, create places in a full intake or approve course and registration claims.
14Sector options
How far should the learner journey go?
The appropriate model depends on catalogue scale, application complexity and existing student systems. A larger build is not automatically better; every option needs clear ownership and an honest hand-off.
| Criterion | Brochure site | Structured course catalogue | Catalogue with application hand-off | Full application flow |
|---|---|---|---|---|
| Core purpose | Explain the provider and direct learners to staff or external references. | Let learners find and compare governed course, intake and delivery facts. | Preserve selected course and intake context into an existing admissions system. | Collect, validate and manage application stages through a designed digital workflow. |
| Best fit | A small, stable offer with assisted admissions and few changing facts. | Multiple courses or campuses where comparison and content reuse matter. | Providers with a capable student system but a weak public discovery layer. | Complex admissions where existing platforms cannot support the required applicant journey. |
| Content governance | Simple, but facts can disappear into prose and downloadable documents. | Strong when fields, owners, effective dates and source rules are maintained. | Requires catalogue identifiers to map reliably into the application destination. | Requires end-to-end ownership across content, identity, documents, status and support. |
| Measurement | Enquiries and outbound clicks, with limited progression visibility. | Course comparison, intake interest and enquiry quality. | Application starts and hand-off completion by selected course or intake. | Start, save, validation, submission and admissions progression where appropriate. |
| Where it fails | Learners cannot compare enough detail and staff answer repetitive questions. | A catalogue becomes confidently wrong if source ownership is weak. | Identifier or session failures force applicants to choose everything twice. | Custom complexity can duplicate the student system and create sensitive-data risk. |
15Measurement
How success is measured in this sector
Course enquiries, application starts, completed applications and enrolments by intake matter, with progression between the website and student system measured where feasible.
Measure course enquiries, application starts, completed applications and confirmed enrolment progression by course and intake where systems permit. Catalogue searches returning no useful result, repeated prerequisite views and hand-off abandonment reveal information problems before application. Schools may prioritise qualified enrolment enquiries and tour bookings rather than a direct application completion.
Define identifiers shared by catalogue and application systems before instrumentation. Preserve consent and avoid sending identity documents, disability adjustments, visa details or other sensitive applicant information into marketing analytics. Cross-domain tracking should be documented and tested, with completion claims limited to events the provider can reliably observe.
Vanity-metric trap: Open-day traffic, handbook downloads and application starts can rise while completed suitable applications remain unchanged. Interest is useful context, but it does not prove that learners understood requirements, chose the right intake or reached an enrolment outcome.
Instrumentation: Track course searches, zero-result terms, filters, requirement and fee engagement, intake selection, application hand-offs, starts and verified submissions where supported. Use stable course and intake identifiers, test cross-domain attribution and exclude sensitive applicant data from campaign event payloads.
16Seasonality
Seasonality and timing pressures
Intake, open-day, scholarship and enrolment deadlines are operational constraints, not suggested campaign dates. Avoid migrating a catalogue while admissions staff are processing peak applications or while course owners are finalising the next handbook. Freeze source records, redirect archived offerings, test course identifiers and application hand-offs, then train publishers before promotion begins. Schools should account for term calendars; RTOs for rolling cohorts and reporting; higher education for domestic and international cycles. If timing is fixed, stage the catalogue separately from higher-risk application changes.
17Education service matrix
Services ranked for education priorities
Each link describes the sector-specific reason for the work; generic service detail remains on the service page.
Web Design — Make course comparison, eligibility and enrolment steps understandable across learner, parent and employer audiences.
Web Development — Connect governed course records to enrolment and learning systems without duplicating ownership.
UI & UX Design — Design accessible catalogue, application and student-service journeys for varied abilities and literacy.
Website Redesign — Untangle legacy faculties, courses and PDFs while protecting term-critical information and searchable URLs.
SEO & AEO — Expose approved course facts, entry questions and delivery details in a consistent discoverable structure.
20Education terms
Education glossary
Definitions for the systems, measures and operating language used on this page.
- Course catalogue
- A governed collection of courses and offerings that learners can search, filter and compare.
- Intake
- A specific start period or cohort for an offering, with its own dates, status and capacity.
- Prerequisite
- A requirement the provider says must be met before entry to a course or unit.
- Recognition of prior learning
- A provider process for assessing existing skills or experience against course requirements.
- CRICOS
- The Commonwealth Register relevant to providers and courses offered to overseas students in applicable circumstances.
- Student management system
- Software used to manage applications, enrolments, learner records, reporting and related administration.
- Learning management system
- The authenticated environment used to deliver learning materials, activities, assessment or course communication.
- Course code
- A stable identifier used to distinguish an approved course or qualification across systems and publications.
- Delivery mode
- How learning occurs, such as on campus, online, workplace-based or through a defined combination.
- Application hand-off
- The transfer of selected course and intake context from public discovery into the admissions system.
- Effective date
- The date from which an approved fee, requirement, intake or course statement applies.
- Teach-out
- Provider-managed arrangements for existing learners when a course or version is being discontinued or replaced.
How education projects are delivered
A clear framework — not vague agency theatre.
Senior people on the work
You speak with the designers and engineers delivering the project — not an account layer relaying messages.
Documented handover
Deliverables, credentials and working files handed over in your name. Nothing locked behind a proprietary portal.
Search and AI structure by default
Where the engagement produces public pages, technical SEO, schema and entity clarity are part of delivery — not a paid bolt-on.
Quality, support and expectations
- Accessibility
- Keyboard, contrast and form labelling checked before launch
- Performance
- Mobile load and Core Web Vitals considered when the engagement includes build
- Security
- Dependency hygiene, HTTPS, least-privilege access at handover where systems are in scope
- Privacy
- Analytics and forms configured to match your privacy policy when they are in scope
- Support
- Optional maintenance after launch — no forced lock-in
- Timeline
- A focused provider site commonly takes 10–16 weeks; large course migrations, procurement and system integration may require 16–30+ weeks.
21FAQ
Questions Australian education organisations ask before a website rebuild
This is an education-adapted web service, not a claim that Devoq is an education-only agency. We design around course governance, accessible discovery, intake data and application hand-offs. No unverified sector experience is implied; procurement and discovery should confirm that Devoq’s delivery model fits the provider and systems involved.
A focused provider website commonly takes 10–16 weeks. Large course migrations, formal procurement, many reviewers and system integration can require 16–30+ weeks. The schedule must work backwards from intake and open-day deadlines while leaving enough time for source reconciliation, accessibility testing, redirects, training and admissions hand-off checks.
Yes, when there is a defined public-to-learner use case and Moodle’s current supported capabilities fit it. The website can direct authenticated learners or expose approved touchpoints without duplicating the learning environment. Devoq does not assert established Moodle delivery experience here, so access, identity and support dependencies require technical discovery.
Yes, through structured records and permissions matched to institutional roles. Course owners can approve academic facts, admissions can manage process dates and authorised publishers can schedule effective changes. Staff should not manually overwrite fields owned by a student or curriculum system. Training and source rules are part of the scoped handover.
We recognise that provider type, registration and student cohort affect website requirements, but Devoq does not claim verified education-sector experience or give regulatory advice. We build against requirements approved by your governance team and advisers. ASQA, TEQSA, ESOS and accessibility applicability must be confirmed by the provider.
We need provider types, audiences, course and intake sources, application and student systems, content owners, approval stages, accessibility target, procurement constraints and immovable calendar dates. Sample records and data dictionaries are more useful than screenshots. Do not provide real applicant files for ordinary design discovery or interface examples.
Those providers can be scoped, but their priorities differ. Schools balance prospective families with current-community access; RTOs manage codes, modes and rolling cohorts; higher education needs scalable taxonomy; short courses may require date, seat and payment clarity. Architecture follows the actual enrolment model, not a generic education template.
Yes. Remote-first delivery suits providers with regional campuses, distributed staff and online cohorts. Workshops and testing can include participants across locations, while the provider supplies local connectivity, travel, campus and support realities. On-campus research, photography or facilities assessment can be added when remote evidence is insufficient.
Curriculum design, regulatory certification, course approval, student recruitment guarantees, admissions decisions, learning delivery, platform subscriptions and ongoing data cleansing are excluded unless expressly quoted. Devoq cannot approve outcomes or registration claims. The scope identifies migration responsibility, accessibility testing, integration support, content entry and post-launch ownership separately.
Not as the only authoritative learner interface. Handbooks can remain useful fixed references, but essential fees, dates, delivery and entry requirements should be accessible as governed web content. This improves comparison, linking and assistive-technology use. The provider must still decide which source controls each fact and publication period.
Usually, if the catalogue and application system share reliable course and intake identifiers and the vendor supports the transfer. Devoq can design and test that hand-off. It should fail clearly when an intake closes, rather than silently dropping context or allowing applicants to submit against an unavailable offering.
Assign one authoritative source and owner to each field, then use structured records, effective dates and controlled reuse. Avoid copying prerequisites or fees into campaign prose where a referenced block will work. Automated synchronisation helps only after governance is settled; otherwise it can publish the same wrong value across every channel.
Measure useful catalogue searches, qualified enquiries, course-specific application starts, verified submissions and enrolment progression where systems support it. Separate open-day and handbook interest from completed decisions. Stable course and intake identifiers are essential, and sensitive applicant attributes or documents must stay outside general marketing analytics.
Potentially, but only after testing whether the existing student platform can support the required journey. A custom application flow introduces identity, document, accessibility, privacy, status and support responsibilities. Devoq will scope it as operational software, not a larger contact form, and cannot replace admissions policy or decision-making.
22Sector links
Related services, industries and reading
Last updated:
Book a discovery call
Let's collaborate
Ready to adapt the build for education?
Share the current problem, your constraints and what a useful result would look like.
- 01You send the messy versionCurrent site, workflow or rough idea — no brief required.
- 02We reply by the next business dayFrom the people who would do the work, not an account manager.
- 03You get a written scope and quoteFixed, itemised, with exclusions stated. No obligation.