En/Ru

EU AI Act: technical documentation and conformity

For a high-risk system, compliance is not a policy document — it is a working risk-management process, a record of the data you trained on, logs you can actually produce, and oversight a human can actually exercise. We build those with your engineers, in your stack.
EU AI Act: technical documentation and conformity
For a high-risk system, compliance is not a policy document — it is a working risk-management process, a record of the data you trained on, logs you can actually produce, and oversight a human can actually exercise. We build those with your engineers, in your stack.
Evidence, not a policy binder
Contact us

What gets built

We work through the requirements for high-risk systems in the order that lets engineering keep shipping.
01

Risk management system

Identified risks, mitigations, residual risk and the testing that supports the claim — as a process that runs, not a snapshot.
02

Data and data governance

Where training and validation data came from, what is in it, how bias was examined and what was done about it.
03

Logging and traceability

Records the system keeps automatically, retained long enough to reconstruct a decision.
04

Human oversight

What a person can see, override and stop — designed so it is usable under real workload, not only on paper.
05

Accuracy and robustness

Declared metrics, how they were measured, and behaviour under adversarial and degraded conditions.
06

Technical documentation

Assembled from the above, in the structure the Regulation expects, plus the declaration and registration steps.

What is included

01

We work in your repository

Documentation that lives beside the code stays current; documentation in a shared drive does not.
02

Engineering-first

Every requirement translated into something a developer can implement and test.
03

Conformity route

Which assessment path applies, what it needs, and what to prepare before you start it.
04

Handover

Your team can maintain it after we leave — that is the point.

Common questions

How does work start?

With a diagnosis, not a proposal. The first week is spent understanding where you actually are — what is built, what is signed, what is exposed. Only then does the scope get fixed, because a scope written before that is a guess.

How is it priced?

Fixed scope, fixed price, agreed before work starts. We do not bill by the hour: it makes the client pay for our learning curve and rewards slowness. If a question turns out to be bigger than the scope, we say so rather than quietly extending the invoice.

Can we just talk first?

Yes. A one-hour consultation costs $299 and is paid in advance; you pick the time from real availability after payment. You get a written summary with the recommendations afterwards, and if an hour turns out to be the wrong format we say so before you pay.

Which countries do you work with?

The EU, the US and MENA, remotely, with local partners where a filing has to be made by someone admitted in that jurisdiction. We tell you up front when something needs a local lawyer rather than us.

Who actually does the work?

The people you speak to. There is no layer of juniors between the first call and the delivery — which is also why the scope is fixed rather than open-ended.

BOOK A CALL

Talk it through

One hour, fixed price, paid up front. You pick the time after payment — the calendar shows real availability, so the slot you take is the slot you get.

One-hour consultation

$299
  • ✓60 minutes, video call
  • ✓You pick the time after payment — the calendar shows real availability
  • ✓Written summary with the recommendations afterwards