An AI knowledge base for audit methodology

“Should we be using the new checklist?”

Suppose the methodology owner approves a new internal checklist. The accompanying notice says it applies to engagements starting after the change takes effect. The team started its engagement earlier and has already completed part of the previous checklist. The notice does not explain whether teams on earlier engagements may choose to switch or who would approve that decision.

The assistant should find the new checklist together with the notice describing when to use it. In this example, an answer could say: “Your engagement started before the change. The notice says the new checklist applies to engagements started after it took effect.” It should also link to the relevant passage so the engagement lead can read the full statement.

Whether the team can choose to switch during the engagement remains an open question for the methodology owner. The notice does not answer it. AI can help frame that question, explaining that the engagement predates the change and that the earlier checklist is partly complete. Those facts are enough to explain the issue without giving the assistant client workpapers.

The methodology owner and engagement lead decide whether to switch under the firm's policies. The assistant helps locate the guidance they need for that discussion. Evaluating and approving the audit work remain the team's responsibility.

What needs to accompany the guidance

Someone looking for an answer needs more than the newest file in a folder. They need to establish who approved the guidance, which engagements it covers, and when it applies. If work already underway should be treated differently, the author needs to explain that. A file's saved date cannot supply the missing policy.

The previous version may still be needed to explain which instructions the team used. The library should preserve the relationship between versions and describe when each applies. That allows “What should we use for a new engagement?” to lead to a different document from “What guidance did we use when we started this engagement?” The library owner is responsible for documenting that distinction and filling gaps in the guidance.

An assistant is useful if it can find this information when people describe their problem in their own words. When the author has omitted transition guidance, the answer should identify what is missing. The team then knows what to ask, rather than receiving an apparently complete instruction.

Publishing guidance and updating engagement files

Before commissioning a separate knowledge base, check what your current software handles. If people simply struggle to find an approved template, organizing the library and improving change announcements may be enough. A different problem arises when the team knows which version it needs but does not know how updating will affect its work in progress.

For example, Caseware Cloud Engagements 2026-08 describes template version management from draft through publication, but that change is for enterprise authors. In the separate Audit product, the update-method documentation shows that update methods can treat engagement-level edits differently and that update checks are disabled for a document signed off as complete. These are distinct features in different product contexts. A useful question for your administrator is: how does our system carry a firm template change into an active engagement, and what happens to the team's existing work?

Discuss the update method with whoever manages that system. A knowledge base can help locate the firm's instructions, but a chat answer does not confirm that a particular engagement's files have been updated. That is a separate action in the software where the team does its work.

Assessing whether a knowledge base helps

Start with a small collection of approved methodology and a few questions recently sent to its owner. Include one about an engagement that began before a change. The methodology owner can check whether the answer finds the right passage and preserves the condition that determines when it applies. A team member can judge whether the answer is usable without another search through folders.

If every answer ends by referring the question back to the author, look at why. The library may be missing the guidance people ask for most often. Writing it down would then be the first useful change. A separate assistant has a stronger case when the answers already exist but are scattered across instructions and change notices.

Syntalith builds Company Brain applications that connect employees' questions with the firm's knowledge sources. For an audit team, an initial scope could cover the internal methodology library and its change notices. Once we agree on the scope, we can connect those materials to an assistant that identifies the answer's source and relevant version, with access set by the firm. The methodology owner would assess the answers. This work can be considered without connecting client files.

For a first conversation, describe a question that keeps coming up after guidance changes and where the firm publishes its explanations. You do not need confidential documents or a full specification to start that discussion. See Syntalith's pricing page for commercial information. If the challenge also involves separating shared guidance from individual clients' records, read about access boundaries in a law firm's AI knowledge base.