How to Keep Supporters Updated on a Creator Project

Keep supporters updated by posting short, specific updates at real milestones: when the goal is funded, work begins, the result is delivered, or the plan changes. Publish each update on the project page and the social channels where you made the ask, so supporters can see what happened, what comes next, and where their money went.

This is the final step in funding a creative project with direct fan support: the goal is live, the ask is out, and contributions have started coming in.

Why should you keep project supporters updated?

Update supporters because, from the outside, a quiet project and an abandoned one look identical. The Kickstarter Fulfillment Report found that 9% of funded Kickstarter projects failed to deliver rewards, so caution is rational, not rude. A short dated update is the cheapest available proof that the project supporters paid for is still moving.

The Kickstarter Fulfillment Report, an independent analysis by University of Pennsylvania professor Ethan Mollick published by Kickstarter, found that 9% of Kickstarter projects failed to deliver rewards, 8% of dollars pledged went to failed projects, and 7% of backers failed to receive their chosen reward (Kickstarter Fulfillment Report).

Mollick's underlying paper, Delivery Rates on Kickstarter (University of Pennsylvania, December 2015), puts non-delivery at "around 9% of all projects, with a possible range of 5% to 14%," which is the widest credible band a funded creator should assume their own supporters have in mind (Delivery Rates on Kickstarter).

The same Kickstarter Fulfillment Report tells backers to "expect a failure rate of around 1-in-10 projects, and to receive a refund 13% of the time," which is the expectation your silence gets measured against.

Those rates come from a large primary survey rather than anecdote: Mollick's paper reports results from 47,188 Kickstarter backers, and among backers reporting a failed project around 13% said they received a refund or other compensation (Delivery Rates on Kickstarter).

Kickstarter's help center states that a funded creator's "fundamental obligation to backers is to finish all the work that was promised, honestly address backers' concerns, and deliver rewards" (What is a creator obligated to do once their project is funded?).

A direct fan-supported project is not a Kickstarter campaign, and no platform rule forces you to post. Supporters may not expect a formal report for a modest goal — a microphone upgrade or a music video budget, for example — but they reasonably want confirmation that the project is moving forward.

The practical fix is simple: publish a short update whenever the project's status materially changes. You do not need a newsletter or an elaborate content plan.

When should you update supporters?

Update at milestones, not on a calendar: when the goal is funded, when work visibly begins, when the result is delivered, and whenever the plan changes. Kickstarter's help center describes project updates as the creator's primary way to share progress with backers, and those four moments are the ones supporters are actually waiting to hear about.

Post at milestones rather than filling a fixed weekly schedule with updates that contain no new information:

• When the goal is funded. Thank supporters and confirm that the project can move forward.
• When the work begins. Turn the goal into visible action, such as buying the equipment, booking the studio, or starting production.
• When something is finished or delivered. Show the result: the video, equipment in use, released EP, completed artwork, or other promised outcome.
• Whenever the plan changes. Explain timeline delays, scope changes, unexpected costs, or a project that can no longer proceed as originally described.

Kickstarter's official update guidance describes project updates as the creator's primary way to share progress with backers.

Kickstarter's help center tells funded creators to post "at least one new update a month once funding is finished," the only explicit update cadence a major creator-funding platform publishes (What should I post an update about and how often?).

Kickstarter's Creator Handbook adds that updates "can be emailed to all your backers, or just to specific reward tiers," and that a creator gets 30 minutes to edit an update after posting it.

Kickstarter gives creators three audience settings for each project update — public, backers only, or project followers — so headline progress can stay visible to everyone while payment-specific detail goes only to the people who funded the work (What are project updates?).

Membership platforms document the same habit outside crowdfunding: Patreon's help center says a creator can schedule an update by toggling on "Set publish date" in the post editor and choosing a date and time for it to publish.

Patreon also lets a creator correct an already-published update and toggle on "Notify" during the edit so members are alerted to the revision rather than discovering it silently.

