Enhanced fact find: Additional support (vulnerability)

[david.mann]

Additional support requirements (vulnerability)

We support the capture of multiple vulnerability records for each client.  In order to help you use the enhanced fact find in front of a client (if you want to), we have avoided the use of the word “vulnerability”.

There is a single field for each individual within a client record, labelled “Is your client currently vulnerable?”.  This is designed to be a single source of information which you can use in your management reporting - making the report easy to build - or set via tasks within threads you may have set up.

This field contains three options: -

• Blank - this is the default and means that you have not assessed the client’s vulnerability yet
• Yes - the client is currently vulnerable
• This might mean that the client has a permanent vulnerability or has a temporary vulnerability which you can’t / haven’t yet confirmed has ended
• No - the client is not currently vulnerable
• They may have had vulnerabilities in the past but are not now vulnerable

We have intentionally chosen not to calculate / derive the “Is your client currently vulnerable?” indicator based on the data in the table.  To do that would mean we have to assume either the indicator or a table entry is always incorrect.   As vulnerability is so critical to get right, we rely on the Xplan user manually setting that indicator as a record of the latest outcome from an interaction with the client.

Field label	Field ID (e.g. Xmerge syntax)
Do you currently require any additional support?	is_client_vulnerable

The table view is populated from these fields:

Field label	Field ID (e.g. Xmerge syntax)
Record date	xpt_group_vulnerability_record_date
Has consent been given to record these details?	xpt_group_client_consent_vulnerable
Status	xpt_group_vulnerability_status
Type	xpt_group_vulnerable_reason_detail
Reasons why additional support required	xpt_group_client_vulnerability_note
Start date	Xpt_group_vulnerability_start_date
Permanence	Options:  Permanent Temporary
End date	Xpt_group_vulnerability_end_date Only shown for vulnerabilities recorded as “Temporary” in the “Permanence” field.
Additional support required	xpt_group_mitigation_for_vulnerability

Handling multiple vulnerabilities

Previously, it was possible to select multiple vulnerability reasons.  Now that we have a list, which supports multiple records, there is no need to record multiple reasons in one record.

It is now best practice to enter individual reasons for vulnerability - they can have different start / end dates and mitigating support arrangements.

If you view a vulnerability record which was recorded within the classic screens and has multiple types already selected, these will be shown as a multi-select field.  You can freely edit these as you need to.  If you decide to delete types so that only one is left selected, then the Type field will appear as a standard choice field when you next edit it.

If you have already selected a single reason for vulnerability in a record, you will only see a choice field allowing you to capture one type at a time.

Useful links

• Main article & video

• Key details
• Contact details
• Health & lifestyle
• Estate
• Dependants
• Goals
• Occupation details
• Income
• Expenses
• Assets
• Liabilities
• Pensions
• Annuities
• Retirement details
• Life insurance
• Health & general insurance
• Affordability
• Death, incapacity & retirement
• Capital Gains Tax
• Professional advisers
• Additional notes
• GDPR & marketing preferences