MétaCan
Menu
Back to cohort
Record W2022503842 · doi:10.2308/aud.2006.25.1.69

“Order Effects” Revisited: The Importance of Chronology

2006· article· en· W2022503842 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueAuditing A Journal of Practice & Theory · 2006
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicAuditing, Earnings Management, Governance
Canadian institutionsSimon Fraser University
Fundersnot available
KeywordsAuditOrder (exchange)PsychologyPresentation (obstetrics)Audit evidenceAccountingTask (project management)Social psychologyBusinessInternal auditManagementEconomicsJoint audit

Abstract

fetched live from OpenAlex

This study examined whether auditors, when they are processing mixed evidence, take into consideration the chronological order of the evidence (giving rise to what this study refers to as a trend effect), or if their evaluations are influenced primarily by the order of presentation (giving rise to what the audit literature refers to as a recency effect). The study's primary objective was to determine whether awareness of the temporal order of evidence would prevent auditors from placing more weight on evidence that they most recently processed (i.e., whether the trend effect dominates the recency effect). Auditors were given an experimental task of going-concern assessment. Auditors evaluating undated mixed evidence exhibited recency effects similar in magnitude to those shown by auditors who were asked to evaluate dated mixed evidence, in which the presentation order was consistent with temporal order. However, auditors evaluating evidence in which temporal order and presentation order were varied orthogonally took into consideration the chronological order of the evidence. This, in turn, led to a significant reduction in the effect of recency. Additional analysis indicates that auditors who evaluated dated mixed evidence chose audit opinions consistent with the trend reflected by the chronology of the evidence.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.005
metaresearch head score (Gemma)0.066
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.829
Threshold uncertainty score0.942

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.066
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.005
GPT teacher head0.229
Teacher spread0.224 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it