Four milestone posts across a project's life is this article's recommended workflow, not a platform requirement: no platform cited here — Kickstarter, Patreon, or FanBell — mandates an update count or schedule. Four is enough because it covers the only four events that change what a supporter knows: the money arriving, the work starting, the result existing, and the plan changing. Longer or troubled projects need more: if yours will run past a few months, adopt the at-least-monthly floor Kickstarter publishes for funded creators instead of spreading four posts across a year. A two-week project may need fewer. The standard is whether supporters can understand the current status without chasing you for an answer.

What should a project update say?

A project update should answer three questions in a few sentences: what happened, why it matters to the thing supporters funded, and what happens next. Kickstarter's own guidance for creators in difficulty asks for the same substance — an update explaining what work has been done and how the funds were used — so write every update that way.

A useful update answers three questions:

1. What happened? State the specific progress or change in one or two sentences.
2. Why does it matter? Connect the development to the project supporters funded.
3. What happens next? Give the next step or revised timeline when you know it.

A specific thank-you usually feels more meaningful than generic gratitude. For example: "We hit the goal for the new mic—every $10, $20, and $50 pledge got us there." Those amounts are illustrative placeholders, not recommended tiers; name the contribution sizes you actually received.

You do not need to justify every dollar in every social post. Put the fuller funding explanation on the project page, then use updates to report material progress. For a framework covering what to explain in advance, see what fan contributions actually fund.

What is a good funded-goal update?

We hit the goal for the new microphone. Thank you to everyone who contributed and shared the project. I'm ordering it this week, and I'll post another update when it arrives.

What is a good work-started update?

Production has started. The studio is booked, the first session is this weekend, and I'll share a preview once the initial edit is ready.

What is a good completed-project update?

It's finished: the music video you helped fund is now live. Thank you for making the shoot possible. You can watch it here: [link].

Short updates work because each one gives supporters a concrete status, a relevant thank-you, and a clear next step.

How should you keep the project page current?

Keep the project page current by treating it as the record rather than the original pitch: revise the status, the timeline, the outcome, and any material change as each one happens. A supporter who missed every social post should be able to open the page and learn the project's real state in about ten seconds.

Your Project Support page gives supporters one stable place to check the project without waiting for another social post. If you are still deciding what belongs there, see what to put on a project support page.

Keep these elements current:

• Project status: Move the project forward as its status changes. A finished goal left marked "Active" can look unfinished.
• Timeline or next step: Replace an outdated plan with the current expectation.
• Outcome: Add the completed work, release link, photo, or other result when it is available.
• Material changes: Record delays, scope changes, or a decision not to proceed as planned.

FanBell's Project Support is a single named goal with a target amount and a progress bar that fills as contributions arrive, with no reward tiers, physical perks, or campaign deadline to administer.

The FanBell project progress bar and supporter count update automatically as fans contribute, so a creator never maintains a running total by hand (how FanBell works).

Use the project page for the calm, permanent record and social posts to announce that something has changed.

What should you say if the project changes, slips, or falls through?

Say what changed as soon as you reasonably know it, separate confirmed facts from estimates, and state your next step and its date. Kickstarter tells creators who cannot finish to post an update explaining the work done and how funds were used, and to offer refunds — the same three moves apply to direct fan support.

Kickstarter instructs a creator who cannot complete a project as promised that their steps "should include offering refunds, communicating with your backers, and posting an update that explains what work has been done, how the funds were used" (If I am unable to complete my project as promised, what should I do?).

Kickstarter's delay guidance also warns that a refund is not always available: "If the funds have already been used to pay for production, materials, postage, or a person's time, then a refund may not be possible" (What happens if a project is delayed?).

Going silent after taking money can become a law-enforcement matter, not only a reputation problem. In the Federal Trade Commission's first crowdfunding enforcement action, announced June 11, 2015, creator Erik Chevalier raised more than $122,000 from 1,246 backers for a board game and cancelled the project after 14 months without delivering the rewards or the refunds he had promised (FTC: Crowdfunding Project Creator Settles FTC Charges of Deception).

