Systems × rules × evidence

From your systems to the rules that apply, and the evidence behind them.

Trusq connects AI systems, ICT systems and digital products to applicable released obligations, owners, actions and source-linked evidence. When a relevant rule changes or an accepted system change affects the assessment, the relevant work can return to review while earlier evidence and decisions remain available.

See Trusq in action Map one system

Registered objects

Register AI systems, ICT systems and digital products. Each active object counts once; a linked AI profile does not add a second charge.

Controls and expected evidence, per system

Each applicable obligation becomes a named control with a stable identifier, an owner, an expected kind of evidence and a visible review state. Trusq shows the reason a control applies and links it to the source; your team keeps the decision.

Example · Meridian Group (fictional) · Recruitment screeningExample · fictional data

Approved, on file
Back in review
Not affected

Each control is Trusq's own way of tracking one obligation that this system's declared facts put in scope. The identifiers, families and expected-evidence lists are Trusq's, not the law's, and Trusq shows no compliance percentage and no maturity score.

Controls for Recruitment screening
Control	What it is	Owner	Review state	Expected evidence
TRQ-DOC-01	Technical documentation `Art. 11, Annex IV · Technical documentation`	Head of Engineering	~~Reviewed~~Needs recheck	Annex IV pack v4 approved
TRQ-RSK-01	Risk management system `Art. 9 · Risk management`	Risk lead	Reviewed	Risk file v7 approved
TRQ-OVS-01	Human oversight design and assignment `Art. 14, Art. 26 · Human oversight`	Head of Talent	Evidence in progress	Oversight plan · draft
TRQ-LOG-01	Automatic logging and record retention `Art. 12, Art. 19, Art. 26 · Logging and record-keeping`	Platform lead	Reviewed	Retention record v2 approved
TRQ-FRA-01	Fundamental rights impact assessment `Art. 27 · Fundamental rights impact assessment`	Legal counsel	Open	None yet

Meridian Group (fictional). Control identifiers, families and legal references come from the Trusq control catalogue (2026-09-03); owners, states and evidence names are fictional.

Trusq example register showing 12 fictional AI systems, mapped obligations and the regulatory-change impact panel — **Meridian Group (fictional).** Inspect the read-only register, its mapped obligations and the affected systems behind a regulatory change. Open the example register →

From system to owned evidence

01SystemPurpose, role, owner and declared context

02RulesApplicable obligations and source versions

03ChangeRegulatory impact or updated declared fact

04ControlsApplicable controls, owners and expected evidence

05ActionReason, owner and review state

06DossierEvidence, approval and history

Want to inspect the result at register scale? Open the 12-system Meridian example register →

Your AI changes. Its compliance record keeps up.

Update a provider, model version, intended purpose or operating context in the workspace or through an inventory integration. Trusq preserves exactly what changed, puts only the controls that depend on that fact back into review, and keeps the earlier evidence and decisions intact.

Example · Meridian Group (fictional) · one change, five controlsExample · fictional data

Approved, on file
Back in review
Not affected

Before · 1 Sep 2026

TRQ-DOC-01Reviewed
TRQ-RSK-01Reviewed
TRQ-OVS-01Evidence in progress
TRQ-LOG-01Reviewed
TRQ-FRA-01Open

The change

High-risk implementation timeline updatedRegulation (EU) 2026/1744

After · 2 Sep 2026

TRQ-DOC-01Needs recheck
TRQ-RSK-01Reviewed
TRQ-OVS-01Evidence in progress
TRQ-LOG-01Reviewed
TRQ-FRA-01Open

Nothing is discarded. Annex IV pack v1–v3 stay retained; v4 keeps its approval, reviewer and date while the recheck runs.

Meridian Group (fictional). One verified change moves exactly one control back into review. The other four keep the state and the evidence they already had. No score, no percentage. Fictional data.

When a rule changes

The same record also works the other way round: when an official source changes a rule that a registered system carries, Trusq traces it to that system and puts only the control that depends on it back into review.

Example · Meridian Group (fictional) · when a rule changesExample · fictional data

Verified official changeHigh-risk implementation timeline updatedRegulation (EU) 2026/1744 · published text retained with its source version
Affected registered systemRecruitment screeningProvider · human resources · NL · declared model version 2026-09
Obligation and control in scopeTRQ-DOC-01 Technical documentationDerived from the obligation this system already carries under Art. 11 and Annex IV
Prepared actionReconcile the Annex IV pack with the amended datesOwner: Head of Engineering · review state visible to the whole team
Evidence stateAnnex IV pack v4 · approved, now marked Needs recheckThe earlier approval, its reviewer and its date are kept

Meridian Group (fictional). One worked example of the operating loop set out above: an official change traced to the system it affects, the control that carries it, the action and the evidence that already exists. Fictional data.

Work in Trusq or connect your existing workflow

Workspace

A shared operating view

Manage systems, changes, actions and evidence with clear ownership and review status.

Dossier

Evidence that remains reconstructable

Export systems, obligations, approved evidence, rule updates and audit history together.

Business integrations

API and signed webhooks

Synchronise registered system facts and route verified regulatory impacts into existing tools.

Explore integrations →

Accountable by design

Your team keeps the decision

Trusq prepares traceable regulatory work and evidence for review. Applicability, conformity and final approval remain with your authorised decision-makers.

Explore the interactive demo Start the 14-day evaluation