OpenReview score lag rattles authors

OpenReview’s transparency makes every score tweak feel high-stakes, but the AC is far more likely to care about the substance of the rebuttal than the timing of one edit. The real risk is not the delayed update itself, but sounding accusatory or desperate if you try to manage the reviewer’s workflow in public.

• –OpenReview exposes rebuttal-period discussion and score changes, so delayed updates can look ambiguous even when they are harmless
• –A factual, neutral follow-up is safer than calling out a reviewer in a way that sounds like score policing
• –ACs usually weigh the review quality, rebuttal content, and final discussion more than whether a reviewer edited instantly
• –This is a UX problem as much as a process problem: authors can see the process, but not the reviewer’s intent or whether the change was just forgotten
• –The thread reflects a common conference-review anxiety loop where visibility amplifies uncertainty