A NAACL reviewer's first suspicion about related work is not that you missed a paper — it is that you missed a lineage: the chain of prior datasets, task definitions, and evaluation critiques your work silently inherits from. The section's job is to prove you know what you inherited and to state, in one checkable sentence, what you changed.
| Lineage | Question asked | Where it lives |
|---|---|---|
| Task lineage | Who defined this task and its metrics? | Anthology main + Findings volumes |
| Data lineage | What corpus is yours derived from, and what did its paper warn about? | Dataset papers, LREC-COLING, data cards |
| Method lineage | What is the nearest prior system, and is it a baseline? | *ACL venues + ML conferences |
| Evaluation critique | Has this metric or protocol been challenged? | Methodology papers, often at this very family of venues |
| Regional/community lineage | Who worked on these languages before, including outside English-language venues? | AmericasNLP and sibling workshops, LatinX in AI resources, regional journals |
The fifth row is where NAACL differs from its siblings. For work on languages of the Americas there is frequently a body of prior effort in workshop proceedings, regional publications, or Spanish- and Portuguese-language venues; a related-work section that cites only high-prestige anthology hits while ignoring the community that built the field's resources reads, at this chapter, as exactly the erasure the venue renamed itself to counter.
# Sweep the bibliography for suspicious entries before upload
grep -oE 'https?://aclanthology\.org/[^ }]+' refs.bib | sort -u | \
xargs -I{} sh -c 'curl -s -o /dev/null -w "%{http_code} {}\n" {}' | grep -v '^200'
# Anything non-200 gets hand-checked; no URL, no trust.
naacl/findings distinction.naacl-camera-ready guards against.Proceedings of NAACL, Findings of the ACL: NAACL 2025) rather than letting three formats coexist.If the paper was reviewed in an earlier cycle, related work is one of the places the mandatory change summary must be visible: reviewers get your prior reviews, so "R3 named two uncited baselines" followed by an unchanged section is a documented broken promise. Update the section, then say so in the summary with section numbers.
End the section with one sentence a reviewer could falsify:
"Unlike [nearest prior system], which evaluates on translated test sets, we evaluate on natively authored Spanish and Quechua data and show the translation-based protocol overstates accuracy by 6-9 points."
Test it: does it name the nearest work? Does it state a difference in method or evidence, not adjectives? Could a reviewer check it against your tables? If any answer is no, the section has organized citations but not positioned the paper.
[Lineage coverage] task / data / method / evaluation / regional -> ok or gap
[Delta sentence] <the falsifiable sentence>
[Citation-status errors] <Findings/workshop/preprint mislabels>
[Resolution sweep] <all resolve / list of failures>
[Resubmission trace] n/a | <reviewer ask -> section change>