Ask which staff question the document serves
Identify the intended users and the questions the document is meant to help answer. In a fictional distributor, a product-care guide may support customer-service questions while an unexplained sales export does not serve the same purpose. Record why the item is being proposed rather than accepting it because it is available. A small collection with an explicit purpose is easier to review than an intake queue driven solely by file volume. Keep material outside the agreed use case pending a separate decision.
Find the person who can explain it
Name the business owner who can confirm what the document means and whether it is suitable for the proposed use. The uploader is not necessarily that person. Ask where the original comes from and whether another team maintains it. If nobody can explain an unfamiliar file, do not give it apparent authority by making it part of the staff answer service. Create an intake question with an owner and next action so the uncertainty is visible rather than forgotten in a folder.
Check that the relevant content is readable
Open the actual document and inspect the parts expected to answer questions. Check tables, diagrams, scanned text and attachments rather than assuming a successful upload means their meaning was preserved. Ask the implementation team to show what the service can actually read from a representative section. In the fictional product-care guide, a footnote may qualify an instruction in the table above it. If that relationship is lost, send the document back for preparation or a different approved presentation.
Record the scope and necessary context
Identify which product, department or business process the material applies to. A document may be accurate within a narrow situation but misleading when presented as general guidance. Keep the contextual information staff need alongside the source reference. Do not invent a broader policy from a working note. Ask the owner to resolve unclear scope before intake is approved. The administrative reviewer should identify missing context, while the responsible business person decides what the content is authorised to represent.
Use clear intake decisions
Give each proposed document a state such as accepted for the defined purpose, awaiting clarification or excluded with a reason. Record who made the decision and any preparation still needed. Do not call an item accepted because it was copied into storage. Keep the decision linked to the source so staff can find the supporting explanation. Avoid silently discarding rejected items without informing their owner; the team may still need an approved alternative to answer the original staff question.
Test the admitted material with a real-shaped question
Use an approved question that depends on the document and inspect whether the relevant content is available with its necessary context. Include a question outside the documented scope and confirm the expected referral or uncertainty remains visible. Record any preparation issue discovered through the exercise. This is a check on the admitted source, not proof that the entire knowledge service is ready. Feed unresolved content questions back to the named owner before the document is relied on for ordinary work.