Review Process (lang-review-process)
Knowing how Language actually evaluates a manuscript lets you pre-empt the objections before you
submit. Language runs double-anonymous review under co-editors and an editorial team, drawing
referees from across subfields, and it screens hard at intake: a paper that is a descriptive data
dump, that lives inside one framework, or that rests on undocumented data may be returned
before external review. This skill maps the process and stress-tests the paper against it.
When to trigger
- Before submission, to predict reviewer objections and the likely outcome
- After a decision letter, to read the outcome category correctly (then route to
lang-rebuttal)
- Deciding whether the piece fits a full article or a shorter/online section
- Calibrating expectations for a first-round outcome
What the process looks like (verify on the author pages)
- Intake screen. Editors check fit, section, anonymization, and whether the paper makes a
theoretically grounded claim for a general audience. Data dumps and framework-internal exercises can
be returned without review.
- Double-anonymous external review. Referees from the relevant subfields — and often one from
outside it — assess the generalization, the analysis, the evidence, engagement across frameworks, and
the transparency of data and glossing.
- Decision. Typical categories: accept (rare on first pass), minor revisions, major
revisions / revise-and-resubmit, reject. A substantive R&R is the normal good outcome.
- Perspectives track. A Perspectives target article is reviewed, then paired with invited
Commentaries and an author Rejoinder — a different rhythm from the standard article.
What reviewers are asked to weigh (anticipate each)
| Reviewer question |
Pre-empt it with… |
| Is there a real theoretical claim, not just description? |
lang-theory-building — state the general claim + predictions |
| Does it engage rival frameworks fairly? |
lang-literature-positioning — adjudicate, don't ignore |
| Can the data bear the generalization? |
lang-research-design — scope the claim to the evidence |
| Are the statistics appropriate? |
lang-data-analysis — mixed-effects, effect sizes, no pseudoreplication |
| Can I check the data and glosses? |
lang-data-and-transparency — share data/code, source glosses |
| Is it readable outside the subfield? |
lang-writing-style — theory-neutral statement, glossed jargon |
Desk-return filters (the intake traps)
| Intake trap |
Why it triggers a return |
Fix before submitting |
| Descriptive data dump |
no theoretical stakes |
frame what the data are a case of |
| Single-framework parochialism |
ignores rival analyses |
make the adjudicating prediction explicit |
| Undocumented data |
reviewers cannot check it |
source glosses; share analysis data/code |
| Wrong venue |
belongs at a subfield journal |
re-route, or broaden the claim |
| Anonymization break |
double-anonymous integrity |
strip identifiers and metadata |
Calibration (Language review culture, hedged)
Orienting heuristics, not guarantees; confirm process details on the current author pages. Language
review rewards a grounded, framework-fluent, checkable paper and is patient with careful revision:
the realistic first-round outcome for a promising submission is a major revision, not acceptance,
and the revision often asks you to broaden the framework engagement or firm up the statistics.
Illustrative: a phonetics paper returns with "revise and resubmit — strengthen the model and engage the
exemplar-theoretic alternative"; the productive response refits a mixed-effects model, adds the rival's
prediction and tests it, and documents the measurement pipeline, rather than defending the original as-is.
Anti-patterns
- Submitting without pre-empting the obvious cross-framework objection
- Reading a major-revision letter as a rejection (or a rejection as negotiable)
- Assuming a subfield-journal analysis will clear the general-audience bar unchanged
- Ignoring the intake filters and getting returned before review
- Treating a Perspectives Commentary like a standard referee report
Output format
【Predicted intake risk】data-dump / parochial / undocumented / wrong-venue / anon-break / none
【Top reviewer objections】the 2–3 most likely, with the pre-empting skill
【Likely first-round outcome】accept / minor / major-R&R / reject (hedged)
【Section fit】full article / research report / online section / Perspectives
【Action】fixes to make before submission
【Next】lang-submission (pre-decision) or lang-rebuttal (post-decision)
Supplementary resources
1---2name: lang-review-process3description: Use when anticipating how a Language (LSA) manuscript will be judged — the double-anonymous review, the general-audience and cross-framework bar, the desk-return filters (descriptive data dump, single-framework parochialism, undocumented data), and the decision categories. Sets expectations and stress-tests before submission; it does not write the paper.4---56# Review Process (lang-review-process)78Knowing how *Language* actually evaluates a manuscript lets you pre-empt the objections before you9submit. *Language* runs **double-anonymous** review under co-editors and an editorial team, drawing10referees from **across subfields**, and it screens hard at intake: a paper that is a **descriptive data11dump**, that lives **inside one framework**, or that rests on **undocumented data** may be returned12before external review. This skill maps the process and stress-tests the paper against it.1314## When to trigger1516- Before submission, to predict reviewer objections and the likely outcome17- After a decision letter, to read the outcome category correctly (then route to `lang-rebuttal`)18- Deciding whether the piece fits a full article or a shorter/online section19- Calibrating expectations for a first-round outcome2021## What the process looks like (verify on the author pages)2223- **Intake screen.** Editors check fit, section, anonymization, and whether the paper makes a24 theoretically grounded claim for a general audience. Data dumps and framework-internal exercises can25 be **returned without review**.26- **Double-anonymous external review.** Referees from the relevant subfields — and often one from27 outside it — assess the generalization, the analysis, the evidence, engagement across frameworks, and28 the transparency of data and glossing.29- **Decision.** Typical categories: **accept** (rare on first pass), **minor revisions**, **major30 revisions / revise-and-resubmit**, **reject**. A substantive R&R is the normal good outcome.31- **Perspectives track.** A Perspectives target article is reviewed, then paired with invited32 **Commentaries** and an author **Rejoinder** — a different rhythm from the standard article.3334## What reviewers are asked to weigh (anticipate each)3536| Reviewer question | Pre-empt it with… |37|-------------------|-------------------|38| Is there a real theoretical claim, not just description? | `lang-theory-building` — state the general claim + predictions |39| Does it engage rival frameworks fairly? | `lang-literature-positioning` — adjudicate, don't ignore |40| Can the data bear the generalization? | `lang-research-design` — scope the claim to the evidence |41| Are the statistics appropriate? | `lang-data-analysis` — mixed-effects, effect sizes, no pseudoreplication |42| Can I check the data and glosses? | `lang-data-and-transparency` — share data/code, source glosses |43| Is it readable outside the subfield? | `lang-writing-style` — theory-neutral statement, glossed jargon |4445## Desk-return filters (the intake traps)4647| Intake trap | Why it triggers a return | Fix before submitting |48|-------------|--------------------------|-----------------------|49| Descriptive data dump | no theoretical stakes | frame what the data are a *case of* |50| Single-framework parochialism | ignores rival analyses | make the adjudicating prediction explicit |51| Undocumented data | reviewers cannot check it | source glosses; share analysis data/code |52| Wrong venue | belongs at a subfield journal | re-route, or broaden the claim |53| Anonymization break | double-anonymous integrity | strip identifiers and metadata |5455## Calibration (Language review culture, hedged)5657Orienting heuristics, not guarantees; confirm process details on the current author pages. *Language*58review rewards a **grounded, framework-fluent, checkable** paper and is patient with careful revision:59the realistic first-round outcome for a promising submission is a **major revision**, not acceptance,60and the revision often asks you to broaden the framework engagement or firm up the statistics.61Illustrative: a phonetics paper returns with "revise and resubmit — strengthen the model and engage the62exemplar-theoretic alternative"; the productive response refits a mixed-effects model, adds the rival's63prediction and tests it, and documents the measurement pipeline, rather than defending the original as-is.6465## Anti-patterns6667- Submitting without pre-empting the obvious cross-framework objection68- Reading a major-revision letter as a rejection (or a rejection as negotiable)69- Assuming a subfield-journal analysis will clear the general-audience bar unchanged70- Ignoring the intake filters and getting returned before review71- Treating a Perspectives Commentary like a standard referee report7273## Output format7475```76【Predicted intake risk】data-dump / parochial / undocumented / wrong-venue / anon-break / none77【Top reviewer objections】the 2–3 most likely, with the pre-empting skill78【Likely first-round outcome】accept / minor / major-R&R / reject (hedged)79【Section fit】full article / research report / online section / Perspectives80【Action】fixes to make before submission81【Next】lang-submission (pre-decision) or lang-rebuttal (post-decision)82```8384## Supplementary resources8586- [`../../resources/external_tools.md`](../../resources/external_tools.md) — tooling to close the gaps reviewers flag87- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — Language editorial and review-process sources
brycewang-stanford