> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/plan/professional-development/add-event-occurrences.md).

# Add Event Occurrences

Learn how to add occurrences with dates, location, and delivery methods to a professional development event proposal in PEARS.

Each event proposal requires at least one occurrence. An occurrence represents a specific scheduled instance of the event and includes details such as dates, location, and delivery methods. You can add multiple occurrences if the event takes place more than once.

{% hint style="info" %}
**TIP:** The red asterisk **\*** next to the heading of a field indicates that the field is required.
{% endhint %}

## Add an Occurrence

{% stepper %}
{% step %}

#### Navigate to the Event Times Section

On the event proposal form, scroll to the **Event Times** section. One occurrence is shown by default; click **Add Event Time** to add another. At least one occurrence must be added before the proposal can be saved.
{% endstep %}

{% step %}

#### Set the Schedule Type

Select the scheduling option that applies to this occurrence:

* **TBA** — Check this box if the event does not have a confirmed date yet. The start and end date fields are hidden and not required.
* **Ongoing** — Check this box if the event is a self-paced activity with no fixed schedule, such as a self-study module or video. The start and end date fields are hidden and not required; PEARS uses the start and end dates of the selected reporting period.

If neither box is checked, specific dates are required.
{% endstep %}

{% step %}

#### Enter Start and End Dates (if applicable)

If the occurrence is not marked as **TBA** or **Ongoing**, enter the **Start date** and **End date** for this occurrence. Both fields are required when a specific schedule is set, and the end date cannot be earlier than the start date.
{% endstep %}

{% step %}

#### Enter a Location

In the **Location** **\*** field, enter the location where this occurrence will take place.
{% endstep %}

{% step %}

#### Enter Other Information (optional)

In the **Other information** field, enter any additional details about this occurrence. Use the rich text editor to format the content as needed.
{% endstep %}

{% step %}

#### Select Delivery Methods

In the **Delivery methods** field, select one or more methods that describe how this occurrence will be delivered (e.g., in-person, virtual, hybrid).
{% endstep %}

{% step %}

#### Add Editors (optional)

In the **Editors** field, select other PEARS users who should have permission to edit this occurrence.
{% endstep %}

{% step %}

#### Select a Reporting Period

In the **Reporting period** **\*** field, select the reporting period that this occurrence falls within. Only current and future reporting periods are available.
{% endstep %}

{% step %}

#### Save the Occurrence

Click **Save** at the bottom of the event proposal form to save the proposal and its occurrences. To add more occurrences, click **Add Event Time** and repeat these steps.

![Screenshot: The Event Times section of the event proposal form showing the Add Event Time button, the TBA and Ongoing checkboxes, Start date, End date, and Location fields, the Other information rich text editor, and the Delivery methods and Editors fields](https://2560412328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff0820LrBGQ9ZA8SC4BR1%2Fuploads%2Fgit-blob-7aaece9ffe598fd3d4823e806705871c1861d13d%2Fpd-event-occurrence-form.png?alt=media)
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**NOTE:** You cannot select both **TBA** and **Ongoing** for the same occurrence. Choose one or the other, or leave both unchecked to enter specific dates.
{% endhint %}

{% hint style="warning" %}
**NOTE:** At least one occurrence is required before the event proposal can be saved or submitted for review.
{% endhint %}

{% hint style="warning" %}
**NOTE:** Unless you have permission to edit past reporting period data, occurrences in past reporting periods are read-only. All fields (dates, location, delivery methods, other information) are disabled, and the **Remove** button is not available. To make changes to an event, create a new occurrence in the current reporting period.
{% endhint %}