---
title: "Field consistently goes to Supervision even though text is legible"
slug: "field-consistently-goes-to-supervision-even-though-text-is-legible"
updated: 2024-09-24T07:52:00Z
published: 2024-09-24T07:52:00Z
canonical: "help.hyperscience.ai/field-consistently-goes-to-supervision-even-though-text-is-legible"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Field consistently goes to Supervision even though text is legible

## Issue

Text in a document is clearly written and easily identifiable, but the field is consistently sent to Transcription Supervision.

## Affected versions

All versions

## Affected configurations

All configurations

## Cause

Field properties likely need adjusting. Inclusion of additional or unneeded information can negatively affect the system’s confidence for a field, causing it to send the fields to Supervision for verification from a keyer.

Common causes include:

- Fields drawn during layout creation contain table borders or lines drawn on the form.

![FieldsContainLines.png](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/fieldscontainlines.png)
- Fields drawn during layout creation contain unnecessary/avoidable text printed on the form.

![FieldsContainSurroundingText.png](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/fieldscontainsurroundingtext.png)
- Field has text on the form which is unavoidable, but **Dropout** is not enabled.

![FieldsDontHaveDropoutEnabled.png](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/fieldsdonthavedropoutenabled.png)

## Solution / Workaround

Modify the field to look for text specifically where you would expect to see writing. Note that a character that goes below the bottom line, such as *g*, *j*, *y*, *p*, *q*, and others, will still be recognized even if part of the character is outside of the box.

It is easiest to ensure you’ve drawn the field correctly by zooming in as far as you can on the document when creating the fields in the Layout Editor.

Using the example field above, since we only expect people to be writing on the line shown, you can draw the field so that it includes the space above the line, not the line itself.

![FieldsDontContainLines.png](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/fieldsdontcontainlines.png)Conversely, if you are drawing a box for a field that contains text within the space where you would expect writing, you should still draw your bounding box within any lines as stated. However, you should also enable the **Dropout** option for the field, which would cause the application to ignore the pre-printed text on the form.

![FieldsContainSurroundingTextDroputEnabled.png](https://cdn.us.document360.io/87894cef-4958-4f3f-be6f-b75a78c82548/Images/Documentation/fieldscontainsurroundingtextdroputenabled.png)