Keeping an Admissions AI Agent's Knowledge Base Current

An admissions agent is only as accurate as its knowledge base

An admissions chatbot's knowledge base goes stale exactly where mistakes hurt: course costs, ATAR and prerequisite details, entry pathways and dates. Keeping it current is an organisational job more than a technical one: one source of truth, an owner for each content type, a review rhythm that follows the intake cycle, and a short route for urgent changes.

A note on method: no paid keyword-volume tool was available, so this article was scoped from public search results. Every external source cited was opened. Nothing here comes from Skolbot or its customers, and we state no figures beyond sourced ones.

Why the knowledge base ages faster than the website

In a retrieval-based set-up, the agent pulls passages from an index of your documents and writes its answer from them. The original retrieval-augmented generation paper presents this as a way to reach external knowledge and keep it updated. Change a document and the answers can change, with no retraining.

The flip side: if last year's course guide stays indexed next to this year's, the agent can quote either with equal confidence. Our guide to chatbot hallucination guardrails covers invented answers; this one is about answers that were right last intake and are wrong now.

Typical causes:

• Duplicates: an old PDF, a blog post, an exported FAQ. Nothing says which one counts.
• Orphan copies: a fees table pasted into a working document nobody maintains.
• Changes outside the process: a revised prerequisite approved by a faculty board and never updated in the index.

Set the source of truth and a document hierarchy

For each kind of information, decide which document is authoritative. The agent should read that one, not a copy.

Add a conflict rule: if two passages disagree, the agent does not pick one. It flags the clash to your team and, meanwhile, offers the applicant a human adviser.

A review rhythm tied to the Australian cycle

Australian applications are organised by state: UAC for NSW and the ACT, VTAC in Victoria, QTAC in Queensland, SATAC in South Australia and the Northern Territory, and TISC in Western Australia. Many providers also take direct applications, particularly private colleges and TAFE pathways. State on your own pages which route applies to each course, and for whom (Year 12 school leavers, mature-age, VET pathway, international), before the agent talks about it. Entry measured by ATAR, adjustment factors and alternative entry schemes are details to publish on a page the agent can cite, never to improvise.

1. Before offers and applications open: a full review of fees, courses, prerequisites, supporting documents and process pages. Archive anything tied to the previous intake.
2. During the application period: short, frequent checks on dates, routes and any change to entry requirements.
3. Offers and acceptance: check messages on response dates, deferral, scholarships and accommodation. These are the questions applicants worry about most.
4. Before the term or semester starts: orientation, enrolment, timetable. See our note on keeping admitted students engaged.
5. After the start: retire what expired and review the questions handled badly. Mid-year intakes need their own pass. For the initial corpus, see how to train an AI chatbot on your school's data.

Owners, versions and traceability

Content without an owner goes stale. Three roles are enough for most providers:

• Content owner (fees, courses, student services) fixes the source and declares the change.
• Knowledge-base manager reindexes, removes the old document and checks the result.
• Approver, usually the head of admissions, signs off anything that commits the institution: fees, requirements, dates.

For each document keep an upload date, an expiry or next-review date, the intake it covers and the owner's name. A change log answers "why did the agent say that yesterday?". Check that your platform supports this metadata and rollback; do not assume it.

Expired documents should be removed from the index, not merely down-weighted. If you must keep the history, archive it outside what the agent can search.

When a date or requirement changes overnight

A moved closing date, a cancelled information session, a corrected fee: these arrive mid-cycle. Prepare a short route:

1. The owner corrects the source page.
2. The manager reindexes and removes the old version the same day.
3. A test question on the changed point confirms the new answer.
4. Meanwhile, a temporary instruction ("for this topic, hand over to an adviser") can suspend the automatic reply. Confirm your tool allows it before you need it.
5. The log records the time of the fix.

Set your own target for how long a wrong fact may circulate; the aim is that it never survives a working day.

Test freshness instead of hoping

Build a small question set whose correct answer changes over time: "When do applications close for next year's intake?", "What does the Bachelor cost?", "Is there an interview?". After every significant update, rerun it and mark each answer correct, cautious or out of date. Only the first two pass.

Add trap questions about last year, or about a figure that no longer exists. A good answer names the intake and points to the source page. For the wider context, see the guide to AI chatbots in student recruitment.

Consumer law, privacy and admission decisions

Australian providers are regulated by TEQSA, and information given to prospective students sits under consumer law as well as sector rules; treat the agent's answers as part of the information you publish. Check what applies to your registration with your compliance team.

Keep applicant files, results and emails out of the knowledge base. For privacy, the OAIC administers the Privacy Act and the Australian Privacy Principles; agree retention and handling with your privacy officer.

The EU AI Act lists systems intended to determine access or admission to educational institutions as high-risk. That is EU law, relevant if you recruit in Europe. An information agent answering from published pages is not automatically in scope, but it moves closer if it ranks or screens applicants. So no screening rules belong in the knowledge base.