When using document matching with fuzzy text matching or the threshold feature enabled, the returned values are highlighted in the same blue color as standard text snips. This can be confusing to users since these settings allow for slight variations, such as small misspellings or rounding differences, which wouldn’t match exactly without these features enabled. To improve clarity and transparency, we should differentiate these values by shading them in a different color, making it clear to users that these results were influenced by the specific parameters they set. For example, if a threshold of $1 is set, and the input is $3, a returned value of $3.12 should be highlighted in a different color to indicate it's within the allowed threshold.

The problem: It is difficult at a glance to understand which document matching snips are exact vs fuzzy text/threshold. In all cases it is shown as a blue and there is no indication that the match differs. This can lead to confirmation bias because there is a combination of exact and non-exact matches. In these cases people may not review the output correctly.

In addition to the visibility issue there is also the challenge that if a Document Matching template is created including Fuzzy Text/Threshold the end user may not be aware that the template incudes this and this could lead to confusion.

User type: Both prepares and reviews are affected by this in their workflows.

Workaround: A validation column can be added to your sheet to compare the sample data to the snipped data and highlight where this differs. Excel has fuzzy text matching so in this case users already have access to this functionality and should be aware of the how to mitigate the risk when using this kind of functionality.