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.
Last verified August 2026.
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?
Supporters contributed because they trusted you to pursue the project. They may not expect a formal report for a $300 microphone upgrade or music video budget, but they reasonably want confirmation that the project is moving forward.
Kickstarter says funded creators should communicate with backers through updates, especially when they encounter problems or expect delays (creator obligations, verified August 2026). Although a direct fan-supported project is not necessarily a Kickstarter campaign, the underlying trust principle is useful: explain meaningful progress and disclose changes before supporters have to ask.
The practical fix is simple: publish a short update whenever the project's status materially changes. You do not need a newsletter or elaborate content plan.
When should you update supporters?
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 (project updates, verified August 2026).
Four milestone posts across a project's life are a practical rule of thumb, not a universal requirement. Some projects will need fewer; longer or changing projects may need more. The standard is whether supporters can understand the current status without chasing you for an answer.
| Milestone | What to post | Where to post |
|---|---|---|
| Goal funded | Confirm the result and thank supporters | Social channels and project page |
| Work starts | Show the first concrete action | Social channels |
| Delivered or finished | Share the completed result | Social channels and project page |
| Plan changes | Explain what changed and what happens next | Social channels and project page |
What should a project update say?
A useful update answers three questions:
- What happened? State the specific progress or change in one or two sentences.
- Why does it matter? Connect the development to the project supporters funded.
- 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” connects the thanks to what supporters actually did.
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?
Your Project Support page gives supporters one stable place to check the project without waiting for another social post. Treat it as the source of truth rather than only the original pitch. 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.
On FanBell, the project progress bar and supporter count update automatically as fans contribute; creators do not need to calculate those running totals manually (how FanBell works, verified August 2026).
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, then distinguish confirmed facts from estimates. Kickstarter's funded-project guidance specifically directs creators to communicate setbacks and keep backers informed rather than disappearing when fulfillment becomes difficult (creator obligations, verified August 2026).
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.
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.
FanBell does not route paid asks through private social DMs; creators share their FanBell page where their audience already follows them (how FanBell works, verified August 2026). 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 a useful rule of thumb rather than a mandatory schedule. 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.
Keep reading
Ready to get paid for the interactions you already get?
Create your free FanBell link