11 August 2026 · 5 min read

What a student workshop actually rewards

The ACL 2026 Student Research Workshop took 130 of 402 submissions. Its public process says what it selects for: one thing proved, one measured, one related to the field.

My undergraduate paper on the CYK algorithm was selected for the ACL 2026 Student Research Workshop, and the most useful thing I learned from the process was not about parsing. It was about what a workshop like that is built to select for, which you can read off its public process without any inside knowledge at all. The preface to the proceedings gives the numbers: 402 submissions, 379 direct and 23 committed through ACL Rolling Review, 130 accepted, an acceptance rate of 34.7% against 32.2% the year before, 109 archival papers and 21 non-archival, and 114 submissions that went through the optional pre-submission mentoring.

Those numbers describe a selective venue that nonetheless explicitly welcomes work in progress from students. That combination is unusual, and it tells you a lot about what a reviewer at such a venue is looking for.

What the process says

The call for papers laid out the year. Pre-submission mentoring closed on 13 February 2026 and feedback went back on 26 February. Direct submissions closed on 19 March, ARR commitments on 16 April, reviews were returned on 24 April, and the accepted list was published on 10 June, ahead of the workshop with ACL in San Diego in early July.

The ACL 2026 Student Research Workshop calendar A timeline with six dates in 2026: mentoring deadline 13 February, mentoring feedback 26 February, direct submission deadline 19 March, ARR commitment deadline 16 April, reviews returned 24 April, accepted papers listed 10 June. 13 Feb Mentoring closes 26 Feb Feedback sent 19 Mar Submission 16 Apr ARR commitment 24 Apr Reviews back 10 Jun Accepted list
Source: ACL 2026 SRW call for papers.

Three features of that process matter. First, mentoring is optional and comes before submission, which means the venue expects that a student's writing, not their idea, is the likeliest weak point, and offers to fix it early. Second, every submission gets full double-blind review, or arrives with ARR reviews already attached, which means the venue is not grading effort; it is checking claims. Third, work in progress is explicitly welcome, which means the venue would rather have a small result it can verify than a large one it cannot.

A fourth feature hides in the archival split. Of the 130 accepted papers, 21 are non-archival: the authors present at the workshop, get the reviews and the audience, and keep the right to publish the work somewhere else later. That option exists because the venue knows that student work is often the first version of something, and it would rather see the first version presented than held back for a main conference that may be a year away. For a student choosing between the two, the archival choice is a statement about whether this version is the finished statement of the result or a milestone on the way to one, and it is worth deciding before submission rather than after acceptance.

ACL 2026 SRW submissions and acceptances Two columns: 402 submissions and 130 accepted papers, an acceptance rate of 34.7%. Of the accepted papers, 109 are archival and 21 non-archival. Submitted and accepted, 2026 Papers; 34.7% accepted, against 32.2% in 2025 402 Submitted 130 Accepted 109 archival 21 non-archival
Source: Proceedings of the ACL 2026 Student Research Workshop, preface.

Prove, measure, relate

What a reviewer can check falls into three kinds. A claim with a proof, which they check by reading the proof. A claim with a measurement, which they check by reading the table and the method that produced it. A claim that places the work against a current line of research, which they check against what they already know. I have come to think of a paper that clears a venue like this as one that contains exactly one strong claim of each kind, stated so that all three are findable from the abstract. I call it the prove-measure-relate triad, and I use it as a self-review before anything goes out.

The triad is not a template for the paper's sections. It is a test of whether the paper has a checkable spine. A reviewer with three papers to read tonight is looking for the thing they can verify, and a paper that makes six claims of which two are checkable is weaker on all six than a paper that makes three claims of which three are checkable.

The reason the three kinds are different is that each fails differently and each is checked with a different tool. A proof fails by having a gap, and the reviewer finds it by reading slowly. A measurement fails by measuring the wrong thing or by having no baseline, and the reviewer finds it by asking what the table would look like if the claim were false. A relation fails by placing the work next to something it does not resemble, and the reviewer finds it because they know the neighbouring work better than the author does. A paper that leans on one kind alone leaves two of the reviewer's tools idle, and an idle reviewer looks for other things to say.

Applied to the CYK paper, the spine looks like this. The proved claim: a deterministic CYK recogniser built from first principles runs in O(n cubed times the grammar size) time and O(n squared) space, with the proof written out rather than cited. The measured claim: that implementation benchmarked against LR(1), Earley and recursive descent parsers on the same grammars, with the comparison in a table. The related claim: the probabilistic extension, Viterbi decoding over a PCFG in the log domain, placed against Compound PCFGs and against transformer-constrained neural parsing, with the Pumping Lemma proofs marking where context-free recognition stops. Each claim is one sentence in the abstract and one section in the paper.

The triad mapped onto the paper Three boxes in a row, labelled prove, measure and relate, each with the claim from the CYK paper that fills it: the complexity proof, the benchmark against three parsers, and the placement against Compound PCFGs and neural parsing. Below each box, the reviewer's check: read the proof, read the table, compare with the field. Prove O(n^3 |G|) time O(n^2) space proof written out Measure CYK against LR(1), Earley, recursive descent one table, one method Relate PCFG Viterbi in log space against Compound PCFGs and neural parsing reviewer reads the proof reviewer reads the table reviewer vs the field each claim is one sentence in the abstract and one section in the paper
Illustrative: the spine of the paper as the triad sees it, not a diagram of its table of contents.

What the triad cuts

The value of the test is in what it refuses. A second measurement that does not support one of the three claims is a distraction, even if it took a week. A background section that explains what a context-free grammar is belongs in a dissertation and not in a workshop paper, because no reviewer at ACL needs it and every reviewer will notice the pages it costs. A claim of novelty without one of the three kinds of support behind it is the claim reviewers are best at rejecting, and student papers make it most often, because a student has been told for four years that the point is to be original.

The triad also cuts the temptation that undergraduate work is most prone to, which is doing everything. A B.Tech dissertation wants breadth: the theory, the implementation, the extensions, the comparisons, the literature. A workshop paper wants three checkable things. The same body of work can be both, if the paper is the subset and the dissertation is the whole. Mine was, and the discipline of choosing the subset was harder than any of the proofs.

What it does not reward

It is worth being plain about what a venue like this does not select for, because the public numbers make it tempting to over-read them. An acceptance rate near a third is not a measure of how good the accepted papers are; it is a measure of how many checkable papers arrived. A venue that welcomes work in progress is not rewarding ambition; it is rewarding a student who knows exactly which part of their ambition is finished. And the mentoring programme, with 114 submissions in it, is the venue saying the quiet part: the difference between accepted and rejected student work is very often the writing, and the writing is fixable.

If I had to compress the whole process into one instruction for a student about to submit, it would be this. Before you write the abstract, write three sentences: here is what I proved, here is what I measured, here is what this sits next to. If any of the three is blank, the paper is not ready, and no amount of additional work on the other two will fill it. If all three are full, the abstract writes itself, and the reviewer will find each claim exactly where they expect to.

ResearchACLWriting
All writing

Written by Mohd Shayan

Get new posts by email

Occasional essays on engineering, AI, and building for the people technology leaves behind.

One email per new post. Unsubscribe any time.

Subscribe with RSS