Customer: IBA
Use Case:
IBA frequently receives Word-based tenders with nested sections and questions where the source document’s hierarchy does not follow Responsive’s sequential structure. For example, a section may immediately contain a subsection and questions that need to visually begin at a deeper indentation level.
Current Behavior:
Responsive requires section, subsection, question, and sub-question levels to be created hierarchically. A user cannot independently select a deeper level, such as Sub Question Level 1 or Level 2, unless the preceding hierarchy has already been established.
Requested Behavior:
Allow users to independently select the desired section, subsection, question, or sub-question level from the available hierarchy rather than requiring each preceding level to exist first.
Business Impact:
IBA relies heavily on Word-based tender responses and has invested in standardized Word templates and styles to minimize post-export formatting. The current hierarchy restriction can cause the first question beneath a subsection to export at the wrong indentation or numbering level, requiring manual correction in Word after export.
Example:
If a tender contains Section 8 followed immediately by Subsection 8.1 and its first question, IBA may need that question to use a deeper sub-question style. Responsive currently forces the first question to begin at the initial question level, even when that does not match the source document’s structure.
Priority:
Medium. This does not block IBA from completing tenders, but it creates recurring manual formatting and numbering cleanup after export and limits their ability to fully standardize the Responsive-to-Word workflow.
Desired Outcome:
Give users greater control over document hierarchy so Responsive project structures can accurately reflect source tender formatting and export into established Word templates with less manual remediation.
