How Robin AI handles uncertainty with N/A answers

Introduction

When creating Tables in Robin, you can assign different Answer Formats for each topic, such as options, values, dates etc. These formats provide more concise answer types that ensure faster review and greater ability to receive structured data.

When using these more concise answer types, you may occasionally see "N/A" responses in your report.

‍

What "N/A" means

For more structured answer types, "N/A" indicates Robin couldn't find the requested information in your contract. This serves as standardized shorthand for:

• When the relevant information isn't found in the contract; or
• The answer to your question does not neatly fit within the formatting constraints you’ve given the AI; or
• Robin isn’t certain it can provide an accurate answer.

With longer "Summary" answer types, Robin instead uses plain language to explain why information couldn't be found, as these formats allow for more detailed explanations.

‍

N/A in practice

Imagine you've asked for a numerical answer for liability caps in a supplier agreement. However, this contract does not actually contain any liability language. After analyzing the contract, Robin responds with "N/A."

This response means the supplier agreement doesn't contain liability provisions. Rather than speculating or providing an ambiguous answer (such as 0), Robin has clearly communicated the absence.

‍

Why it matters

This approach reflects a fundamental principle for using AI in legal: effective systems must have appropriate ways to handle uncertainty and absence of information. Legal professionals should be cautious of systems that always provide definitive answers, as these may generate misleading information when faced with ambiguity.

Trustworthy legal AI recognize boundaries, communicate clearly when they cannot find requested information, and enable ‘human in the loop’ workflows to ensure accuracy. Transparency around limitations walks hand-in-hand with capabilities and performance.

‍