Building an Online Job Application Form Small Teams Can Live With

Short answer: a job application form needs contact details, the role, right-to-work confirmation, a CV upload and two or three screening questions — and the screening questions are the whole point, because they let you sort applicants without reading every CV. As of September 2026 BotForms starts at $29/month with 5 GB of storage, which is far more than a year of CVs.

The hiring process at most small businesses is an email address on a careers page. Applications arrive as replies with attachments, someone copies names into a spreadsheet, two of them get lost in a promotions folder, and three weeks later nobody can say who was told what.

It works, in the sense that people do get hired. It is also the reason good candidates go quiet — they applied, heard nothing for eleven days, and took the other offer.

An applicant tracking system solves this, and for a business hiring two people a year it is a large piece of software bought for a small problem. A form solves most of it.

What breaks with an email address

Applications are not comparable. Everyone sends different information in a different order. Comparing six candidates means reading six documents and holding the relevant bits in your head.

Attachments scatter. The CV is in the mailbox, your note about the phone screen is in a spreadsheet, the interview time is in a calendar, and the connection between them is memory.

There is no status. Nobody can answer "where is this person up to" without reconstructing it from an email thread.

Nobody gets told no. Not from malice — there is no list to work through, so the rejections that require effort do not happen. This is the part that costs you: candidates talk, and a business that does not reply gets a reputation for it among exactly the people you want next year.

Screening happens last. You read a full CV to discover the applicant cannot work the shift pattern. A form asks that in question three.

The fields that earn their place

Field	Why it is there	Required
Name and phone	Contact, and phone is how you reach people fastest	Yes
Email	Written correspondence and the rejection note	Yes
Role applied for	A dropdown, so applications sort themselves	Yes
Right to work in the country	The fastest disqualifier there is	Yes
CV upload	The document, attached to the answers	Yes
Two or three screening questions	The actual sorting mechanism	Yes
Availability or notice period	Decides whether the timing works at all	Yes
Short free-text: why this role	Replaces the cover letter, kept to a few sentences	Optional
How they heard about the role	Tells you which channel is worth paying for	Optional
Portfolio or certification upload	Only where the job requires evidence	Conditional

Eight to ten fields. An application form longer than that loses the people with options, who are the ones you are advertising for.

Screening questions are the whole trick

This is the difference between a form and an email address, and most application forms waste it.

A screening question is one whose answer can remove someone from consideration or move them up. Not "tell us about yourself" — something with a hard edge:

• Can you work the shift pattern this role requires? (yes / no)
• Do you hold a current licence or certification of type X? (yes / no / in progress)
• Are you able to commute to the site location? (yes / no)
• How many years have you done this specific task? (bands, not free text)

Three of these, answered as options rather than prose, let you sort a pile in minutes rather than an evening. They are also fairer than skimming, because every applicant answers the same question and gets judged on the answer.

Two cautions. Keep them job-related and keep them off protected characteristics — age, health, family status and the rest do not belong on an application form. And do not auto-reject on a single answer without a human glance; "in progress" on a certification is often the right hire.

If you want a hand writing them, this is a genuinely good use of question-generation — describing the role and letting the builder draft the screening set is covered in AI that writes and optimises form questions.

The CV upload

The one field that changes the administrative experience most. A CV that arrives attached to the application sits with the answers rather than in a mailbox.

Practical settings: accept PDF and Word, cap the size somewhere around ten megabytes, and say on the field what you accept, because the alternative is someone photographing their CV. For roles that need evidence — a portfolio, a ticket, a certificate — add a second, clearly-labelled upload rather than asking them to zip everything together. The mechanics are in file and photo uploads on forms.

Name the field for what you want. "CV or resume (PDF or Word)" gets you the document; "Attachments" gets you anything.

Validation saves the follow-up email

Application forms are where mistyped contact details hurt most, because the candidate believes they applied and you believe they never did.

Validate the email format, validate the phone as digits with a sensible length, and require the fields you genuinely need rather than everything. A form that rejects a submission over an optional field teaches people to abandon it. The rule set is in validation rules that stop bad data.

One detail specific to hiring: if the role has a hard requirement, put that question early and make it required. Discovering it at the end wastes both sides' time.

Who sees applications

Applications contain personal data and should not be visible company-wide by default. The hiring manager and whoever books interviews is usually the whole list.

Forwarding CVs by email is how that boundary erodes — one forward and the document is in a mailbox outside your control. Scoped access, where a named person can read the applications for their role and nothing else, is both tidier and easier to remove when the hire is made. The shape of that decision is in who on your team should see form submissions.

Keeping and deleting applications

Two rules, and they take five minutes to set.

Say how long you will keep it. One line on the form: unsuccessful applications are kept for a stated period and then deleted, and candidates can ask for removal sooner. The period is a business decision — the usual reason to keep them at all is to revisit a near-miss for the next opening.

Be able to actually delete. If someone asks, you should be able to find their application and remove it without a search through three systems. That is far easier when the application is one record rather than an email, a spreadsheet row and a file in a shared drive. The wider version of this is in form data retention and privacy.

Running the process without an ATS

A form gives you a list. Add two habits and it behaves like a pipeline.

Export at the shortlist stage. Pull the applications to a spreadsheet, add columns for stage and notes, and work from that. Twenty applicants do not need a database. Exporting submissions to CSV or Excel covers the mechanics and the encoding trap that mangles names.

Reply to everyone, in batches. Two templates — invite and decline — sent on a fixed day each week. This is the cheapest reputational investment available to a small employer, and it takes about twenty minutes.

When you are hiring continuously across several roles with multiple interviewers, that is the point to buy an ATS. Below it, the form plus a spreadsheet is not a downgrade; it is the right size.

After the offer

The person who was a candidate on Friday is a new starter on Monday, and needs to send you bank details, emergency contacts and signed documents. That is a different form with different sensitivity, and it should not be bolted onto the application. The sequence for collecting it cleanly is in client onboarding forms — same pattern, different audience.

Getting started

Build one form for your next role rather than a general careers form. Ten fields, three screening questions, one CV upload. Put it behind the "apply" button, route it to the hiring manager, and set a weekly slot for replies.

The measure of whether it worked is not how many applications arrive. It is how long it takes you to get from the closing date to a shortlist — that number usually halves, because the sorting already happened on the way in.

BotForms builds the form from a description of the role, handles CV uploads, and keeps applications in one dashboard with scoped access for the hiring manager. Starter is $29/month with 5 GB of storage, Pro $79 with 25 GB and three users, Business $199 with 100 GB and ten — all with a 30-day trial. See features, pricing, or start a trial.