Customer
Nasdaq
Business Impact
Nasdaq processes a high volume of large and complex RFPs. The current file mapping and auto-identification process requires consistent document formatting to accurately establish parent/sub-question relationships. Manual formatting adjustments are not operationally feasible and do not align with the customer's standard workflows.
Current Behavior
- File Mapping Agent relies heavily on document structure and formatting consistency to identify question hierarchies.
- Parent and sub-question relationships are not consistently recognized when source documents use varying layouts, numbering conventions, or formatting styles.
- Customers may need to manually adjust formatting (e.g., bold/unbold text) to improve identification accuracy.
Requested Enhancement
Improve the File Mapping Agent's intelligence to:
- Automatically detect parent and sub-question relationships using contextual understanding rather than formatting alone.
- Recognize hierarchy through numbering schemes, indentation, section structures, and semantic relationships.
- Support a wider variety of RFP document formats without requiring manual source file modifications.
- Accurately map sections, subsections, questions, and sub-questions even when formatting styles are inconsistent.
Customer Feedback
- Manual formatting of every RFP is time-consuming and operationally inefficient.
- Modifying source files is not a standard practice within their organization.
- They have observed cases where parent and sub-question distinctions are evident to a human reviewer, yet the agent fails to establish the relationship.
- They require a more reliable and scalable solution for handling large-volume RFP imports.
Expected Outcome
Reduce manual intervention during imports and improve the accuracy of automated question hierarchy mapping, leading to faster RFP setup and a better user experience for organizations handling complex RFP documents.
Priority Justification
High-value enterprise customer processing large volumes of RFPs where import efficiency and hierarchy recognition directly impact adoption and time-to-value.
Recommendation: Submit as an Enhancement Request and link it to the support ticket TKT-218261. If Product asks whether there are examples where correctly formatted hierarchies are still misidentified, then Support may additionally investigate those specific files separately to determine whether any underlying defect exists.
