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

Can Researchers Combine AI Outputs Collected Before and After a Model Update?

Combining AI-generated data across model versions may introduce measurement inconsistencies that affect research conclusions. Learn when pooling is defensible, how to assess equivalence, and what alternatives are available when outputs differ.

1065
Combining AI Outputs Across Model Updates Guide 1065 of 1196
01 · The Question

Can AI-Generated Research Data From Two Model Versions Be Analyzed Together?

A researcher uses an AI model to classify interview responses, extract variables from scholarly articles, or score student writing. Halfway through the project, the AI provider updates the model. The remaining observations are processed using the newer version.

Both versions produce the same categories or numerical scores. Does that mean their outputs can be combined into one dataset?

Not necessarily. If the versions apply different decision boundaries, interpret instructions differently, or produce different error patterns, pooling their outputs may introduce artificial differences into the analysis.

The methodological question is whether observations generated by different AI versions remain sufficiently comparable for the intended scientific interpretation.

02 · The Short Answer

Combining AI Outputs Is Possible When Their Comparability Is Defensible

In Brief

Researchers can combine AI outputs collected before and after a model update when there is sufficient evidence that the outputs are comparable for the intended research purpose. Using the same labels, scoring scale, or prompt does not establish equivalence. Researchers should evaluate version-related differences and their potential effects on the study's measurements and conclusions before pooling the data.

When comparability cannot be established, alternatives may include reprocessing observations with one validated model version, analyzing version-specific data separately, or conducting sensitivity analyses. The appropriate approach depends on the model's role, the available original data, and whether version-related differences can be distinguished from other study effects.

03 · What You Need to Know

When AI Outputs From Different Versions Can Support a Common Analysis

Why Is Combining AI Outputs a Measurement Problem?

When AI-generated classifications, scores, or extracted values become research variables, the AI system forms part of the measurement procedure.

For the resulting observations to be meaningfully compared, researchers need confidence that the procedure produces sufficiently consistent interpretations across relevant conditions.

Suppose an AI model scores students' critical reflection on a five-point scale. The original version emphasizes evidence-based reasoning, while the updated version places greater weight on writing fluency. Both produce scores from 1 to 5, but those scores may no longer represent the intended construct in the same way.

Combining them without investigation could introduce measurement differences that are incorrectly interpreted as differences between students or changes over time.

This concern is closely related to treating AI updates as potential research instrument changes.

What Does Comparability Mean for AI-Generated Data?

Comparability means that outputs produced under different measurement conditions can support the same intended interpretation with an acceptable degree of uncertainty.

It does not necessarily require every individual output to be identical.

For example, two validated human raters may occasionally disagree while still producing measurements sufficiently consistent for a particular research purpose. Similarly, two AI versions may produce some different outputs without making every combined analysis invalid.

The acceptability of those differences depends on their magnitude, pattern, and consequences.

Output consistency The extent to which model versions produce identical or similar results for the same inputs.
Measurement comparability The extent to which outputs from different versions support equivalent interpretations and intended analytical uses.

A high output-agreement rate can support comparability, but it does not establish validity if both versions make similar errors.

What Types of AI Outputs May Be Combined?

The required evidence depends on the type of output and its role in the analysis.

Output Type Potential Version Difference Relevant Evaluation
Binary classifications Different positive and negative assignments Paired agreement, sensitivity, specificity, and discordant-case analysis
Multicategory labels Different category boundaries or confusion patterns Confusion matrices, category-specific agreement, and reference-based evaluation
Ordinal rubric scores Different scoring thresholds or severity Paired score distributions, weighted agreement, and rubric alignment
Continuous measurements Systematic offsets or changes in variability Paired differences, agreement analysis, and measurement error assessment
Extracted numerical values Different extraction or interpretation errors Comparison with source records and field-specific accuracy
Generated qualitative codes Different interpretations or thematic boundaries Codebook alignment, expert review, and examination of discrepant cases
Free-text summaries Different omissions, emphasis, or unsupported statements Source-grounded assessment of fidelity and completeness

Pooling numerical measurements is not the same as combining qualitative interpretations. Researchers should use evaluation methods appropriate to the data and the epistemological assumptions of the study.

How Can Researchers Test Comparability Between Model Versions?

A useful approach is to construct a bridge sample: a representative collection of observations processed by both model versions.

