FG26/4 · Field logic
Required does not mean “free text accepted”
FG26/4 contains Required fields that also prescribe dropdown values or additional handling rules. Structural validation therefore has to check both presence and whether the value is represented in the expected form.
Presence and validity are different checks
A field can be populated and still fail structurally because the value does not match the accepted controlled set, or because the selected answer triggers another dependency that has not been completed.
Keep triggered dependencies explicit
Where an answer changes what information is required next, treat that dependency as a deterministic rule rather than a manual memory aid. This is where spreadsheet-only workflows often drift.
Do not normalise unsupported values silently
If the source uses a term that does not map cleanly to an accepted value, surface the mismatch for remediation rather than coercing it without evidence.