# Humrel Review Process

> Use when calibrating expectations for the Human Relations (HR) review process — the editorial scoping screen, double-anonymous developmental review, decision types, timelines, and when a sibling journal is the better route. Sets expectations; it does not draft the rebuttal (see humrel-rebuttal).

- Skill: `thedixitjain/humrel-review-process` (Agent Skill)
- Install (CLI): `npx skillmds add thedixitjain/humrel-review-process`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedixitjain/humrel-review-process/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: thedixitjain (https://skillmd.com/u/thedixitjain)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/thedixitjain/humrel-review-process

---



# Review Process (humrel-review-process)

## When to trigger

- A submission is in (or about to enter) the HR pipeline and you want to calibrate odds and timing
- A decision letter arrived and you must read it correctly (R&R vs. reject vs. resubmit-as-new)
- You are deciding whether to persist at HR or reroute to a sibling
- A coauthor expects fast quantitative-style turnaround and needs the developmental reality

## How HR review actually works

HR runs a **two-gate** process. First, an **editorial scoping screen**: the handling editor assesses fit and whether the manuscript shows a plausible "unique and substantive theoretical contribution." HR is explicit that "suitable data are a necessary but not sufficient feature to get to full peer review" — so a competent empirical paper with no theoretical advance, or one that reads as a sibling-journal paper, can be returned *before* reviewers see it. Second, if it passes, it goes to **double-anonymous peer review** (typically multiple reviewers) and a developmental cycle. Reviews engage the argument seriously and tend to push on theory, contribution, and craft as much as on method.

## What HR decisions usually mean

| Decision | Read it as | Your move |
|----------|-----------|-----------|
| Desk return (scoping) | fit/contribution not legible, or sibling-shaped | reframe (`humrel-contribution-framing` / `humrel-literature-positioning`) or reroute |
| Reject after review | a fundamental theory/contribution gap, not just fixes | rethink the contribution before any resubmission elsewhere |
| Major revision (R&R) | the *idea* is promising; deepen theory + evidence | revise substantively, then `humrel-rebuttal` |
| Minor revision | contribution accepted; tighten and clarify | targeted edits; do not reopen the theory |
| Conditional accept | nearly there | comply precisely; preserve anonymized files |

An R&R at HR is an invitation to make the contribution *deeper*, not merely to add robustness — treat it as a developmental opportunity.

## Calibrating expectations

- **Theory-first bar.** Acceptance turns on the theoretical contribution and HR fit, not on a clean estimate alone. Methodological polish without theoretical payoff underperforms.
- **Timelines vary** and are volatile; do not promise coauthors a specific turnaround (检索于 2026-06；以官网为准). Plan for a developmental, multi-round cycle rather than a fast accept/reject.
- **Plural-methods reality:** a strong ethnography or critical paper competes on equal footing with quantitative work — the binding question is always the contribution.

## When a sibling is the better route

If reviews repeatedly say the paper is empirically sound but theoretically thin, or that it belongs elsewhere, that is signal. Consider Work, Employment and Society (sociology of work), JMS (managerial relevance), AMJ (US empirical OB), Organization Studies (organization-theory internal), or Organization (critical) — see `humrel-literature-positioning` for the boundary logic. Rerouting is a strategy, not a defeat.

## Checklist

- [ ] You can name which gate the paper is at (scoping screen vs. full review)
- [ ] The decision type is read correctly (R&R ≠ accept; desk return ≠ reject-after-review)
- [ ] An R&R plan deepens the *contribution*, not just adds robustness
- [ ] No specific timeline promised to coauthors (volatile)
- [ ] Anonymized files preserved for the next round
- [ ] If reviews say "wrong journal," a reroute target is identified honestly

## Anti-patterns

- Treating the scoping screen as a formality and submitting a contribution-thin paper
- Reading "major revision" as "almost accepted" and revising superficially
- Promising coauthors a fixed turnaround
- Assuming quantitative work is favored (it is not — contribution decides)
- Resubmitting a rejected paper elsewhere without rethinking the theoretical gap reviewers named

## Output format

```text
【Journal】Human Relations
【Skill】humrel-review-process
【Gate】scoping screen / full double-anonymous review
【Decision read】desk return / reject / major R&R / minor / conditional
【Binding issue】theory/contribution / fit / method / craft
【Plan】deepen contribution + which humrel-* skills
【Reroute?】stay at HR / consider sibling (which + why)
【Next skill】humrel-rebuttal (if R&R)
```

---

**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Human-Relations-Skills/skills/humrel-review-process/SKILL.md`