asplos-review-process

ASPLOS Review Process

ASPLOS 2027 runs a staged pipeline that differs from every sibling venue in two places: an explicit rapid-review screen on the first two pages, and a Major Revision outcome with journal-like mechanics. Everything below is the 2027 cycle as verified 2026-07-08; stage design is re-decided per edition.

Stage map

What the rapid review is for — in the CFP's own framing

The 2027 CFP models the screen on early triage at high-impact journals: most submissions may not advance past it, and the point is to concentrate expert reviewer effort on papers where the committee can review with high confidence. Two consequences for authors:

• The screen prioritizes work at the architecture-languages-OS intersection. A paper that reads like a pure single-community result in its first two pages is the archetypal rapid casualty, whatever its page-7 content.
• Rapid rejection is cheap and fast for the PC but carries little diagnostic signal for you beyond "the first two pages did not make the case." Re-aim the framing before re-aiming the venue.

Full review: what systems-intersection reviewers probe

A useful red-team script — have a non-author run it against the submitted PDF:

R1  Is the claimed coupling real? Try to mentally re-implement each half
    without the other; if either succeeds, expect a "why not <single venue>?"
R2  Is the baseline the strongest deployed alternative, tuned, on the same
    platform? Find one stronger baseline the paper skipped.
R3  Does the evidence class match the claim (silicon vs FPGA vs simulator)?
    Flag any latency/energy claim resting on an unvalidated model.
R4  Attribution: is the win traced to the mechanism via ablation, or asserted?
R5  Generality: does anything survive a workload/technology parameter change?
R6  Are the citation and formatting rules met? (Reviewers do notice.)