Skip to content

Commit 567ff5f

Browse files
Update docs/editor_tips.md
Co-authored-by: Matthew Feickert <[email protected]>
1 parent 5c7d4c9 commit 567ff5f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/editor_tips.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ One of your jobs as the editor is to ensure the review keeps moving at a reasona
3434

3535
**Manage author responsiveness**
3636

37-
We ask authors to respond to reviewer feedback within 2 weeks and complete requested changes within 4-6 weeks, matching the timeliness we expect from reviewers. If an author hasn't responded after 2 weeks, give them a friendly nudge. If there's no response after 4 weeks without clear communication about delays, warn the author that their paper may be rejected due to lack of engagement and escalate to your Track Editor-in-Chief. This ensures reviewers' time is respected and prevents reviews from stalling indefinitely.
37+
We ask authors to respond to reviewer feedback within 2 weeks and complete requested changes within 4-6 weeks, matching the timeliness we expect from reviewers, unless otherwise negotiated with the editor. If an author hasn't responded after 2 weeks, give them a friendly nudge. If there's no response after 4 weeks without clear communication about delays, warn the author that their paper may be rejected due to lack of engagement and escalate to your Track Editor-in-Chief. This ensures reviewers' time is respected and prevents reviews from stalling indefinitely.
3838

3939
**Check in twice a week**
4040

0 commit comments

Comments
 (0)