Manuel B. Garcia

Manuel B. Garcia serves as the Senior Director for Educational Technology and Digital Learning at FEU Institute of Technology, Manila, Philippines. Read More

Contact Info

1607, FEU Tech Building,
P. Paredes St, Sampaloc,
Manila, Philippines
mbgarcia@feutech.edu.ph

Follow Me

What Should You Do if a Collaborator Uses AI in a Way the Research Team Did Not Approve?

Unapproved AI use is not automatically research misconduct, but it should be assessed promptly. Determine what the collaborator did, what information was exposed, which rules applied, and whether the research needs correction or reporting.

95
When a Collaborator Uses Unapproved AI Guide 95 of 783
01 · The Question

What if a Collaborator Uses AI Without the Team's Approval?

You discover that a collaborator used an AI tool the research team had not approved. Perhaps they generated analytical code, uploaded interview transcripts for summarisation, rewrote manuscript sections, or used an external system with project data.

What should you do?

The answer should depend on what actually happened. An unapproved grammar edit to public text is not equivalent to uploading identifiable participant information to an unauthorised service. Treating every deviation as a scandal would be disproportionate. Ignoring every deviation because "AI is just a tool" would be equally unhelpful.

The first task is to establish the facts and contain any ongoing risk.

02 · The Short Answer

Stop, Establish the Facts, and Assess the Consequences

In Brief

If a collaborator uses AI in a way the research team did not approve, stop any continuing questionable use, determine exactly what tool was used and what information or research activity was involved, preserve relevant records, and assess whether the action violated only an internal team rule or also an institutional, ethics, privacy, funder, contractual, or publication requirement.

The appropriate response should be proportionate to the consequences. Some cases may require only correction and clarification of team procedures, while data exposure, participant risk, compromised analysis, or an external policy breach may require institutional reporting, ethics review, remediation, or reconsideration of affected research outputs.

03 · What You Need to Know

“Unapproved AI Use” Describes a Process Failure, Not Yet Its Severity

First Determine What Actually Happened

A vague statement such as "they used ChatGPT on the study" is not enough to assess the situation.

Establish the tool or service used, account type, task performed, information entered, outputs produced, dates of use, whether material was retained by the service, how the output entered the research workflow, and whether the activity is continuing.

A factual reconstruction is more useful than beginning with accusations.

Question Why It Matters
What AI system was used? Different services and account configurations have different institutional approvals and data arrangements.
What information was entered? Determines potential privacy, confidentiality, contractual, security, and intellectual-property consequences.
What did the AI produce? Helps identify effects on methods, analysis, writing, code, or interpretation.
Was the output used in the research? Determines whether results, records, or manuscripts may need review or correction.
Is the activity continuing? Determines whether immediate containment is needed.
Which rules applied? Distinguishes an internal procedural deviation from a potentially reportable external breach.

Stop Ongoing Exposure Before Debating Blame

If confidential or participant information is still being sent to an unapproved service, stop the affected future processing while the situation is assessed.

Containment should be proportionate. Do not automatically delete research records, destroy outputs, or instruct collaborators to erase evidence. Those actions can interfere with investigation, audit, data-retention requirements, or the ability to understand what occurred.

Preserve relevant records while obtaining guidance on what should happen next.

Distinguish an Internal Rule Violation From an External Compliance Problem

A team can establish rules that are stricter than the minimum required externally. Breaking one of those rules does not automatically mean that law, ethics approval, or institutional policy was violated.

Internal deviation The collaborator departed from the team's agreed procedure, but the activity may still have complied with applicable external requirements.
External compliance issue The activity may also have breached institutional policy, ethics approval, privacy or security requirements, a contract, funder condition, journal rule, or applicable law.

This distinction matters for proportionality. A team should not label a colleague's procedural mistake as research misconduct merely because the internal workflow was not followed.

Do Not Automatically Call It Research Misconduct

"Research misconduct" is a formal term in many systems and should not be used casually.

Under the U.S. federal research misconduct framework administered by the Office of Research Integrity, research misconduct means fabrication, falsification, or plagiarism in proposing, performing, reviewing, or reporting research. It does not simply mean every violation of a research policy or every instance of poor practice.

Other countries and institutions may use different definitions and broader categories of unacceptable research practice. The relevant institutional framework should therefore determine classification.

Unapproved AI use could contribute to misconduct in some circumstances, for example if it facilitates fabrication or falsification, but the fact that AI was used without team approval does not by itself establish that conclusion.

Assess Whether Research Data Were Exposed

If the collaborator entered participant, confidential, proprietary, or restricted information into an AI service, determine exactly what was transmitted.

