Requiring Fields Upon Event Submission

When a user submits an event to your platform via the Public Submission Form, by default there are only three fields that are marked as Required. Those fields are:

  • Name
  • Description
  • Start Date

We are often asked, “Why are only three fields required?,” and there are two main reasons:

  1. Increasing the number of required fields directly correlates to a decrease in the likelihood of a user completing the submission process.
    • Users may be unsure what the best answer or selection may be for many items.


  2. NameDescription, and Start Date technically communicate the only details needed for an event, thus answering the question, “What is it, and when will it happen?”
    • There are also several types of “events” that you can add to the calendar that don’t need a time or physical location — i.e. all-day events, holidays, closings, academic dates, etc.

– Note –

Ultimately, our goal is to create a balance between user submissions and administrative edits.

Balancing User Submission and Administrative Edits

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 an Event Admin before being posted to the calendar.

Custom Rejection Messages

If an Event 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 Fields

You’re able to assign Custom Fields to your Public Submission Form and mark them as required. These fields are controlled by Platform Admins.

Custom Submission Form Guidelines

You can provide your users with context surrounding how to fill out the Public Event Submission Form with Custom Guidelines within the form or along the right side. These fields can be marked as required.