03 · What You Need to Know
Designing Fair Time Conditions for Human-AI Performance Evaluation
Why do time limits affect human-AI comparisons?
Time constraints influence how tasks are performed.
Human researchers may use additional time to consult evidence, reconsider an interpretation, or verify a calculation. Generative AI systems may produce answers rapidly but require additional processing when retrieval, code execution, or iterative verification is enabled.
Restricting both conditions to the same short deadline may therefore affect them differently.
However, this does not automatically make equal time limits inappropriate. If the intended application requires decisions within a fixed period, deadline-constrained performance may be precisely what the study needs to measure.
The methodological issue is whether the time constraint represents the intended task or introduces an artificial advantage.
What is the difference between a fixed-time and a completion-time evaluation?
Fixed-time evaluation
Measures task performance within a predefined deadline, with incomplete or late outputs handled according to established rules.
Completion-time evaluation
Measures how long each condition takes to produce an output meeting specified completion or acceptance criteria.
These designs answer different questions.
A fixed-time study may investigate which performer achieves greater accuracy within two minutes.
A completion-time study may investigate how long humans and AI require to produce an acceptable research summary.
Researchers should avoid treating results from one design as direct evidence for the other.
When are equal time limits scientifically justified?
Equal deadlines are appropriate when time is an essential characteristic of the intended application.
For example, a study might examine rapid identification of predefined errors during a time-sensitive review process.
Another study might compare human and AI performance under a standardized examination protocol.
In these cases, a common deadline can establish a meaningful performance constraint.
However, researchers should justify the duration and consider whether it permits both conditions to demonstrate the capabilities relevant to the research question.
A deadline selected merely because AI can easily meet it may produce a comparison with limited practical validity.
When should researchers avoid imposing identical deadlines?
Identical deadlines may be inappropriate when the study concerns ordinary professional workflows rather than performance under time pressure.
For example, a researcher preparing a systematic review ordinarily needs time to inspect source documents, verify eligibility criteria, and resolve ambiguous cases.
Comparing that process with AI generation under an arbitrary thirty-second deadline would not necessarily represent the actual workflow.
Instead, researchers may allow each condition to complete the task and record the elapsed time.
Output quality should then be evaluated using comparable acceptance criteria.
This approach can reveal whether faster generation translates into faster completion of acceptable work.
Which timing measures should researchers distinguish?
| Timing measure |
Definition |
Research relevance |
| Response latency |
Elapsed time from request submission to a defined response endpoint |
Technical responsiveness of the AI system |
| Time to first output |
Time until the first visible or streamed output appears |
Perceived responsiveness |
| Generation completion time |
Time required to produce the complete initial AI output |
Initial automated processing efficiency |
| Human task completion time |
Time required for a human to complete the specified task |
Human performance under defined conditions |
| Verification time |
Time required to check output correctness or acceptability |
Human oversight burden |
| Total workflow time |
Elapsed time required to obtain the final accepted result |
Practical productivity and operational efficiency |
These measures should not be treated as interchangeable.
In particular, initial AI generation time is not necessarily equivalent to the time required to obtain a verified research output.
Should AI generation time include prompt preparation?
The answer depends on the evaluation objective.
A model-level latency benchmark may reasonably begin timing when a standardized prompt is submitted.
A productivity study may need to include the time required to formulate prompts, prepare documents, select tools, and review generated results.
Prompt development can represent a substantial component of AI-assisted work, particularly when tasks require iterative refinement.
Researchers should therefore identify whether prompt preparation is included, excluded, or treated as a separate activity.
Excluding it may be appropriate for some technical evaluations but misleading for claims about total researcher productivity.
Should human preparation time be included?
Human preparation should be handled consistently with the research objective.
For example, experienced researchers may need to familiarize themselves with an unfamiliar interface or classification rubric before testing begins.
Such familiarization may be treated as preparation rather than task completion time.
However, consulting source material or examining methodological assumptions may be integral to performing the task and should not automatically be excluded.
Researchers should distinguish experimental familiarization from substantive work required for an acceptable answer.
Preparation rules should be established before testing.
How can researchers calculate total task completion time?
For a sequential workflow, total completion time can be calculated by adding the durations of the necessary stages.
If a comparable human-only task requires 15 minutes, the observed time difference is three minutes.
However, the comparison is meaningful only if both workflows produce outputs meeting comparable quality requirements.
How should researchers calculate time savings?
One descriptive measure expresses the difference in completion time relative to the baseline workflow.
This result describes the relative difference under the tested conditions.
It does not establish that the workflow will save 30% of time across all tasks or institutions.
Researchers should also distinguish the ratio of group mean times from the mean of participant-level percentage savings, because these calculations need not produce identical results.
How do time limits influence accuracy?
Time pressure may affect accuracy differently across tasks and performers.
Human participants may make more errors when they cannot verify information or reconsider difficult decisions.
AI systems may also experience quality changes when constrained by computational budgets, response lengths, or execution timeouts.
Researchers should therefore examine the relationship between time and correctness rather than assuming that speed and accuracy are independent.
A model that responds quickly but makes consequential errors may be less useful than a slower workflow that produces dependable results.
What is a speed-accuracy trade-off?
A speed-accuracy trade-off describes a relationship in which faster performance may be associated with reduced correctness, or greater deliberation may improve accuracy at the cost of additional time.
However, this relationship is not universal.
Some systems may be both faster and more accurate than alternatives.
Researchers should measure the relationship empirically rather than assuming that faster performance necessarily produces more errors.
For human-AI comparisons, relevant outcomes may include task accuracy at fixed deadlines, completion time at a defined quality threshold, or the distribution of errors across different time conditions.
Can researchers evaluate performance across several time limits?
Yes. A study can compare performance under several predefined deadlines.
For example, human and AI conditions might be evaluated with two-minute, five-minute, and ten-minute limits, provided these durations are meaningful for the task.
Such a design can reveal whether relative performance changes as more time becomes available.
However, repeated testing may introduce practice effects, fatigue, or exposure to earlier answers.
Researchers should consider randomization, counterbalancing, and appropriate statistical methods.
When the same AI system is tested repeatedly, model context and response variability should also be controlled or documented.
How should incomplete tasks be handled?
Researchers should establish rules for incomplete responses before evaluation.
In a fixed-deadline study, an unfinished task may count as unsuccessful, receive partial credit, or be classified separately, depending on the task requirements.
However, the same substantive completion criteria should generally apply across conditions.
Researchers should not exclude unfinished human responses while retaining incomplete AI responses, or vice versa, without justification.
Timeouts, refusals, and technical failures should also be documented.
Excluding incomplete cases can artificially improve reported performance when completion probability differs between conditions.
Should researchers measure accuracy per unit of time?
Accuracy per unit of time may appear attractive as an efficiency metric, but its interpretation requires care.
Dividing an accuracy proportion by elapsed time produces a ratio that may not correspond to a meaningful practical outcome.
For example, an extremely fast system with poor accuracy could obtain a favorable ratio despite producing unusable results.
Researchers may instead measure correctly completed tasks per hour or time required to obtain an output meeting predefined acceptance criteria.
These measures connect efficiency to actual task success.
However, they should still be interpreted alongside consequential error rates and the resources required for verification.
How should completion time be summarized statistically?
Completion times are often skewed rather than normally distributed.
Some tasks may be completed rapidly, while difficult cases require substantially longer periods.
Researchers may report medians, interquartile ranges, and relevant percentiles alongside means when appropriate.
When comparing conditions, the statistical method should account for paired tasks, repeated participants, and other dependencies.
For tasks that remain incomplete at the end of observation, time-to-event methods may be relevant if their assumptions match the study design.
Researchers should report uncertainty and avoid drawing strong conclusions from a small number of timing observations.
How do participant expertise and fatigue affect timing?
Human task completion time may vary with expertise, experience, task familiarity, and fatigue.
Experienced researchers may complete familiar tasks quickly but spend more time examining ambiguous cases.
Novices may require additional time to understand instructions or locate relevant information.
Researchers should document participant characteristics and consider whether task order influences performance.
For lengthy evaluations, breaks or balanced task allocation may be necessary.
The choice of human comparator population can therefore influence both speed and accuracy.
How should AI latency variability be handled?
AI response times may vary because of service load, network conditions, output length, tool use, or model configuration.
Researchers should avoid estimating AI speed from one request.
Repeated measurements under documented conditions can provide a more informative description.
When tool-enabled AI systems are evaluated, retrieval and code-execution time should be included if they are part of the intended workflow.
Researchers should distinguish model inference latency from total system completion time.
The broader principles of AI cost and speed evaluation apply.
Should human verification time be included in AI comparisons?
Yes, when verification is required to obtain an acceptable final output.
For example, an AI-generated research summary may take seconds to produce but several minutes to verify against the source article.
If the study concerns practical productivity, excluding verification time can exaggerate the apparent advantage.
Researchers should distinguish mandatory review from correction of AI-generated errors.
Both may contribute to total workflow time, but they represent different activities.
Evaluating human oversight requirements can help determine whether AI assistance genuinely reduces researcher workload.
Does faster performance establish greater productivity?
Not necessarily.
Productivity concerns the amount of acceptable work completed relative to the resources used.
Rapidly producing inaccurate or incomplete outputs may create additional correction work.
Conversely, a slower system may produce outputs requiring little verification.
Researchers should therefore assess whether the final outputs satisfy comparable quality criteria.
Claims that AI improves productivity should be supported by evidence about the complete workflow rather than generation speed alone.
How should researchers report timing conditions?
A transparent report should identify the timing objective, deadlines, start and end points, permitted preparation, tool access, and rules for incomplete tasks.
Researchers should explain whether the evaluation measures fixed-deadline performance or time required to obtain acceptable results.
Relevant participant characteristics, AI configurations, and environmental conditions should be documented.
Results should include appropriate measures of variability and uncertainty.
Conclusions should distinguish observed speed advantages from broader claims about competence, productivity, or professional replacement.