@Rochester Submission Guidelines

• Keep your submissions to under 150 words. Use links to provide further details.
• Submissions must have a direct connection to the University of Rochester. We reserve the right to decline submissions that don’t meet that criterion.
• In an effort to lessen repetition and keep issues brief, we do not repeat the same submission more than twice, and we do not repeat items in consecutive issues. Recurring events such as info sessions about programs the University offers will be shared no more than once a month. Submitting your group’s recurring events for an upcoming month so that they can be listed together with ample notice is suggested.
• We do not include events related to patient recruitment.
• We do not include personal fundraising or community fundraising efforts. We recognize that our faculty, staff, and students are passionate about helping the Rochester community thrive—and we thank you for it! But, because of the large volume of requests, we limit our fundraiser listings to those that directly support the University or one of its units.
• Photos that accompany submissions will be considered. Keep in mind that only horizontal photos that are at least 600 pixels wide and in jpeg format can be used. Photos will be included at the discretion of the editors based on quality, appropriateness, and other considerations.
• We currently do not accept video submissions.
• We periodically include compilations of recent awards and honors in the newsletter. If you have news to share about a faculty or staff member, student, or department/unit that has recently achieved a significant professional accomplishment or received a prestigious national or international award or honor, please let us know.
• In coordination with Human Resources and the Office of the President, we share notices about faculty, staff, trustees, or students who have died recently. Notices include a link to an obituary and, if applicable, a date that the University will lower its flags in honor of the person who has died. If there is a faculty or staff member’s death notice you’d like to share in @Rochester, please be sure Human Resources has been notified; their staff will share the news with us accordingly.
• All submissions are edited for clarity and brevity. @Rochester follows the Chicago Manual of Style and the University Style Guide.

University Communications publishes @Rochester on weekday mornings throughout the year, except on University holidays and select days during the summer and winter breaks.

Submit items in a timely manner; send the info at least a week or two before a scheduled event or deadline. We do our best to accommodate requests for items to run on a particular day. The more time we have to consider submissions and suggestions, the better, but the deadline for each following day’s issue is 2 p.m. each business day.

Materials received after that may not be considered for the following day’s issue. We do our best to accommodate requests for items to run on a particular day.

Please use the form on this page to submit an item for @Rochester. Submissions will be reviewed by the editorial team and considered for publication. Some submissions may be edited for clarity and brevity.

All events in @Rochester must be entered into the University’s Events Calendar. An event that does not appear in the calendar will not be considered for @Rochester.

Learn how to submit an event to the University events calendar:

• Overview
• Submission guide

To submit an event listing to @Rochester, use the submission form below to send the link to the listing in the University Events Calendar.

Faculty, staff, and students automatically receive @Rochester, but others are welcome to subscribe, too. Use the online form to sign up, or email your full name and email address to at-rochester@rochester.edu.

Recent archives can be found at Rochester.edu/newsletters/@rochester. Earlier issues are available in the Digital Collections of River Campus Libraries.

You can contact the editorial team by emailing at-rochester@rochester.edu.