Introduction to ControlShift Petitions

ControlShift was built on the idea that people should be able to start and run campaigns on the issues that matter most to them, with support from existing advocacy organizations that they know and trust.

On ControlShift, the cornerstone of a campaign is a petition. These petitions may be stand-alone petitions – like 'Save My Local School'– petitions that are part of a larger, distributed effort –like 'Raise the Minimum Wage [in my town]' – or petitions that are included under a partnership with a like-minded organization. We'll take an in-depth look at the latter two use cases later in this tutorial, but for the moment, we'll start with stand-alone petitions. 

For most of our organizations, visitors to their CSL instance are able to create their own petitions, whether on a specific topic, like the environment, or on any issue they choose, by clicking the start a campaign button included on the homepage or the button in the header.

After clicking to start their campaign, the user is brought to a form asking for basic information about their campaign, including the petition title, whom they are targeting, what they want them to do, and why it's important. They can also specify a location for the campaign and, if your organization has categories enabled, choose a category that the petition falls under.

Once they've finished entering that information, they'll be brought to a screen asking them to review their text and add a picture, before launching the petition. After launch, they're brought to their new petition's manage screen.

This screen is the main hub from which a petition creator runs their campaign. From here they can take a number of campaign actions, including emailing their supporters, sharing on social media, and collecting signatures offline.

Let's take an in-depth look at the things petition creators can do to run their campaigns.

Have more questions? Submit a request


Powered by Zendesk