> 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/managing-events-and-shifts/leading-shifts.md).

# Leading Shifts

How to get started with preparing for and leading a shift, and instructions for running different types of shifts.

[**Running Shifts**](#running-shifts)

[**Shift Resources**](#shift-resources)

## Running Shifts

Depending on the phase of the campaign, there are different types of shifts you can lead. This may include petitioning, door knocking, tabling, phone/text banking, or postcard writing. Here is a checklist with steps to help get you started.

### Before Your Shift

* [ ] **Find a location** 
  * For canvassing activities, consider upcoming events or public spaces with a lot of foot traffic where you can easily reach voters 
  * Postcard writing or text banking can be hosted in public spaces such as vegan restaurants or coffee shops, or in your home or private space
  * Consider how many people the location can comfortably fit, and cap attendance as needed
* [ ] **Prepare supplies** 
  * Think through any resources that may be needed, and ensure that you’re able to supply them (e.g. making sure you have postcards & pens) 
* [ ] **Consider feeding people**
  * Depending on the time and location, consider whether food should be served. \*Note: It’s common, but not required, to provide a simple dinner for evening shifts hosted in someone’s home. 
  * If food will be provided, be sure to note this in the event details
  * You can use or share the social events [food guide](https://handbook.proanimal.org/for-organizers/campaign-guides/social-and-community-events-guide/event-role-checklists/cooks#food-guide-for-cooks) for cooking ideas
* [ ] **Create an event in Stampede**
  * Any shift you choose to lead should be [entered into Stampede](/for-organizers/organizer-guide/managing-events-and-shifts.md#scheduling-events), with all relevant details. People can RSVP to attend from here
* [ ] **Spread the word**
  * Once posted to Stampede, you can do some [outreach](#filling-your-shift) to make sure people are aware of the event and sign up to attend
* [ ] **Make sure you're familiar with the process & steps for the shift activity**
  * Review available [resources](#shift-resources) so you can guide activists during the shift

### **During Your Shift**

* [ ] **Let people eat & socialize before diving in**
  * Allow 30 minutes or so for people to arrive, settle in, socialize, and eat
* [ ] **Provide instructions and resources**
  * Give a quick overview of what you’ll be doing
  * Distribute any resources needed
  * Run through the step-by-step process and invite questions
  * Allow newcomers to shadow you as needed
* [ ] **Take photos!**
  * Take photos of people working or socializing during the event
  * Share a photo to Slack in **#campaign** after the event
* [ ] **(If applicable) Debrief at the end of the shift**
  * If this is a newer campaign activity that we’re still working out, it might be helpful to get feedback from attendees at the end to see how it could have gone smoother

## Shift Resources

Here are some resources you can reference for step-by-step instructions on leading various types of shifts. 

* [Postcard Shifts](https://handbook.proanimal.org/for-canvassers/how-to-write-postcards-to-voters)
* [Petitioning Shifts](/for-organizers/leading-a-petitioning-shift.md)

**\*Note:** *More guides will be added to this section as we try out different shift types.*


---

# 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/managing-events-and-shifts/leading-shifts.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.