Intermediate4 min readWorkplace AI for Individuals

Workplace AI disclosure: when you actually have to say so

Check policy, contract, regulatory and formal-process requirements together. Record the applicable clause, owner, recipient and timing, then describe the AI contribution truthfully.

What you should be able to do

Check all four disclosure triggers. Policy, contract, regulation and a direct question can apply together; disclosure does not replace permission to use the tool or process the data.

Saved only in this browser.
In this article

Check every applicable source of a workplace disclosure requirement: policy, contract, regulation and the form or process you are completing. One can apply alongside another. A disclosure also does not supply permission to use AI or to send confidential material to a tool.

For choices left to your judgment, keeping your name on AI-assisted work gives a broader authorship test. This guide helps you locate an actual obligation and give the relevant recipient an accurate account of what the tool did.

The four workplace-specific triggers

TriggerWhat to establishWho can resolve uncertainty
Company policyExact work category, required wording, recipient and timingPolicy owner or manager
Client contract or statement of workWhether the clause covers this deliverable and production methodContract or account owner
Applicable regulationSystem, organisational role, jurisdiction, duty and exceptionsResponsible legal/compliance/product team
Direct question in a formal processWhat the question asks about this workProcess owner if wording is ambiguous

Follow the requirements that apply. If instructions conflict, record the clauses and ask the responsible owners to resolve them before the affected delivery or launch. Do not select the most convenient rule. An unclear response is not evidence that no requirement exists.

The regulatory trigger is about the actual system and role

An employee using AI to edit a private draft is different from an organisation launching an AI chat service for customers. In EU AI Act scope, Article 50 distinguishes provider duties concerning direct interaction and machine-readable output marking from deployer duties concerning certain biometric uses, deepfakes and public-interest text. A company can have different roles for different systems.

There are material qualifications. Interaction notices have an obviousness exception. The public-interest text provision includes an exception for human review or editorial control with editorial responsibility; it is not a blanket requirement to label every AI-assisted document. Other duties, including contracts and sector rules, can still apply. Use the Commission’s Article 50 guidance to frame the question, then have the responsible team determine the actual obligation and exception for the system.

As checked on 28 September 2026, the Commission’s enforcement FAQ states that transparency obligations apply from 2 August 2026, with a limited Article 50(2) marking/detection transition to 2 December 2026 for systems placed on the market before 2 August. That transition does not postpone every transparency duty. Recheck the current legal position before a launch or material change.

Raise a concrete question: “For customer chat service X, who owns the Article 50 role and notice assessment, what decision was recorded, and where is the approved first-interaction notice?” This is more useful than an employee guessing that a vendor’s generic badge meets the organisation’s obligations.

The decision framework

Consider this fictional consulting team:

WorkKnown requirementDecision record
Internal outline reformatted with an approved toolPolicy permits this use and does not require an internal labelRecord the policy version; check that no other applicable requirement exists
Client report whose contract requires disclosure of AI draftingContract applies even if the internal policy has no label ruleTell the specified client recipient what was drafted and checked, using required wording
New customer-facing chat serviceOrganisational transparency assessment neededProduct owner obtains the applicable role, notice, marking and exception decision before launch
Audit form asking whether the report was AI-assistedDirect question applies alongside the contractAnswer truthfully; do not describe drafting as spelling correction

A useful disclosure identifies the contribution and the checks actually performed. For example: “AI drafted the initial structure. We checked each quoted passage against the supplied documents and rewrote the recommendations.” Use that wording only if those checks happened. “Human reviewed” is misleading if the only review was a spell-check.

Validation and fallback

Use the workplace disclosure decision guide to record all applicable triggers, not just the first match. Keep the policy or contract clause, its date/version, the decision owner, required recipient and required timing.

If the answer remains unclear, ask a named owner in writing and pause the affected external delivery or launch when the unresolved requirement could change it. Internal preparation can continue within approved data and tool boundaries. Avoid publishing confidential prompts or source documents as a supposed transparency measure; disclose the contribution to the authorised recipient at the required level of detail.

A disclosure is complete only when it reaches the right person at the right time in the required form. A note hidden in an internal task tracker does not satisfy a contract that requires notice to the client before delivery.

Four cumulative disclosure checks cover policy, contract, regulation/role and a formal-process question, then require a dated clause, decision owner, intended recipient and timing.
Check every applicable trigger and record the actual clause and responsible owner. Disclosure reaches the specified recipient at the required time and does not replace data/tool-use permission. Open the full-size diagram.

Read next

Continue through the same learning path with the next practical articles.