Interaction Designer: Steve O'Connor
Content Designer: Lisa Matthews, Ivy Halstead-Dawber
Policy: Jen Halshaw, Tony Leavy
With the idea that the Task Service Index (TSI) would start to be used by people outside the core policy team, they requested an approval process be put in place to help manage and control the flow and quality of tasks. This process could also give more data around tasks such as how far ahead are they created, how long tasks stay live, etc. that could be very useful in forming future policy or reshaping the landscape and timeline of services.
Things we know about a service task within the TSI:
- when entered in the system it will be in draft form
- it needs the approval of that service's Deputy Director (DD)
- the policy team will need to approve of the final version
- it could go live on DfE Connect immediately it is approved
- it might go live at a specified later date
- tasks will need to be removed at some point after completion date
A rough prototype of the flow was created in Figma, and the the possible statuses were discussed. The approved statuses were:
- Draft - Added to TSI, no approvals
- DD approved - Approved by Deputy Director
- Queued - Approved by TSI policy team, task is not yet live due to a later publish date
- Published - Task is published to the live TSI i.e. viewable for SBPs in external service
- Inactive - Task is no longer active but is still in the TSI - past date of completion for instance
- Decommissioned - Task has been decommissioned by TSI team and is no longer available.
The current status would be displayed on the task listing in TSI and also on the task details page. On the details page it can be changed to reflect it's current status and move it through the system.
With the statuses in place and the mechanism for changing it, we plotted out the flows between statuses so that we could build the correct options into the screens.
The complete approval process and task lifecycle can be viewed in the Figma file.
