Branch by team
A dropdown routes each team to a section listing the access and tools that team needs, so IT gets a specific list instead of a general one.
An onboarding form turns a new starter's first day from a scavenger hunt into a working setup. Payroll details, emergency contact, equipment preferences, dietary needs, shirt size for the swag run, asked once, a week before they arrive.
Not a stock template. Build it in a few minutes from a blank form, or describe it and let AI draft the questions on a paid plan.
It is also the form most likely to over-collect. Ask for what you need to pay them, equip them, and keep them safe. Everything else is curiosity wearing an HR badge.
A starting point, not a rulebook: every question below is a real Questionful question type, and all of them are editable once the form is in your account.
| Question | Question type |
|---|---|
| Full legal name | Short answer |
| Preferred name Ask it. It matters more than people expect | Short answer |
| Start date | Date |
| Which team are you joining? Branch to team-specific access questions | Dropdown |
| Emergency contact name and number | Short answer |
| Which equipment do you need? | Checkboxes |
| Any accessibility or workspace requirements? | Paragraph |
| Dietary requirements | Checkboxes |
| Upload your signed contract or ID Paid plans | File upload |
A dropdown routes each team to a section listing the access and tools that team needs, so IT gets a specific list instead of a general one.
One open question about accessibility or workspace requirements, before day one, is worth more than any policy document. Make it optional and do not explain it away.
A file upload question collects the signed contract or ID with everything else, stored encrypted on EU infrastructure with signed download links.
The webhook payload carries every answer, so one submission can create the IT ticket, the payroll record, and the desk booking without anyone retyping.
Legal and preferred name, start date, team, emergency contact, equipment and access needs, accessibility requirements, and any documents you need signed. Nothing beyond what you need to pay, equip, and look after the person.
Files are stored on EU infrastructure, encrypted at rest, with public bucket access blocked and downloads through signed links. Even so, move the data into your system of record and delete the response. Retention is much easier when it is not sitting in a form.
Yes. A team dropdown routes each choice to a section with only that team's access and equipment questions.
Indirectly: every submission POSTs as JSON to Zapier, Make, or your own endpoint, which can create the tickets and accounts.
Route each answer choice to its own section, so people only see what applies.
Feature19 types, including specialist ones most builders skip.
FeatureEvery response POSTed as JSON to any endpoint, signed if you want it.
TemplateStructured candidate intake with a CV upload and screening questions.
TemplateEverything you need before the first call, asked once.
TemplateAsk what would have kept them, while they will still tell you.
Use caseTurn recurring internal requests (time off, IT tickets, purchase approvals) into structured forms with a real audit trail.
Use caseReplace the CV inbox with a structured application form: same questions for everyone, CV attached, and every submission comparable.
Unlimited forms and 100 responses a month, free. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.