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: tuition, admission averages and prerequisites, application routes and dates. Keeping it current is an organizational 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 describes this as a way to reach external knowledge and keep it updated. Change a document and the answers can change, without retraining.

The flip side: if last year's viewbook 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 tuition table pasted into a working document nobody maintains.
• Changes outside the process: a revised prerequisite approved by a faculty council 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 advisor.

A review rhythm tied to the Canadian cycle

Canadian admission is provincial, and routes differ. In Ontario, many applications to universities go through OUAC, while other provinces use their own application services or apply directly to the institution; for applicants coming from Quebec, the CEGEP route adds a different set of prerequisites and timelines. Describe the route that applies to each program on your own pages before the agent talks about it, and say who the page is for (Ontario secondary students, out-of-province, international, mature).

1. Before applications open: a full review of fees, programs, prerequisites, supporting documents and process pages. Archive anything tied to the previous intake.
2. During the application period: short, frequent checks on dates and routes.
3. Offers and acceptance: check messages on response dates, deposits, scholarships and residence applications. These are the questions admitted students worry about most.
4. Before the term starts: orientation, residence, registration. See our note on keeping admitted students engaged.
5. After the term starts: retire what expired and review the questions handled badly. 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 institutions:

• Content owner (fees, programs, student services) fixes the source and declares the change.
• Knowledge-base manager reindexes, removes the old document and checks the result.
• Approver, usually the director 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 deadline, a cancelled open house, 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 off to an advisor") 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 business day.

Test freshness instead of hoping

Build a small question set whose correct answer changes over time: "What is the application deadline for next fall?", "What are the fees for the BA?", "What is the prerequisite for the first-year program?". 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.

Personal information and admission decisions

Keep applicant files, transcripts and emails out of the knowledge base; it should hold publishable information. The Office of the Privacy Commissioner of Canada is the federal reference on privacy; provincial public-sector rules and, in Quebec, Law 25 may also apply depending on your institution. Settle 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.