When entering a new application our customer enters their clients name, dob, and license details. The system then checks if the client already exists. If they exist the rest of the their details are returned and populate the remaining fields on the application.
We need a way to force our customer to verify with their client that each field hasn't changed, such as addresses, phone numbers etc without them just clicking "Next, next, next" and using the details which are already in the system. This is because they can be lazy and it is critical that all details have been verify and are current.
The application has over 80 fields and is split up over multiple pages. We are trying to encourage our customers to take care when creating an application. We are looking for a compromise between filling out everything again and using existing details without verification.
The user entering the details is our customer. They are entering THEIR customers details. Our customer has a habit of be lazy when one of THEIR customers already exists in our system. To prevent this we're currently forcing them to re-enter all details again (not pre populating anything). This is tedious and creates duplicate data.
The other extreme is to pre populate every field with THEIR customers existing details. This would allow them to continue being lazy and "forget" to check if THEIR customer's details have changed since last entered (e.g. moved house, changed phones etc).
We are seeking a solution in the middle somewhere. Some action by our customer to indicate they've checked if a certain field has changed (by asking THEIR customer) and if it hasn't tick a box or click an icon. The issue is where to strick this balance? By subsection? By field? How and what to indicate no change?