How do you keep a knowledge base up to date without hiring someone for it?
Make maintenance automatic by tying every answer to an owner, a sign-off date, and an expiry. Employees ask in their own words, Duna matches questions to curated Q&A, and flags ageing answers as Indicative. The system routes unclear or expired topics to the right expert, requests a re-verification, and republishes as Verified. No content manager required.
Treat updates as a by-product of real questions, not a side project. In Duna, company knowledge lives as curated Q&A, each answer signed by a named expert with a date and an expiry. When someone asks, Duna presents existing knowledge, it does not generate new content. The result is simple: answers are either Verified with source and date, Indicative if ageing or awaiting confirmation, or Routed to the right expert when confidence is below the threshold.
Here is how it works in practice. Matching is language-agnostic, so an employee can ask in Polish and get matched to an answer curated in Dutch. If the match meets the confidence threshold and the answer is within its expiry, Duna returns the Verified answer and shows who signed it and when. If the answer is close but past its expiry or flagged for re-check, Duna shows it as Indicative and automatically asks the signer to re-verify. If no curated answer qualifies, the question is routed, with an explainable confidence trace so the expert sees what was tried. Attachments are not indexed, so search runs only on curated answers.
Say a shift supervisor asks, What is the current lockout procedure for Line 3 during maintenance. Duna matches this to the lockout Q&A, but the answer expired last week. The supervisor sees the Indicative label and the last signer’s name and date, so they know to pause and expect a confirmation. Duna sends a re-verification request to that expert. The expert edits the step order to reflect a new checklist, signs off, and the answer returns to Verified. The same re-verification loop runs without a project plan or a content administrator.
Governance is built in. Teams decide expiry periods per topic, for example quarterly for safety steps, annually for HR policy, or no expiry for facts that do not change. Ownership is explicit, and responsibilities can be reassigned if roles change. Every change leaves an audit trail with versions, comments, and dates. Hosting is in the EU in Germany or fully self-hosted, and confidence is explainable, which helps experts review suggested matches quickly. Over time, unanswered questions become new Verified Q&A, so coverage grows as a by-product of everyday work.
Related questions
Who sets expiry dates and how should we choose them?
Expiry is set per answer by the expert or owner at sign-off. Choose a period that matches the rate of change for that topic, such as monthly for fast-moving procedures and yearly for stable policies. You can adjust the period later, and Duna will use it for reminders and labels.
What happens if the signer is away or leaves the company?
Re-verification requests can be reassigned to a new owner at any time. If no one responds, the answer remains Indicative until it is re-verified, and the routing rule sends new questions to the designated team or fallback expert. The audit trail preserves previous versions and sign-offs.
What if my question has no answer yet?
If no curated answer meets the confidence threshold, Duna does not guess. It routes your question to the right expert, along with the explainable match context. Their reply becomes a new Verified Q&A with an owner, a date, and an expiry, so the next person gets the answer immediately.
Duna keeps company knowledge as verified question-and-answer pairs, so an answer either carries a named expert and a date, or it does not appear at all. Book a 15-minute demo.