Describe the income evidence your property team or benefits agency needs to review. Makeform turns the request into a structured intake with reporting periods, uploads, attestations, and a route to human review. The form organizes submitted information; it does not independently verify income or decide whether an application qualifies.
Route records to Google Sheets, Slack, and Zapier for review.
Sample prompts for the builder
Choose a complete prompt, adapt it to your written process, or send it into the Makeform builder. Each example collects applicant- or employer-submitted evidence for a reviewer; it is not an automated verification result.
Prompt ready4 formats
Audience
Applicants submitting income information to a property manager
Format
Applicant form with income sources and file uploads
Prompt size
686 chars
Brief qualitySends to builder
Example form structure
Applicant form with income sources and file uploads
Prompt exampleEditable in builder
Applicant and application reference
Short answerFirst ask
2
Income amount, frequency, and period
Number
3
Do you want to add another income source?
Yes / no
4
Upload the requested supporting evidence
File upload
5
Applicant attestation and signature
Signature
Suggested routing tags
Suggested
Ready for review
Follow-up needed
Employer response
Ask for the reporting period beside every amount. A number without a pay frequency or date range creates extra follow-up and can lead reviewers to compare unlike periods.
Step 1
Request
ask only for evidence required by your reviewed process
Step 2
Submit
applicant or employer provides dated income details
Step 3
Review
authorized staff assess the record and follow up
Step 4
Record
retain the decision trail under your own policy
Why structured intake matters
A document inbox is not an income review workflow.
Loose attachments force reviewers to infer whose evidence they received, which dates it covers, and whether another source is still missing. A structured income verification form connects each applicant-submitted document to the context a human reviewer needs.
Comparable reporting periods
Pair every amount with its basis, pay frequency, and reporting dates. Reviewers can understand regular, seasonal, and irregular income without guessing what a bare number means.
Questions that follow the source
Show wage, self-employment, or no-current-income fields only when selected. Respondents see relevant questions while the reviewer receives a consistent record.
Visible human review status
Route submissions into ready, missing information, employer response, and follow-up queues. Those labels support staff work; they are not an automated judgment about truth, eligibility, or approval.
Built for review teams
One intake pattern, four evidence paths.
Start with the closest path, then replace examples with requirements approved by your program or property team.
Applicant self-report
Collect current sources, amounts, frequencies, reporting periods, and selected uploads in one submission. Repeatable source blocks keep a second job or household member connected to the same case.
Employer response
Give HR or payroll contacts a focused form tied to an authorization and request reference. Capture responder role, work contact, dated pay information, and variable-pay notes for staff review.
Benefits case documentation
Organize household and source records around a case reference without turning the form into an eligibility calculator. The agency's authorized reviewer applies the program's current rules.
Changes and recertification
Ask what changed, when it became effective, and what current period is being reported. Conditional follow-up separates a changed-income record from a routine periodic update.
Evidence intake workflow
From a written request to a review-ready record.
Build the request around your established policy, make the reporting period explicit, and send each response to an authorized person rather than presenting an automated verification result.
Tell Makeform whether an applicant, household member, or authorized employer contact responds; which reporting period matters; and which evidence your reviewed process requests. Avoid collecting extra identifiers merely because an old paper form included them.
02
Edit sources and conditional paths
Add the source categories your team actually handles, then branch into relevant details. Keep amount, frequency, gross or net basis, and period together. Add another-source and another-household-member loops where needed.
03
Send responses to authorized staff
Notify the assigned reviewer or route the record through your existing case workflow. Use an application or case reference in notifications instead of placing unnecessary sensitive income details in subject lines or broad team channels.
04
Review, follow up, and record
A person checks whether the response matches the request, resolves unclear dates or missing evidence, and documents the next step. Makeform structures the submission but does not authenticate documents or make the underlying decision.
Email vs PDF vs structured intake
Choose a collection method that preserves context.
The useful difference is not whether a document is digital. It is whether the reviewer can connect each submitted amount and attachment to a person, source, reporting period, request, and follow-up status.
Approach
What the reviewer receives
Operational tradeoff
ApproachEmail and loose attachments
What the reviewer receivesA message with files, often without standardized periods, source labels, or case references.
Operational tradeoffEasy to start, but reviewers spend time matching records and requesting missing context.
ApproachDownloadable PDF or document
What the reviewer receivesA familiar fixed layout that may be printed, scanned, or returned with blank fields.
Operational tradeoffUseful when a fixed document is required, but repeatable sources and routing remain manual.
Approach
Generated online intake form
What the reviewer receivesStructured source, amount, frequency, period, evidence, attestation, and request reference fields.
Operational tradeoffBest for consistent collection and human follow-up; the reviewer still evaluates the submitted evidence.
Field guide
What an income verification form should collect.
Use these six sections as a practical starting point. Keep only what your organization is authorized to request, publish clear instructions, and explain that a qualified staff member—not the form—reviews the evidence.
Person and request
Match the response to the right record.
Begin with enough information to associate a response with an existing application or case. A property, unit, program, or internal request reference is usually more useful than repeatedly asking for highly sensitive identifiers.
Applicant or household member name and preferred contact.
Application, case, property, or request reference supplied by your team.
Respondent relationship, such as applicant, employer contact, or authorized representative.
Income source
Name the source before asking for numbers.
Source categories determine which follow-up questions make sense. Use plain labels and an other option, then apply conditional logic so wage earners, self-employed applicants, and people reporting no current income do not face the same irrelevant fields.
Source category and source or employer name.
Employment status, position, or source description when relevant.
Repeatable blocks for multiple jobs, sources, or household members.
Amount and period
Make every amount interpretable.
An income amount is ambiguous without timing and basis. Keep the amount beside pay frequency, whether it is gross or net according to your instructions, and exact reporting dates. Let respondents explain irregular or partial periods.
Amount and frequency, such as weekly, biweekly, monthly, or annual.
Beginning and end date for the reported period.
Context for overtime, commission, seasonal hours, gaps, or recent changes.
Supporting evidence
Ask for documents with a stated purpose.
List the evidence your reviewed process requests and identify the period it should cover. Use file upload fields tied to the source rather than a single unexplained upload box. Do not imply that uploading a document makes it authentic or acceptable.
Document type and reporting period requested by your organization.
Source-specific file upload with file format and readability instructions.
A cannot-provide option that opens a reason and staff follow-up path.
Notice and attestation
Set expectations before submission.
Tell respondents who receives the information, why it is requested, and how to ask questions. An attestation records what the respondent states; it does not convert the submission into independent verification, official acceptance, or an approval decision.
Purpose, intended reviewer, and your organization's privacy or retention notice.
Applicant or responder attestation using wording reviewed by your organization.
Clear statement that staff may request clarification or additional information.
Reviewer routing
Turn receipt into an accountable next step.
Route by property, program, office, or assigned reviewer and use neutral operational statuses. A missing-information tag can create a task without making a negative eligibility inference, while a review-complete status can record who handled the response.
Assigned team or reviewer based on the request reference.
Statuses such as received, ready for review, follow-up needed, and review complete.
Internal notes, review date, and a record of requested follow-up.
Related tools
Build the surrounding application workflow.
Income evidence intake is one part of a broader property or benefits process. Use these live Makeform tools for connected requests, keeping each form's purpose and review responsibility clear.
Practical answers for property managers, program administrators, and employer contacts designing a careful evidence intake and review process.
What is an income verification form?
An income verification form is a structured request for income details and evidence submitted by an applicant, household member, employer, or authorized respondent. It connects the person and case reference to a source, amount, frequency, reporting period, uploads, and an attestation. The form organizes information for a human reviewer. It does not independently authenticate documents, confirm statements, calculate eligibility, or approve an application.
What fields should I include in an income verification form?
Start with the applicant or household member, a case or application reference, respondent role, source category, source or employer name, income amount, frequency, gross or net basis according to your instructions, and reporting-period dates. Add source-specific questions, requested document uploads, an explanation field for irregular income, and an attestation reviewed by your organization. Ask only for fields your process actually needs. Avoid passwords, account credentials, full payment-card details, and unnecessary government identifiers.
Can an employer complete the form directly?
Yes. Create a separate employer response path with the requesting organization, request or case reference, employee name, authorization reference, responder name and role, work contact, employment status, start date, gross pay, pay frequency, reporting dates, and variable-pay context. Send it only through your established authorized process. Your staff should review the response and resolve discrepancies; receiving an employer submission through the form is not the same as Makeform independently verifying it.
How should I handle multiple jobs or household income sources?
Use a repeatable source section. For each source, capture whose income it is, the source category, amount, frequency, period, context, and matching evidence. Then ask whether the respondent needs to add another source or household member. This preserves the relationship between a figure and its document while avoiding one oversized free-text answer. A reviewer can compare the records according to your organization's current rules without the form making an eligibility judgment.
Does the form verify pay stubs or guarantee acceptance?
No. Makeform collects the information and files respondents submit, but it does not independently authenticate pay stubs, contact issuers, confirm income, or decide whether evidence satisfies a landlord, lender, benefits agency, or government authority. An authorized human reviewer applies the organization's approved process, requests clarification when needed, and records the outcome. State that distinction in the form so respondents understand that submission is a step in review, not a promise of acceptance or approval.
How can I reduce unnecessary sensitive-data collection?
Begin from the decision your authorized reviewer must make and remove fields that do not support it. Use an internal case reference instead of repeatedly collecting a sensitive identifier, request only the evidence period needed, and keep detailed income data out of notification subject lines or broad chat channels. Never request passwords, authentication secrets, or full payment-card data. Add your own access, retention, and deletion instructions, and direct respondents to the appropriate contact for questions about your policy.
Is this income verification form generator free?
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and use the intake without a response cap. A paid tier is available only to remove the Makeform badge. Revise sources, periods, instructions, conditional paths, and routing before sharing. Your organization remains responsible for its request language, authorized evidence collection, and submission handling.
Where do submitted income records go?
Responses arrive in the Makeform inbox and can connect to tools such as Google Sheets, Slack, or Zapier for an established internal workflow. Route records only to authorized reviewers, use neutral statuses such as received or follow-up needed, and avoid broadcasting sensitive details. You can send a receipt to the respondent while clearly explaining that receipt confirms delivery only. It does not mean the evidence was verified, accepted, or approved by the property team, program, lender, or any authority.
Replace scattered attachments with a review-ready intake.
Generate an income evidence form built for careful human review.
Unlimited free forms and responsesConditional income-source pathsClear human review handoff
