...
Task | Status | Priority | Assigned | Description | Comments | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Progess bar |
| Agree metics for defining '% completion' | 💬 | ||||||||
Progess bar |
| Show workflow for when 'ready for sourcing' | 💬 | ||||||||
Progress bar |
| 1 - high | Hide from UI designs | 💬 | |||||||
Tool tips |
| Add/illustrate how tool tips work | |||||||||
Add applicants - summary |
| Show workflow and wfs on how a user would add an applicant from the fact find summary | |||||||||
Add applicants - fact find |
| Show workflow and wfs on how a user would add an applicant from the fact find applicants page. How does this impact other fact find pages which rely on the number of applicants | |||||||||
Define standing data for revised workflow |
| 3 - low | Understand requirements for the new UJ Asking general questions → Product → Fact Find → Amend Product if needed. | 💬 | |||||||
Left-aligned labels |
| Confirm this is the approved UI | 💬 | ||||||||
Fact Find catagories |
| 2 - med | Consider splitting Fact Find Pages into sections on the main nav. ie Core questions, residential mortgae questions, equity release questions | 💬 | |||||||
Section notes |
| Consider as part of the standing data a section for taking notes in each section | |||||||||
Ability to copy data across |
| consider where this adds value | 💬 | ||||||||
Standing data |
| 3 - low | Need to agree standing data set (templates) that come out of the box that follow this workflow: | 💬 | |||||||
Criteria search |
| 3 - low | Can we integrate with Knowledge bank for criteria search? | 💬 | |||||||
Affordability checks |
| 3 - low | can we integrate Brokersense (or other) for affordability checks? | 💬 | |||||||
Move 'Add Fact Find' |
| 3 - low | Currently the fact find sits in the product tab – should, as a quick fix, move this to the case summary tab? | 💬 | |||||||
Customer portal |
| 2 - med | This should be consistent with the new FF. Is this in scope ? | 💬 | |||||||
Multiple document upload |
| 2 - med | is there a requirement to upload documents in the broker Fact find? | 💬 | |||||||
Drag and drop |
| 2 - med | is there a requirement to upload documents in the broker Fact find? | 💬 | |||||||
User support |
| To help adoption of new UI and reduce support calls – should we include links in the new UI to help guides/byte size videos ? | |||||||||
Customer Vulnerability |
| Add vulnerability - yes/no. if yes, add comment box to allow broker to fill in details | |||||||||
Customer Vulnerability |
| Can we have an agreed set of criteria that should a customer meet that it autoflags in the system that they are vulnerable. This criteria can be customised by the broker firm | |||||||||
Customer Vulnerability |
| Flags could include visual indicators on customer profile. Warning pop banners when a user opens a case/factfind etc | |||||||||
Customer Vulnerability |
| 3 - low | This needs a lot of consideration. Guidelines are 'fluffy' 4 key areas. Health, financial etc. need to consider what comes out of the box | 💬 | |||||||
Customer Vulnerability |
| Add hover over interaction to the warning symbiol - informing detail of vulnerability | |||||||||
Customer Duty |
| 3 - low | Need to arrange education on Customer Duty and what it is. | 💬 | |||||||
CRM Brand customisation |
| 3 - low | Need to agree if this is a requirement or not | 💬 | |||||||
Custom Fields |
| 2 - med | Requirement to add multiple custom fields - Alan to confirm | ||||||||
Testing |
| 2 - med | Need to arrange customer testing of prototype | 💬 | |||||||
Testing |
| 2 - med | Agree metrics for success | 💬 | |||||||
Testing |
| 2 - med | Agree analytic tools for CRM | ||||||||
Applicant name |
| Applicant name | |||||||||
Budget Planner |
| include ONS Data integration | 💬 | ||||||||
Property purchase |
| add hometrack integration to property purchase UI | 💬 | ||||||||
Submit Fact Find |
| We need to reconsider CTAs labeling | 💬 | ||||||||
Submit Fact Find |
| Clear visual statement if the Fact find has been completed and by who (poss. Across header?) | |||||||||
AML and PEP checks |
| 3 - low | This is to be considered in the case UI workflow | 💬 | |||||||
Adding additional data |
| need to show how the UI will work when broker adds dependencies or adds additional liabilities | 💬 | ||||||||
Add promotional banner |
| Add promotion banner to the log in page | |||||||||
Super user menu |
| Add super user menu to the fact find summary page - includes 'change fact find' and 'view editable questions' toggle | |||||||||
Labelling of subsets |
| Main challenge is brokers dont use subsets. Is it an education? will better labelling help? | 💬 | ||||||||
Agree standard data set out of the box |
| 3 - low | Single set of qs that dynamically update fact find based on products selected. Inc all subsets | ||||||||
Dependants |
| Dont use full DOB component. Brokers use year of birth for minors to comply with GDPR | |||||||||
Hometrack |
| 3 - low | Broker suggested adding this to customer portal as well. | ||||||||
Autosave |
| 1 - high | Scenario - what if broker accidentally deletes some data (eg name, DOB). How do they recover it. | ||||||||
System messages |
| Add 'dont show me this again' feature to system messages on login screen | |||||||||
System messages |
| 1 - high | Add warning message panel to summary/fact find pages currently the warning panels dont stand out enough | 💬 | |||||||
New applicant |
| Need to agree on how do we add applicants from FF Summary, during filling FF, and how do we view/edit applicant details | 💬 | ||||||||
Products |
| Add ability to remove products | |||||||||
Fact Find name |
| Add ability to change FF name | |||||||||
Sources of income |
| Table with sources of income, and adding a source of income flow | |||||||||
Budget Planner |
| Add a postcode input field, so that a user can import the data from a specific area | |||||||||
Fact Find Structure |
| 1 - high | Can applicant data be stored against the applicant profile. Needs discovery/testing Speak to Alan | ||||||||
Lock Page feature |
| 1 - high | Brokers still need ability to 'lock' or mark a page as 'completed'. This needs reflecting on the pages menu | 💬 | |||||||
Unlinking applicants |
| Whats the workflow when you unlink/remove applicant | 💬 | ||||||||
Applicants treatment |
| 1 - high | What happens in the background when a broker adds an applicant during a FF Process? | 💬 | |||||||
System messages |
| Once we agree how linking/removing applicants work, we need to update system messages in warning modals | 💬 | ||||||||
Forms |
| 3 - low | Design all forms based on Auto Layout - as soon as we agree on label alignment | ||||||||
Design file |
| Clean the Design file and separate static designs pages from a prototype flow | |||||||||
Prototype |
| Prepare both FF Summary and Forms prototypes for the Interviews | |||||||||
Fact Find Summary |
| Validate if brokers need to see "Show all possible questions" filter | 💬 | ||||||||
Spelling |
| 1 - high | Check spelling of 'available' | ||||||||
Quick key commands |
| 3 - low | Can brokers use browser quick key commands such as ALT FIND to locate content ? Needs to be discussed with Alan to see if this doable | ||||||||
Accessibility |
| 2 - med | After wrapping up this stage, go through all designs again and make sure everything is accessible & colour contrast | 💬 | |||||||
Request Broker Fact Finds |
| 1 - high | Should we request copies of broker fact find so we can get an idea of the size/structure/questions? | ||||||||
Budget Planner calculations |
| 2 - med | Ability for brokers to add functionality to build simple calculation tools and provide sub totals for grouped data. Eg Add up all credit commitments and summerise the total commitment | ||||||||
Timestamped Notes |
| 1 - high | Some open fact finds could possibly be years old and contain misleading time sensitive comments. Customer asked if they could be timestamped. | 💬 | |||||||
Creating new applicants |
| 1 - high | When adding a new customer it should check the brokers customer database for matching so as to avoid creating duplicate records Change the workflow so that when adding/linking new applicant that the first step is to check if there is an existing applicant Include check point that when user ‘Adds applicant’ or ‘add more details’ to a new applicant the system checks and if there is a match then brings back model user wants to create new user or use existing with ability to see a summary view of existing applicant | ||||||||
Budget Planner ONS feed |
| 3 - low | add ability to copy ONS data to the submission fields | ||||||||
Budget Planner ONS feed |
| 3 - low | Include regional option | ||||||||
Multiple applicants |
| 1- high | Ability to change/choose main applicant | 💬 | |||||||
Multiple applicants |
| 1 - high | Make better use of real estate to fit two applicants. Improve labelling when scrolling multiple applicants | ||||||||
Multiple Applicants - source of income |
| 1 - high | Need to show how multiple applicants works of source of income table | ||||||||
Multiple Applicants - source of income |
| 1 - high | Need to show how multiple applicants works of budget planner table | ||||||||
Save and close fact find rule |
| 1 - high | Document rule that CTA returns iuser to where they opended the FF ie case view |
...