Where possible, the sample should cover the range of values, difficult cases, relevant subgroups, and conditions likely to influence the outputs.

The comparison should use the same original inputs, task instructions, and reference standards wherever feasible.

Researchers can then examine whether differences are random, systematic, concentrated in particular categories, or associated with participant or document characteristics.

For consequential research variables, an independent reference standard is particularly valuable. Agreement between model versions alone cannot establish that either version measures the intended construct correctly.

When planning the comparison, researchers should distinguish material changes in model performance from differences that are inconsequential for the intended analysis.

Is High Agreement Enough to Justify Pooling?

Not always. Overall agreement can conceal important patterns.

Consider a classifier that labels most observations as negative. Two versions might agree on 95% of cases while disagreeing disproportionately on rare positive cases that are central to the research question.

Similarly, two scoring systems may have highly correlated outputs while one systematically assigns higher scores.

Researchers should examine the distribution and severity of disagreements, not merely an aggregate agreement percentage.

For continuous measurements, the Bland–Altman approach provides a framework for examining agreement and systematic differences between measurement methods. For categorical data, agreement statistics and confusion matrices may be more appropriate.

The statistical method should match the measurement scale and intended interpretation.

Should Researchers Define an Acceptable Difference Before Comparing Versions?

Where feasible, yes. Defining an acceptable difference before examining the results helps prevent researchers from selecting a convenient threshold after observing the data.

An equivalence margin should reflect the substantive consequences of measurement differences.

For example, a one-point discrepancy on a five-point assessment scale may be consequential if it changes a student's classification into a predefined proficiency category. The same numerical difference may be less consequential in another analytical context.

Researchers should justify the margin using the measurement purpose, existing validation evidence, expert judgment, or relevant methodological standards.

Statistical nonsignificance is not evidence of equivalence. A small study may fail to detect an important difference simply because its estimates are imprecise.

When formal equivalence testing is appropriate, the analysis should assess whether the confidence interval for the relevant difference falls within a justified equivalence margin.

What if the Model Update Occurs at the Same Time as a Change in the Study Population?

This creates a particularly difficult interpretation problem.

Suppose the original model processes responses from the first semester, while the updated model processes responses from the second semester.

If the later scores are higher, the difference could reflect a genuine change in participants, a change in the model, or both.

When model version and study period are completely aligned, their effects may be statistically inseparable without additional information or design features.

A bridge sample processed by both versions can help identify measurement differences. Reprocessing a common collection of original observations may also provide useful evidence.

Simply adding a model-version indicator to a regression does not resolve perfect confounding between version and time.

Can Statistical Adjustment Make Outputs From Different Versions Comparable?

Sometimes, but only under defensible assumptions.

If the relationship between versions can be estimated reliably using overlapping observations, researchers may be able to develop a calibration or harmonization procedure.

However, a simple numerical correction may be inadequate when the update changes category definitions, construct interpretation, or subgroup-specific error patterns.

Statistical adjustment also introduces uncertainty that should be reflected in subsequent analyses.

Researchers should avoid treating harmonization as a purely computational problem when the underlying measurement meaning may have changed.

Is Reprocessing All Data With One Model Version Better Than Pooling Mixed Versions?

Reprocessing can be a strong option when original inputs remain available and a single validated version can be applied consistently.

It may eliminate version-related differences in the measurement procedure, although ordinary model variability and other sources of error remain.

However, reprocessing is not always possible or desirable.

If AI outputs influenced participant interactions, adaptive interventions, or real-time decisions, later reprocessing cannot recreate the original experience.

Likewise, a newer model should not automatically replace an earlier one merely because it is more recent. Its suitability for the research task must be established.

When an update occurs during data collection, researchers should consider whether affected processing should be temporarily paused while comparability is evaluated.

When Should Researchers Analyze Model Versions Separately?

Separate analysis may be appropriate when the versions measure meaningfully different quantities, when equivalence cannot be demonstrated, or when the research question explicitly concerns differences between versions.

Version-specific analyses can preserve transparency and avoid presenting heterogeneous measurements as interchangeable.

However, separating data may reduce statistical precision and complicate longitudinal interpretation.

Researchers should also examine whether each version is confounded with participant characteristics, collection periods, or other study conditions.

Separate reporting does not automatically solve those design limitations, but it can make them visible.

