after
integrated verification
My redesign moved all verifications to the field level within an integrated, data-backed checkbox (storing the verification datetime on save). This new data point allowed our imports to forcibly retain verified values, only accepting incoming data by forced overwrite or if a verification was not present.
even more...
ui enhancement
By setting a state-dependent style on each field when verified, the ui now highlights key data fields that had already been verified for any page user. This lets users to quickly scan the page and easily distinguish between reliable intel as well as fields that still need to be researched and/or verified.
demonstrating value
Demonstrating data verification to client recipients was equally important; one of our key (and most requested) deliverables is prospect data verification. This was easily achieved by applying a field level indicator on all client-facing prospect documents, reinforcing our product's value with each notification.
before
dangerous peripheral verification
Users were limited to a single dropdown to select fields they had verified, but not the fields themselves. When set, this dropdown selection was for reference only and set no integrity on the selected options or their related fields' values. This peripheral verfication method allowed all data fields to be overwritten by new, incoming prospect data when clients would provide new calling lists, so callers' research would be lost.