Define the collection around a decision
A useful first collection is smaller than an organisation’s entire document estate. Choose a decision that people already make, such as finding the applicable installation instruction for a particular equipment family. Identify the documents that support it, the versions that matter and the material that is explicitly outside scope. This makes both success and failure easier to recognise. A broad search box can hide uncertainty behind apparent coverage; a defined collection gives the user a reason to understand what the service can answer and where a different source or colleague is still needed.
Carry permission into the question
Two colleagues can ask identical words while being entitled to different material. The retrieval design therefore needs a reliable way to connect the current user and task to the access conditions of the underlying sources. Discuss what should happen when a document changes visibility or someone changes role. These are operating questions, not merely settings at launch. A review should include realistic cases involving mixed-access collections, so that the team examines what an answer reveals as well as whether a search result itself can be opened by the person asking.
Expose disagreement in the sources
Knowledge collections often contain disagreement for understandable reasons: an older handbook, a regional exception or a working note that never became policy. An answer that blends them into one smooth instruction can remove the very distinction the user needs. Define how the service should represent competing material and when it should ask for context instead of completing the response. The reviewer’s task is then to resolve a visible choice. This is more actionable than discovering later that a plausible sentence quietly combined documents written for different circumstances and different audiences.
Test the absence of an answer
The evaluation set should include questions whose answers are missing from the collection, along with questions that appear answerable until a crucial detail is considered. Observe whether the service recognises the gap, asks a useful follow-up or directs the reader to an appropriate owner. A polished refusal with no route forward may still leave the employee stranded. The desired behaviour is a productive boundary: a clear statement of what is known, what is missing and what information would make the task answerable, without filling the space with invented certainty or irrelevant text.
Operate the collection as a service
Once people rely on retrieval, document stewardship becomes part of the service. Name the owners who can correct material, retire obsolete items and respond when recurring questions reveal a gap. Give feedback a destination beyond a generic thumbs-down button. A report that the installation guide omits a common field condition should reach someone who can improve the source, not only someone who can adjust the answer. The strongest knowledge service creates a practical loop between use and maintenance, so that its source material becomes more useful as well as more searchable over time.
Editorial draft prepared for the BGX concept preview. This is not a regulatory announcement or evidence of a deployed client project.