> For the complete documentation index, see [llms.txt](https://handbook.proanimal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.proanimal.org/for-organizers/organizer-guide/engaging-activists/weekly-action-checklist.md).

# Weekly Action Checklist

In order to stay on top of activist engagement, here is a recommended checklist for weekly outreach and actions.

You should perform these tasks for all the activists assigned to you. For guidance on using Stampede for easy outreach, you can follow the instructions [here](/for-organizers/organizer-guide/engaging-activists.md#using-stampede-for-outreach).

*Filter to see only your assigned activists, by selecting “My team” in the search and filter bar on the* [*Stampede organizing page*](https://stampede.proanimal.org/organizing)*. You’ll see a number rating to the right of each person’s name.*

* **For anyone marked 0 – Pending:** 
  * [ ] Make sure their ladder status has been [updated](/other/archived-pages/archive-activist-steward-guide/archive-new-activist-onboarding.md#updating-stampede-profile-statuses) to “Prospect” if they have completed their onboarding call.
  * [ ] If they haven’t scheduled an onboarding call, consider emailing or texting them with a reminder to do so.
* **For anyone marked 1 – Prospect:** 
  * [ ] [Reach out](/for-organizers/organizer-guide/engaging-activists.md#using-stampede-for-outreach) to invite them to an upcoming shift or community event. 
* **For anyone marked 2 – Recruit:**
  * [ ] If they attended their first shift in the past week, [reach out](/for-organizers/organizer-guide/engaging-activists.md#using-stampede-for-outreach) to see how it went, how they’re feeling, and if they have any concerns. Invite them to another upcoming shift/event
  * [ ] If they did not sign up for or attend a shift over the past week and haven’t [RSVPd](/for-organizers/organizer-guide/managing-events-and-shifts/managing-your-event.md#checking-rsvps) to anything, reach out to invite them to an upcoming shift or event
* **For anyone marked 3 – Member:** 
  * [ ] If they haven’t attended any shifts/events in the past few weeks and haven’t been attending biweekly [1:1](broken://pages/1i36n7wv6pU4oQgzV7Ms#id-1-1s) calls with you, [text them](#using-stampede-for-outreach) to check in


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://handbook.proanimal.org/for-organizers/organizer-guide/engaging-activists/weekly-action-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.