Credit for work already on file: done once, never twice

The reason to run several frameworks in one register is that they ask for the same things in different words. Veritome gives credit across them in two ways — and refuses to in a third, which is worth knowing.

One record, two programmes

Some templates are placed in two programmes: the clause 4–10 records ISO/IEC 42001 and ISO/IEC 27001 share — context, interested parties, roles, risk, objectives, change, competence, communication, documented information, operational control, monitoring, internal audit, management review, corrective action. Such a record has an information-security section alongside its AI-management questions, and the step reads Filled once · counted in ISO 27001 too. Complete it once and it is complete in both. Nothing is copied; there is one record, and approving it re-plans the sibling programme.

Done, credited

A step whose every part is already credited — by an EU AI Act obligation you completed with verified evidence, or by an approved step in another programme — is marked Done, with the provenance beside it: ↺ credited from your EU AI Act work. It is Done like any other; the note says where the work came from, and the step names the records that did it. Partial credit does not close a step: if one part is still open, the step stays open.

Where credit shows

Only in three places, and always as a note on the work rather than a figure of its own:

• Also counts toward — on an obligation or a step, one chip per other framework the approved record is credited in.
• Credited — the Done · credited status and the ↺ credited from … note on a step or a Statement of Applicability row.
• One figure per programme — the ↺ count beside a standard on the Overview's Programmes panel, and the programme page's subtitle, which says how many of the done steps were credited by work already on file.

Where the credit comes from

Two sources feed it:

• Your EU AI Act journey — an obligation with verified evidence credits the parts of a standard it answers, without you creating anything per obligation.
• Your approved records — an approved step credits what it closes, in its own programme and the others.

That credit runs one way: the EU AI Act journey credits the standards. No programme record files evidence against an EU AI Act obligation, and Related links credit nothing in either direction.

What is not credit: the Act's own reuse routes

The EU AI Act itself says, in six places, that work you have already done counts — Art. 27(4) lets a fundamental-rights impact assessment draw on the GDPR DPIA; Art. 26(9) says a deployer uses the provider's instructions for use in that DPIA; Art. 8(2), Art. 17(3), Art. 17(4) and Art. 26(5) let documentation, quality management and monitoring sit inside procedures other Union law already requires. Veritome shows those routes on the obligation and prefills from them. They never count toward a completion figure or the Statement of Applicability, and they never change an obligation's status: whether your internal governance rules genuinely reach the Act's requirement is not a fact the product can see, so you declare reliance and the status stays yours. See DPIA overlap.

What this means for effort

The number of steps a programme credits depends on what you have already done. The programme page shows it; this help centre deliberately does not quote a figure, because yours will differ.