Check Input Reference

Gap Examples

Examples of controlled Check Input findings using the [gap type] [element] shape.

How to Read These

A Check Input finding combines a gap type with an element. The gap type names the kind of problem. The element names the part of the ask affected.

These examples are reading aids. They do not change the controlled vocabulary or add new valid gap terms.

missing

is not present in the ask.

missing actor: who is responsible, affected, addressed, approving, deciding, or expected to act is not present in the ask.
missing trigger: what starts the action, workflow, state change, or decision is not present in the ask.
missing action: what should happen is not present in the ask.
missing outcome: what result should exist when it is done is not present in the ask.
missing scope: where the request applies, and where it stops is not present in the ask.
missing constraint: what rule, limit, requirement, exclusion, or success condition governs it is not present in the ask.
missing dependency: what must exist, happen, connect, or be true first is not present in the ask.
missing sequence: what order, timing, or progression matters is not present in the ask.

unclear

is present, but not specific enough to use safely.

unclear actor: who is responsible, affected, addressed, approving, deciding, or expected to act is present, but not specific enough to use safely.
unclear trigger: what starts the action, workflow, state change, or decision is present, but not specific enough to use safely.
unclear action: what should happen is present, but not specific enough to use safely.
unclear outcome: what result should exist when it is done is present, but not specific enough to use safely.
unclear scope: where the request applies, and where it stops is present, but not specific enough to use safely.
unclear constraint: what rule, limit, requirement, exclusion, or success condition governs it is present, but not specific enough to use safely.
unclear dependency: what must exist, happen, connect, or be true first is present, but not specific enough to use safely.
unclear sequence: what order, timing, or progression matters is present, but not specific enough to use safely.

ambiguous

allows more than one reasonable interpretation.

ambiguous actor: who is responsible, affected, addressed, approving, deciding, or expected to act allows more than one reasonable interpretation.
ambiguous trigger: what starts the action, workflow, state change, or decision allows more than one reasonable interpretation.
ambiguous action: what should happen allows more than one reasonable interpretation.
ambiguous outcome: what result should exist when it is done allows more than one reasonable interpretation.
ambiguous scope: where the request applies, and where it stops allows more than one reasonable interpretation.
ambiguous constraint: what rule, limit, requirement, exclusion, or success condition governs it allows more than one reasonable interpretation.
ambiguous dependency: what must exist, happen, connect, or be true first allows more than one reasonable interpretation.
ambiguous sequence: what order, timing, or progression matters allows more than one reasonable interpretation.

unstated

is being assumed but was not said.

unstated actor: who is responsible, affected, addressed, approving, deciding, or expected to act is being assumed but was not said.
unstated trigger: what starts the action, workflow, state change, or decision is being assumed but was not said.
unstated action: what should happen is being assumed but was not said.
unstated outcome: what result should exist when it is done is being assumed but was not said.
unstated scope: where the request applies, and where it stops is being assumed but was not said.
unstated constraint: what rule, limit, requirement, exclusion, or success condition governs it is being assumed but was not said.
unstated dependency: what must exist, happen, connect, or be true first is being assumed but was not said.
unstated sequence: what order, timing, or progression matters is being assumed but was not said.

undefined

is named or implied without a usable definition.

undefined actor: who is responsible, affected, addressed, approving, deciding, or expected to act is named or implied without a usable definition.
undefined trigger: what starts the action, workflow, state change, or decision is named or implied without a usable definition.
undefined action: what should happen is named or implied without a usable definition.
undefined outcome: what result should exist when it is done is named or implied without a usable definition.
undefined scope: where the request applies, and where it stops is named or implied without a usable definition.
undefined constraint: what rule, limit, requirement, exclusion, or success condition governs it is named or implied without a usable definition.
undefined dependency: what must exist, happen, connect, or be true first is named or implied without a usable definition.
undefined sequence: what order, timing, or progression matters is named or implied without a usable definition.

conflicting

may block, contradict, or compete with another requirement.

conflicting actor: who is responsible, affected, addressed, approving, deciding, or expected to act may block, contradict, or compete with another requirement.
conflicting trigger: what starts the action, workflow, state change, or decision may block, contradict, or compete with another requirement.
conflicting action: what should happen may block, contradict, or compete with another requirement.
conflicting outcome: what result should exist when it is done may block, contradict, or compete with another requirement.
conflicting scope: where the request applies, and where it stops may block, contradict, or compete with another requirement.
conflicting constraint: what rule, limit, requirement, exclusion, or success condition governs it may block, contradict, or compete with another requirement.
conflicting dependency: what must exist, happen, connect, or be true first may block, contradict, or compete with another requirement.
conflicting sequence: what order, timing, or progression matters may block, contradict, or compete with another requirement.

incomplete

is started but missing required pieces.

incomplete actor: who is responsible, affected, addressed, approving, deciding, or expected to act is started but missing required pieces.
incomplete trigger: what starts the action, workflow, state change, or decision is started but missing required pieces.
incomplete action: what should happen is started but missing required pieces.
incomplete outcome: what result should exist when it is done is started but missing required pieces.
incomplete scope: where the request applies, and where it stops is started but missing required pieces.
incomplete constraint: what rule, limit, requirement, exclusion, or success condition governs it is started but missing required pieces.
incomplete dependency: what must exist, happen, connect, or be true first is started but missing required pieces.
incomplete sequence: what order, timing, or progression matters is started but missing required pieces.

implied

is suggested indirectly but not stated.

implied actor: who is responsible, affected, addressed, approving, deciding, or expected to act is suggested indirectly but not stated.
implied trigger: what starts the action, workflow, state change, or decision is suggested indirectly but not stated.
implied action: what should happen is suggested indirectly but not stated.
implied outcome: what result should exist when it is done is suggested indirectly but not stated.
implied scope: where the request applies, and where it stops is suggested indirectly but not stated.
implied constraint: what rule, limit, requirement, exclusion, or success condition governs it is suggested indirectly but not stated.
implied dependency: what must exist, happen, connect, or be true first is suggested indirectly but not stated.
implied sequence: what order, timing, or progression matters is suggested indirectly but not stated.