Registered Traveller – Service Assessment
...caseworking tool’s code open, or provide a very strong justification why specific areas should not be. The Registered Traveller service needs to ensure it has the analytical tools and user...
...caseworking tool’s code open, or provide a very strong justification why specific areas should not be. The Registered Traveller service needs to ensure it has the analytical tools and user...
...arrangements needed to support continuous deployment must come to fruition. It is essential that the team which owns the service is able to deploy code rapidly in response to user...
...the system being replaced does not currently collect user data via an analytics tool and there is also no analytics data collection within the new service. Collecting and analysing data...
...12 Yes 13 No 14 No 15 Yes 16 Yes 17 Yes 18 Yes 19 Yes 20 Yes 21 Yes 22 Yes 23 Yes 24 Yes 25 Yes 26 Yes...
...team: work to publish the service’s code openly as soon as possible take action on GDS’s design recommendations made for both ‘View Driving Record’ and ‘Share Driving Record’ (to be...
...9 No 10 Yes 11 No 12 Yes 13 No 14 Yes 15 No 16 Yes 17 Yes 18 No 19 No 20 No 21 No 22 No 23 No...
...co-located with ACU during development. Oversight by Foreign and Commonwealth Office (FCO) Digital Transformation Unit (DTU). Development team were not present at user testing, instead having results relayed to them....
...to the user’s passage through border controls at the enrolment stage (instead of requiring a much longer interview) and that there is no longer a reliance on email We recommend...
...No 16 Yes 17 Yes 18 Yes 19 Yes 20 Yes 21 Yes 22 Yes 23 No 24 Yes 25 Yes 26 No Details of criteria that are not applicable...
...surveying those who had successfully booked appointments. For internal users, this has included separate surveys of posts currently using Clickbook and of those not using the service. In addition the...