Describe your program and approval path. Makeform creates a stipend request form for requester details, amount, period, justification, supporting files, and review coding.
Send stipend requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor the program rules, or send it to the builder. Edit the example structure before publishing.
Audience
Employees requesting a monthly wellness benefit
Format
Request form with receipt upload and policy check
Prompt size
265 chars
Example form structure
Request form with receipt upload and policy check
Employee, department, and manager
Expense date and vendor
Requested stipend amount
How does this fit the program?
Upload the receipt
Suggested routing tags
New requests
Needs information
Ready for payment
Ask separately for the requested amount, covered period, and calculation. Reviewers can then understand the number without decoding a long justification.
Step 1
Request
identity, amount, dates, and purpose
Step 2
Verify
guidelines, documents, and budget code
Step 3
Review
administrator records the decision
Step 4
Process
approved request moves to payment
Why use one request form
A structured stipend request form keeps amounts, receipts, explanations, and missing information visible before payment work begins.
Required fields capture the same amount, dates, category, justification, and evidence from every requester.
Conditional fields reveal travel, recurring-payment, or evidence questions only when relevant.
Send submissions to the administrator and a shared sheet for consistent status tracking.
Adapt it to the program
Start with a use case, then replace its categories, evidence, and routing with your program rules.
Wellness, home-office, or learning requests with employee, manager, expense category, amount, and receipt fields.
Term dates, student program, budget breakdown, supporting documents, and other funding information in one submission.
Participant reference, completed milestone, project code, amount, and requested payment date without collecting banking data.
Program objectives, provider details, itemized costs, and conditional travel questions for preapproval or reimbursement.
Request workflow
Turn existing program rules into a clear form connected to reviewers and payment records.
Name the audience, categories, amount, period, evidence, and request recipient.
Add guidelines, required fields, category choices, and useful justification prompts.
Publish or embed the form, then notify the administrator on submission.
Send responses to a shared workflow for status, payment references, and follow-up.
Form vs email vs document
A policy explains eligibility; the form turns amount, rationale, dates, and evidence into a review record.
Field guide
These six sections help administrators identify the requester, evaluate the request, and hand off an approved record.
Requester
Use identifiers your office can match to existing records and route to the correct department.
Amount
Pair the total with currency, dates, frequency, and an itemized calculation reviewers can check.
Purpose
Prompt for the activity, need, or outcome supported, with guidance for a useful answer.
Evidence
Keep receipts, enrollment details, schedules, or quotes with the request and label required evidence.
Administration
Ask only for coding applicants know. Keep reviewer status in the internal workflow.
Confirmation
Show program guidance near a final check of the amount, period, and attachments.
Related tools
Use a dedicated form for reimbursements, scholarships, travel, grants, or general payments.
Collect incurred expenses, dates, categories, receipts, and reimbursement totals.
Open toolRoute a general payment request with payee, amount, timing, and coding details.
Open toolGather applicant, academic, eligibility, and supporting information for scholarship review.
Open toolStructure project goals, budgets, schedules, and attachments for grant applications.
Open toolBuild a broader reimbursement intake for staff, volunteers, or program participants.
Open toolCollect itinerary, purpose, expected costs, and routing details before a trip.
Open toolFAQ
Practical answers for administrators building an employee or student stipend intake.
A stipend request form lets an employee, student, participant, or coordinator request a defined payment. It records the requester, program, amount, period, justification, evidence, and review coding.
Include name, email, employee or student ID, program, category, amount, currency, dates, calculation, justification, and uploads. Add manager, project, fund, cost center, or payment date when needed.
Follow your program rules. Explain which receipt, quote, enrollment record, or program description is acceptable, and show uploads only for categories that need evidence.
Yes. Use requester type to show employee fields such as department and manager or student fields such as ID, program, and term. Separate forms may suit very different policies.
Collect whether it is one-time or recurring, dates, frequency, amount per payment, and expected total. Keep the calculation visible and use a consistent renewal process.
Yes. Collect the manager, coordinator, department, or program used for routing, notify the reviewer, and send responses to Google Sheets, Slack, or another connected workflow.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect stipend requests without a response cap. The paid tier is only for removing the Makeform badge.
Keep the request focused on review and use your established payment system for sensitive payout data. Collect a payment method or payee reference without requesting full account details.
Replace scattered stipend emails with one clear intake.
