Content owner
- Owns
- The calendar, handbook, or policy set — and whether it is current.
- Does not
- Does not hand Retriive the right to rewrite institutional policy.
Assurance
If it cannot be cited,
it does not ship.
CampusQ is built for institutions that will be asked — by a student, an auditor, or a dean — where an answer came from. This page is the contract behind that expectation.
The answer contractThree things every response
Three things every response
has to carry.
This is not a style guide. It is the minimum bar for anything CampusQ is allowed to say in production.
A live source
The claim comes from a current institutional document your team owns — not a stale scrape, not model memory.
A precise citation
The response points to the section it used. If CampusQ cannot show the source, it does not invent the answer.
A recoverable trail
Questions, answers, and sources are logged so advising, compliance, and security can reconstruct what happened.
Who stays accountableThe model answers.
The model answers.
People still own the truth.
CampusQ does not absorb institutional authority. It surfaces it — with a named owner behind every source.
Operational owner
- Owns
- Which cohorts see CampusQ, how exceptions escalate, and what “good enough” means for your queue.
- Does not
- Does not get replaced by the model on high-stakes judgment calls.
Retriive
- Owns
- Indexing, retrieval quality, evaluation tooling, and the technical layer that keeps answers cited.
- Does not
- Does not become the authority on what your institution teaches or requires.
Evidence before expansionProve it on your questions
Prove it on your questions
before you widen access.
A polished demo on someone else's content is not evidence. We score CampusQ against the documents and queues you already run.
Citation accuracy
Measured on your questions against your sources — not a generic demo corpus.
Coverage gaps
The questions your documents do not yet answer, surfaced as a list your owners can act on.
Queue impact
Volume, topics, and deflection measured on real traffic once a cohort is live.
When those numbers hold, the deployment path moves from a grounded pilot to a department cohort — still on your traffic, still with a place to stop.
Product boundariesWhat CampusQ will
What CampusQ will
not do.
Trust is easier to keep than to rebuild. These limits are intentional.
No uncited claims
CampusQ is built to refuse confident answers it cannot ground. Silence beats a plausible guess.
No orphaned knowledge
Sources stay in your systems. Retriive indexes them; your owners keep the originals and the update path.
No black-box handoff
Admin access, evaluation evidence, logs, and runbooks transfer with the deployment — not months later.
After go-liveYou keep the controls
You keep the controls
that matter in a review.
Sources, admin access, audit history, evaluation evidence, and operating docs travel with the deployment. Retriive can co-manage the technical layer — without becoming a single point of hidden knowledge.
Get started
Bring the questions that already fill your queue.
We measure citation quality on your sources first. Expansion comes only after the evidence holds.