3.12 Input fields could benefit from validation (Observation)
3.12.1 Input fields could benefit from validation
Several input fields in the form allow unrealistic or invalid entries without raising an error. For example, in the Decisions section, the date entry field for “When was JohnTest’s mental capacity to make decisions last assessed by a professional (such as a psychiatrist or social worker)?” accepts dates far in the past or future without error.
Similarly, on the Edit Client Details page, the postcode and phone number fields accept any character sequence, including invalid formats. This lack of validation can lead to inaccurate or incomplete data being submitted, potentially impacting later processing and increasing the need for manual corrections.
Introducing validation would help guide users towards entering information in the expected format and catch mistakes before submission.
FIGURE 3.19: Date entry field on Decisions section
FIGURE 3.20: Postcode and phone number on Edit Client Details
3.12.2 Recommendation
Add client-side and server-side validation to ensure that entered data meets expected constraints:
- Dates should be realistic and fall within sensible ranges for the given context.
Postcodes should match the correct UK postcode format.
Phone numbers should allow only valid characters and lengths appropriate for UK numbers.
Where an input fails validation, provide clear, accessible error messages that explain the problem and how to fix it.
3.12.3 Resources
3.12.4 Spot Check: February 2026
This issue has not been addressed. Date fields still accept unrealistic values (such as dates in the distant past or future), and postcode and phone number fields continue to accept invalid formats without validation.
This remains an ‘Observation’.