The Request
Hey there! It may be valuable to implement a service applicability pattern in the future, like the UK Gov's Check a Service is Suitable. This pattern is incredibly common across the UK Gov but has not yet made its way to BC.
Implementing it would result in fewer ineligible applications for services and a reduction in email/phone questions regarding eligibility. I'm not sure about the demand for this kind of pattern in BC gov as it's not yet commonplace, but could provide all kinds of value if (or when!) it starts being adopted.
The Implications
This is a relatively complicated pattern from a design standpoint. It is up to each service provider to ask the right questions - in addition, how the pattern communicates the users' eligibility status can make a difference in how users interpret the results. To combat this, the UK Gov team created some guidance on the wording they've found to be successful.
Overall, this pattern will need to come with clear guidance on how to use it effectively, with perhaps a well-thought out example.
Additional Reference Material
More guidance on how to implement and approach this pattern can be found on the UK Gov's blog.
Thanks for the idea! Sounds like a potentially very valuable pattern for services to reduce round-trip communication and potentially even increase service uptake.
What we'd need to explore here would be:
potential interest or opportunity for stakeholders to adopt the pattern
--> (please invite people to comment or provide input here, if you sense interest/curiosity!)
scope for how the toolkit might provide either new or existing building blocks to simplify for those interested in adopting the pattern.
The Request Hey there! It may be valuable to implement a service applicability pattern in the future, like the UK Gov's Check a Service is Suitable. This pattern is incredibly common across the UK Gov but has not yet made its way to BC.
Implementing it would result in fewer ineligible applications for services and a reduction in email/phone questions regarding eligibility. I'm not sure about the demand for this kind of pattern in BC gov as it's not yet commonplace, but could provide all kinds of value if (or when!) it starts being adopted.
The Implications This is a relatively complicated pattern from a design standpoint. It is up to each service provider to ask the right questions - in addition, how the pattern communicates the users' eligibility status can make a difference in how users interpret the results. To combat this, the UK Gov team created some guidance on the wording they've found to be successful.
Overall, this pattern will need to come with clear guidance on how to use it effectively, with perhaps a well-thought out example.
Additional Reference Material More guidance on how to implement and approach this pattern can be found on the UK Gov's blog.