Posts
-
Selecting organisation level permissions by type
Grouping permissions by type instead of organisation to better handle validation errors
-
Displaying safeguarding information
The way we show sensitive material to users differs, depending on whether or not they have permission to view
-
Sorting by reject by default (RBD) date
Let users sort by RBD date
-
More context for providers
Help providers make sense of application form responses by showing them guidance to candidates
-
Notifications
Notify users when certain things happen and let users configure what notifications they receive
-
Reasons for rejection iteration 3
Combined some questions onto one page, added an additional question and improved content
-
Setting user permissions: context and user research
Users and organisations need to configure permissions to make decisions, see safeguarding information and set controls for other users. Here’s how we arrived at our designs
-
Reasons for rejection iteration 2
Helping providers give useful feedback to candidates who’ve been rejected
-
Setting up permissions (iteration 4)
Showing a confirmation page after agreeing to the data sharing agreement, not asking users to setup permissions when they both run and ratify their courses, explaining the consequences of inviting someone from outside the organisation and various other content improvements.
-
Setting up permissions (iteration 3)
Handling when the user belongs to multiple organisations and including clearer guidance for how permissions work.
-
Setting up permissions (iteration 2)
Helping users understand what it means to set up organisational permissions and what default access means. Plus a few other improvements.
-
Setting up permissions
Let providers set up permissions between themselves and their partner organisations
-
Making a decision iteration 2
Let users make offers to different training providers, courses, locations
-
Breaking apart the application page (sub navigation)
Help providers navigate the parts of an application more easily with sub navigation
-
Improved header
Changes to the header and navigation layout
-
Reasons for rejection
Helping providers give useful feedback to candidates who have been rejected
-
Application layout changes
Various layout changes to make room for new features and improve existing ones
-
Giving teacher training providers longer to make decisions on applications because of coronavirus (COVID-19)
Communicating temporary changes to the decline by default and reject by default decision dates.
-
Process and rules for changing a course
Process that providers follow when changing a candidate’s course.
-
Card layout for application list
Use a card layout to fit more information inside each row without sacrificing readability and scannability.
-
Tracking conditions individually
Let providers track and update the status of offer conditions individually.
-
Timeline
Added a timeline component as a form of audit trail.
-
Improving check and confirm content
Improving the content for checking and confirming a provider workflow action.
-
Offer panel
New offer panel design to better accomodate various states and content.
-
Offer a different course
First iteration of making an offer to a different course.
-
Withdrawing an offer
Flow for withdrawing an offer.
-
Adding users
First iteration of letting users invite other users to their organisation(s) to help manage applications.
-
Marketing page for providers
A page selling the benefits of joining the Apply pilot.
-
Filtering applications
Let users find items a long list of applications by status and provider.
-
As launched on 26 November 2019
List applications, make offer or reject.
-
An interface for minimal service provision
Looking towards rolling out the pilot.
-
Make an offer
First pass at making a conditional or unconditional offer.
-
Application states
Create new states with filters.
-
New panels and application tables
Bring 2018 version inline with design system.
-
Fewer statuses
Trying a smaller set of statuses.
-
First designs for a minimum viable service
A minimum viable service that could allow the providers to access and manage their ITT applications.