BEST PRACTICE: Requiring Fields Upon Event Submission

Need some background on public submissions? Start with our introductory guide: Pending Queue


When a user comes onto your platform to submit an event the public submission form only requires that they fill out three fields: Event Name, Description and Start Date.

We are often asked, “why are only three fields required?,” and the answer is very simple:

1. Increasing the amount of required fields directly correlates to a decrease in the likelihood that a user will complete the submission process. Especially considering a user may be unsure what the best answer or selection may be for many items.

2. These three fields technically communicate the only details needed for an event: What is it and when is it? There are several kinds of “events” that you can place on a calendar that don’t have a time or a physical location:All-day events, holidays or academic dates/deadlines, and closings.

Taking these reasons into consideration, our goal is to create a balance between user submissions and administrative edits. Here’s how you can strike a balance on your platform:

The Pending Queue

All public event submissions by non-admins or trusted users are sent to the pending queue where they must be approved by a Platform or Event Admin before being posted to the calendar.

Custom Rejection Messages

If an admin is not satisfied with what information is or isn’t provided they can send a message directly to the submitter detailing why the event wasn’t approved and what information they would like added in order for it to be posted.

Custom Submission Guidelines

While it’s not possible to add more required fields, you can add guidelines to the public event submission form to communicate any requests. Instructions available here.

 

Related Articles