How Should Researchers Conduct Sensitivity Analyses?

Sensitivity analyses examine whether substantive conclusions change under alternative defensible analytical decisions.

For mixed-version AI data, researchers might compare results obtained from the pooled dataset, version-specific subsets, or a consistently reprocessed dataset.

They may also investigate the effect of excluding uncertain observations or applying a justified calibration procedure.

These analyses should not be used to select whichever result most strongly supports the hypothesis.

Instead, researchers should report how conclusions vary across plausible approaches and explain which assumptions each analysis requires.

If results change substantially depending on how model versions are handled, that instability is itself important methodological information.

What Should Researchers Report When Combining AI Outputs?

The methods section should identify the model versions, processing dates, relevant configurations, and number of observations generated under each version.

Researchers should describe the evidence supporting comparability, including the bridge sample, reference standards, agreement measures, and any predefined acceptance criteria.

If outputs were calibrated, reprocessed, or analyzed separately, those procedures should be explained.

Where appropriate, report sensitivity analyses and limitations related to unavailable versions, incomplete logs, or uncertainty about deployment changes.

These details help preserve the interpretability of the study even when AI performance evidence becomes less applicable to newer systems.

04 · A Practical Example

Deciding Whether to Pool Student Reflection Scores From Two AI Models

Hypothetical Example

A Longitudinal Study Using Two Versions of an AI Scoring System

A research team evaluates changes in university students' critical reflection over a semester. The first 150 reflections are scored using Model A, while another 150 are scored after the provider introduces Model B.

Both models assign scores from 1 to 5 using the same written rubric.

Step 1: Identify the pooling assumption.

The team recognizes that combining the scores requires evidence that both versions produce measurements suitable for the same interpretation.

Step 2: Construct a bridge sample.

The researchers select 80 reflections covering different score levels and response characteristics. Both models score the same responses.

Step 3: Establish reference judgments.

Trained human raters independently score the reflections using the predefined rubric and resolve disagreements through an agreed procedure.

Step 4: Examine differences.

Suppose Model B assigns scores one point higher than Model A for 24 reflections, one point lower for 6, and identical scores for 50. The imbalance suggests a possible upward shift that warrants further investigation.

Step 5: Assess construct alignment.

The team compares both models with the human reference scores and investigates whether the differences are associated with response length, writing fluency, or actual critical-reflection quality.

Step 6: Choose an analytical strategy.

If the original reflections remain available, the team may reprocess all 300 responses using one validated model version. If that is impossible, version-specific analyses and sensitivity analyses may be necessary.

Step 7: Report the implications.

The final manuscript documents the model change, comparison results, selected analytical procedure, and remaining uncertainty.

The hypothetical results do not establish that Model B is less accurate. They indicate that the two versions may not be interchangeable without further evaluation.

Pooling the original scores without investigating the systematic difference could produce an artificial increase in measured critical reflection over time.

Reprocessing with a single validated version may reduce this particular source of inconsistency, but the resulting scores still require appropriate validity evidence.

05 · What Researchers Often Get Wrong

Common Mistakes When Combining AI-Generated Data Across Versions

Misconception

Does the Same Output Scale Mean Two AI Versions Are Equivalent?

No. Identical labels or numerical ranges do not establish that the versions apply the same criteria or measure the same construct consistently.

Misconception

Is High Correlation Enough to Justify Pooling AI Scores?

No. Strong correlation can coexist with systematic differences. Researchers should examine agreement, bias, and the consequences of individual-level discrepancies.

Misconception

Does a Nonsignificant Difference Prove That Model Versions Are Equivalent?

No. Failure to reject a difference does not establish equivalence. Appropriate equivalence analysis requires a justified margin and sufficiently precise estimates.

Misconception

Can a Regression Variable Always Correct for Model Version?

No. Statistical adjustment may be inadequate when version is completely confounded with time, when measurement meaning changes, or when the version effect cannot be estimated reliably.

Misconception

Should Researchers Always Replace Earlier Outputs With Those From the Newest Model?

No. A newer model is not automatically more valid for the intended task. Reprocessing should use a system with adequate evidence of measurement suitability.

Misconception

Does Reporting the Model Update Make Pooling Scientifically Acceptable?

No. Transparency is necessary, but disclosure alone does not establish comparability. Researchers should provide evidence or acknowledge the analytical limitations created by mixed-version measurements.

