Rejected Reason for Workflow

Feature Request: Configurable BOE Rejection Reasons Dropdown

Summary:
Introduce a configurable dropdown field to capture standardized rejection reasons when a BOE (Basis of Estimate) is rejected. This control should allow administrators to define and manage the list of reasons, so users can consistently select the appropriate reason(S) at the point of rejection.

Problem Statement:
When a BOE is rejected today, there is no structured way to capture why it was rejected. Teams may rely on free-text comments, emails, or offline conversations, which leads to inconsistent data, missing context, and limited ability to report on rejection trends. This makes it difficult to identify common rejection drivers, enforce process discipline, and support continuous improvement of BOE quality.

Proposed Solution:
Add a required, configurable dropdown field for “Rejection Reason” that appears whenever a BOE is set to a rejected status.
Allow administrators to:

• Create, edit, and deactivate predefined rejection reasons (e.g., “Insufficient supporting documentation,” “Incorrect assumptions,” “Calculation error,” “Scope misalignment,” “Formatting/structural issues”).

• Control which rejection reasons are available per workspace/project or BOE type, if applicable.
  Make selection of at least one rejection reason mandatory when changing a BOE to a rejected state.
  Optionally allow an additional free-text “Rejection Notes” field to capture more detail, while still requiring a standardized dropdown selection.
  Ensure rejection reasons are stored as structured data, visible in BOE history/audit trails, and available for reporting and dashboards (e.g., counts by rejection reason over time).

Benefits:
Provides standardized, structured data on why BOEs are rejected, enabling meaningful trend and root-cause analysis.
Reduces ambiguity and miscommunication by clearly documenting the reason for each rejection.
Supports continuous improvement of BOE quality by highlighting common problem areas and training needs.
Improves governance and process consistency by enforcing a required rejection reason at the time of status change.
Enables better reporting to leadership and stakeholders on BOE performance and process health.