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

Is Changing a Coding Decision After Seeing the Outcome Necessarily Misconduct?

Changing a coding decision after seeing an outcome is not necessarily misconduct. Revisions may correct errors or improve a coding framework, but outcome-driven recoding can become problematic when it distorts the research record or selectively creates a preferred result.

456
Changing Coding After Outcomes Guide 456 of 530
01 · The Question

You Saw the Outcome and Now Think a Case Was Coded Wrong. Can You Change It?

A participant was coded as “nonadherent,” but after examining the outcome you reconsider the classification. A survey response was placed in Category B, yet Category A now seems plausible. A qualitative excerpt was assigned one code, but later analysis suggests that another interpretation may fit better.

Changing codes during research is not inherently suspicious. Coding frameworks develop, errors are discovered, and ambiguous cases sometimes require reconsideration.

The complication is timing. Once you know how a coding decision affects the result, your preferred outcome can influence what suddenly seems like the “better” coding choice.

02 · The Short Answer

A Coding Decision Can Change, but the Outcome Should Not Quietly Become the Coding Rule

In Brief

Changing a coding decision after seeing the outcome is not necessarily misconduct. A code may legitimately be corrected or revised when new evidence, a clarified coding framework, or a defensible methodological reason supports the change. The integrity concern arises when coding is selectively changed because of its effect on the desired result and the resulting research record becomes misleading.

The best test is whether the revised coding can be justified from the source material and coding framework independently of the outcome. Researchers should preserve consequential changes, apply revised rules consistently to comparable cases, and distinguish legitimate refinement from result-driven recategorization.

03 · What You Need to Know

Coding Is an Interpretive Process, but It Still Needs Rules and Evidence

“Coding” Can Mean Different Things Across Research Methods

In quantitative research, coding may involve translating information into analyzable categories: yes/no responses into binary values, diagnoses into groups, occupational categories into numerical codes, or behavioral observations into predefined classifications.

In qualitative research, coding often involves assigning interpretive labels to text, images, observations, or other material. Codes may evolve as researchers develop a deeper understanding of the dataset.

These processes involve different assumptions. A coding revision that is entirely normal in an iterative qualitative analysis may be more consequential in a confirmatory quantitative analysis where category definitions were fixed in advance.

There is therefore no sensible universal rule that says “changing a code after seeing outcomes equals misconduct.”

Correcting a Coding Error Is Usually Different From Redefining a Category

Suppose the codebook defines “1 = treatment” and “0 = control.” A participant assigned to treatment was accidentally entered as 0. Correcting the value to 1 based on the randomization record restores the dataset to the underlying evidence.

That is different from deciding after analysis that several control participants should now be treated as members of the intervention group because moving them improves the treatment effect.

Coding correction The existing code conflicts with the source evidence or established coding rule, and the revised code restores consistency.
Outcome-driven recoding The classification is changed because the researcher knows that the new code produces a more favorable or convenient result.

A Revised Coding Framework Can Be Scientifically Legitimate

Researchers sometimes discover that their original categories are poorly defined. Two categories may overlap. A code may be too broad to capture an important distinction. New cases may expose ambiguities that were invisible when the codebook was developed.

Revising the framework can therefore improve the analysis.

The critical questions are why the framework changed and what happens next. If the definition of a category changes, researchers should ordinarily reconsider all comparable cases under the revised definition rather than changing only the particular cases that improve the desired result.

Apply the New Rule to the Dataset, Not Just to the Problematic Case

Suppose a study codes participants as “high engagement” when they attend at least 75% of sessions. After seeing the outcomes, researchers decide that attendance alone does not capture engagement and add completion of weekly activities as a second criterion.

If there is a genuine theoretical and methodological reason for the revised construct, researchers should apply that definition consistently to everyone to whom it applies.

Changing the classification of one inconvenient participant while leaving comparable participants untouched is much harder to defend as a general improvement to the coding framework.

The Source Evidence Should Still Support the New Code

A coding decision should not float free from the underlying evidence.

If a transcript clearly states that a participant had never used the technology before the study, recoding that participant as an experienced user because doing so improves a subgroup analysis would contradict the source material.

Where evidence is genuinely ambiguous, researchers may have more than one defensible interpretation. That ambiguity should be handled according to an appropriate coding procedure rather than resolved opportunistically according to the outcome.

Blinding Can Reduce Outcome-Driven Coding

When feasible, coding decisions can sometimes be made without knowledge of variables that might bias classification. For example, an adjudicator determining whether an event meets a predefined outcome criterion may be blinded to treatment assignment.

Blinding is not possible or appropriate in every study, especially in many qualitative designs. Still, the underlying principle is useful: if knowing the outcome could influence a subjective classification, consider whether the decision can be made independently of that information.