Relevant questions include whether the information contained direct identifiers, whether individuals could be re-identified, whether the service retains submitted information, whether provider personnel or subprocessors can access it, and whether the transfer complied with the institution's approved data-handling arrangements.

If a potential privacy or security incident occurred, follow the institution's incident-response procedure rather than attempting to resolve the matter entirely within the research team.

Watch Out

Do not ask the collaborator to conceal, delete, or retrospectively rewrite records merely to make the AI use less visible. Accurate records are essential for determining what occurred and what remediation is appropriate.

Assess Whether the Research Itself Was Affected

Unapproved AI use can create a methodological problem even when no sensitive data were exposed.

If AI generated analytical code, classifications, summaries, statistical interpretations, synthetic observations, or manuscript claims, determine whether those outputs affected the study's results or conclusions.

Re-run analyses where necessary. Verify code independently. Compare AI-assisted classifications with the approved analytical procedure. Check references against original sources. Remove unsupported generated claims.

The goal is to determine whether the research record remains defensible.

Human Verification After the Fact May Not Solve Every Problem

Researchers sometimes respond, "But I checked the output afterward."

Verification can address accuracy, but it does not necessarily resolve confidentiality, privacy, ethics, contractual, or security violations created when information was uploaded in the first place. Nor does checking generated text automatically make a prohibited AI workflow compliant.

Accuracy and permission are separate questions.

Check Whether the Ethics Protocol Was Affected

If the unapproved use involved participant data or altered an approved research procedure, determine whether the responsible ethics body needs to be notified.

The team should not independently assume that retrospective disclosure is unnecessary. Follow the institution's established process for protocol deviations, unanticipated problems, amendments, or other reportable events as applicable.

Check Funder and Contractual Obligations

Funders, data providers, industry partners, and collaborating institutions may impose requirements concerning confidential information, data processing, security, or AI use.

If the unapproved activity potentially violated those requirements, the project lead should determine what notification or remediation process applies.

This is one reason teams should identify funder AI requirements before a problem occurs.

Publication May Need to Pause

If the affected material has entered a manuscript, abstract, report, or submission, verify it before proceeding.

A journal submission should not continue merely because a deadline is inconvenient. Determine whether generated material is accurate, whether methodological reporting needs revision, whether AI disclosure is required, and whether the journal permits the use.

If the manuscript has already been submitted, the appropriate response depends on the significance of the issue and the journal's policies. Seek editorial or institutional guidance when correction is necessary.

The Response Should Address the System, Not Only the Individual

An incident can reveal that the team's rules were unclear, inaccessible, outdated, or never communicated to junior researchers.

ORI guidance on collaborative research emphasises clear roles, management, communication, training, and written agreements. If a reasonable collaborator could not tell what the team's AI expectations were, disciplinary language alone will not fix the underlying governance problem.

After the immediate issue is addressed, review whether the team's AI rules need clarification.

04 · A Practical Example

A Collaborator Uploads Interview Transcripts Without Approval

Hypothetical Example

AI-Assisted Qualitative Coding Was Not in the Team Plan

A collaborator uploads several de-identified interview transcripts to a public generative AI service and asks it to suggest themes. The research team's plan prohibited participant-level data from being entered into public AI systems.

Contain The team asks the collaborator to stop uploading additional transcripts while the issue is assessed.
Establish the facts The project lead determines which transcripts were uploaded, what information they contained, which service and account were used, and what outputs were produced.
Preserve records The prompts, relevant outputs, dates, and available service information are retained rather than erased.
Check external requirements The team reviews institutional data-security rules, the ethics approval, participant information, and any contractual restrictions.
Assess the research The team determines whether AI-generated themes influenced coding or conclusions and independently reviews affected analysis.
Escalate where required If the upload constitutes a reportable privacy, security, or ethics incident, the team follows the institution's formal procedure.
Prevent recurrence The team clarifies its AI rules and confirms that all collaborators understand the permitted workflow.
05 · What Researchers Often Get Wrong

Common Mistakes After Unapproved AI Use

Misconception

Any Unapproved AI Use Is Research Misconduct

Not automatically. Research misconduct has specific definitions in formal systems. Determine what happened and which rules were violated before applying a serious label.

Misconception

If the AI Output Was Accurate, There Is No Problem

Accuracy does not resolve unauthorised data transfer, confidentiality, ethics, security, contractual, or disclosure issues.

Misconception

The Collaborator Should Delete Everything Immediately

Automatic deletion can destroy records needed to assess the event and may conflict with research-record or retention requirements. Preserve evidence and follow the applicable incident process.

Misconception

