Skip to main content
Audact
See the offer

Part of the Audact layer

The evidence bundle an auditor actually asks for.

Manual pack on request · generator: Planned

A FRIA where the customer's deployment falls within Article 27, Article 50 templates, an AI literacy log and an ISO 42001 skeleton (not a certification). Put together by hand, on request, against the receipts your own deployment produced rather than a document last touched in March. We do not ship an evidence artefact we have not tested ourselves: the generator that would assemble it automatically is planned; the production export it needs was retested on 26 August, measured on browser calls rather than over a telephone line.

  • Included in Agency Voice
  • Auditor-ready export
  • Patent-pending governance stack (UK IPO)
Talk to salesSee the pack

Contents

Eight artefacts, each mapped to a specific expectation.

  • AI fact-sheet

    Produced on request

    One page per AI system you operate: provider, model, use case, jurisdiction and deployment-risk tier.

  • Model matrix

    Produced on request

    A versioned table of every LLM, speech-to-text and text-to-speech provider, with model identifiers, a change log and the EU sub-processor flag.

  • Policy versions

    Produced on request

    A hashed snapshot of the governance policies inside the configuration seal, with the differences between versions.

  • Article 50 templates

    Produced on request

    Disclosure copy per language and per jurisdiction, with the sign-off log. Ready to hand over on request.

  • Evidence summary

    Produced on request

    Aggregate counts of interactions, disclosures and exceptions, with the Merkle root of each window carried alongside. Checking inclusion against that root uses the inclusion proof from the call's Article 50 report, set against the root published at api.audact.ai/v1/metachain.

  • AI literacy log (Article 4)

    Produced on request

    Training completion per role: who was onboarded on which model risk, and when.

  • FRIA (Article 27)

    Produced on request

    Produced where the customer's deployment falls within Article 27. Fundamental Rights Impact Assessment, pre-populated from your deployment. Editable and exportable.

  • ISO 42001 skeleton (not a certification)

    Produced on request

    A structured starting point for your own management-system work, pre-populated with the Audact controls.

Why it exists

A standing record instead of a point-in-time report.

Much of what a large advisory engagement produces can be produced from the evidence chain instead: authenticated and machine-checkable.

That matters most at the moment the evidence is asked for. A report is stale the day it ships; a pack drawn from the chain reflects the deployment as it is when you export it.

  • Procurement questionnaires: hand over a versioned pack instead of filling in a template.
  • A supervisory-authority enquiry: request the pack the same day; the generator is planned.
  • Audit preparation: the AI-management-system controls are already populated.
  • Insurance underwriting: a structured, versioned view of your deployment posture as it changes.

Cover

What sits behind it.

The generation path from a live deployment to a FRIA, and the multi-jurisdiction overlay logic underneath it, are part of Audact's patent-pending governance stack, filed at the UK Intellectual Property Office. Applications are pending; nothing here is granted, and nothing here is a certification.

Next step

Audit-ready, every day.

The Assurance Pack is included in an Agency Voice agreement. Status: Manual pack on request · generator: Planned. Start with white-glove onboarding, or ask us to put together an anonymised pack from a reference deployment (a related party, disclosed in full on the customers page) so you can hand it to counsel first.

Apply for a founding seatTalk to engineering

Related