From Jane (7 Oct 2026):<\/p>\n
\nNot Known doesn't do much. The "Answer it instead" is just sending people round in a circle to ask the same question again. If there are fields where we need to keep track of unknowns we should record it that way. I think getting rid of it is best. Leaving a field blank means they don't know. However, if it's a required field we need to know what to do.<\/p>\n<\/blockquote>\n
Where it is<\/strong><\/p>\n
\n
- The "Not known" link and the "Answer it instead" link under a question:
pages\/visit-v2.php<\/code> (around line 904\u2013919).<\/li>\n- Offered only where a question has
allow_unknown<\/code>; recorded as anunknown<\/code> answer:code\/form_v2_visit_rules.inc.php<\/code> (around lines 343 and 656\u2013666).<\/li>\n<\/ul>\nProposed<\/strong><\/p>\n
\n
- Remove "Not known" from the visit screen. Blank means not known.<\/li>\n
- Keep an explicit "not known" only on the specific questions where the customer needs to track it, as a real answer choice on that question.<\/li>\n<\/ul>\n
To decide<\/strong><\/p>\n
\n
- A required question left blank: block finishing the visit, or allow a reason ("does not apply" already exists)? Which questions, if any, genuinely need "not known" recorded?<\/li>\n<\/ul>\n"}