Treat “not applicable” as a valid process outcome, not an empty answer. Determine applicability before calculating progress and record why a question or entire form does not apply to a file. This prevents unjustified reminders and distorted reports.
An empty field may mean someone has not started, skipped an answer, lacks information or should never have seen the question. Treating all these situations as “incomplete” directs the team to the wrong files.
Choose the right level of exclusion
An entire subject may not apply, such as a financing step for a service already paid for. Sometimes only one question does not apply, such as a follow-up for clients without a selected option. Use the smallest stable exclusion: category, form or question.
Yindle Portal can activate categories per file and exclude individual questions. Progress calculations treat a form whose questions are all excluded as not applicable. That differs from a started form with one unanswered mandatory question.
Let the source determine the decision
For each exclusion rule, record which data determines it. Is it contract type, selected service, property type or a previous option? Decide who may change that source data and what then happens to existing answers. Avoid manual exclusions without a reason; they cannot be explained later.
A conditional question may disappear during completion when its condition changes. Check whether a previous answer is ignored, deleted or retained visibly. Hidden input must not continue influencing a calculation unnoticed.
Worked example: fictional leasing provider
Fictional provider RijHelder guides business drivers through vehicle delivery. Only drivers choosing home charging receive questions about parking and the meter cupboard. The “charging facilities” subject does not apply to office chargers. An excavation question appears only after the choice “charging point in the garden”.
RijHelder bases the first exclusion on the chosen charging location. If a driver changes that choice, the subject appears with an explanation as a new task. Previous progress is reassessed. An empty field therefore does not automatically mean the driver is behind.
Use an applicability table
| Component | Rule | Source | Change after entry |
|---|---|---|---|
| Charging facilities | Home charging only | Selected location | Open a new task |
| Excavation | Garden installation only | Answer in the form | Ignore the old answer and show it in the history |
| Business invoice | Only when the employer pays | Contract type | Administrator check required |
Add how clients see the decision to the table. Sometimes showing nothing is clearest. For an important part of the process, “not needed for your file” may provide reassurance.
Test transitions, exports and reminders
Create tests for applicable to not applicable and vice versa. Check that reports use the correct denominator, exports explicitly show the status, and reminder selections skip excluded files. Also test a client with two files governed by different rules.
Watch forms that have already been submitted. A later rule change must not rewrite a historical submission as though the new logic had always applied. Retain the original context or deliberately start a new version.
Make it clear to support why a section does not apply, but share only the explanation the employee needs. An internal source code such as “CT-04” does not help the customer. The customer view might say “This section is not part of your chosen package”, while administrators see the specific source and decision date.
A difficult edge case arises when two rules conflict. Contract type says a form applies, while an earlier choice excludes it. Define a fixed priority and block impossible combinations during entry. Do not make portal administrators guess on the spot which rule takes precedence.
Check notifications and dashboards after every change too. An exclusion that reaches only the form page, but not the open-action counter, still shows the customer a task they cannot complete. Where technically possible, use the same applicability function as the source for every view.
For analysis, you can track the proportion marked not applicable per section. Use that signal to improve the setup, not as a performance measure. If ninety per cent of files exclude a question, a separate route may be clearer than a general list full of exceptions.
Read more about file structure in the guide building a customer portal and see Yindle Portal. To develop applicability rules, review three unusual files with Yindle.