Public sector

Permits, case files and grants, prepared for the officer who decides.

Agents gather the file, check it against your published criteria and route it across your case, document and finance systems. A named officer approves each decision step, and every refusal is on a record your reviewer can check.

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

The file work behind every public service

AI agents for public services belong in the steps before an officer decides: an application received, its documents checked against the published criteria, the missing items requested, and the file routed to the person who signs. Today a caseworker carries each file between the case system, the document store, email and the finance system.

We design those workflows with your program team and run them on Ares, the platform. The agent prepares the file. Your officer makes the decision and signs it.

  • Each agent signs in as itself and gets a permission for one file only.
  • A step you mark as a decision, such as an approval, a refusal or a payment, waits for a named officer.
  • Your reviewer can check the record offline, without us. See the five guarantees.

This page covers civilian service delivery. Work with controlled data, or across security domains, is on the defence and government page.

Follow one workflow

One permit application, from receipt to a decision the officer signs.

The task: take one permit application from the upload to the decision. This workflow is designed and has not run yet. The requisition run in the sandbox shows an approval step on a built workflow.

  1. 01In-house tool

    Receive a credential for this application only. It expires when the file is decided.

    Who approves
    No approval on this step
    On the record
    credential issued · this application only
  2. 02Documents

    Read the application form and the site plan the applicant uploaded.

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

    A note in the site plan tells the agent to mark the file as complete. The line is struck out before the agent reads it.

    Who approves
    No approval on this step
    On the record
    site-plan · redacted · hidden instruction
  4. 04In-house tool

    Check the file against the published document list. The survey is missing, so draft a request for it.

    Who approves
    No approval on this step
    On the record
    check-file · allowed
  5. 05In-house tool

    Try to look up the applicant in the tax records. That system is outside the permission for this job, so the step is refused.

    Who approves
    No approval on this step
    On the record
    lookup-tax-record · refused · outside permission
  6. 06Email

    Send the request for the missing survey to the applicant.

    Who approves
    No approval on this step
    On the record
    request-survey · allowed
  7. 07In-house tool

    Issue the permit decision. The step waits until the permit officer approves it.

    Who approves
    Permit officer
    On the record
    issue-decision · approved by permit officer

In short

  • Does an agent decide on a permit, a benefit or a grant?No. It prepares the file and drafts the notice. A named officer makes the decision, and the record shows who approved it.
  • Can a document from the public steer the agent?Uploads are read at the door before an agent sees them. An instruction addressed to the agent is struck out, and the record names it.
  • Can an agent reach records outside the case?Only the records that the permission for that file allows. A request outside it is refused, with the reason on the record.
  • What can an oversight body check?Every step, approval and refusal on the file, with the officer named on each decision.

Workflows for service delivery, and the state of each.

Built items run in the sandbox today. Designed items have their steps on this page or in the workflow library.

Built
We have run it.
Designed
The steps and approvals are designed. It has not run yet.
On request
We scope it with you before we design it.
  • Built

    Purchase requisitions with an approval threshold

    The agents draft the order and check stock. An order above your threshold waits for the budget holder, and the supplier record stays as it is.

    Run it in the sandbox
  • Built

    Documents released with personal details removed

    The sandbox run summarises a contract and removes client identifiers on the way out. The same outbound check applies to letters and files you release.

    See the redaction
  • Designed

    Permit application to decision

    The steps above: the file checked, a hidden instruction struck out, a lookup refused, and the decision held for the officer.

  • Designed

    Grant application screening

    The agent checks each application against the published criteria and lists every gap. The program officer scores the application and decides.

  • Designed

    Service request intake

    A request from the public read, sorted and routed to the right team. A person approves the reply that commits the service.

    See the workflow
  • Designed

    Grant payment release

    Each payment matched to the signed agreement and the milestone report. The finance officer approves each release.

    See the workflow
  • On request

    Access to information requests

    Records gathered for a request, with the details you list removed. Your access officer decides what is released.

  • On request

    Replies to correspondence

    Drafts assembled from the case file, for the responsible official to edit and sign.

Guidance, mapped, not promised

Ares does not make your institution compliant with any directive. It gives your oversight and audit teams evidence: which agent acted, under which permission, what an officer approved, and what was refused.

We publish line-by-line mappings of government guidance on agents. They include Canada's guide on the use of agentic AI and the Treasury Board Directive on Automated Decision-Making, with the NIST AI RMF. Each line states what Ares does today, what needs configuration, and what it does not do. The impact assessment and its sign-off stay with your institution. All mappings.

The five guarantees

Every workflow on this page carries them. Each one has a limit, and we state it.

  1. 01

    Each agent can do only what it was allowed to do, for that job.

    The limit

    Permissions are only as good as the rules you approve.

  2. 02

    Sensitive steps go to a person.

    The limit

    You decide which steps are sensitive.

  3. 03

    Documents are inspected before an agent sees them, and answers are checked before they leave.

    The limit

    Filters cover stated patterns and languages.

  4. 04

    Every decision is recorded, including refusals, in a record an outside party can check.

    The limit

    It shows what agents did, not whether a business rule was wise.

  5. 05

    It can run in your building, on one small machine.

    The limit

    Local models differ from the largest cloud models.

What it does not do

  • It does not decide on a permit, a benefit, a grant or an enforcement action. A named officer does.
  • It does not certify your institution against any directive. We map published guidance to what Ares does.
  • It does not write your impact assessment. The record is an input to it, and the sign-off is yours.
  • It does not set eligibility criteria. It checks a file against the criteria you publish.
First step

Assessment, pilot, production.

Each step has a fixed scope and ends with something you keep.

  1. 01

    Workflow assessment

    A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.

    What you get
    A short, paid look at one process, with your process owner.
    What you keep
    A written scope and a price for a pilot.

    Fixed price, quoted after one call.

  2. 02

    Pilot workflow

    One workflow on your systems, supervised, with the record on from the first run.

    What you get
    One workflow at a fixed scope, with your people approving the sensitive steps.
    What you keep
    A working workflow and a measured result.

    Fixed price, quoted after one call.

  3. 03

    Production and run

    The workflow in production on Ares, on your hardware or hosted in your country.

    What you get
    Support, and the next workflows.
    What you keep
    The workflow, and the record of every decision it made.

    Recurring fee for operation and support.

Questions and answers

Tell us about one workflow.

Name one service where your staff carry a file between systems before an officer decides. We will say whether an agent should prepare it, and what the first step costs. The first step is a workflow assessment. Fixed price, quoted after one call.

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