Set Requirements and “Complete” Rules: Verification and Status

Understanding Requirements

A requirement is any item a user must submit.

Examples include:

• Document
• Image
• ID proof
• Insurance card
• Utility bill

The system only works properly when requirements are set correctly.

Requirements Configuration Screen

To set requirements, open the configuration section.

Here, you can:

• Add a new requirement
• Select the type of requirement
• Mark it as required or optional

This screen controls the entire requirement setup.

Required vs Optional Requirements

Required Requirements

Required means:

• This item must be submitted
• Process cannot be marked complete without it

Examples:

• Government-issued ID
• Insurance card
• Signed agreement

If a required item is missing, status will remain Incomplete.

Optional Requirements

Optional means:

• Submission is not mandatory
• Process can still be completed without it

Examples:

• Additional supporting document
• Secondary address proof

Optional items are stored in the system but do not block completion.

How Requirement Completion Works

The completion logic checks:

• Are all required items submitted?
• Has verification been completed?

If both are true, status becomes Complete.

Understanding Verification

Verification is the process of validating submitted documents.

Verification results:

• Pass
• Fail
• Pending

These results directly impact completion status.

How Verification Affects Completion

Completion is only achieved when:

• Required items are submitted
• Verification status is Pass

If verification fails:

• Completion is blocked
• User must re-submit

If verification is pending:

• Review is still in progress

Status Flow Example

1. Requirement added
2. User uploads document
3. Verification begins
4. Result received (Pass / Fail)
5. System updates completion status

This flow is automatic.

Common Requirement Templates (Examples)

ID Template

Used for: Identity verification

Includes:

• Front ID image
• Back ID image

Insurance Card Template

Used for: Coverage verification

Includes:

• Card number
• Expiry date

Utility Bill Template

Used for: Address verification

Includes:

• Recent bill
• User name
• Address

Best Practices for Completion Rules

• Always mark critical documents as required
• Clearly label optional items
• Keep verification rules simple
• Provide users with a clear re-upload option

This reduces errors and speeds up workflow.

Common User Mistakes

• Marking required items as optional
• Ignoring verification failures
• Using outdated templates
• Not testing completion logic

These mistakes slow down the process.

Final Summary

Requirements form the foundation of the system. Verification ensures quality of submissions. Completion rules make the final decision.

When setup is clear:

• Errors are minimized
• User experience improves
• Workflow runs smoothly