Describe the wage and employment details your organization needs to request. Makeform turns the brief into an employer-completed wage verification form with applicant authorization context, structured pay fields, an employer contact section, and a clear review trail. The form collects information for your team to review; it is not an official verification service and does not decide whether an applicant qualifies.
Route completed employer responses to your inbox, Google Sheets, Slack, or Zapier.
Sample prompts for the builder
Choose the scenario closest to your workflow, edit its details, and send it to the Makeform builder. Each structure is an example for an information request, not an independent wage determination.
Prompt ready4 formats
Audience
Property teams requesting wage details from an applicant's employer
Format
Employer response form with pay and status fields
Prompt size
701 chars
Brief qualitySends to builder
Example form structure
Employer response form with pay and status fields
Prompt exampleEditable in builder
Employer and authorized respondent
Short answerFirst ask
2
Employment status, title, and start date
Multiple fields
3
Gross pay rate and pay frequency
Number & dropdown
4
Usual hours and recent gross earnings
Number
5
Respondent attestation and completion date
Checkbox & date
Suggested routing tags
Suggested
Awaiting employer
Ready for review
Follow-up needed
Ask for pay frequency beside the pay rate. A number such as 2,400 means little until a reviewer knows whether it is weekly, twice monthly, or monthly.
Step 1
Prepare
set the case reference and requested wage period
Step 2
Request
send the information form to the employer contact
Step 3
Respond
employer supplies wage details from available records
Step 4
Review
authorized staff assess the response and follow up
A reviewable wage request
Turn scattered employer replies into comparable records.
Phone notes and unstructured emails leave basic questions unanswered: which pay period, gross or net, usual or temporary hours? A focused wage verification form asks every employer for the same context while preserving space for variable work arrangements.
Pay details with their context
Pair each gross rate with compensation type and pay frequency, and each earnings amount with a defined date range. Reviewers can understand what each number represents without guessing.
Questions that follow the job
Conditional sections can open overtime, commission, seasonal, or assignment questions only when relevant, keeping a standard request readable for every employer.
One employer response trail
Record the respondent's work contact, completion date, and employer-records attestation beside the wage fields so staff know who supplied the information and when.
Designed around human review
Keep collection, verification, and decisions separate.
Makeform helps you build and route the request. The employer supplies the answers, and your authorized reviewer decides whether follow-up or supporting records are needed under the requesting organization's own process.
Information request, clearly labeled
Introductory copy can tell the employer why the information was requested, identify the relevant applicant or case, and explain how staff will use the response for review.
Employer-completed record
The respondent identifies their role and work contact before entering details from available employer records. The applicant does not fill in the employer's wage section.
Controlled follow-up routing
Notify the assigned reviewer when a response arrives and tag submissions that need clarification, rather than implying that an automated form made a qualification decision.
Sensitive fields kept narrow
Use a case reference and worker name instead of collecting bank credentials, full payment-card data, passwords, or unnecessary government identifiers.
Build the request
From a wage question to a consistent employer response.
Start with the review context, generate the fields, check the language, and route completed responses to the people responsible for evaluating them.
Name the organization receiving the response, the employer audience, the wage period, and any variable-pay situations. Include your reviewed applicant-authorization and privacy language when your process requires it.
02
Edit fields and instructions
Separate rate, frequency, hours, and period totals into structured fields. Remove anything your reviewer does not need, add definitions for gross wages, and avoid credentials or unnecessary identifiers.
03
Send to the employer contact
Share the request through your established process with the correct employer representative. Tell respondents where to ask questions and who within your organization handles corrections.
04
Route for staff review
Send completed responses to the assigned inbox or worksheet, mark missing or inconsistent details for follow-up, and retain the employer's original submission alongside staff notes.
Request methods compared
Why structured employer intake beats a phone-note chain.
The goal is not to make the form an authority. It is to give authorized staff a complete, legible employer response with enough context to perform their own review.
Approach
What the reviewer receives
Practical fit
ApproachPhone call and handwritten notes
What the reviewer receivesA summary that may omit the pay frequency, reporting period, respondent role, or exact wording of the employer's answer.
Practical fitUseful for follow-up, but difficult to standardize as the primary intake record.
ApproachStatic document sent by email
What the reviewer receivesA familiar layout, plus manual download, version tracking, attachment handling, and re-entry into the case system.
Practical fitWorks when a requesting organization requires its own reviewed document format.
Approach
Generated online information request
What the reviewer receivesStructured employment, pay, period, and respondent fields in one submission, ready for authorized human review and follow-up.
Practical fitBest for repeatable intake where your organization controls the questions and review process.
Field guide
What a useful wage verification form should include.
A strong request connects each wage figure to the employment arrangement, the relevant period, and the employer representative who supplied it. Use these six sections as a practical starting point, then align the language with your organization's reviewed process.
Request context
Identify the case without overcollecting.
Give the employer enough information to match the request to the right worker while minimizing sensitive data. A case reference, worker name, and requesting-team contact are usually more useful than asking for a broad set of identity fields.
Requesting organization, team contact, and case or application reference.
Worker or applicant name and another limited matching detail only if needed.
Purpose statement, response instructions, and your reviewed authorization context.
Employer respondent
Record who completed the employer section.
Ask for the business name and the respondent's role, work email, and work phone. This creates a clear follow-up path without suggesting that Makeform checked the identity or authority of the person responding.
Employer legal or operating name and work location when relevant.
Respondent name, job title or department, and business contact details.
Preferred contact route for a reviewer who needs clarification.
Employment status
Describe the current work arrangement.
Employment status supplies the frame for the wage numbers. Use defined choices for active, leave, ended, seasonal, temporary, or variable assignment, then collect dates and job details that explain the selected status.
Current status, position or assignment, and original start date.
Full-time, part-time, seasonal, temporary, or variable schedule.
Known end date or scheduled status change, with an unknown option.
Pay rate & frequency
Make every compensation figure interpretable.
Do not use one vague field labeled wages. Ask whether compensation is hourly, salaried, piece-rate, commission-based, or another method; capture the gross rate; and pair it with a clear pay frequency.
Gross base rate and whether it is hourly, weekly, annual, or another basis.
Pay frequency such as weekly, biweekly, semimonthly, or monthly.
Overtime, differential, tips, bonus, or commission fields only when applicable.
Hours & earnings periods
Anchor totals to real date ranges.
A reviewer needs to distinguish typical scheduled hours from hours actually worked and a current rate from gross pay already earned. Repeating groups can capture several completed pay periods without squeezing them into a comment box.
Usual scheduled hours per week and an explanation of variable hours.
Pay-period start, end, hours, and gross earnings for each requested period.
Year-to-date gross earnings with the through-date clearly shown.
Attestation & review trail
Close with source and timing, not a guarantee.
An attestation can ask the employer respondent to confirm that answers reflect available business records to the best of their knowledge. It should not say that the response guarantees eligibility, acceptance, or any official result.
Respondent name, role, completion date, and optional typed acknowledgment.
Confirmation that the information reflects available employer records.
Internal review status, follow-up notes, and reviewer assignment kept outside the employer section.
Related tools
Build the surrounding applicant and employer workflow.
Use separate forms for applications, references, employer information, and property follow-up so each audience sees only the questions relevant to its role.
Practical answers for property teams, agencies, and employers building a structured information-request workflow.
What is a wage verification form?
A wage verification form is an information request that an employer completes about a worker's employment and wages. It commonly records employment status, position, start date, gross rate, pay frequency, usual hours, and earnings for defined periods. In this workflow, the form creates an employer-supplied record for authorized staff to review. Makeform does not independently confirm the answers or turn the submission into an official verification.
Who should complete the employer section?
Send it to the employer representative identified by your organization's process, such as an HR, payroll, owner, manager, or records contact. Ask that person to provide their name, role, and business contact information and answer from available employer records. Keep applicant-entered information outside the employer response section so reviewers can distinguish the request context from the employer's answers.
Which wage fields should the form include?
Start with compensation method, gross pay rate, pay frequency, usual scheduled hours, and gross earnings for specifically named pay periods. Add conditional fields for overtime, shift differential, commission, tips, bonuses, seasonal work, or variable assignments only when they matter. Every amount should have a basis or date range; otherwise the reviewer cannot reliably interpret it. Avoid passwords, bank credentials, full payment-card details, and unnecessary government identifiers.
Can the form handle hourly, salaried, and variable work?
Yes. Use a compensation-method choice to show the right follow-up fields. Hourly work can ask for rate and hours, salary can ask for the annual or period basis and pay frequency, and variable work can use repeating groups for completed pay periods. Seasonal and staffing workflows can also collect assignment dates, known end dates, and comments about expected variability without treating an estimate as guaranteed future income.
Does submitting this form guarantee that a landlord or agency will accept it?
No. Submission does not guarantee acceptance, eligibility, housing approval, lending approval, or any other decision. Each landlord, agency, lender, or other requesting organization sets its own process and may require a specific document, applicant authorization, supporting records, or follow-up. Use this generator to create a structured employer-completed request and review record, then align it with the requirements your organization has already reviewed.
How should we handle applicant authorization and privacy language?
Use the authorization, notice, retention, and privacy wording approved for your organization and workflow. Makeform can display that supplied wording and collect the necessary acknowledgment fields, but it does not provide legal advice or determine whether the wording is sufficient for a jurisdiction or recipient. Minimize the data requested, limit response access to authorized staff, and give the employer a clear contact for questions or corrections.
Is the wage verification form generator free?
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect responses without a usage cap on the free plan. The paid tier removes the Makeform badge. You can still tailor every question, instruction, option, and routing label before sharing the employer request.
What should staff do after an employer responds?
Route the response to the authorized reviewer, check that the respondent, pay basis, frequency, hours, and requested periods are present, and flag inconsistencies or missing context for follow-up. Preserve the original employer response beside any reviewer notes. Staff should apply the requesting organization's own reviewed criteria and procedures; Makeform collects and routes the information but does not make qualification, eligibility, underwriting, or acceptance decisions.
Replace wage follow-up threads with one structured request.
Generate an employer-completed wage information form for clear human review.
Unlimited free forms and responsesStructured employer-supplied wage fieldsEditable review and routing workflow
