Skip to content
Services

Three engagements and what each produces.

Assessment, documentation and assurance run in sequence or on their own. All three produce artefacts that a regulator, a notified body, an auditor or an enterprise buyer can read. We do not deliver slide decks summarising what someone else should build.

Assessment

01

Compliance assessment and product remediation

We look at the application as built: its models, data flows, human review steps and the points where it affects a person. We work out which regime applies in each market you sell into. Then we tell you what has to change in the product as well as in the policies.

Built against

  • EU AI Act
  • Law 25 s.12.1
  • PIPEDA
  • Colorado SB 26-189
  • NIST AI RMF

What we examine

  • 01

    A statement of intended purpose, deployment context and affected populations precise enough to survive a classification argument

  • 02

    Your role in the value chain as provider, deployer, importer or distributor. Most scoping goes wrong here first

  • 03

    Model and data lineage: third-party models, fine-tuning sets, retrieval sources and what your vendor contracts permit

  • 04

    Automated decision points, the degree of human involvement and whether that involvement is meaningful or nominal

  • 05

    Disclosure surfaces, synthetic-content marking, logging and retention against Article 50 and the equivalent state provisions

  • 06

    Existing controls: we build the programme on what you have instead of replacing it

What you receive

4 artefacts
  • Art. 6 · Annex III

    Regulatory applicability determination

    A written and reasoned classification per system and per market. It includes the Art. 6(3) analysis where you are arguing out of high-risk.

  • Art. 9–15

    Gap register

    Every gap tied to a specific provision, an owner, an effort estimate and a date. The format is sortable rows instead of narrative.

  • Engineering

    Product change specification

    The interface, logging, oversight and data changes the product needs. We write them so an engineering team can size and schedule the work.

  • Programme

    Remediation roadmap

    Sequenced against statutory dates and your release calendar. It separates what blocks launch from what can follow it.

Documentation

02

Governance documentation and conformity artefacts

The regulator, the notified body, the enterprise buyer and the auditor all ask for the written record in different words. We write it in the structure the instrument specifies. We build it to survive the next model version without a rewrite from scratch.

Built against

  • EU AI Act
  • EN 18286
  • ISO/IEC 42001
  • ISO/IEC 42005
  • ISO/IEC 23894
  • OSFI E-23

What we examine

  • 01

    What documentation already exists, in what form and how much of it can be recovered rather than replaced

  • 02

    Where the facts live (repositories, model cards, evaluation runs and incident logs) and who is accountable for keeping each current

  • 03

    The change surface: what a model update, a new data source or a new market does to each artefact

  • 04

    The evidence trail behind each claim: a technical file that cannot be substantiated is worse than none

What you receive

7 artefacts
  • Art. 11 · Annex IV

    Technical documentation file

    All nine sections: system description, development process, monitoring, functioning and control, performance metrics, risk management, lifecycle changes, standards applied, declaration of conformity and post-market monitoring plan.

  • ISO/IEC 42005:2025

    AI system impact assessment

    Scoped assessment of benefits and harms to individuals, groups and society. We record the analysis instead of asserting the result.

  • Art. 9 · ISO/IEC 23894

    Risk management system record

    A continuous and iterative system covering identification, estimation, evaluation, mitigation and residual-risk acceptance. It is not a one-time register.

  • ISO/IEC 42001

    AI management system documentation

    Sized to the organisation: policy, objectives, roles, Annex A control applicability, internal audit programme and management review.

  • Art. 47 · Annex V

    EU declaration of conformity

    Drafted with the conformity route and applied harmonised standards established and evidenced.

  • Art. 72

    Post-market monitoring plan

    What is collected, how often it is reviewed, what triggers re-assessment and how it connects to serious-incident reporting under Art. 73.

  • Art. 13

    Instructions for use

    Deployer-facing documentation covering capabilities, limitations, expected performance and required human oversight measures.

Assurance

03

Evaluation design, metrics and the audit programme

Most AI risk assessments stop before anyone proves the system behaves as claimed. We design the evaluation: metrics, datasets, thresholds and cadence. Then we set up an audit process that produces evidence on a schedule instead of during a fire drill.

Built against

  • EU AI Act
  • NIST AI 600-1
  • ISO/IEC 42001
  • OSFI E-23

