> 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/engage/program-activities/copy-a-program-activity.md).

# Copy a Program Activity

Learn how to copy an existing program activity in PEARS to create a new record with the same general information.

You can copy an existing program activity to create a new record that starts with the same general information. This saves time when you are creating multiple similar program activities.

{% stepper %}
{% step %}

#### Navigate to the Program Activity

From the PEARS homepage, hover over the **Engage** menu in the top navigation bar and click **Program Activities**. Select the program activity you want to copy from the list to open its detail page.
{% endstep %}

{% step %}

#### Open the Copy Form

On the program activity detail page, click the **More** dropdown menu and select **Copy**.

![Screenshot: The More dropdown open at the top right of a program activity detail page, listing Print, Copy and Download Excel Report](https://2560412328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff0820LrBGQ9ZA8SC4BR1%2Fuploads%2Fgit-blob-0f91349fb882bd2419037ae0b95461294abc7f2e%2Fprogram-activity-more-menu-copy-v2.png?alt=media)

{% hint style="info" %}
**TIP:** If **Copy** is grayed out, hover over it to see why — for example, there is no Unit where your Role lets you add program activities, or no type of work at one of those Units has a current reporting period.
{% endhint %}
{% endstep %}

{% step %}

#### Edit the Program Name

The **Name** field is pre-filled with "Copy of" followed by the original program activity name. Edit this name to give the new record a unique, descriptive name.

![Screenshot: The Copy page for a program activity with the Name field pre-filled with Copy of and the original name, the Unit, What type of work is this? and Reporting periods fields filled in from the original, checkboxes for All 3 Program Sessions and/or Virtual Modules, Collaborators, Youth Programming, Attached Surveys and Program Demographics, and the Copy button](https://2560412328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff0820LrBGQ9ZA8SC4BR1%2Fuploads%2FNdlNZFWix2kAgXLfsVFZ%2Fprogram-activity-copy-form-v5.png?alt=media)
{% endstep %}

{% step %}

#### Choose Where the Copy Goes

Below the name, choose where the new program activity is filed. Each field starts with the original's answer where it is still available:

* **Unit** — The Unit the copy belongs to. The field lists the Units where your Role lets you add program activities, and starts with the original's Unit when it is one of them.
* **What type of work is this?** — The type of work the copy reports. It starts with the original's types of work that the selected Unit still offers.
* **Reporting periods** — The reporting period for each type of work. It starts with the current reporting periods of those types of work.

Changing the Unit changes the types of work listed, and changing the type of work changes the reporting periods listed. When a field has only one option, PEARS selects it for you and the field cannot be changed.
{% endstep %}

{% step %}

#### Select Data to Copy

The general information from the original program activity is always included in the copy. A linked community event is not copied, so the copy starts with no linked event. You may also choose to copy additional sections by checking the corresponding boxes. Only the sections the original program activity actually contains appear in the list:

* **All # Program Sessions and/or Virtual Modules** — Copies the sessions and virtual modules from the original; the label shows how many there are. Each copied session keeps its length. If any copied session is shorter than 1 minute or longer than 1,439 minutes, the copy's **General Information** section shows as incomplete, and the copy cannot be marked as complete until you edit it and save a valid length for each session. If you leave this unchecked, the delivery method changes to **In Person** and PEARS creates a single program session dated today.
* **Collaborators** — Copies the collaborator list from the original.
* **Partnerships** — Copies the partnerships from the original that are filed under a reporting period the copy is filed under.
* **Partners** — Copies the partners linked to the original, except partners that have ended.
* **SNAP-Ed Custom Data**, **Youth Programming**, and the other custom data sections — Each custom data section the original has gets its own checkbox, labeled with the section name.
* **Attached Surveys** — Copies the surveys attached to the original program activity.
* **Program Demographics** — Copies the demographic data from the original.

{% hint style="warning" %}
**CAUTION:** Select only the data that applies to the new program activity. For example, if the new program activity will have a different audience, you should not copy the Program Demographics, as the demographic data from the original may not apply.
{% endhint %}
{% endstep %}

{% step %}

#### Copy the Program Activity

Click the **Copy** button to create the new program activity. PEARS creates the record and opens its detail page. Check that the date range and the rest of the copied data are correct.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**NOTE:** The copy keeps only the answers that apply where it is filed. Choices in lists that the copy's Unit doesn't offer, program areas that its reporting periods don't offer, and answers that depend on them, such as an "Other, please specify" entry, are left off. If the copy is filed under different reporting periods than the original, its **Action plans** are set to **Not linked to an Action Plan**. Review the new record and fill in anything left blank.
{% endhint %}

{% hint style="warning" %}
**NOTE:** Some data sections may not be available for copying if the original and new program activities use different reporting period formats. For example, demographics and youth programming data cannot be copied from a pre-2023 program activity to a 2023+ program activity because the data formats are different, and they are not copied between a program activity in a reporting period before 2027 and one in a 2027 or later reporting period, because 2027 collects race and ethnicity as a single question. Sessions cannot be copied forward either when the original uses a delivery method other than Face-to-face. Unavailable checkboxes appear disabled, with an explanation beneath them.
{% endhint %}
