> 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/reflect/success-stories/mark-a-success-story-as-complete.md).

# Mark a Success Story as Complete

Review all required fields and mark a success story as complete in PEARS.

After completing all required sections of a success story, you can mark the record as complete. Marking a success story as complete signals that the record is finished and ready for review.

{% hint style="warning" %}
**NOTE:** You will not be able to mark the success story as complete until all of the following requirements are met.
{% endhint %}

## Completion Requirements

* **General Information** — The story title, reporting periods, program areas, unit, and other general information must be saved.
* **Collaborators** — The **Collaborators** section must be saved. Saving it marks the section complete, even if you add no collaborators.
* **Partnerships** — If your organization has turned on the **Partnerships** section for success stories, it must be complete.
* **Custom Data** — All required custom data fields, if configured for your organization, must be completed.
* **Story** — The **Story Narrative** field is required. If the success story has a SNAP-Ed reporting period and a program area set up for SNAP-Ed data, the **Background** field is required as well.
* **SNAP-Ed Custom Data** — If the success story has a SNAP-Ed reporting period and a program area set up for SNAP-Ed data, the socioecological frameworks, approaches, and related framework indicators fields must be completed.

{% stepper %}
{% step %}

#### Review the success story record

Open the success story and verify that all required sections listed above are complete. Address any missing information before proceeding.
{% endstep %}

{% step %}

#### Resolve any incomplete sections

Use the **Progress** panel on the right side of the detail page to identify which sections still need attention. Click on any incomplete section to navigate directly to it and fill in the missing fields.
{% endstep %}

{% step %}

#### Mark as complete

Click **Mark as Complete** in the **Progress** panel, then click the **Mark as Complete** button to confirm. The success story is marked complete, and a **Completed** badge appears next to its title on the detail page.

{% hint style="info" %}
**TIP:** If any section is incomplete, the page shows a message asking you to finish adding your success story data instead of the **Mark as Complete** button. Return to the **Progress** panel to find the sections that still need attention.
{% endhint %}

![Screenshot: The Mark as Complete page of an incomplete success story, showing the message that you need to finish adding all your Success Story data in place of the Mark as Complete button, and the Progress panel with only General Information checked](https://2560412328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff0820LrBGQ9ZA8SC4BR1%2Fuploads%2FBawT7usr7vkmhv32QtLf%2Fsuccess-story-mark-as-complete-page.png?alt=media)
{% endstep %}
{% endstepper %}

## Mark as Incomplete

If you need to make changes to a completed success story, you can mark it as incomplete to re-enable editing. Navigate to the success story detail page, click **Mark as Incomplete** in the **Progress** panel, then click the **Mark as Incomplete** button to confirm. The **Completed** badge is removed and all sections are editable again.