Skip to main content

Security & governance

Auditability and Logs

Know what each agent did, why and with whose approval. Logs and records make it possible to review a decision, investigate an exception and improve the workflow.

Conceptual agent action passing an access gate, a human approval checkpoint and an audit log, with one action stopped at a lock, linked by purple particles.

What can be recorded

The level of detail is agreed with you, balancing traceability with data minimisation.

Actions

Tool calls, system updates and their results.

Approvals

Who approved, corrected or rejected a proposed action.

Evidence

The inputs and sources used for a decision, where retention is agreed.

Using records in practice

Records serve operations, not just compliance.

01

Trace

Follow one item from input to outcome.

02

Investigate

See why an exception happened.

03

Report

Summarise outcomes for an agreed period.

04

Improve

Use patterns to refine instructions and tools.

Retention is agreed, not assumed

Logs can contain personal data, so they follow the same rules as other records.

  • Agree what is logged and for how long.
  • Restrict who can view detailed records.
  • Export records when you need them for review.

Common questions

Export options are agreed during scoping, for example reports or data delivered to a system you control.

Only where agreed for the workflow, for the agreed period.

We choose the model and provider for each task during scoping, based on the language, accuracy, latency and data-handling requirements. The workflow is not tied to one provider, so a step can be changed later if the agreed requirements change.

Discovery call

Start with the work that slows you down.

Bring us a process, a recurring enquiry or a pile of documents. We will explore where agents fit and what a useful implementation needs.

Book a discovery call