Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Not In Good Order
Governance, Ownership & Risk

Not In Good Order

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Governance, Ownership & Risk

Not In Good Order, or NIGO, describes documents or submissions that are incomplete, inconsistent, or do not match what the process requires. In digital agreement workflows, NIGO checks help catch bad attachments before submission, reducing rework, review delays, and avoidable rejection cycles.

What NIGO Means in Digital Agreement Workflows

Not In Good Order, or NIGO, is a process-quality label, not a security verdict. In agreement and submission workflows, it signals that required material is missing, inconsistent, unreadable, or formatted in a way the process cannot accept, so the item needs correction before it can move forward.

The practical value of the term is that it separates a recoverable submission defect from a completed review outcome. A NIGO finding usually means the workflow has enough structure to validate inputs, but not enough completeness or consistency to proceed without rework.

Why NIGO Creates Delay and Rework

NIGO matters because it interrupts straight-through processing. A missing attachment, mismatched field, or unsupported file can force manual review, trigger resubmission, and extend cycle time even when the underlying request is otherwise legitimate.

That delay is often the real cost. Each return to the sender adds coordination overhead, increases the chance of version confusion, and can create a backlog when many submissions fail the same checks.

Common Triggers for a NIGO Finding

Most NIGO cases come from basic process mismatch rather than complex error. Typical triggers include incomplete forms, inconsistent names or dates across documents, invalid signatures, expired supporting material, or attachments that do not match the submission requirements.

In digital workflows, poor file quality can be just as disruptive as missing data. Scanned documents that are illegible, attachments in the wrong format, or files uploaded to the wrong field often fail validation even when the sender believes the package is complete.

How Organisations Reduce NIGO Rates

The most effective reduction happens upstream, before submission. Clear checklists, field validation, required-document prompts, and pre-submit quality checks help catch obvious defects early and reduce avoidable review loops.

Good workflow design also makes the rules visible. When users can see what is missing, what must match, and which attachment belongs where, NIGO becomes a controlled exception instead of a recurring operational burden.

Risk and Threat Considerations

NIGO is mainly an operational quality problem, but it can become a control weakness when incomplete or altered submissions slip through weak validation. In regulated or high-trust workflows, repeated NIGO conditions may also indicate poor process design, weak document verification, or a gap between what the workflow expects and what users actually submit.

Failure mechanism: Incomplete, inconsistent, or misleading submissions bypass adequate pre-checks, forcing manual correction later or, in worse cases, allowing bad input to enter a downstream approval path.

Impact: The result can be delayed processing, repeated rework, avoidable rejection, and reduced confidence in the reliability of the workflow itself.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AT-01 — Identity Management, Authentication, and Access Control AwarenessNIGO workflows depend on users understanding required submission conditions.
Recommendation — Use workflow training to reduce incomplete or inconsistent submissions before review.
CIS Controls v8CIS-14 — Security Awareness and Skills TrainingClear user guidance reduces repeated submission defects and rework.
Recommendation — Train submitters on required documents and validation rules before they send requests.
ISO/IEC 27001:2022A.5.15 — Access ControlSubmission workflows rely on controlled, rule-based acceptance and review paths.
Recommendation — Define who can submit, review, and approve to keep workflow decisions consistent.

Practitioner Guidance

Why practitioners should care: NIGO is a useful signal of process quality, not just user error. If the same defect patterns recur, the issue is often in the workflow design, submission guidance, or validation logic rather than in individual submissions alone.

Governance implication: Treat NIGO rates as an operational health metric for the process owner. High return rates usually justify tightening pre-submit checks, clarifying acceptance rules, or simplifying the required evidence set.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org