06 · What This Means for You

How to Choose Between Pooling, Reprocessing, and Separate Analysis

The appropriate decision depends on the measurement role of the AI system and the strength of the available comparability evidence.

Begin by determining whether model version could change the substantive meaning or statistical properties of the research variable.

A simple decision framework

If the AI outputs are peripheral and do not determine research variables
Use verification proportionate to their role without automatically imposing a formal pooling analysis.
If representative testing supports acceptable measurement equivalence
Pooling may be defensible, provided the evidence and remaining limitations are documented.
If original inputs are available and versions differ materially
Consider reprocessing all observations with one validated model version.
If equivalence is uncertain and reprocessing is impossible
Consider version-specific analyses, sensitivity analyses, or appropriately qualified conclusions.
If model version is completely confounded with collection period
Avoid claiming that statistical adjustment alone separates model effects from genuine temporal differences.
If the outputs influence consequential participant decisions
Apply stronger validation and oversight before relying on combined results.

For long-running studies, establish a version-tracking procedure before data collection begins. Preserve raw inputs and reference judgments where permissible, and consider using a fixed model version when measurement continuity is important.

The central objective is not to make all outputs numerically identical. It is to ensure that combining them does not create misleading evidence about the phenomenon under investigation.

07 · A Quick Checklist

Before Combining AI Outputs Across Model Versions, Check These Points

Before pooling AI-generated research data, check:
Identify which observations were processed by each model version.
Document the relevant model identifiers, prompts, configurations, and processing dates.
Define the research construct and intended interpretation of the AI-generated variable.
Construct a representative bridge sample processed by both versions when feasible.
Compare outputs against independent reference judgments where appropriate.
Examine systematic differences, subgroup effects, and consequential disagreements.
Define and justify acceptable measurement differences before interpreting equivalence results.
Determine whether model version is confounded with time, participant groups, or other study conditions.
Consider reprocessing, separate analysis, or sensitivity analysis when pooling is uncertain.
Report the comparability evidence, analytical decision, and remaining limitations.
08 · Frequently Asked Questions

Frequently Asked Questions About Combining AI Outputs From Different Versions

Can I combine AI-generated scores from two model versions?

Potentially, if evidence supports adequate measurement comparability for the intended analysis. Identical scoring scales alone are insufficient.

What if the two AI versions agree on most observations?

High agreement is useful evidence, but researchers should examine where disagreements occur, their consequences, and whether both versions align with an appropriate reference standard.

Can I use a statistical test to prove the versions are equivalent?

Formal equivalence testing may be appropriate for some outcomes, provided a defensible equivalence margin and suitable statistical design are available. A nonsignificant difference test does not establish equivalence.

Should I reprocess all data using the latest AI model?

Not automatically. Reprocessing with one validated version may improve consistency, but the latest model must be suitable for the research task, and original inputs must remain available.

Can I include model version as a covariate in regression?

Sometimes, if the design provides sufficient information to estimate version-related differences and the adjustment is substantively justified. It cannot resolve complete confounding or changes in the meaning of measurements.

What if the old AI model is no longer accessible?

Archived inputs, outputs, and reference judgments may support partial comparison. If equivalence cannot be established, researchers should consider alternative analyses and disclose the limitation.

Does this problem also affect qualitative research?

Yes. Updated AI systems may interpret codes, themes, or contextual meanings differently. Researchers should examine codebook consistency, interpretive differences, and the role of human judgment rather than relying solely on numerical agreement.

Can AI outputs be combined if the model update did not change overall accuracy?

Possibly, but similar overall accuracy does not establish measurement equivalence. Error patterns, systematic differences, and the intended analytical use must also be considered.

09 · The Bottom Line

Pooling AI Outputs Requires Evidence of Comparable Measurement

The Bottom Line

Researchers can combine AI outputs generated before and after a model update when the outputs remain sufficiently comparable for the intended scientific interpretation. Shared labels, prompts, or numerical scales do not establish that comparability.

Use representative cross-version testing, appropriate reference standards, and sensitivity analyses to support the decision. When meaningful differences remain unresolved, reprocessing with one validated version or reporting version-specific results may be more defensible than treating heterogeneous measurements as interchangeable.

10 · Sources and Further Reading

Authoritative Sources on Measurement Agreement, Equivalence, and AI Evaluation

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