Citation

The value of a corporate answer is not only fluent wording but an inspectable basis. A citation shows the relevant document passage and answers where the information came from.

That reference invites the user to read the source. For policies, prices, contracts, or employee rights with exceptions, surrounding text matters more than a short answer alone.

A useful source is a current passage that actually answers the question. A distant paragraph containing one matching word, or an old version, can create false confidence.

Scope is essential. The assistant’s files, role access, and department should be correct, and out-of-scope documents should not enter the cited result.

Before using an answer, compare the source title, passage, document date, and question conditions. If there is a conflict, keep the current file in scope.

A citation provides an audit trail but is not document management. Updating files, separating old versions, and approving consequential decisions remain team processes.

A useful way to evaluate citation is to follow one real question from the source document to the final answer. Record which file was selected, what context reached the model, and what a reviewer would need to verify. This turns a definition into an operational check and makes the result comparable across teams.

The same check should include ownership and change management. Decide who updates the relevant documents, how an outdated result is reported, and which access boundary applies. KobiGPT can provide the assistant and the cited document context, but the organisation still owns the source material, permissions, and the decision made from the answer.