Qualitative Coding Often Evolves During Analysis

Qualitative researchers should be particularly cautious about importing rigid assumptions from confirmatory statistical research into interpretive methods.

In many qualitative approaches, researchers iteratively develop codes, revisit earlier material, merge categories, split codes, refine interpretations, and move between data and emerging concepts. Such iteration can be part of the method rather than a deviation from it.

That does not mean anything goes. The researcher should still be able to explain how interpretations were developed, how contradictory or deviant cases were treated, and whether material was selectively recoded or omitted merely to create a cleaner narrative.

Inter-Rater Disagreement Is Not Evidence of Misconduct

Two competent coders may classify an ambiguous response differently. Resolving that disagreement through discussion, adjudication, or a predefined procedure is not inherently suspicious.

The concern would be different if disagreements were resolved according to which coding produces the preferred hypothesis, while the stated coding procedure suggests another basis for adjudication.

Changing Codes After Seeing Outcomes Creates a Risk, Not an Automatic Verdict

Outcome knowledge can create motivated reasoning even when researchers are trying to act responsibly. A classification that previously seemed clear may suddenly appear ambiguous when its analytical consequences become visible.

That does not mean every reconsideration is dishonest. It means the decision deserves a stronger evidentiary basis.

Useful questions include: What new information justifies the change? Would the code have been changed if the outcome pointed in the opposite direction? Does the revised definition apply consistently to other cases? Can someone reviewing the source material understand why the new code is preferable?

Recoding Can Become Part of a Broader Outcome-Driven Analysis

Changing a code may alter group membership, participant eligibility, outcome classification, exposure status, or another variable used in the analysis. Consequently, recoding can sometimes function like changing the analysis itself.

If researchers repeatedly alter coding rules, rerun analyses, and retain whichever combination produces the desired conclusion, the concern overlaps with changing analyses after seeing the results.

If recoding effectively removes participants or observations from the analytical population, it may also overlap with outcome-driven participant exclusion.

Could Outcome-Driven Recoding Become Falsification?

Potentially. Under the U.S. Public Health Service definition, falsification includes manipulating research materials, equipment, or processes, or changing or omitting data or results such that the research is not accurately represented in the research record.

Whether a particular recoding constitutes falsification depends on the facts. A legitimate disagreement over an ambiguous classification is not equivalent to intentionally or recklessly changing data so that the record becomes inaccurate.

A formal PHS misconduct finding also requires a significant departure from accepted practices of the relevant research community, intentional, knowing, or reckless conduct, and proof by a preponderance of the evidence. Honest error and differences of opinion are excluded.

Watch Out

If you cannot explain why a code should change without mentioning that the new coding improves the result, you probably do not yet have a methodological justification for the change.

04 · A Practical Example

One Ambiguous Classification, Two Ways to Resolve It

Hypothetical Example

Was the Participant an Experienced User?

A study compares novice and experienced users of an educational platform. The codebook defines an experienced user as someone who used the platform regularly for at least six months before enrollment.

Original coding Participant 58 is coded as novice because the intake record states that the participant had used the platform twice before the study.
The outcome appears Participant 58 performs exceptionally well. Moving the participant into the experienced group would strengthen the difference between groups.
Outcome-driven recoding The researcher changes Participant 58 to experienced because “the performance suggests prior expertise,” despite having no new evidence of six months of regular use.
A legitimate alternative situation Instead, suppose the researcher discovers a previously overlooked enrollment record documenting eight months of regular platform use. That source evidence conflicts with the original code.
Defensible correction The researcher changes the code, records the reason, preserves the source evidence, and checks whether similar coding errors occurred elsewhere in the dataset.

The same cell changes from “novice” to “experienced” in both scenarios. The evidentiary basis for the change is what makes the situations fundamentally different.

05 · What Researchers Often Get Wrong

Common Misunderstandings About Changing Coding Decisions

Misconception

Once a Code Is Assigned, It Can Never Change

Codes can legitimately change when errors are discovered, evidence is clarified, or the coding framework develops. In some qualitative methodologies, iterative recoding is an expected part of analysis. The important issue is whether the revision is methodologically defensible and represented accurately.

Misconception

Changing a Code After Seeing an Outcome Automatically Means Falsification

No. Timing creates a potential source of bias but does not by itself establish misconduct. Researchers may discover genuine coding errors after outcomes become visible. The evidence and rationale for the change remain crucial.

Misconception

If Two Codes Are Both Plausible, I Can Choose Whichever Produces the Better Analysis

Ambiguity does not justify outcome-based selection. Use the coding framework, source evidence, adjudication procedure, or another defensible method to resolve the case. If genuine ambiguity remains analytically consequential, sensitivity analysis may be more informative than quietly choosing the favorable classification.

Misconception

A Coding Change Is Harmless If Only One Case Is Affected

