Products/udX/udX Audit
Part of the udX family

udX AuditWhen the governing source changes, your documents follow.

Many documents (contracts, internal policies, templates) must satisfy a governing source: a law, a regulation, a master template. When that source changes, every affected document has to be updated. udX Audit automates exactly that: it detects the change, derives the precise edits needed, and presents them for your approval.

The principle

Two document roles, one audit relationship.

udX Audit works with two document categories. The governing document is the reference being checked against: a statute, a regulation, a master contract, an internal policy. The target document is the one that has to satisfy it: a specific customer contract, a derived work instruction.

This structure is what makes the audit precise: instead of re-reading whole documents on every change, udX Audit knows exactly which requirement of the source maps to which passage of the target.

  • Governing documentThe reference: law, regulation, master template or internal policy.
  • Target documentThe document that must comply: a customer contract, a work instruction, a policy derivative.
  • Human in the loopThe AI detects and proposes: a person reviews, approves and stays accountable.

How it works

From first mapping to continuous monitoring.

01

Initial audit

On the first comparison, udX Audit determines what from the governing document is already satisfied in the target, and whether the target is supposed to satisfy each requirement at all. Not every clause of a source applies to every target.

02

Requirement mapping

The result is a reliable mapping between source requirements and target content: the foundation for every later check.

03

Continuous monitoring

From then on, udX Audit checks at a configurable interval, or on demand, whether the governing document has changed.

04

Change proposal as tracked changes

When a change is detected, the necessary edit is drafted directly in the affected target document as a visible tracked change: never as a silent overwrite.

05

Review & approval

Every proposal is presented for review. Only after explicit approval does the change become final.

Core functions

What udX Audit does.

Source-target mapping

Initial audit of which source requirements apply to and are satisfied by the target document.

Change detection

Automatic monitoring of governing documents for substantive changes.

Configurable audit cycles

Scheduled at the interval you choose, and additionally triggerable manually at any time.

Tracked changes

Proposed edits are marked traceably in the target document: the track-changes principle.

Review & approval

Nothing is finalised without an active human confirmation.

Scales across portfolios

A single source change can be applied to every affected target document in one automated pass.

Typical scenarios

Where udX Audit earns its keep.

Updating internal policies after a new regulatory circular (e.g. BaFin)
Adjusting contract clauses after a change in legislation
Reconciling customer contracts against an updated master template
Continuous compliance checks of large contract portfolios against evolving standards

udX Audit is specialised in the structural audit relationship between exactly two document roles. Its sibling udX Chat answers open, free-form questions across your entire document base.

Discover udX Chat

Never miss a change in your governing sources.

Book a free 30-minute call. We show you udX Audit live and tell you honestly whether it fits your compliance process.

Book a demo

Frequently asked questions

What does udX Audit do?

udX Audit monitors governing documents such as statutes, regulations or master templates for changes. When the source changes, it derives the edits required in the affected target documents and presents them as tracked changes for approval.

What is the difference between a governing and a target document?

The governing document is the reference being checked against: a statute, a regulation, a master contract or an internal policy. The target document has to satisfy that reference, for example a specific customer contract or a derived work instruction.

Does udX Audit change my documents on its own?

No. Every edit is proposed as a visible tracked change in the target document, never as a silent overwrite. A person reviews, approves and stays accountable. The AI detects and proposes; a human decides.

Why is this more precise than re-reading the documents?

Because the initial audit builds a reliable mapping: which requirement of the source applies to which passage of the target, and whether it applies at all. Later checks only examine what is genuinely affected instead of re-reading everything.