Test attributes in Analyzer in Sign

Last updated on Aug 17, 2026

Test an attribute against real documents before you rely on it across a larger document set.

Testing helps you identify inconsistent results, unexpected matches, and missing values. Use the results to refine the attribute definition and examples before applying the attribute more broadly.

Before you begin

Make sure:

  • You can view and edit attributes.
  • The attribute already exists.
  • You have access to documents that are expected to contain the value.
  • You select no more than 10 documents for each test.

Test an attribute

Open Attributes.

Select the attribute you want to test.

The attribute definition opens automatically.

Select Test.

Attribute definition showing the control used to start testing.
Testing lets you evaluate a definition on a small document set before applying it more broadly.

Select two or more documents to test, up to a maximum of 10.

  • All files is selected by default as the source list.
  • Use the collection selector to narrow the list to a specific collection.

Pick up to 10 files and select Add files.

Analyzer runs the extraction and displays the evaluation results.

Attribute test document selector showing All files, a collection filter, search, and selected documents.
Starting from All files lets you test against any accessible document while the collection selector can narrow the sample set.

Review test results

The results table shows each selected document with:

  • {Attribute name} — The extracted value.
  • Attribution Content — Source content supporting the result.
  • Explanation — The assumptions and conditions Analyzer used when determining the value.
  • User feedback — Feedback you have provided during evaluation.

Hover over a file and select Review to inspect the complete extracted outputs.

Attribute evaluation results showing extracted values, attribution content, explanation, user feedback, and the Review action.
Reviewing extraction details together helps reveal whether a problem comes from the result itself, its supporting source, or how Analyzer interpreted the definition.

Review a result in context

Select Review to inspect a result against the source document.

The review view shows:

  • The source document with the extracted location highlighted.
  • The complete extracted value.
  • Attribution Content.
  • Explanation.
  • Feedback controls for marking the result correct or incorrect.

Use the navigation controls next to the document name to move through the selected test documents.

Document review showing highlighted source content beside the extracted value, explanation, attribution, and feedback controls.
Reviewing the highlighted source alongside the explanation helps you decide whether the definition or the extracted result needs adjustment.

Excel and CSV files

Excel and CSV files cannot be previewed directly in Analyzer.

When testing against these file types, download the extracted results and attribution data to compare them with the source file.

Provide feedback

Mark each result as correct or incorrect.

When you mark a value as incorrect, provide examples that clarify what Analyzer should include or exclude.

Use examples that are:

  • Specific.
  • Taken directly from representative source content.
  • Focused on the pattern you want Analyzer to recognize or avoid.

Analyzer adds the inclusion and exclusion examples you provide to Advanced options in the attribute definition.

Attribute feedback panel with fields for inclusion and exclusion examples after a result is marked incorrect.
Feedback can update the attribute definition directly by turning reviewed examples into reusable extraction guidance.

Refine and retest the attribute

Review the feedback and examples added during testing.

If the examples accurately describe the intended result, select Retest to evaluate the updated definition against the same documents.

If you marked results correct or incorrect without adding examples, the attribute definition does not change and retesting produces the same behavior.

When examples alone are not enough, edit the Detailed attribute description and retest.

Review the Explanation values when results are unexpected. They can help identify how Analyzer interpreted the definition and where additional clarification may be needed.

Use Advanced options when needed

Use Advanced options when the main definition does not provide enough guidance.

You can add:

  • Inclusion examples to show values that should be extracted.
  • Exclusion examples to show values that should not be extracted.

Use one to five examples when possible. Too many examples can make the attribute overly specific.

Know when to refine or recreate an attribute

Refine an attribute when you see:

  • Missing values that should have been found.
  • Results that are broader than expected.
  • Incorrect values that resemble the intended concept.
  • Inconsistent results across similar documents.

If repeated refinement does not produce reliable results, consider recreating the attribute with:

  • A simpler definition.
  • A narrower scope.
  • Fresh examples.
  • A more appropriate value type.

Know when an attribute is ready

An attribute is ready for broader use when:

  • It consistently returns the expected value across representative documents.
  • Documents without the target information correctly return no value.
  • Output format matches the intended result.
  • Results remain stable after minor refinements.

After validating the attribute on a small sample, expand testing to a broader document set to identify remaining edge cases.