29. After acceptance
The email says Accept, or Accept to Findings, which is also a win (Chapter 3). Congratulations. The work is not done. Acceptance starts a short, deadline-driven last mile. You owe a camera-ready version with its own rules, a talk or poster, and some effort to get people to read what you wrote. This chapter covers that last mile. It is mostly logistics, but you can get logistics wrong, and the camera-ready deadline is as fixed as the submission one.
The camera-ready
The final version is more than the submission with the author names pasted on. Several things change, and a few are easy to forget.
- The extra page. Accepted papers get one more content page: "up to nine (9) pages of content" for a long paper (five for a short), plus unlimited acknowledgments and references (ACLPUB). The page is for the changes reviewers asked for. Do not pad it. Use it to honor what you promised in the rebuttal.
- De-anonymize. Add the author names and affiliations under the title. Use full names: "do not abbreviate given names to initials." Turn every anonymized self-citation back into a normal one ("as we showed in Okeke 2024," not "(Anonymous, 2024)"). Restore the code and data links you withheld for review.
- Add the acknowledgments. A new, unnumbered Acknowledgments section goes "immediately before the references". It does not count toward the page limit and was absent from the review version. Thank your funders with grant numbers, your compute providers, and the people who helped. Do not try to thank reviewers by guessing who they were.
- Sign the license. You sign the ACL copyright/license agreement on behalf of all authors through the conference system. Authors retain most rights; it is routine.
- Final polish. Turn off page numbers (the final version is unnumbered), make every figure and table legible, fix the typos reviewers flagged, and confirm you are still within the limit. Then send the code and data you said you would.
Honor what you promised
The extra page exists for the changes you committed to in the rebuttal. You may have written "we will add the significance test," "we will discuss Müller et al.," or "we will release the code." The camera-ready is where you make good. Area chairs and careful reviewers do sometimes check, and they notice a dropped promise. Kept promises are also how trust in the review process survives.
Poster or oral?
Most accepted papers present as posters; a smaller set get oral or spotlight slots. A poster is no consolation prize. It often gets you better conversations than a talk does. Conferences also ask for materials uploaded ahead of time: a poster PDF, slides, and often a pre-recorded video for the virtual audience. Check your conference's presenter instructions and the upload deadline, which comes weeks before the event.
Giving the talk
*ACL talks are short. ACL 2025 gave each presentation eight minutes plus three for questions (ACL 2025 FAQ). You cannot present the whole paper in eight minutes, so do not try. Tell the story:
- One arc. The problem, why it matters, your one idea, the single result that supports it, and the takeaway. Cut everything else.
- Slides that read from the back row. Big fonts, one point per slide, few words, colorblind-safe figures (Chapter 19 on figure craft applies here too). Describe each figure aloud for anyone who cannot see it well.
- Practice and time it. Run it out loud until it fits with room to spare. Anticipate the obvious questions. "I don't know, good question" is a respectable answer.
Making a poster that works
A poster is a visual argument. It is not your paper shrunk to fit. The classic failure is eight pages of 10-point text taped to a board, which nobody reads.
- A title and a one-sentence takeaway large enough to read from across the aisle. Many people will only get that far.
- A few figures, little text. The poster supports your spoken explanation and does not replace it.
- Rehearse the one-minute and the five-minute version, and give people a way to find the paper later. A QR code to the Anthology page is plenty.
At the conference
The hallway matters most. The talks are recorded; the conversations are not. Introduce yourself, ask people about their work, and have a thirty-second and a two-minute description of yours ready. Being a first-year is no handicap. Most people are generous, and "I'm a first-year PhD student working on X, could you tell me about Y?" opens almost any door.
Getting the work seen, honestly
Get the paper read without overselling it:
- Put it where people look. Post it to arXiv if you have not, and let the ACL Anthology page be the canonical link.
- Say it plainly. A short, honest thread or post does more than hype: the problem, what you found, one figure, a link. The "we beat SOTA" reflex from the jargon chapter reads as thin; let the result speak.
- Release what you promised, and make it easy to use: a documented repository, a model card, a dataset card. Reusable artifacts are cited far more than unreusable ones (Chapter 25).
- Keep your record current. Update your website and your Semantic Scholar / Google Scholar profile so the paper is findable under your name.
Common mistakes
- Treating the camera-ready as a formality. Forgetting the acknowledgments, leaving a self-citation anonymized, or skipping the de-anonymization leaves a sloppy last impression on months of work.
- Padding the extra page instead of spending it on the reviewer-requested changes.
- Dropping a promised change or release. People notice, and it erodes the trust the rebuttal earned.
- A talk that reads the paper aloud, or a poster that is the paper at 8 point. Tell a story; show an argument.
- Overselling. Hype ages badly and the field has a long memory. Modest, accurate claims win respect.
Further reading
- The ACLPUB final-version instructions and the *ACL camera-ready FAQ: the authoritative checklist for the final version.
- Your conference's own presenter and author guidelines (e.g. the ACL 2025 FAQ) for talk lengths, poster sizes, and upload deadlines, which change every year.
- The rebuttal, for the promises the camera-ready must now keep.