Turn scattered notes from a hiring manager into a consistent job description form. Collect the business need, role outcomes, responsibilities, qualifications, working conditions, compensation context, and approvals HR needs to draft and review a new position.
Send role requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a scenario, adapt the details, or send the prompt into the Makeform builder. Each example shows a practical intake structure, not a completed job description.
Audience
Department leaders defining a newly approved position
Format
Multi-section intake with business case and approvals
Prompt size
500 chars
Example form structure
Multi-section intake with business case and approvals
Requester, department, and proposed title
Why is this new role needed now?
First-year outcomes and responsibilities
Is this role a people manager?
Budget owner and approval status
Suggested routing tags
New headcount
Replacement role
HR review
Ask for measurable outcomes separately from recurring duties. That distinction gives HR clearer material than a long list of tasks without priorities.
Step 1
Request
manager explains the role and business need
Step 2
Structure
outcomes, duties, skills, and context stay separate
Step 3
Review
HR and approvers resolve gaps and inconsistencies
Step 4
Draft
approved inputs become the source for job copy
Better role intake
Email threads encourage managers to send a title and a recycled list of duties. A structured job description form makes the important distinctions visible: why the role exists, what success means, which qualifications are truly necessary, and who owns the decision.
Use the same sections for business need, outcomes, responsibilities, skills, working context, and approvals. HR can compare submissions without translating each manager's preferred format.
Conditional logic can reveal team-size questions for managers, travel details for field roles, or shift and equipment questions for operations jobs while keeping unrelated prompts hidden.
The submission becomes a shared source record. HR can identify missing outcomes, inflated requirements, unclear ownership, or approval gaps before turning the material into candidate-facing language.
Common hiring situations
A finance analyst and a warehouse supervisor need different follow-up questions, but HR still needs a consistent core record. Start with the shared form and branch only where the work changes.
Capture the unmet business need, funding owner, expected outcomes, proposed level, and dependencies before a title becomes fixed by repetition.
Prompt the manager to reconsider inherited duties and qualifications instead of uploading an old description unchanged.
Add team scope, decision rights, budget ownership, stakeholder relationships, and success measures for people managers.
Collect location, schedule, equipment, travel, physical demands, licenses, and work environment in manager-friendly fields.
From blank page to usable intake
The goal is not to make managers write polished recruiting copy. It is to collect complete, distinguishable facts that HR can question, approve, and shape into a clear description.
Tell Makeform who completes the intake, which role types you hire, what HR must know, and which leaders approve headcount. Name the actual handoffs so the generated sections follow your process.
Keep outcomes apart from activities and required qualifications apart from preferences. Use dropdowns for controlled choices, long answers for context, and helper text that asks for evidence rather than polished prose.
Show management scope only when the role has reports, travel frequency only when travel is required, and physical-demand details only for relevant work. Managers see a shorter form while HR still receives precise detail.
Notify the HR partner or send submissions to your connected workflow. Use status fields or routing tags for new headcount, replacements, revisions, and requests that still need budget or leadership review.
Intake choices
A job description document is valuable after the role has been defined. During intake, however, managers need prompts that expose assumptions and HR needs fields that can be reviewed consistently.
Field guide
Six sections turn a vague hiring request into useful drafting material. Keep prompts concrete, explain how answers will be used, and let HR review judgment-sensitive details before publishing a description.
Ownership and reporting
Start with the requester, hiring manager, department, location, proposed title, and reporting line. These fields establish ownership and give HR the people to contact when scope or language needs clarification.
Business need
Ask what problem the hire addresses, why the work matters now, and what happens if it remains uncovered. For replacements, ask what changed since the previous description rather than assuming the role should return unchanged.
Outcomes and success
Outcomes describe the change the role should create; responsibilities describe recurring work. Ask managers for both. Time horizons such as 90 days and one year make vague expectations easier for HR to challenge and clarify.
Responsibilities and scope
Collect recurring responsibilities as distinct entries and ask for importance or approximate effort. Add decision rights, stakeholders, people-management scope, systems, budgets, and territories so candidates can understand the operating context.
Qualifications
Give required and preferred qualifications their own fields, then ask why each requirement matters to the work. That extra prompt helps HR spot inherited credentials, inflated years of experience, or tool names that should be described as transferable capability.
Work context and review
Finish with employment type, location, schedule, travel, work environment, compensation context, and reviewers. Conditional questions keep sensitive or specialized details with the people responsible for reviewing them before candidate-facing publication.
Related hiring tools
Once the manager's inputs are reviewed, use live Makeform tools for requisition details, candidate applications, interviews, feedback, and onboarding.
Collect the operational request, hiring timeline, headcount status, and approvals that sit alongside the role definition.
Open toolTurn the approved hiring plan into a structured way for candidates to submit relevant information.
Open toolGather scheduling needs and interview context when a candidate is ready to move forward.
Open toolGive panelists consistent criteria and a clear place to record role-related observations after interviews.
Open toolCollect availability and coordination details without mixing scheduling messages into evaluation records.
Open toolCarry approved employee and role details into a structured onboarding intake after the hire is made.
Open toolFAQ
Practical answers for HR teams replacing email-based role intake with a consistent manager workflow.
A job description form is an internal intake that managers complete to define a new or changing role. It collects structured facts such as the business need, reporting line, expected outcomes, responsibilities, qualifications, work context, and required reviewers. HR can use those answers as source material for a candidate-facing description, but the manager's submission should still be reviewed and edited rather than treated as final copy.
The description form focuses on what the role is: why it exists, what it owns, what success looks like, and what capabilities are relevant. A requisition form often focuses on authorization and recruiting logistics such as headcount status, budget, target date, recruiter, and approval routing. Teams can combine them or keep them connected as separate stages, depending on who supplies and approves each set of information.
Start with requester, hiring manager, department, title, reporting line, location, employment type, and reason for hiring. Then ask for measurable outcomes, prioritized responsibilities, decision scope, stakeholders, required and preferred qualifications, tools, schedule, travel or work conditions, compensation context, target date, and reviewers. Use conditional follow-ups for people management, shifts, driving, travel, equipment, or other details that apply only to some roles.
Usually it is more useful to ask for role facts in separate fields than to present one large blank box. Managers can explain the business need, outcomes, duties, scope, and qualifications in their own words. HR can then reconcile overlaps, question assumptions, standardize the structure, and write clear candidate-facing copy. A long-answer field can still capture extra context that does not fit the guided questions.
Yes. Ask first whether the request is new headcount, a replacement, or a substantial role change. New-position branches can collect the business case, proposed scope, and funding status. Replacement branches can request the current description and ask what should stay, stop, or change. Both paths can return to shared sections for outcomes, responsibilities, qualifications, working context, and review.
Separate required qualifications from preferences and ask the manager to connect each requirement to an actual responsibility or outcome. Add prompts for comparable experience, training the team can provide, and the capability behind a named tool or credential. These questions create better material for HR review; they do not replace the organization's own hiring policies, compensation review, or judgment about the final description.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and reuse the intake without a response cap. The paid tier removes the Makeform badge. You can begin with one department, refine the prompts with manager feedback, and copy the form for different role families while keeping a consistent HR review structure.
Submissions arrive in the Makeform inbox and can be connected to tools such as Google Sheets, Slack, and Zapier. Route them according to your own process: for example, notify the HR partner, label new versus replacement requests, and send approved inputs to the next recruiting stage. Keep editing and approval ownership explicit so a submitted request is not mistaken for a published job description.
Give every hiring request the same useful starting point.
