Conditional Logic Web Forms: Hidden Fields, Blank Cells and Testing Load
The real work in a conditional form is not hiding and showing questions but writing down three decisions first: is an answer typed into a field that later gets hidden deleted on submission, does a blank cell in your report separate “not asked” from “left blank”, and will every path each new condition creates be tested? Google Forms and Microsoft Forms jump to the next section or question based on a single answer; with few paths and one deciding question, that is enough. When a condition depends on a combination of answers, a field is required only under a condition and the response feeds a priority decision, an application that applies those decisions together with the record earns its keep.
This page is for operations managers designing service request, quote request or application forms. I cover single-field rules (type, range, duplicates) on the rules-based data entry form page; here the subject is questions shown or skipped by answer.
The three kinds of conditional logic
Conditional logic does three different jobs, and each leaves a different trace in the record:
- Show / hide: a field on the same page opens or closes depending on an earlier answer. Answer Yes to “Has the machine stopped?” and “Downtime start” appears. Risk: what happens to a value already typed in when the field closes.
- Skip to section: the answer decides which group of questions comes next; the skipped section is never seen. Selecting “Spare part” goes straight to the parts section. Risk: one wrong first answer sends the person down a wrong path.
- Conditionally required: a field is visible but required only for a specific answer. “Under warranty” makes serial number and invoice date required. Risk: a badly set condition creates a form nobody can finish.
Condition map: draw the table before building the form
A condition map records in one table who sees each question, who must answer it and what happens to its data if hidden. Without it, contradictions surface with the first complaint, not in the meeting. The redrawn map for the example company:
| Question | Who sees it | Required | If hidden (data / report) |
|---|---|---|---|
| Request type | Everyone | Yes | — |
| Has the machine stopped? | Fault, maintenance, spare part | Yes | Deleted / Not asked |
| Downtime start | Stopped = Yes | Yes, “Don’t know” allowed | Deleted / Not asked |
| Under warranty? | Fault, spare part | Yes | Deleted / Not asked |
| Serial no, invoice date | Warranty = Yes | Yes | Deleted / Not asked |
Deleted: removed on the server at submission. Not asked: the report shows this state, not a blank cell.
I check three things on the map. Does the customer know the answer to the routing question for certain? “Request type” often not; “is the machine stopped right now” yes. Does a field depend on two conditions combined? Then an off-the-shelf tool needs separate sections. Is there a path that never reaches a required field? Then the form cannot be submitted on that path.
Example: one month of a service request form, 412 responses
The company below and every number are fictional; the figures were calculated and checked with a Python script.
A machine service company takes service requests through a website form that branches by hiding and showing fields; every response lands as a row in a table. “Has the machine stopped?” is asked only on the Fault branch, “Downtime start” only on the Fault + Yes path, and it is optional. One month brings 412 responses: 236 faults, 98 scheduled maintenance, 61 spare parts, 17 installations. In 141 faults the machine had stopped.
Reading the month row by row, the planner finds:
| problem | rows | cause | result |
|---|---|---|---|
| Wrong branch | 23 | Description text shows machines had stopped, but 14 chose maintenance and 9 spare part | Downtime never asked, not flagged urgent |
| Hidden-branch data | 11 | Fault + Yes and a downtime start entered, then type changed (7 spare part, 4 maintenance) | The old “Yes” and downtime start stayed in the record |
| Not asked / blank confusion | 38 | Downtime start asked and left blank | Invisible among 298 blank cells |
The downtime report counts “Has the machine stopped = Yes” rows and shows 152. The real number of stopped machines is 164: 141 faults plus 23 requests where the question was never asked. The report has 11 too many and 23 too few; the net gap is only 12, so nobody notices either error.
In the redrawn map, the downtime question is also asked on the maintenance and spare part branches. Replaying the month, all 23 requests would be flagged urgent, provided the customer answers truthfully. Hidden fields are deleted on submission, so the 11 stale rows never enter the record. Downtime start becomes required with a “Don’t know” option; I cannot say how many would pick it, but none would appear as a blank cell.
Is an answer typed into a hidden field saved?
Whether it is saved depends on how the form is built; hiding a field on screen does not delete its value. The example’s website form made the field invisible without removing it from the submission, which is how 11 rows were contaminated.
The rule I recommend:
- Only fields on the final path are saved. Before writing the record, the server deletes the value of every field not visible under the final answers.
- A draft may keep it. While filling in, the value can be held so it reappears on switching back, but it never reaches the record.
- The person is told. Changing the request type shows a one-line notice of which answers will be removed.
- The server checks again. Hiding in the browser is a convenience; someone sending the request by hand can fill a hidden field, so the condition map is reapplied on save.
Blank cells: not asked, or not answered?
A blank cell can mean the question was never asked, or it was asked and left blank. In the example, Downtime start has 298 blank cells: 260 not asked, 38 left blank. A report treating blanks as “missing” sees 298 gaps; one treating them as “not asked” never sees the real 38.
If you are staying with the spreadsheet, a check column separates them. With B request type, C has the machine stopped and D downtime start, this Excel formula in E2, filled down, rebuilds from the condition map the path on which D is asked:
=IF(AND(B2="Fault",C2="Yes"),IF(D2="","Left blank","Answered"),IF(D2="","Not asked","Hidden-branch data"))
On the 412 rows it gives 103 “Answered”, 38 “Left blank”, 260 “Not asked” and 11 “Hidden-branch data”. Warnings: a single-space cell counts as “Answered”, and a stale “Yes” in column C needs its own column built the same way (type not Fault and C filled means hidden-branch data). The formula is updated by hand when a branch is added; forget it and the column miscounts silently.
In the application to be built, the distinction can live in the record: each field carries a state of “answered”, “left blank”, “not asked” or “don’t know”.
Every condition adds paths to test
A request type with k yes/no conditions has 2^k paths; the form’s total is the sum across types. The example’s existing form had 7 paths (4 for faults, one for each other type). Adding the downtime question to two more types and the warranty question to spare parts raised it to 11.
My test plan for the example has 38 runs: one complete and one required-field-blank submission per path (22), switching between the four request types (12), and switching both ways on the two yes/no questions (4). The switching tests are what would catch the 11 contaminated rows; a happy-path-only plan never shows them.
One more condition (“is remote access allowed?”) makes 15 paths if asked only on faults, 21 if asked on the three types that get the downtime question. So for every new condition I first ask whether it changes a decision; if not, an unconditional optional field is cheaper.
Where Google Forms and Microsoft Forms branching stops
In Google Forms, routing uses Go to section based on answer in the question’s More menu; Google says it works only for multiple choice and dropdown questions, an answer can also lead straight to submission, and the next section can be chosen at the end of each section (Google: sections). Checkboxes are not on that list, so a multi-select answer does not route.
In Microsoft Forms, branching is added to a question or a section and only moves forward: Microsoft says you can branch only to a consecutive question, not a preceding one, and an answer can lead to the end of the form (Microsoft: branching logic).
Limits I draw from those pages (my inference; try them in your own form):
- Routing looks at one question’s answer. “Stopped and under warranty” needs intermediate sections, and sections grow with paths.
- In Google Forms, a single conditional question goes in its own section. Conditional requirement works the same way: the question is required, but only people routed there see it.
- Conditions only see answers inside the form. Checking another record, such as “is this serial number under warranty”, cannot be built in an off-the-shelf tool.
- In the response table, unasked and blank questions both appear as blank cells.
When does branching outgrow a ready-made tool?
If one question routes your form, there are no more than five paths (my suggested threshold) and responses do not set a priority or a price, stay with a ready-made form tool; I would not recommend commissioning an application. A check column fixes the blank-cell confusion, and a wrong branch is often fixed by changing the routing question (“is the machine stopped” instead of “request type”). If requests can already go through the request screen of an ERP or service system, use that fully first.
| Option | When | Limit |
|---|---|---|
| Ready-made form, skip to section | One routing question, a few paths | Combined conditions need extra sections; test data behaviour on switching back |
| Ready-made form + check column | The report counts blank cells | Formula updated by hand when the form changes |
| ERP or service system request screen | Requests already go there | Branching only as far as that system allows |
| Application to be built | Combined conditions, conditional requirements, priority decisions | Written scope, server, maintenance, testing on every change |
Conditions, records and reports in the application to be built
For a service request like the example, the condition map can live inside the application as one table that the screen, the server check on save and the report all read. It can be built to your needs; the scope is set in writing at the first step. What can be included:
- Deleting hidden fields on submission, keeping them in a draft, and showing which answers will be removed.
- Conditions on combinations of answers and conditional requirements; checking a serial number against the warranty record, if you hold one digitally.
- A “not asked / left blank / don’t know” state for every field, with reports counting by state.
- The form version recorded with each submission, so a map change does not reinterpret old records.
- Re-running every path and switching scenario before a map change goes live.
AI can only add a flag: a request described as “line stopped, production waiting” but typed as Scheduled maintenance can be shown to the planner as “type may not match”. A person decides type and priority.
The application runs on a virtual private server (VPS) that can be opened in your company’s name. The data is yours; export it to Excel or CSV whenever you want. For small and mid-sized teams there are no per-user licences; the cost is server and maintenance. The source code sits in a repository you can access, with run instructions, a dependency list and known limitations. How I work in general: custom web apps for your team.
The first consultation is paid. Bring your form’s questions and which answer opens what, and we start from the condition map; reach me through the contact page.
What I have not verified
- Whether, in Google Forms or Microsoft Forms, an answer in a skipped section is submitted after the person goes back and changes an earlier answer; I have not tested it, and the official pages do not say.
- Microsoft’s page does not explicitly list which question types can carry branching.
- I have not run the check-column formula in a real Excel file; its logic was tested in the Python script.
- I read the sources on 01.11.2026; tool behaviour can change with updates.
Frequently Asked Questions
Can our team change the conditions later?
Simple, frequently changing parts such as option lists can be edited from an authorised admin screen. Changing who sees a field or whether it is required alters the number of paths, so it is tested first and then released. I would not make every condition freely editable.
What happens to old responses when the form changes?
An old response is read under the rules of the version it was submitted with. A question that did not exist then counts as “not in that version”, not “left blank”; otherwise past months suddenly look incomplete in the report.
Can the same form hold internal fields the customer never sees?
Yes; visibility can depend on role as well as on answers. The customer sees the request questions, while the planner fills in priority and assigned technician on the same record. Internal fields are never part of the data the customer submits.
How do I work?
Work-hour packages
Tell me about your business and what you need on WhatsApp or by phone; we agree on a work block of somewhere between 5 and 40 hours and I start doing what is needed. What you get is not a calendar window — it is net working hours spent directly on your business. I can use 40 hours working three days straight, or deliberately spread it out and finish it over a year — whatever the work calls for. I do not spend my time estimating how long something will take, I spend it doing the work; every hour I spend leaves a lasting result in your business. We keep going for as long as you find it useful.
Why not monthly?
Does a 40-hour block mean one week?
On a fixed monthly fee both sides are watching the wrong thing: you watch a fixed cost, the other side watches how many more contracts like this they can line up. Working by the hour puts us both in front of the same thing — the real value of the work that got done. I know not having an upfront answer to "how much will this cost in total?" is the natural cost of this model. But instead of paying a fixed fee for months to a setup that is not producing results, you only pay for the qualified time spent on your work — and you see exactly where that time went, start to finish. That is why my clients keep coming back.
