The short answer
Ask someone outside the organising team to open the actual fundraiser link on a phone while signed out. Check the offer, prices, deadline, collection instructions and contact details. Review the checkout and fee explanation before payment, then check what the organiser can see. Use approved sample names for participant pages. A real test payment needs an authorised payer and an agreed reconciliation plan.
Start with a supporter who has not seen the plan
Give a colleague or parent volunteer the link and ask them to explain what the fundraiser is for, what they can buy or contribute, and what happens next. Do not guide them through every step. Their first questions will reveal missing information that feels obvious to the committee.
Use the link you intend to print or send, including the QR code if there is one. Open it on a phone without an organiser session. An editor preview can hide problems that affect a normal visitor. Check that the link identifies the intended school, campaign and participant rather than a previous fundraiser.
Follow one realistic order up to the payment decision
For a product drive, choose a product option and a quantity a family might actually order. Check the pack size, price and collection details against the supplier agreement. For a donation campaign, check the selected amount and any participant attribution. Read the final fee explanation instead of assuming the amount on the first screen is the amount charged.
A walkthrough does not require submitting a payment. Use a provider-supported preview or test method if one is available for your campaign. Do not put test card numbers into a live checkout or invent bank transfers to make an order look paid. Ask support if you cannot verify an essential step without creating a live transaction.
| Check | What a passing result looks like |
|---|---|
| Product and quantity | The selected option and pack size match the written offer |
| Checkout amount | The supporter can understand the total and any additional fees |
| Deadline and collection | Dates, location and instructions agree across the page and message |
| Help route | A working organiser contact is visible before someone pays |
| Small screen | Buttons, quantities and important information remain usable on a phone |
Check participant pages with approved sample details
For an athon, check both the main campaign and a direct participant link. Decide which names, photos, class details and totals the school permits supporters to see. A page that is absent from a public list can still be accessible to anyone with its direct link. Test the actual visibility rather than treating a joining code as page protection.
Use fictional participants or school-approved display names while checking the setup. Confirm whether the campaign mode and team structure are correct before adding the real group. On Raised, its athon testing guide warns that changing between participant modes removes existing team and member data, so resolve that choice before inviting families.
Make sure the organiser can finish the job
Ask the person doing collection or reconciliation to inspect the reports they will use. Can they find an order, distinguish payment states and identify the product quantities to buy? A good-looking page is only half the workflow. Confirm which organisers need access and who will answer supporter questions during the campaign.
If the school approves a genuine paid test, use an authorised payer and record its purpose. Agree beforehand whether it will remain a real contribution or need a refund, and check any fees or refund conditions. After payment, reconcile the receipt, organiser record and attributed participant. A pending checkout does not prove settlement or bank payout.
- Check the correct school or group receives the campaign proceeds.
- Keep test records identifiable and out of the supplier's final order unless intended.
- Assign someone to resolve each problem found during the trial.
- Repeat the affected step after a change; do not rely only on the first screenshot.
Make a clear go-or-fix decision
Keep a short launch record with the checked link, date, tester and outstanding issues. Fix a wrong price, exposed personal detail, broken checkout or incorrect receiving organisation before sending the campaign widely. Small wording improvements can be scheduled, but families need accurate information from the first message.
After the final check, send the approved link and one set of instructions. Keep the organiser contact available during the first wave of orders so genuine questions reach someone who can act. If an essential setting changes later, revisit the relevant test before promoting the page again.
Wording you can adapt
Campaign link: [URL] Checked on: [date] Supporter walkthrough by: [name] Organiser reports checked by: [name] Problems still to fix: [list or none] Approved to share by: [responsible organiser]
Check a Raised campaign before sharing it
Raised supports product-order campaigns and participant-based fundraising. Its athon testing guide explains how to check team setup, direct participant links and the supporter fee experience before inviting families.
Confirm your campaign's actual visibility and payment settings. Public-list privacy is not the same as access control on a direct link. A real payment is still a charge, even when its purpose is testing.
Read Raised's pre-launch testing guideRaiseFunds and Raised are made by the same team. We recommend Raised where its features fit the task. Check current fees and campaign settings before launching.
Sources and next steps
Product details were checked against the sources below on 15 November 2026. Planning examples are illustrative, not promised fundraising results.
- Raised: testing an athon before launch
- Raised: participant visibility and display names
- Raised: choosing participant and team modes
- Raised: current checkout fees and payment settings
- Raised: product-order workflow
Spotted an outdated detail? Tell us what needs correcting.