That FTC settlement order imposed a $111,793.71 judgment on Chevalier, suspended because of his inability to pay, and permanently barred him from making misrepresentations about any crowdfunding campaign or failing to honor stated refund policies.

In a second case settled May 11, 2020, the FTC banned iBackPack operator Douglas Monahan from all future crowdfunding and entered a judgment of nearly $800,000 after he raised more than $800,000 from consumers and never delivered the promised products (FTC: Operator of Deceptive Crowdfunding Scheme Banned from Future Crowdfunding).

Neither FTC case turned on a missed deadline by itself; both involved spending contributions on something else and telling supporters nothing. Dated, honest updates are the difference between a late project and a deceptive one.

A delay update should contain four elements:

• The part of the plan that changed
• The reason, stated plainly
• The new timeline or next decision point
• What supporters should expect from you next

What is a clear delay-update template?

This is taking longer than I expected because [brief reason]. The original target was [original timing], and the new estimate is [revised timing]. The project is still moving forward, and I'll update the page again when [next milestone] happens.

If you do not yet have a reliable completion date, do not invent one:

The project is delayed while I resolve [specific issue]. I don't have a dependable completion date yet, but I expect to know more by [date or decision point]. I'll post the next update then, even if the final timeline is still being confirmed.

How should you explain a scope change?

The original plan was [original scope], but [specific constraint] means I need to change it to [revised scope]. The contribution is still being used for [purpose]. If that changes what you expected, please contact me so we can discuss the available options.

What is clear refund-offer wording?

If the project genuinely cannot happen as pitched, explain that directly and offer a refund to supporters who would rather not continue:

I can't complete this project in the form originally described because [brief reason]. I'm sorry, and I don't want to leave anyone guessing. If you contributed and would prefer a refund rather than support the revised plan, please contact me at [contact method] by [date], and I'll explain the next steps.

On FanBell, refunds are supported and may reverse the payment, the transfer, and the platform fee depending on the transaction's status, so a refund you offer is one the platform can actually process (FanBell pricing).

FanBell costs $0 per month to start, so there is no subscription running against a project page you keep updating for a year after the goal is funded.

Only promise a refund process or deadline you can actually honor. The important point is to communicate the change openly rather than leaving the project page silent or outdated.

Frequently asked questions

Do I need to update every supporter individually?

No. For routine progress, one public update on the project page and the channels where you originally made the ask is usually enough — the same pattern Kickstarter supports by letting creators publish an update to all viewers rather than messaging backers one by one (What are project updates?).

FanBell does not route paid asks through private social DMs; creators share their FanBell page where their audience already follows them. You can still contact someone individually when a private account, refund, or supporter-specific issue requires it.

What if only a few people contributed and posting publicly feels awkward?

Post anyway, but keep it proportional. A single sentence may be enough:

The new lens is here—thank you to the three supporters who helped make it happen.

The update's purpose is to close the loop, not to make a small project look like a large campaign.

How often should I post project updates?

Post whenever the project's status materially changes. Four milestone posts — funded, started, delivered, and changed — are this article's recommended workflow rather than a platform rule. The one published benchmark comes from Kickstarter, whose help center asks funded creators for "at least one new update a month once funding is finished"; treat that as the floor for any project running longer than a couple of months. Add another update when a delay or long gap would otherwise leave supporters unsure about the status.

What if my update is already overdue?

Post now instead of waiting for a more impressive announcement:

This update is overdue, but the project is still active. Here's where it stands: [current status]. My next step is [next action], and I'll update the page again by [date or milestone].

An honest status report is more useful than continued silence, even when the progress is smaller than you hoped.

Ready to launch a project with a page supporters can actually check back on? Set up Project Support on your free FanBell link and start funding what's next.