Short answer. A form that works is judged after the “Send” button. Six things must happen: the input is checked while typing, not afterwards; the sender receives an acknowledgement with a number; spam and duplicates are set aside; the submission becomes a request, not a spreadsheet row, with an owner and a status; the right person is notified; and you measure how many open the form, how many send it, how long before you answer. Before that, sort the fields: at the door, ask only what is needed to call back. A free tool is enough for a few submissions a week handled by one person; beyond that, it is an application.
This guide is for the manager who receives enrolments, quote requests, applications or complaints through a form: a school, a training centre, a workshop, an agency, a clinic, an association. And for the founder based in France whose requests arrive from Algeria while they sleep. The definitions and recommendations quoted come from public sources: the web form, data validation, the CAPTCHA and its limits, the Post/Redirect/Get pattern, the E.164 standard for phone numbers, the W3C tutorials on forms. The workshop, its eight submissions and its rates are a constructed example. This guide does not cover the legal rules on personal data: see your legal adviser.
The same week, in a spreadsheet then as tracked requests
The figure shows eight submissions in a week, in a spreadsheet then handled as requests.
What it is. A web form allows a user to enter data that is sent to a server for processing. Everything is in the last word: processing, by whom, and when? A tool such as Google Forms, survey software included in Google's free office suite, can pour the answers into a spreadsheet that updates as new responses are received. It is convenient, and that is where requests get lost: a row has no owner, no status and no time limit.
Four accidents. In the example, out of eight rows: a duplicate, because the sender clicked twice; a spam message, arriving at three in the morning; a request with no answer for six days; a request two colleagues replied to, each on their own. None is flagged by the spreadsheet. The same form, a different arrival. The page can stay the same: what changes is that each submission becomes a numbered request, entrusted to someone.
«A row has no owner, no status and no time limit.»
After “Send”, six steps
The accented step is the fourth: create a request, not a row.
Check. Data validation consists in making sure a piece of data is correct and useful before accepting it. The W3C recommends validating user input to help users avoid mistakes, and being as accommodating as possible of different forms of input for the same data: a form is easier to use if it can interpret multiple notations. Confirm. Again according to the W3C, give users feedback about the result of their submission, whether successful or not; a success message confirms that the task is complete. A request number, displayed and sent by message, spares the call “did you receive it?”.
Filter. Spambots search the internet for web forms in which to submit fake content. They are set aside without punishing the sender: an invisible field only a bot fills in, a minimum delay between opening and sending, a limit per address. The CAPTCHA, the test that asks you to prove you are human, has a cost: those based on reading text shut the door on blind or visually impaired users. Duplicates. Reloading the page after sending can resubmit the same content; the Post/Redirect/Get pattern exists so that the page shown after a submission can be reloaded without ill effects. Create, notify, track. The submission becomes a request; its owner receives an alert, through the channels described in the guide to notifications; and the request keeps a status until the answer.
A form that works, in five layers
The accented layer is handling: it is the one the spreadsheet lacks.
Labels. Each field has a visible label: the W3C asks for labels to identify all form controls, including text fields, checkboxes, radio buttons and drop-down menus. A field whose caption disappears as soon as you type forces people to guess. Two languages, one phone. The form is filled in on a phone, in French or in Arabic: wide fields, the right keyboard for a number, and no fifty-line menu.
The phone number. It is the field that matters, and the one that too often refuses the numbers of senders living abroad, when it accepts only one format. The E.164 standard defines the numbering plan of the worldwide telephone network; a conforming number has only digits, fifteen at most. So the form accepts 0550…, +213… or +33…, and stores the number in a single form. Attachments. A photo taken on a phone is heavy: it is reduced on sending, and the upload resumes if it is cut, as explained in the guide to photos in an application.
Twelve fields, or five
The figure sorts twelve fields: five stay, seven are struck out.
The sort. For each field, one question: is it needed to call this person back? In the example, three fields were of use to nobody, and four are better asked in the first exchange, when the person already has an answer in front of them. Five remain: who, how to reach them, what, where, and an optional file. The figures. In the example, 41 people out of 100 went to the end of twelve fields, 63 to the end of five. These are constructed figures: yours are measured, by counting those who open the form and those who send it.
What is not removed. The free field, “your need in one sentence”, is worth more than ten tick boxes: the sender says what they want in their own words. Forms that book. If the form allocates a place, a slot or limited stock, it is no longer a form: two people can take the last place at the same time. That case is covered in the guide to online booking. Internal requests, purchases, breakdowns, access, follow the same logic, described in the guide to the intranet.
«Each field is a question put to a stranger.»
Free tool or application: six questions
The figure gives six questions for choosing.
When the free tool is enough. A few submissions a week, a single person handling them, one reply and that is it: keep the tool, and add two habits to it, a confirmation message and one person who opens the spreadsheet every morning. When it no longer is. As soon as several people handle them, a request goes through steps, documents must be checked and kept, or the sender wants to know where things stand: it is then a tracking area, described in the guide to the customer area.
The data. If the request must end up in your software, for management, schooling or invoicing, retyping it by hand recreates the errors the form was meant to avoid. The connection, with or without a programming interface, is described in the guide to integrating existing software. Where the answers live. With a free tool, they live in the account of whoever created the form: check that this account is the company's, not an employee's.
Four weeks, from sorting the fields to measuring, in 2027
Four weeks in the example, the first one to sort the fields.
- What the manager receives: a short form in two languages, checks while typing, a numbered acknowledgement, spam and duplicates set aside, each submission turned into a request with an owner, and three figures every week.
- What the company no longer does: open a spreadsheet to guess what has been handled, have two people reply to the same request, forget a request for six days, hear “did you receive my form?”.
- What is measured: opens, submissions, share of those who go to the end, time to first reply, requests without an owner.
- What Symloop does: sorting the fields, the form and its checks, protection, the acknowledgement, the turning into tracked requests, the connection to your software, then the measurement.
Week 1, the sort: what is asked at the door, what is asked later, and who receives what. Week 2, the form and its checks: labels, formats, attachments, two languages, tested on several phones. Weeks 2 and 3, protection and the acknowledgement.
Weeks 3 and 4, requests and alerts: each submission becomes a request, with an owner and a status. Week 4, measuring: opens, submissions, time to first reply, and the field where people give up. Three figures are then reread every week; the first to look at is the time to first reply, because it is the one the sender feels.
- How do you make an online form?
- By starting with sorting the fields: only what is needed to call the person back. Then by taking care of what follows the submission: input checked while typing, a numbered acknowledgement, spam and duplicates set aside, and each submission turned into a request with an owner and a status.
- How do you make an online enrolment form?
- Like any form, with two extra cares: an immediate confirmation carrying a number, and, if places are limited, a mechanism that stops two people taking the last one at the same time. The documents requested are uploaded from the phone, with their status: received, missing, to redo.
- Is a free form enough?
- Yes, for a few submissions a week handled by a single person, provided you add a confirmation message and open the spreadsheet every morning. As soon as several people handle them, or there are steps or documents to keep, an application is needed.
- How many fields are needed?
- As few as possible: what is needed to call back and understand the need. In this guide's example, five fields out of twelve were enough. The rest is asked in the first exchange. Measure at your place the share of those who go to the end before and after the sort.
- How do you avoid spam without a CAPTCHA?
- With means invisible to the sender: a hidden field only a bot fills in, a minimum delay between opening and sending, a limit on submissions per address. A test to solve remains possible as a last resort, knowing that it also turns away real people.
- How do you avoid duplicates?
- By preventing a double send on click, by redirecting to a confirmation page that can be reloaded without resending anything, and by recognising two identical submissions from the same number within a short time: they are merged into a single request.
- How do you know whether someone replied to a request?
- By giving each request an owner and a status: received, in progress, answered. The time since receipt is shown beside it. That is what a spreadsheet lacks, where a row says neither who is dealing with it nor how long it has been waiting.
- Does the form work on a phone and in Arabic?
- It must: that is where it will be filled in. Wide fields, labels always visible, the numeric keyboard for the phone number, and both languages with the correct writing direction. It is tested on several phones before opening.
- Can photos or documents be attached?
- Yes. The photo is reduced before sending, the upload resumes if it is cut, and the format and size are checked while typing, with a clear message if the file does not go through.
- How long does it take, and where do we start?
- Four weeks in this guide's example. Start with sorting the fields and with one question: who receives the submission, and within what time must they reply? The form is built around that answer.