What we examine

  • 01

    The system's claims restated as testable propositions that define the population and what counts as failure

  • 02

    Which metrics carry regulatory weight for your classification and which are only comfortable to report

  • 03

    Subgroup performance and disparity measures chosen to fit the decision before anyone sees results

  • 04

    Robustness under distribution shift, adversarial input and prompt injection where the system is exposed to untrusted content

  • 05

    Where oversight in practice departs from the design: override rates, time on task and automation bias

  • 06

    The independence of the review function relative to the team that built the model

What you receive

6 artefacts
  • Art. 15

    Evaluation specification

    We fix the metrics, datasets, thresholds, acceptance criteria and the statistical basis for each before the run.

  • Measurement

    Metric register

    Every metric with its definition, owner, collection method, reporting cadence and the decision it is allowed to inform.

  • Art. 10(2)(f)

    Bias and subgroup analysis

    Examination of possible biases likely to affect health, safety or fundamental rights. We record each mitigation and its residual effect.

  • Art. 15 · NIST AI 600-1

    Red-team and robustness protocol

    Structured adversarial testing scoped to the generative-AI risk taxonomy. Findings are tracked to closure.

  • ISO/IEC 42001 §9.2

    Internal audit programme

    Scope, schedule, criteria, auditor competence and independence, reporting lines and the management review that consumes it.

  • OSFI E-23

    Model validation report

    Independent validation for regulated financial institutions. It covers conceptual soundness, data quality, outcomes analysis and ongoing monitoring.

How we work

Five phases.

The scope phase is meant to shrink the rest of the engagement. It routinely does.

  1. 011–2 weeks

    Scope

    We inventory the AI in the product, establish your role in each value chain and confirm which markets and regimes apply. Most engagements narrow here. The scope you feared is usually larger than the one you have.

  2. 023–5 weeks

    Assess

    Classification, gap analysis against the applicable provisions and a read of the controls you already run. We work from the system as built and with the engineers who built it.

  3. 034–8 weeks

    Document

    We draft the artefacts and you review them. Then we fix the places where the record and reality disagree. Finding those disagreements is the useful output. The document follows from it.

  4. 043–6 weeks

    Evaluate

    Evaluation design, the first full run and the thresholds that decide what ships. If you have no measurement capability yet we build the harness with your team instead of handing over a specification.

  5. 05Ongoing

    Sustain

    The audit calendar, the monitoring plan and the review that keeps documentation current through model changes. Governance programmes usually fail at this stage. It is the part we hand over most carefully.

Engagement shapes

Three ways to start.

Fees are fixed against a fixed scope or set per phase once the scope is known. We do not price on hours.

  • Diagnostic

    3–4 weeks

    Fixed fee for a fixed scope.

    Classification, applicability across your markets and a prioritised gap register. That is enough to brief a board, size a programme or answer a buyer's security review honestly.

    • AI system inventory
    • Applicability determination per market
    • Prioritised gap register
    • Executive briefing
    Enquire
  • Programme

    3–6 months

    We build the full record once.

    Assessment through documentation and evaluation. It ends with a complete conformity file and a working audit calendar. This is the usual shape for a team with a real deadline.

    • Everything in the diagnostic
    • Full Annex IV technical file
    • Impact and risk assessments
    • Evaluation design and first run
    • Internal audit programme
    Enquire
  • Retained

    12 months+

    Standing capacity.

    A named principal, a monthly review and documentation maintained through your release cycle. It suits organisations that ship model changes faster than a project engagement can absorb.

    • Named principal and defined response times
    • Documentation maintained through releases
    • Quarterly regulatory horizon review
    • Audit and certification support
    Enquire
Questions

On engagements.

We specify them and work alongside the engineers who implement them. We do not take over a codebase. For a substantial change such as logging architecture, an oversight interface or an evaluation harness we write the specification at a level an engineering team can size. Then we review the implementation against it.

No. Conformity assessment by a notified body and certification against ISO/IEC 42001 must be performed by accredited bodies independent of the party that prepared the documentation. We prepare you for those assessments and support you through them. We cannot also sit on the other side of the table.

We design the artefacts around that question from the start. Version-dependent content sits apart from stable content. A documented change-assessment step decides whether a model update is a substantial modification that requires re-assessment. Teams that write a technical file as a single narrative document rewrite it every quarter.

Diagnostics are fixed-fee against a fixed scope. Programme work is priced per phase after the scope stage. You commit to the assessment before you commit to the documentation. Retained engagements are a monthly fee against a defined response time and review cadence. We do not price on headcount or hours.

Engage

Tell us what you are shipping.

We will tell you what attaches to it and whether you need us for four weeks or six months.