How campaign review works
Every campaign is read by a person before it appears publicly. Here is what we look for and what gets sent back.
Every campaign is read by a person before it appears publicly. Here is what we look for and what gets sent back.
This guide is for an owner preparing to submit a campaign for Pledzy's required pre-publication review. The objective is to submit a page that can be evaluated quickly for clarity, plausibility, reward terms, and prohibited investment language. That requires more than a persuasive headline: the plan should be understandable, costed, and usable by the people responsible for carrying it out.
The guidance below separates the decision from the promotion. It explains what to prepare, how to test the plan, what can go wrong, and what to do next. Examples are illustrative unless they describe Pledzy's published fees or workflow.
Quick answer: What we look for
- A real business or organisation behind the page.
- A project the money clearly pays for.
- Reward tiers the business can plausibly deliver.
- Nothing misleading about returns, ownership or guarantees.
Quick answer: What gets sent back
Usually not fraud — usually vagueness. A goal with no breakdown, tiers with no delivery detail, or a story that never says what the money buys. We send it back with notes and you can resubmit.
Quick answer: Plan for it
Publish a few days before the date you want to launch so review does not sit on top of your launch plan.
What human review is for
This guide is for an owner preparing to submit a campaign for Pledzy's required pre-publication review. The objective is to submit a page that can be evaluated quickly for clarity, plausibility, reward terms, and prohibited investment language. That requires more than a persuasive headline: the plan should be understandable, costed, and usable by the people responsible for carrying it out.
A useful way to test the idea is to ask what a careful reader could verify without already knowing the owner. The answer should come from the project, the numbers, the images, and the terms—not from urgency alone. For example, a reviewer checks the business, use of funds, goal, timeline, images, rewards, risk language, and consistency across the page, then approves or returns notes.
The review path from draft to decision
Move in sequence and keep a written record of each decision. A sequence prevents one attractive part of the campaign—usually the headline or reward—from getting ahead of the budget and operating reality.
- 1
Step 1: Complete every required campaign field
Complete this before moving on. Record the person responsible, the evidence used, and any assumption that still needs confirmation. If the answer changes the budget, timeline, or reward promise, update those connected parts at the same time.
- 2
Step 2: Make the budget and goal agree
Complete this before moving on. Record the person responsible, the evidence used, and any assumption that still needs confirmation. If the answer changes the budget, timeline, or reward promise, update those connected parts at the same time.
- 3
Step 3: State reward delivery terms precisely
Complete this before moving on. Record the person responsible, the evidence used, and any assumption that still needs confirmation. If the answer changes the budget, timeline, or reward promise, update those connected parts at the same time.
- 4
Step 4: Remove language about profit, ownership, interest, or guaranteed results
Complete this before moving on. Record the person responsible, the evidence used, and any assumption that still needs confirmation. If the answer changes the budget, timeline, or reward promise, update those connected parts at the same time.
- 5
Step 5: Build review time into the intended launch schedule
Complete this before moving on. Record the person responsible, the evidence used, and any assumption that still needs confirmation. If the answer changes the budget, timeline, or reward promise, update those connected parts at the same time.
What reviewers examine
Consider this practical scenario: a reviewer checks the business, use of funds, goal, timeline, images, rewards, risk language, and consistency across the page, then approves or returns notes. The point is not to copy the numbers or offer. It is to show how the promise, evidence, costs, audience, and delivery plan should agree with one another.
A worked example should make tradeoffs visible. If one line changes, revisit the connected goal, schedule, and communication rather than allowing the public page and operating plan to drift apart.
| Part of the plan | What it should show |
|---|---|
| Draft | Owner completes story, budget, media, rewards, and deadline |
| Submitted | Campaign leaves editing flow for reviewer assessment |
| Changes requested | Owner receives notes and can revise |
| Approved | Campaign becomes eligible to appear publicly |
Document the decision before you publish
Create a one-page working brief that states the audience, the intended outcome, the evidence, the main constraint, and the person responsible for the next action. For this topic, that means writing for an owner preparing to submit a campaign for Pledzy's required pre-publication review and keeping the central outcome visible: submit a page that can be evaluated quickly for clarity, plausibility, reward terms, and prohibited investment language.
The brief is not campaign copy. It is the record behind the copy. Attach quotes, calculations, policies, photographs, delivery assumptions, or professional advice where they apply. Mark what is confirmed, what is estimated, and the date each estimate was checked. When a fact changes, update the working brief first and then every public promise that depends on it.
A second person should be able to use the brief to find the source of a number and understand why a deadline or reward term was chosen. If they cannot, the public explanation is likely relying too heavily on the owner's memory. This small discipline also makes later updates easier because the original assumptions are still visible.
How to respond to requested changes
Most weak campaigns are not missing enthusiasm. They are missing one operational connection: a cost does not appear in the goal, a reward has no capacity limit, a deadline ignores review or fulfillment, or a trust signal is described as a guarantee.
- Submitting placeholders or copied boilerplate.
- Using unsupported superlatives or financial-return language.
- Leaving the risks section generic.
- Resubmitting without addressing the review note.
Submission-ready checklist
Use this list as a final pause before publishing, pledging, or beginning fulfillment. A checked box should represent a real decision or piece of evidence, not an intention to solve it later.
- ✓The business and project are identifiable.
- ✓The use of funds is specific.
- ✓The timeline is plausible.
- ✓Rewards have terms and dates.
- ✓Photos belong to the business.
- ✓The page states that backing is not investing.
Measure the result and close the loop
Decide what a responsible result looks like before activity begins. The measure should connect to the promised outcome rather than vanity metrics. Visits and shares can explain attention, but the more important evidence is whether people understood the offer, whether commitments became collected payments, whether the planned work moved forward, and whether rewards were delivered as described.
Keep a short decision log during the campaign or review process. Record questions people ask repeatedly, assumptions that proved wrong, operational changes, and the reasons behind any delay. These notes become the raw material for honest updates and make the next campaign easier to plan.
Close with proof appropriate to the promise: a receipt or completed milestone where it is safe to share, a photograph of the finished work, a fulfillment update, or a clear explanation of what changed. Do not publish private backer, banking, tax, insurance, employee, or security information in the name of transparency.
- ✓The success measure connects to the stated outcome.
- ✓Pledged and collected amounts are not treated as interchangeable.
- ✓Changes are recorded with dates and reasons.
- ✓Backers receive an update before a promised date passes.
- ✓The final proof protects private information.
The bottom line
The strongest next step is simple: Complete every required campaign field. Then complete the checklist before making the promise public.
Pledzy can organize the page, review it before publication, and help the community find it. The owner remains responsible for the accuracy of the campaign and the delivery of its rewards.
