Employees may conceal AI use because acknowledging help feels costly: they expect less credit, more work or doubts about their competence. Unclear rules can also leave them unsure what to disclose. Others may be hiding an unapproved tool or a known violation. Silence alone does not distinguish these situations. Ask about the task, the tool and the reason for staying quiet before choosing a response.
For a team leader, the aim is useful visibility into how work was produced and checked. That requires a clear agreement about what must be disclosed, who needs to know and what happens next. The broader people and change guide covers support for adoption; this article focuses on the decision to acknowledge AI help.
Disclosure can carry a perceived cost
In an August 2026 r/ChatGPT discussion, a Reddit user described using AI to prepare strategy documents and asked whether to tell their boss. They considered changing the language to sound more like their own writing. The reported speed and quality are unverified, and the employer's rules are unknown. The revealing detail is the choice they were weighing: make the assistance visible, or disguise it.
The replies did not agree on what disclosure would bring. One Reddit user worried that showing how the work was done could make the worker seem replaceable. Another emphasized responsibility for checking anything submitted. These are individual judgments, not evidence of what the original poster's manager would do. They show why an invitation to “share your AI successes” can leave the consequential question unanswered.
There is experimental evidence for reputational concerns. In four preregistered experiments, Jessica Reif, Richard Larrick and Jack Soll examined anticipated and actual social evaluations of AI assistance. Participants expected negative judgments and were less willing to disclose AI help than other help. In an employee-vignette experiment, evaluators rated an AI-assisted worker as less competent and diligent, and lazier. The evaluations varied with the task and the evaluator's own AI use. The 2025 PNAS paper.
These experiments measured perceptions in controlled online settings. They do not establish how many employees conceal AI use, whether their work was worse, or how every manager responds. Nor is concealment universal: Atlassian's June 2026 research reported that most respondents in its survey of US knowledge workers described themselves as transparent about AI use. Its separate experiment still found penalties attached to disclosure. A team can contain both open use and a reason to hesitate.
Ask what the employee expects to lose by acknowledging assistance. Credit, control over saved time and confidence in the rules need different answers. Where the concern is about staffing decisions, discuss job uncertainty honestly; an enthusiastic account of the tool will not settle it.
Separate an undisclosed process from an unapproved tool
An employee might use an approved assistant to improve wording without mentioning it. Another might upload restricted material to a personal account. Both could be described as “hidden AI use,” but the manager's obligations differ.
Use the work itself to establish which question needs an answer.
| What you establish | What remains unresolved | Appropriate next step |
|---|---|---|
The tool and inputs were permitted, but the assistance was not mentioned. | Was disclosure required for this handoff, and did the employee understand it? | Clarify the expectation and examine why acknowledgment felt unwelcome. |
The employee used a service or account outside the approved process. | What data went where, and which controls or approvals were missing? | Follow the security process and arrange a permitted way to meet the work need. |
The employee understood a specific restriction and deliberately evaded it. | What happened, with what consequences and evidence? | Use the relevant incident or conduct process, with a fair account of the facts. |
The UK's National Cyber Security Centre describes shadow AI as use outside approved systems and processes. That is a tooling and control problem, not a synonym for every unmentioned spelling improvement. Its shadow IT guidance also asks organizations to learn from unmet needs and take a positive, no-blame approach to people driven toward workarounds. This supports investigating the failed process; it does not authorize a manager to promise immunity from every rule.
If the approved route cannot do the work, give the request an owner and an answer. Otherwise, the employee is left with the same obstacle after being asked to reveal it.
Make the first disclosure useful
Suppose Jamie Lee, a museum communications officer, uses an approved assistant to draft an exhibition announcement from permitted, non-sensitive facts. Jamie checks the dates against the curator's notes and the access details against the access coordinator's record. The manager needs to understand those checks before approving the announcement. Jamie wants to know whether mentioning AI will cause the checked work to be dismissed as effortless.
Begin with the announcement and the people relying on it. Ask Jamie to explain what the assistant contributed and where Jamie changed or verified it. That makes assistance and judgment visible together.
For this conversation, work through four questions:
- What help was used? Identify the tool, account, inputs and contribution. A wording suggestion is different from generating the access information.
- What did the employee check? Compare the announcement with the curator's dates and the access coordinator's details. Leave missing facts unresolved until the responsible person answers.
- Who needs the explanation? Agree what the approving manager must know and whether the museum's policy requires any further disclosure. Do not invent a public labeling rule.
- What happens to the credit and the time? Evaluate the finished announcement and Jamie's checking work. Discuss any change in workload explicitly instead of assuming a faster draft creates capacity for another campaign.
If Jamie used a prohibited account, the conversation also needs the museum's security response. Keep that boundary clear before inviting more details. A manager can listen fairly and explain the process without pretending to control decisions that belong to someone else.
Judge the next piece of work fairly
The next announcement tests whether the agreement is usable. Can Jamie use the permitted facts, explain the assistance and get a decision on an uncertain detail? Does the manager recognize the source checking as part of the work? If the permitted tool still cannot handle the task, that problem remains open even if Jamie now discloses everything.
Check three things separately:
- Visibility: the required people received the agreed explanation.
- Quality: the announcement's dates and access details survived checking and approval.
- Working conditions: the tool, time and decision support were available when the task occurred.
A rise in declared AI use may mean more people are using it, or that existing use has become easier to acknowledge. It cannot by itself show improved quality or trust. Keep the task and observation period in view before interpreting a disclosure count.
Recognition also needs to match the work. If the organization praises instant drafts while ignoring careful checking, its message about responsible AI use is difficult to believe. Performance systems should support useful adoption, including the judgment needed to reject a poor output. Rewarding disclosure as a standalone target risks making the label more important than the result.
Questions and answers
Must employees disclose every use of an approved AI tool?
The required disclosure depends on the organization's rules and the task's handoff. Approval to use a tool does not settle what a reviewer, customer or colleague needs to know about a particular output. A manager approving a museum announcement may need to know how access information was produced and verified, even when the tool itself is permitted.
Agree the audience, information and point of disclosure for the task. If an external requirement may apply, get the responsible policy owner's answer rather than improvising it. Use the task conversation to make that expectation concrete.
Does concealing AI use prove misconduct?
Concealing AI use does not, on its own, establish a violation or its motive. Determine whether the tool and inputs were permitted, whether disclosure was required and understood, and whether a known restriction was deliberately evaded. These findings can require different responses.
Where data may have entered an unapproved service, follow the relevant security process while establishing the facts. Do not dismiss the risk because the output looked good. The comparison of undisclosed and unapproved use identifies the separate questions.
How can a manager invite disclosure without promising immunity?
A manager can explain why the information is needed, who will receive it and how the organization will respond. Describe the boundary between reviewing work, resolving an unclear rule and handling a possible security or conduct incident. Make only commitments the manager has authority to keep.
Start with one concrete output and listen to the reason for staying quiet. Give unanswered tool or policy questions an owner, and explain when the employee will hear back. Fair listening does not require a promise that every possible finding will have no consequences.
Does more disclosed AI use mean adoption has improved?
More disclosed AI use can reflect greater use, greater willingness to acknowledge existing use, or both. The count alone cannot separate those explanations or establish better work. Compare the same kind of task over a stated period and examine the agreed disclosure, accepted output and available support.
For the museum announcement, the useful follow-up is whether the manager received the required explanation and the dates and access details were checked. Review visibility, quality and working conditions separately before drawing a broader conclusion.