The Team Should Keep the Problem Internal

Some deviations can be handled internally. Others may trigger institutional, ethics, privacy, security, funder, contractual, or publication reporting requirements. The team should not suppress an issue that an external authority requires it to report.

Misconception

The Only Question Is Who Is to Blame

Accountability matters, but the immediate research priorities are containment, factual reconstruction, protection of participants and data, assessment of the research record, and compliance with applicable reporting requirements.

06 · What This Means for You

Respond According to Consequence, Not Merely the Word “Unapproved”

A simple response framework

If the deviation involved only low-risk public material and no external requirement was breached
Correct the workflow, document the issue where appropriate, and clarify the team's expectations.
If AI affected analysis, code, interpretation, or manuscript content
Independently verify the affected research and correct or repeat work where necessary.
If sensitive or confidential information was entered into an unapproved service
Stop further exposure, preserve relevant records, and follow applicable privacy, security, ethics, and institutional incident procedures.
If an approved protocol, funder condition, contract, or journal requirement may have been breached
Consult the responsible authority and follow its reporting or remediation process.
If the problem arose because team rules were unclear
Fix the governance problem as well as the immediate incident.

Teams can reduce the likelihood of these situations by deciding who has authority to approve consequential AI uses before collaborators begin experimenting with new tools.

07 · A Quick Checklist

When You Discover Unapproved AI Use

Before deciding how serious the incident is, check:
Stop any continuing AI activity that could create further risk or noncompliance.
Identify the AI service, account type, dates, prompts or tasks, inputs, and outputs involved.
Preserve relevant records rather than automatically deleting evidence of the activity.
Determine whether participant, confidential, proprietary, unpublished, or otherwise restricted information was exposed.
Check which team, institutional, ethics, funder, contractual, legal, and publication requirements applied.
Determine whether AI outputs affected data, analysis, code, interpretations, figures, or manuscripts.
Independently verify or repeat affected research procedures where necessary.
Follow formal incident, ethics, privacy, security, or reporting procedures when applicable.
Correct the team's AI rules, training, or communication if the incident exposed a governance weakness.
08 · Frequently Asked Questions

Frequently Asked Questions About Unapproved AI Use

Is using AI without team approval automatically research misconduct?

No. Formal definitions of research misconduct vary by jurisdiction and institution. Under the U.S. federal framework, research misconduct is fabrication, falsification, or plagiarism. Unapproved AI use should be assessed according to what occurred and the applicable rules rather than labelled automatically.

Should I report the collaborator immediately?

First determine whether immediate reporting is required by an applicable privacy, security, ethics, institutional, funder, or other procedure. For less consequential internal deviations, establish the facts before deciding on an appropriate response.

What if no sensitive data were involved?

The issue may still affect methodology, research integrity, disclosure, or team governance. Assess whether AI-generated material entered the research and whether any external policy was breached.

What if the collaborator says they checked everything AI produced?

Verification can address accuracy but does not necessarily resolve whether the original AI use was permitted. Data transfer, confidentiality, ethics, contractual, and security issues need separate assessment.

Should AI-generated analysis be discarded?

Not automatically. Determine whether the analysis was methodologically valid and whether the workflow itself was permissible. Some work may need independent verification or repetition; other material may remain usable. Preserve records while that assessment occurs.

What if the manuscript has already been submitted?

Assess whether the AI use affects the accuracy, methods, disclosure, or compliance of the submission. If correction or disclosure is required, consult the journal and relevant institutional authority rather than waiting for the issue to be discovered independently.

09 · The Bottom Line

Establish the Consequences Before Assigning the Label

The Bottom Line

When a collaborator uses AI without team approval, first stop any continuing risk, establish exactly what happened, preserve the relevant records, and determine whether the activity affected protected information, research validity, or requirements imposed outside the team.

Respond proportionately. Some cases require little more than correction and clearer procedures; others may require independent reanalysis, incident reporting, ethics review, or formal institutional action. The seriousness depends on the consequences and applicable obligations, not simply on the fact that AI was involved.

10 · Sources and Further Reading

Authoritative Guidance on Research Integrity and Collaborative Responsibility

11 · Cite this Guide

How to Cite This Guide

This guide is intended to be read, shared, and used in research, teaching, and academic work. If you draw on its ideas, explanations, or other content, please acknowledge the source by citing the guide. Doing so gives appropriate credit and helps your readers locate the original resource.

Has the Field Guide helped your research?

If a guide helped clarify a question, inform a research decision, or move your work forward, I would love to hear about your experience. Your story may also help other researchers discover the Field Guide.

Share Your Experience
Takes only a few minutes