Start with a small collection of information people ask for regularly. A service guide, escalation policy and pricing sheet may cover more than a large document dump. Name an owner for each source.
Resolve contradictions before connecting the material. If a policy and a shared spreadsheet disagree, decide which one governs the response. Record when the source was last reviewed and where the next version will appear.
Test ordinary questions alongside gaps and exceptions. If the answer depends on something that changes daily, decide how that information will be checked. Give the workflow a clear way to ask someone for help when it cannot find a reliable answer.
Choose sources that can answer real questions
Start with questions people have asked in the last week. They may want to know which services a branch offers, who can approve an expense or how to move an appointment. Identify the document that should govern each answer. A small set of current guidance is easier to review than a shared folder containing years of drafts, archived rates and conflicting policies.
Give each source an owner and a review date. A person should know which document can be edited and where a replacement appears. Separate information with a clear expiry, such as seasonal opening hours, from procedures that change less often. A source may need a location or audience attached so the wrong branch or team does not inherit its rules.
Resolve contradictions and access before connecting
Look for duplicated material with different wording or figures. If a service sheet lists one price and an internal document another, ask the owner which applies and remove the outdated version from the sources used for answers. Record any genuine differences, such as a branch-specific price, with enough context for someone to pick the right one.
Agree which information each workflow needs to read. A customer-facing call can use approved service information while a management briefing might need figures available only to a small group. Give the workflows access to the sources appropriate to their purpose. Keep confidential material with the people and processes that use it.
Test for gaps as well as good answers
Build a short list of questions with known answers, questions that require live information and questions nobody can answer from the current documents. Ask reviewers to compare results with the original sources. Where a fact is missing, the right response may be to say it needs checking and create a task for the information owner.
Use the first few weeks to spot sources people still have to replace manually. If the same policy question goes to a colleague every morning, check whether the source is missing, outdated or hard to identify. Fix the source first, then retest the answer. That is usually more sustainable than adding instructions around an unreliable document.
Give temporary changes an end date
Temporary closures, seasonal prices and interim approval limits deserve a clear start and end date. If the information is still in use after the date passes, route the question back to its owner for review. This is particularly useful when a public announcement and a staff guide are updated at different times. Add a simple way for colleagues to flag content that seems out of date.