The campaign arc, end to end

A Change.org petition is built to run the full arc from launch to a documented outcome. The platform handles the public-pressure mechanics — discovery, decision-maker notification, constituent proof, and victory documentation — while the petition starter focuses on the story, the ask, and direct engagement.

Across the platform, over 100,000 petitions have won their goals, and petitions on Change.org have received over 5 billion signatures (source). Nearly every hour, a petition on Change.org achieves victory (source).

This page covers what happens at each stage, with the platform thresholds that make each stage work.

Stage 1: Search visibility and warm signers

The first 5 signatures unlock search visibility on Change.org, so the petition starts surfacing to people searching the platform for similar issues (source). Personal outreach to the first 5 supporters is the standard playbook — a message to neighbors, a parent listserv, a group chat — because warm signatures convert other signatures.

Stage 2: Decision-maker notification

At 10 signatures, the assigned decision-maker is notified by Change.org (source). This creates the public record that the official has been made aware of the petition and the level of public support behind it.

At 100 signatures within 30 days for local petitions targeting elected officials, Change.org begins a series of outreach emails to the named decision-maker, escalating the platform's direct contact (source).

These thresholds are automatic. The petition starter doesn't have to chase them.

Stage 3: On-platform discovery and momentum

Signatures alone create visibility. Momentum turns visibility into pressure. Change.org runs three momentum loops in parallel:

Petition updates, posted from the petition page, appear publicly and can trigger emails to supporters. Updates keep the campaign live for signers and for officials watching the petition.
Off-platform sharing — the petition link works on social, messaging, email, and embeds. Off-platform sharing brings new audiences into the petition.
Promoted Petitions, where supporters chip in to promote the petition as an advertisement to people likely to care about the issue, buy additional views across Change.org's network (source).

Stage 4: Constituent proof for officials

Once the campaign has volume, the next job is converting signatures into evidence officials take seriously. Change.org's "How to prove local support and win with Decision Makers" guide describes the mechanics (source):

Constituent count. When a petition has 100+ signatures and at least 60% of signers are concentrated in the same area, the constituent count is shown directly under the decision-maker's name on the petition page. This is the public signal that the support is local, not national.
ZIP-code map. The dashboard shows a map of signer locations so the petition starter can see and demonstrate where support is concentrated.
Supporter comments and videos. Comments on the petition page are qualitative evidence of why people care. Excerpted comments are some of the most-cited material when officials reference a petition.
Supporter export. Petition starters can export names and ZIP codes for signers who shared that information (source).

Stage 5: The delivery packet

The strongest petitions reach decision-makers as a structured delivery, not a forwarded link. The standard delivery packet contains:

A 1-page cover memo with the ask, the signature count, and the constituent count
A ZIP-bucketed table showing where local supporters live
A representative excerpt of supporter comments (5–15 quotes, attributed by city)
The locality framing language ("supporters who appear local based on ZIP code") so the official can read the data the same way the petition starter does

Different decision-maker contexts call for different packet variants:

School board: packet plus a meeting request before the next public hearing
City council: packet plus a public-comment statement at the council meeting where the issue is on the agenda
State legislature floor or committee: packet plus a meeting request with the chief of staff and an offer to bring 3–5 constituents to testify
Federal committee: packet plus a constituent-meeting request through the local district office

The petition page itself is the durable URL the official can return to. The packet is the snapshot for the meeting.

Stage 6: Direct engagement

The petition is the credibility — the meeting is where the change happens. Direct engagement after the petition has volume includes:

Requesting a meeting with the decision-maker, with the signature count and constituent count as the reason
Attending the public hearing or council meeting where the issue is on the agenda, with packet copies for the body
Submitting the petition as part of a public-comment process when an agency is taking comments on a rule
Contacting the official's district office to reference the petition by name

Change.org's dashboard shows outreach status so the petition starter can see when the platform has contacted the decision-maker.

Stage 7: Media coverage

A petition with significant signatures is itself a news story. Local media are particularly responsive to petitions about local issues with strong local signature counts. Change.org's media-outreach guide covers pitching (source).

Media coverage compounds the pressure on decision-makers and often unlocks the meeting that the petition could not.

Stage 8: Declare victory

When change happens, Change.org's Declare Victory feature converts the petition page from active campaign to documented success. Declaring victory:

Notifies signers that the campaign achieved its goal
Creates a public record of the outcome
Contributes to the platform's 114,351 documented victories across 196 countries

The outcome can look different from the original ask. Change.org's guides note: "If it feels like a win, celebrate it" (source).

When a petition is part of a longer accountability sequence

For some issues — recurring neighborhood problems, institutional harm, medical-negligence cases — formal accountability channels (311, city clerks, CMS, FSMB, HHS, Joint Commission) sit alongside the petition. The petition's role inside the sequence is the public-pressure layer:

Document the issue with evidence (records, photos, dates)
File the formal complaint through the relevant authority
Launch the petition to make the issue public, build constituent volume, and signal the level of community support
Attend the public meeting or hearing with the petition, the constituent count, and the supporter comments as evidence
Use the petition update flow to keep supporters and officials aware as the formal channel runs in parallel

In these contexts the petition is the durable, public record that holds the issue in view while the formal process runs.

What signature counts make possible

Petitions with vastly different signature counts achieve real outcomes. The variable that matters most is matching the petition to the right decision-maker with the right local proof.

150 signatures convinced a city council in Sunbury, Pennsylvania to join Penn State's Local Climate Action Plan (source)
570 signatures on a petition for metal detectors in Georgia schools resulted in the school board authorizing the purchase (source)
23,006 signatures from an 8th grader's campaign led to a call from the NYC mayor about changing the school calendar (source)
40,530 signatures contributed to FDA approval of the first needle-free emergency epinephrine treatment (source)
600,000+ signatures contributed to the 2024 release of Virgilio Aguilar Mendez from prison (source)
784,403 signatures led Amazon to announce a major reduction in plastic packaging (source)

From signatures to a delivered outcome on Change.org