Events submitted to or created in Yale-Localist stay in the “Pending Events” view until they are approved. No event is automatically approved and pushed live to the calendar. If an event in the “Pending Events” view disappears unexpectedly, someone else has already approved that event.   

There are two ways to review and approve your events for the calendar: 

  1. On the lefthand side of your dashboard, under “Events,” click “Pending” to take you to the pending events view. 

  1. Or, from your main dashboard view, within the top ribbon, click the “Pending Events” tile to take you to the pending events view. 
screenshot of pending queue in localist

Important! It is encouraged for your team to automatically tag your campus group in the submission form when putting together your events. Doing so guarantees that your events will cleanly populate within the group search criteria, enabling a more efficient review and approval process for all. 

For publicly submitted events: In addition to the events you and your colleagues create within Yale-Localist, Yale community members can also submit events for consideration to your unit’s calendar through the public submission form. Once submitted, and if they’re correctly tagged to your group, these events will appear in your filtered pending view log (see the “Refine Results” guidance below), where you can then process as you would team-created events.

Important! On the right-hand side of your screen, the “Refine Results” menu box allows you to filter down this list so that only your group’s events appear for your review. To do so, identify your campus group in the “Group” drop-down menu; after clicking the “Refine” button at the bottom of the menu box, only the events tagged to your group should then populate for your review. This step significantly narrows down your pending review log, preventing you from accidentally approving events to the live calendar that are not tagged to your group.

Note that if you do not refine the communal pending view, you will see a complete list of every pending event awaiting approval across campus. You are only responsible for reviewing and approving the events tagged to your group, which is why it is important for your team to tag your group to every event created. If an event is untagged, it is unclear who needs to approve it and risks being lost in the pending view if no one knows to claim it.

screenshot of refine results pane in localist
screenshot of group filter in localist

After filtering down the pending list to reflect your group’s events, for each pending event within this list, admins will then click “Review” to the right of the row. Doing so will generate a preview of how the event will look on the live calendar: 

screenshot of filtered pending queue in localist
  • If the event submission looks good, no changes are needed, and it’s ready to publish live, either click the “Publish & Go to Next” button toward the bottom of your screen to publish the event live and take you to the next pending event for review or click the “Publish” button to publish the event live. 
screenshot of pending event in localist
  • If the event submission needs to be edited before going live, click the “Edit” button, which takes you directly into the submission form. As the calendar admin, you can update the form directly before publishing or reject the event. 

If the event submission needs to be rejected, click the “Reject” button, which will then give you the option to include a note outlining why the event was rejected (or what information is necessary for it to be approved) to the submitter. The submitter will then receive that rejection notification by email. 

For guidance on why an event might be rejected, visit the Editorial Guidelines & Best Practices

screenshot of event rejection note in localist

Admins may also choose to batch approve or batch reject events after carefully reviewing their list. To do so, click the checkbox next to the applicable events; then, at the top left of your screen, click the “Batch Actions” button to either batch approve or batch reject the events you selected. 

screenshot of batch action options in localist