Workflow library

An auditor’s request list, answered inside the agreed scope.

The agent reads each request, finds the documents and the job records that answer it, and builds the evidence pack. It reads only inside the scope of the audit. Your compliance lead releases the pack.

DesignedThe steps and approvals are designed. It has not run yet.

A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.

An AI agent for audit evidence collection answers the request list that arrives before an audit: show the approvals for this process, the training for these roles, the records for these jobs. Today people search several systems to answer it, and the answer is rebuilt for each audit. The agent builds it from your systems and from the record of each job that ran on Ares.

This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.

What the compliance lead gets

  • Each request with the documents that answer it, and each gap named.
  • The record of each agent job in scope, as a replay pack the auditor can check offline.
  • A pack that leaves only when the compliance lead releases it.

The compliance page maps published guidance to what Ares does. The full library is on the workflows page.

The steps

One audit request, one site, one period.

The site, the period and the requests are examples. The scope is written into the credential, so the agent cannot drift past it.

  1. 01Ticketing

    Take the audit request and receive a credential for this audit scope only: one site, one process, one period.

    Who approves
    No approval on this step
    On the record
    credential issued · one audit scope
  2. 02Ticketing

    Read the auditor’s request list from the audit ticket.

    Who approves
    No approval on this step
    On the record
    read-requests · allowed
  3. 03Documents

    Find the approved procedures and the signed records that answer each request.

    Who approves
    No approval on this step
    On the record
    collect-documents · allowed
  4. 04Documents

    Try to read the same records for a second site. That site is outside the scope of the credential, so the step is refused.

    Who approves
    No approval on this step
    On the record
    read-other-site · refused · outside audit scope
  5. 05Documents

    Attach the record of each agent job in scope as a replay pack.

    Who approves
    No approval on this step
    On the record
    attach-replay-pack · allowed
  6. 06Office suite

    Build the evidence index: each request, its documents, and each request with no document on file.

    Who approves
    No approval on this step
    On the record
    evidence-index · allowed · gaps named
  7. 07Email

    Release the evidence pack to the auditor. The step waits until the compliance lead approves it.

    Who approves
    Compliance lead
    On the record
    release-pack · approved by compliance lead
  8. 08Email

    Send the pack. Staff home addresses in one training file are taken out before it leaves.

    Who approves
    No approval on this step
    On the record
    send-pack · redacted · staff personal details

The systems, by type

We name systems by type. Yours are named in the assessment.

Ticketing

Holds the audit request and its list. The agent reads it and posts the pack for release.

Documents

Holds the procedures, signed records and training files. The agent reads only those inside the scope.

Office suite

Holds the evidence index the compliance lead reviews: request, evidence, gap.

Email

Carries the released pack to the auditor, checked on its way out.

The approval, the refusal, the record

  • A person approves: Release the evidence pack to the auditor. The step waits until the compliance lead approves it.What an auditor receives becomes your statement of how the process ran, so the compliance lead reviews the pack and its gaps before it leaves.
  • Refused: Try to read the same records for a second site. That site is outside the scope of the credential, so the step is refused.The audit covers one site and one period, and the credential says so; records outside that scope are not the agent’s to read, even when they might help.
  • On the recordEach request, each document read, the refused read outside the scope, the gaps, the release with a name, and what was taken out of the pack.
The record

What goes on the record

  1. credential issued · one audit scope
  2. read-requests · allowed
  3. collect-documents · allowed
  4. attach-replay-pack · allowed
  5. evidence-index · allowed · gaps named
  6. release-pack · approved by compliance lead

One record per step, as designed. This workflow has not run yet.

What it does not do

  • It does not answer the auditor’s questions or argue a finding. Your people do.
  • It does not certify you against a standard. We map requirements to what Ares does; we do not certify the customer.
  • It cannot produce evidence that does not exist. It names each gap.
  • The replay pack covers jobs that ran on Ares. Work done elsewhere has only the evidence your other systems keep.

Questions and answers

Tell us about one workflow.

We will say whether an agent should do it, and what the first step costs.

A senior member of the team replies within two business days.