Arsoc editor strategy

Editor & Committee Strategy (arsoc-editor-strategy)

When to trigger

• The Editorial Committee invited the topic and you are negotiating the review's scope
• You want to anticipate what ARSoc reviewers of a review will push on (different from a paper)
• The editor has asked you to expand, cut, or rebalance coverage
• You are calibrating how the Committee review cycle and the Annual Reviews production timeline work

Who you are working with at ARSoc

ARSoc is run by an Editorial Committee — an editor (检索于 2026-06：co-editors Douglas Massey & Mary C. Waters；以官网为准), associate editors, regular members serving multi-year terms, and occasional one-year guest members — plus the journal's production team at Annual Reviews. Your primary partners differ by phase: the commissioning editor / Committee owns scope and acceptance; the production editor owns format, figures, copyediting, and the volume schedule. Because the article is commissioned, the relationship is more collaborative than adversarial — the Committee wants the review to succeed — but acceptance is not automatic: an invited manuscript is still assessed for accuracy, rigor, and balance (检索于 2026-06；以官网为准).

How review differs for a review article

ARSoc reviewers do not check an identification strategy or replicate results — there are none of the author's own. They evaluate the review as a review:

Reviewer question	What they are really checking
Is the coverage complete?	the saturation/coverage account from arsoc-literature-synthesis / arsoc-transparency-and-reproducibility — can they name an omitted literature?
Is it balanced and accurate?	even-handedness across schools and methods; no self-promotion (arsoc-comprehensiveness-and-balance)
Is there a real framework?	the spine vs. an annotated bibliography (arsoc-organizing-framework)
Is it accessible?	can a sociologist from another subfield follow it (arsoc-writing-style)
Are the appraisals fair and correct?	does the author characterize each study's contribution and limits accurately
Is it the right scope?	not too narrow (specialist review) nor unfinishably broad (handbook)

Reviewers of an ARSoc review are often the reviewed authors themselves — the people whose work is being weighed will read how you weighed it. This makes balance and accurate attribution strategic, not just ethical.

Sociology-specific editorial posture

• Treat the editor conversation as a scope contract about traditions, methods, and levels of analysis: theory, ethnography, historical/comparative work, surveys, experiments, networks, demography, and computational sociology do not ask identical evidence questions.
• When an editor asks for broader coverage, answer by naming which sociological debate the added work changes: mechanism, institution, inequality axis, cultural process, population pattern, organizational field, or methodological boundary.
• Push back on additions that flatten traditions into a bibliography; ARSoc value comes from mapping a debate and its tensions, not from treating every subfield as interchangeable coverage.

Scope negotiation with the Committee

• Lock scope early, in writing. The invitation/acceptance stage is where scope is cheapest to change. Confirm the boundaries — including which traditions and methods are in — before months of reading.
• Negotiate, don't capitulate, on coverage asks. If a referee or editor wants an added literature, assess whether it fits the spine; propose where it goes or explain why it is out of scope — a review cannot grow without bound and must stay in the word/page envelope (检索于 2026-06；以官网为准).
• Surface conflicts of interest. If a likely reviewer is a central author you must critique, tell the editor — Annual Reviews requires disclosure of potential bias, and it protects both the process and you.
• Respect the volume schedule. ARSoc publishes one volume per year; production has fixed deadlines. A late draft can slip a whole volume. Confirm the timeline with the production editor and plan backward from it.
• Keep a coverage ledger. Maintain a short, sharable record of what is in scope and why (and what was deliberately excluded), so when the editor or a referee asks "why not X?", you answer with a decision already made.

Checklist

• Scope agreed with the commissioning editor in writing at the invitation stage (traditions + methods specified)
• Anticipated the six review-referee questions (coverage, balance/accuracy, framework, accessibility, appraisal, scope)
• Coverage-expansion asks evaluated against the spine and the word/page envelope before agreeing
• Conflicts of interest (reviewers who are reviewed authors) flagged to the editor
• Attribution and appraisals double-checked, knowing reviewed authors may referee
• Volume/production timeline calibrated with the production editor (volatile — confirm)
• A plan for which asks you accept vs. push back on, with reasons

Anti-patterns

• Treating an invitation as guaranteed acceptance — invited reviews are still assessed for rigor and balance
• Accepting every "please also cover…" until the review loses its spine and overruns the envelope
• Mischaracterizing a reviewed author's work when that author may be your reviewer
• Hiding a conflict of interest instead of disclosing it (Annual Reviews requires disclosure)
• Missing the production deadline and slipping the volume
• Asserting current editors / timeline / process from memory rather than the live Annual Reviews pages

Output format

【Scope agreement】boundaries (traditions + methods) locked with editor in writing? Y/N
【Referee anticipation】coverage / balance / framework / accessibility / appraisal / scope — prepared each? Y/N
【Coverage asks】evaluated against spine + envelope; accept/push-back plan? Y/N
【COI】reviewed-author referees flagged to editor? Y/N
【Timeline】volume/production schedule calibrated? Y/N · 待核实
【Source status】current editors/process re-confirmed on Annual Reviews pages? Y/N
【Next step】→ arsoc-submission (delivery preflight)