Skip to content

Agent platform

Testing AI agents: dry run and shadow mode

Before an agent changes anything, it should show what it would do. For document processing, the path leads from the dry run through shadow mode and a test week to release for everyday use.

In short

Testing an AI agent means running it without effect first. For document processing in ENGIVERITY, real documents follow in shadow mode, and only after a test week in which the result is compared with your postings does the agent go into daily work.

Updated: November 2026

Why an agent runs alongside first

An agent that reads documents makes mistakes at first, like any new colleague. It is better to see them before they become a posting. That is why we introduce agents that read documents in four steps, and each step brings the agent a little closer to real effect. Shadow mode and test week exist for document processing in ENGIVERITY, and a dry run also in Documents and in Ad Pilot.

How an agent is set up is described on the page building agents. Who approves and where the limits lie is covered under approval and control.

Introduction path

How an agent is introduced

The sections below walk through each step.

01 Dry run The flow shows what it would do without changing anything.
02 Shadow mode In ENGIVERITY the agent reads real documents, checks them and hands over only a preview.
03 Test week Its result is compared with the actual postings and accepted.
04 Release for daily work An administrator switches the document type to live operation.

The dry run shows what would happen

A dry run plays a flow through and leaves out the effect. You see the steps and the result before anything takes hold. What it looks like depends on the module.

By module

Dry run in the modules

Dry run by module
ModuleWhat the dry run does
ENGIVERITY In the flow workshop the system checks a template and plays it through. If defects need fixing, an assistant helps.
Documents Every flow can be run as a trial. A real execution happens only on explicit instruction.
Ad Pilot The advertising platform itself checks a change without applying it. Today Ad Pilot does not write back into the ad account.

In shadow mode the agent works on real documents

Document processing in ENGIVERITY starts each document type in shadow mode. The agent reads, checks and presents documents to a person, exactly as it will later in daily work. The handover to a target system, however, produces only a preview.

Everything produced carries the mark provisional. It appears in the file, for PDF also in the file name, and in every log entry. That way nobody mistakes a preview for a posting.

Only an administrator can switch to live operation. They must give a reason, and the switch is entered in the log. Live operation is off from the start and needs details from you.

The test week measures against your postings

For each document type a test week runs in shadow mode. It compares what the agent has read with what your books actually show.

  1. You upload the export of your postings for the period.
  2. The system sets side by side, per document and field, what was read and what was posted.
  3. An error list shows every deviation with the excerpt from the scan.
  4. An administrator accepts the week. The record is available as an Excel file and as a PDF.

The acceptance target comes down to one strict rule. A field the system considered certain and that was wrong anyway must not occur. Beyonetix quotes accuracy figures only after measuring on your documents, because handwriting and layouts differ from company to company.

Switches per target and blocked areas

Every handover target has its own switch, and it is off from the start. It can be switched on only with a reason, and the change is entered in the log. A file is created only when three conditions coincide. The document must be confirmed, the document type must run in live operation, and the switch must be on.

Individual employees' hours are a case of their own. Timesheets and hour records stay blocked until an administrator has recorded the sign-off from data protection and the works council. That is a matter of co-determination in your company, and Beyonetix does not pre-empt it. Such documents also arrive by upload only, never by email.

When an agent goes into daily work

Release for daily work is a decision for an administrator and depends on conditions that can be put into words.

  • The test week for the document type is accepted.
  • The roles that confirm documents and settle cases are named.
  • The consent for reading documents is in place, and for hours the sign-off from data protection and the works council as well.
  • Everyone involved knows where the handover can be switched off again.

If the test week shows problems, withdraw the release. The document type then works in shadow mode again. The path of a document that an agent processes in daily work is described on the page document processing.

Questions and answers

Questions about testing agents

How long does the introduction take?

That depends on the document types and on details you need to supply, such as the target system, the chart of accounts and sign-offs from your own organisation. One test week per document type is part of it.

What is the difference between dry run and shadow mode?

A dry run shows what a flow would do without anything taking effect. Shadow mode works with your real documents, presents them and hands over only a preview.

Who decides on the move into daily use?

Only an administrator. They need an accepted test week and give a reason, and the switch is entered in the log.

What happens with time recording data?

They stay blocked until an administrator has recorded the sign-off from data protection and the works council together with the file. Until then you see only the notice about the block.

Which document type should your test week start with?

We go through document types, target system and people involved with you and set the introduction path.