Describe the role and get a nanny application form for experience, age-group skills, availability, references, and requirements. Edit before sharing.
Route nanny applications to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a starting point or send the prompt into the builder. Each example shows a structure, not a candidate response.
Audience
Candidates applying to care for young children on weekdays
Format
Detailed application with schedule and references
Prompt size
335 chars
Example form structure
Detailed application with schedule and references
Childcare roles and ages cared for
Weekday availability and start date
Which routine tasks have you handled?
How would you communicate a difficult day?
Two professional childcare references
Suggested routing tags
Review next
Schedule match
References pending
Ask for specific ages cared for and responsibilities handled, not just total years of experience.
Step 1
Define
role, children, duties, and schedule
Step 2
Collect
experience, availability, and references
Step 3
Review
compare job-related answers consistently
Step 4
Follow up
interviews and reference conversations
A clearer first step
A structured application shows whether a candidate's childcare background, schedule, and expectations align with the role.
Collect position dates, children's age ranges, responsibilities, and reasons for leaving in a repeatable format.
Ask for available days, hours, start date, and recurring conflicts before scheduling interviews.
Gather each reference's name, relationship, contact details, and the role they can discuss.
Adapt it to the opening
Start with the care arrangement closest to yours, then keep only questions that help assess the stated work.
Match household schedule, children's ages, duties, and communication preferences to relevant experience.
Standardize intake, tag role preferences, and route schedule matches to a coordinator.
Focus on school pickup, activities, homework, afternoon meals, and weekday availability.
Add travel windows, overnight care, routine planning, and scenarios without collecting document numbers.
Application workflow
Turn the position into a focused form, then review complete submissions in one place.
Include age groups, core hours, duties, location, start date, and role-related travel or driving.
Require essential fields and show follow-ups only when relevant, such as infant-care details after infant experience is selected.
Send every candidate the same form for answers, files, and references.
Review responses, export them to a sheet, and notify the family or coordinator.
Choose the right intake method
Make expectations visible and give each candidate the same space for relevant qualifications.
Field guide
Six focused sections create a useful picture of role fit.
Candidate basics
Collect contact information, a preferred contact method, and general work area. Avoid sensitive identity documents during initial screening.
Childcare history
Ask candidates to describe recent childcare positions with dates, age groups, schedules, responsibilities, and work setting.
Availability
Use checkboxes and time fields for regular days, working times, earliest start date, and schedule flexibility.
Duties and skills
List actual responsibilities and relevant experience. Separate child-focused meals and tidying from broader household work.
Scenario questions
Ask two or three normal, role-specific scenarios, then review the candidate's reasoning and communication approach.
References
Ask how each reference knows the candidate, which childcare role they observed, and how to contact them. Explain when contact may occur.
Related tools
Use Makeform tools for applications, scheduling, interviews, and reference follow-up.
FAQ
Practical answers for families and agencies preparing a consistent candidate intake process.
Include contact details, childcare positions, ages cared for, relevant duties, availability, start date, scenarios, and professional references. Add driving or travel questions only when those duties are part of the role.
A resume presents work history in the candidate's format. An application asks everyone the same role-specific questions about hours, age-group experience, duties, and dates. Allow a resume upload for context.
Yes. Create separate forms or branch into full-time, part-time, backup, or travel sections. Separate forms suit different duties; branching suits roles sharing most questions.
Use checkboxes for recurring days, time fields for working windows, a date field for the earliest start, and a short answer for recurring conflicts. Also state the schedule in the job description.
Yes. Add clearly labeled uploads for a resume and optional training documents. Handle identity or background-screening documents through an appropriate later-stage process instead of requesting sensitive numbers in a general application.
Two or three professional references is a practical start. Ask how each person knows the candidate and which position they can discuss. Combine references with interviews and review.
Yes. Makeform provides unlimited free forms and responses for generating, editing, publishing, and collecting applications. The paid tier removes the Makeform badge.
Yes. Add fields for schedule, age groups, work area, travel, driving, and role type. Tags and exports help sort submissions, while conditional sections hide irrelevant specialized questions.
Replace scattered candidate messages with one clear intake.
