Donation Request Forms: Fields, Examples, and Approval Workflow

A donation request form is an application for support. It is not the same as a donation form that collects money from a donor.

That distinction changes everything. A request form needs eligibility, purpose, amount, evidence, review, and a decision. A payment form needs donor details, an amount, consent, and verified payment status.

Donation request form fields

Use these sections for sponsorship, community support, charitable grants, and in-kind requests.

Requester

• Contact name
• Organization name
• Work email and phone
• Website
• Organization type
• Registration or tax-exempt identifier, when relevant
• Location and communities served

Request

• Type of support requested
• Cash amount or in-kind items
• Intended use
• Date the support is needed
• Event or program date
• Number of people expected to benefit
• Other confirmed funding or sponsors

Evidence

• Short program description
• Budget or cost breakdown
• Proof of registration
• Sponsorship package
• Recent impact report
• Relevant links

Agreement

• Accuracy declaration
• Permission to contact
• Privacy acknowledgement
• Name and authority of the submitter

Choose structured fields where the answer will be filtered or compared. Use a textarea only for the explanation that genuinely needs narrative. The Core Forms field types cover standard inputs, dates, choices, uploads, and consent controls.

Publish eligibility before the form

Do not make applicants finish the form to discover they were never eligible.

State:

• Eligible organization types
• Geographic limits
• Supported causes or programs
• Minimum and maximum request
• Excluded expenses
• Submission deadlines
• Review frequency
• Expected decision date
• Whether repeat applications are allowed

Good eligibility rules reduce weak applications more fairly than a hidden internal screen. They also give staff a consistent reason for approval or rejection.

Use form scheduling to open and close an application window automatically. The closed state should show the next opening date or another legitimate route, not a dead form.

Adapt the form to the request type

Cash, product, venue, volunteer, and sponsorship requests need different evidence.

Core Forms conditional logic can reveal:

• A budget upload for cash requests
• Quantity and delivery fields for products
• Audience, assets, and recognition details for sponsorships
• Date, duration, and role details for volunteer support

This keeps the application relevant without forcing every requester through every section.

For a long grant-style application, use multi-step forms and save and resume. Name steps by task, such as Eligibility, Organization, Request, Evidence, and Review.

Handle supporting documents carefully

Ask only for evidence needed at the current review stage. A first screen may not need bank records, personal identification, or a full board list.

The file upload documentation covers type, size, and count limits. In the form:

• List accepted formats.
• Set a practical maximum file size.
• Tell applicants not to upload passwords or unnecessary personal records.
• State how long documents will be retained.
• Restrict access to the staff who review requests.

If a document is optional, label it optional. Applicants should not have to manufacture a file to satisfy an ambiguous upload field.

Build an approval workflow

A form submission is the start of the review, not the decision.

Use this flow:

1. Save the complete application in Submissions.
2. Send the applicant an Autoresponder with a reference and decision timeline.
3. Notify the responsible reviewer through the Email action or a team integration.
4. Send structured fields to Airtable, Google Sheets, or a case-management system.
5. Record eligibility, reviewer, decision, amount, and decision date in the system of record.
6. Send the final decision from an accountable staff channel.

Core Forms can deliver the application to other systems, but the organization still needs a review policy. Automation should not quietly turn a subjective grant decision into an unexplained score.

Donation request form examples

Local sponsorship request

Collect:

• Event and organizer
• Audience and location
• Sponsorship amount or item requested
• Recognition offered
• Event date
• Sponsorship deck

In-kind product request

Collect:

• Product and quantity
• Beneficiary group
• Distribution plan
• Delivery address and date
• Storage or safety needs
• Proof of eligible status

Employee-supported charity request

Collect:

• Employee sponsor
• Organization
• Relationship to the organization
• Program and amount
• Registration evidence
• Conflict-of-interest declaration

The fields should make the policy enforceable. Do not ask broad questions because they might be interesting later.

If you mean a form that accepts donations

Use a payment form, not this application structure. A donor-facing form typically needs:

• Donor name and email
• Donation amount
• One-time or recurring choice, if supported by the chosen gateway
• Designation or campaign
• Consent and receipt details

Core Forms supports payment-required forms through Stripe, PayPal, Razorpay, and Polar. Follow the Core Forms payment guide and fulfill the donation only after the provider confirms payment.

Never collect raw card details in ordinary WordPress fields.

Core Forms implementation checklist

• Begin with the closest form template.
• Add eligibility text above the form.
• Use conditional sections for request types.
• Add scheduling for application windows.
• Configure safe upload limits.
• Set autoresponder and review notifications.
• Run the accessibility audit.
• Test every conditional branch and closed state.
• Review the stored submission and every downstream record.

FAQ

What is a donation request form?

It is an application used by a person or organization to request cash, products, sponsorship, facilities, or other support.

Is a donation request form the same as a donation form?

No. A request form asks an organization to provide support. A donation form accepts money or a pledge from a donor.

What documents should applicants upload?

Request only evidence needed for the current decision, such as registration proof, a budget, sponsorship package, or impact report. Avoid unnecessary personal or financial records.

Can Core Forms manage a review workflow?

Core Forms can store applications, send acknowledgements and notifications, and route structured data to team tools. The organization’s policy and system of record should control review and approval.

Can Core Forms accept donation payments?

Yes. Core Forms supports Stripe, PayPal, Razorpay, and Polar payment workflows. Payment should be considered complete only after gateway confirmation.