# Your next pullpath

We strongly recommend that every program start with at least one monthly `pullpath`. This gets the entire organization into a regular cycle and gives you a chance to show that you're listening to everyone's feedback, which is the only thing that will keep participation high over time.

For your next month's path, you can save time by first `copying a pullpath`. On the `path list`, use the far right `Edit` dropdown and select `Copy path`. 

![](/files/UR2aEA2O1WyRDkbT16XR)

Then just give it a new name. For example, let's say you're copying the first update you sent in January then you would name this 'February update'.

![](/files/MMBSC4b0sEj22vJs776o)

When you are no longer sending new participants to `pullpaths` , you can `pause` or `archive` them. 

A `paused` path can still be seen by users if they had access to it before but no new users will get it. An `archived` path can no longer be seen any any user. A pullpath must be `paused` before it can be `archived`.

{% embed url="<https://www.loom.com/share/eb66762c39d44f039c68a8a36d867afa>" %}
You can also click Filter drop down and view status = Paused or Archived to find older paths
{% endembed %}

You can also create `folders` to keep things tidy by clicking the drop down next to `Create a path`. Then you can drag & drop paths into folders.

{% embed url="<https://www.loom.com/share/5e0f17b5493f49a7b6f5f478a9841e56>" %}
&#x20;Folders are only for your sanity, they do not impact participants at all
{% endembed %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pullpath.com/getting-started/your-next-pullpath.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.