A single case may have little or substantial analytical influence depending on the dataset. More importantly, the legitimacy of the change does not depend solely on its statistical effect. The research record should accurately represent the evidence regardless of whether the conclusion changes.

Misconception

Qualitative Coding Is Subjective, So Falsification Cannot Apply

Interpretive judgment does not mean there are no standards. Qualitative methodologies differ in how coding and interpretation proceed, but selective alteration or omission can still create a misleading representation of the underlying material. Evaluation should respect the accepted practices of the particular research tradition.

06 · What This Means for You

When a Code Changes, Preserve the Reason for the Change

If you reconsider a coding decision after outcomes are visible, separate two questions: “Is the old code actually wrong or inadequate?” and “Would changing it improve my result?” Only the first can provide the methodological basis for revision.

A simple coding-decision framework

If source evidence shows that the original code was incorrect
Correct the code, document the evidence, and check whether the same error affects comparable cases.
If the coding framework itself needs clarification
Define the revised rule explicitly and reconsider all relevant cases consistently under that rule.
If the case is genuinely ambiguous
Use an appropriate adjudication procedure, independent coding where feasible, or sensitivity analysis rather than resolving ambiguity according to the preferred outcome.
If the only reason for changing the code is that the result improves
Do not treat the analytical benefit as evidence that the new code is correct.
If a revised coding rule materially changes the conclusion
Preserve the original coding and explain the revision sufficiently for others to understand the sensitivity of the result.

Where coding changes amount to corrections of factual data, maintain an audit trail using the same principles applied when researchers document legitimate data corrections. The goal is not to freeze every first judgment forever. It is to make consequential revisions traceable.

07 · A Quick Checklist

Before Changing a Code After Seeing the Outcome, Check This

Before recoding a case or observation, check:
What evidence or methodological reason shows that the original coding should change?
Can you justify the revised code without referring to whether it strengthens your preferred result?
Does the revised code remain consistent with the source material and coding framework?
If the coding rule changed, have you reapplied the revised rule to all comparable cases?
Could the coding decision be adjudicated without knowledge of the outcome or group assignment where feasible?
Have you preserved the original code and documented the reason and timing of the change when consequential?
If multiple codings are genuinely defensible, have you examined whether the substantive conclusion depends on the choice?
Does the final research record accurately represent consequential coding decisions and revisions?
08 · Frequently Asked Questions

Frequently Asked Questions About Changing Coding Decisions

Can I correct a coding mistake after running the analysis?

Yes. Discovering the error after analysis does not make the correction improper. Verify the correct code from the source evidence or coding rule, document the correction, and rerun affected analyses as necessary.

Should I keep the original coding after correcting it?

For consequential changes, preserving an audit trail is good practice. How this is implemented varies by research setting, but another researcher should be able to understand what changed and why without confusing the superseded code with the final analytical value.

What if two coding decisions are equally defensible?

Use an appropriate adjudication procedure and consider whether the result is sensitive to the alternative coding. Choosing solely according to which version supports the hypothesis gives the outcome an inappropriate role in determining the code.

Is recoding qualitative data after reading the whole dataset misconduct?

No. Iterative recoding can be an ordinary feature of qualitative analysis. The appropriate process depends on the methodology. Researchers should nevertheless represent their analytical process accurately and avoid selectively changing or suppressing material simply to manufacture a preferred narrative.

Can I change my codebook during analysis?

Potentially. Some research designs anticipate evolving codebooks, while others use fixed prespecified classifications. If definitions change, document consequential revisions and apply the new rules consistently to relevant material rather than selectively changing favorable cases.

Does changing one code count as falsification?

Not automatically. The number of affected cases does not determine the classification. The issue is whether the change has a legitimate evidentiary or methodological basis and whether it causes the research to be inaccurately represented. A formal misconduct finding also requires the additional elements specified by the applicable policy.

Would having a second coder prevent this problem?

Not necessarily, but independent coding or adjudication can reduce the influence of one researcher's outcome preferences in some designs. The appropriate approach depends on the methodology and should not be imposed mechanically where independent coding is inconsistent with the research tradition.

09 · The Bottom Line

Codes Can Change; Their Justification Should Not Depend on the Result You Want

The Bottom Line

Changing a coding decision after seeing the outcome is not necessarily misconduct. A revision can be legitimate when evidence, error correction, or a defensible methodological refinement supports it, but outcome-driven recoding can become an integrity problem when it makes the research record misleading.

Use the source material and coding framework to decide what the code should be, apply revised rules consistently, and preserve consequential changes. Knowing the outcome does not prohibit reconsideration, but it does give you one more reason to make the basis for that reconsideration visible.

10 · Sources and Further Reading

Authoritative Sources on Coding Changes and Research Integrity

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