---
title: R&D Roadmap
---
[](https://basewise.ai/en/home?hsLang=en)
[](https://basewise.ai/?hsLang=en)
- [Applications](https://basewise.ai/en/applications)
- [About Basewise](https://basewise.ai/en/about-basewise)
- [Insights](https://basewise.ai/en/insights)
- [Contact](https://basewise.ai/en/contact)
More results
[Book your free demo](https://basewise.ai/en/demo?hsLang=en)
[Request your demo](https://basewise.ai/en/demo?hsLang=en)
- [Applications](https://basewise.ai/en/applications)
- [About Basewise](https://basewise.ai/en/about-basewise)
- [Insights](https://basewise.ai/en/insights)
- [Contact](https://basewise.ai/en/contact)
[Book free demo](https://basewise.ai/en/demo?hsLang=en)
# Roadmap
[Scroll](https://basewise.ai/en/rd-roadmap#customer-quote)
## Development roadmap
| Nr | R&D | Planned | Status |
| --- | --- | --- | --- |
| 001 | Customers need clear insight into our roadmap, including planned developments and how we address existing issues. | Q4 2025 | Completed |
| 002 | Requirements Verification Planner (RVP) Creation of a digital assistant to automate requirements analysis and verification planning, assigning verification actions to the appropriate project lifecycle stages. | Q1 2026 | In development |
| 003 | Requirements Quality Analyser (RQA) - The RQA tool is currently in the proof-of-concept stage. - The user experience (UX) is not yet optimized for usability. - Output is not yet fully structured. Plannend improvements: - The output will be more structured and user-friendly. - Users will be able to pre-configure settings to tailor the analysis to their needs, such as: - Selecting which INCOSE rules to apply. - Deciding whether requirement types should influence rule selection. - Adjusting the strictness of the assessment. - A test report will be generated to summarize results. Dataset and functionality: - The tool leverages a vector database containing key SE documents (see TOC above). - It can be used both as a digital assistant for drafting needs and requirements, and for assessing the quality of individual statements and sets, based on selected rule subsets. | Q1 2026 | In development |
| 004 | Chat and knowledge chat - Users should be able to create Word, Excel, and PDF documents directly from chat conversations. | Q2 2026 | In development |
| 005 | Integration with third party sofware like Relatics - Goal: enable direct data exchange with Relatics without file-based input/output formats, supporting workflows such as requirements analysis, verification plan creation, and verification report import/updates. - The platform provides seamless integration with Relatics, removing the need for file-based import/export formats for requirements, verification plans, and verification report updates. | Q2 2026 | In development |
| 006 | RQA Production based - The platform provides Rule-based Quality Assurance (RQA), allowing users to apply INCOSE standards and custom rules to requirements, risk and hazard analyses, supported by a unified UX for third-party integrations. | Q2 2026 | In development |
## Issues
| Nr | Issue | Updated with | Planned | Status |
| --- | --- | --- | --- | --- |
| 017 | Scalability platform - Homepage: The application tile layout did not scale correctly and has been fixed. | - Enhanced scalability of several applications. | Q4 2025 | Completed |
| 016 | DRE - readability - DRE: Chat styling has been improved to enhance readability and usability. | - Improved readability of chat text in DRE. | Q4 2025 | Completed |
| 015 | RQA - issues - Dutch output review comments were previously too extensive and unreliable. This has been corrected. - Column titles using mixed languages are now correctly aligned with the selected input language. | - Improved RQA output through an upgrade to a newer LLM model. - Faster requirement analysis within RQA. - Implemented English column names in RQA and improved overall robustness and stability. | Q4 2025 | Completed |
| 014 | DRE - Requirement Formulation Issues | - Extracted requirements may be incorrect or poorly formulated, particularly in Dutch. - Examples include circular or meaningless statements, such as: *"Projectmanagementplan dient te voorzien in een projectmanagementplan."* - Process-type requirements are often phrased awkwardly or illogically. | Q3 2025 | Completed |
| 013 | DRE - user overall experiences | - DRE 3.0 is currently not user-friendly, slow, and does not consistently deliver the desired results. - The English version performs noticeably better than the Dutch version. - Dutch output for rewritten or newly created requirements is of insufficient quality. - The handling of original text retention is inconsistent. - General design and usability adjustments are required. | Q3 2025 | Completed |
| 012 | Chat - link handling | - Generated URLs open in the same window instead of a new tab. - Returning to the chat screen causes loss of context or the entire session. - Users expect external links to open in a separate tab by default. | Q3 2025 | Completed |
| 011 | Chat - Model Output Differences | - Users report differences between responses in ChatGPT and in the Hegeman AI assistant. - ChatGPT usually provides the correct or more complete answer. - This creates confusion and reduces trust in the integrated AI version. | Q3 2025 | Completed |
| 010 | Platform - point issues | - **User Management**: Fix user creation, role assignment, and admin controls. - **Reliability**: Improve availability, reduce 504 errors, ensure accessibility on corporate networks. - **LLM Flexibility**: Support multiple or local LLMs. - **Security & Deployment**: Add document security and strengthen app deployment workflows. - **Unified Design**: Implement new UI across all apps and platform modules. - **SE Knowledge Base**: Improve large-scale requirement processing and feedback quality. | Q3 2025 | Completed |
| 009 | DRE - Checks, Balances & Workflow Complexity | - Users find the number of checks and interactions required to run DRE too high. - The overall workflow feels heavy, with too many manual confirmations. | Q3 2025 | Completed |
| 008 | Chat History & Session Persistence | - Users cannot access previous chat history, making it easy to lose work. - When clicking a generated URL, navigating back causes the user to lose the full conversation. - Users regularly request chat history as a key feature. | Q4 2025 | Completed |
| 007 | DRE - Drag-and-Drop & Upload Reliability | - Drag-and-drop does not always work on first use; sometimes only upload via file picker works. - The system can freeze or get stuck during document upload, requiring browser restarts. - Allocation to the “system of interest” is poor when source documents lack clear structure (e.g., standards documents like Sydney Water). - Upload failures can result in *Error 504*. | Q4 2025 | Completed |
| 006 | REF - Performance & Robustness | - REF runs occasionally stall or continue far longer than the predicted runtime. - No safeguard exists against accidentally starting overlapping or stacked runs. | Q4 2025 | Completed |
| 005 | REF - User Interface & Workflow | - Upload order is not intuitive: requirements appear at the top, documents at the bottom. - Application settings/options cannot be locked or saved, forcing repeated re-entry by the user. - The REF Requirements Template cannot be downloaded correctly—the link opens inside the current window. | Q4 2025 | Completed |
| 004 | Chat - UI Display & Layout | - Certain applications do not display correctly within the chat interface. - Users need to scroll excessively, or the interface feels too zoomed in. - This impacts readability and overall user experience. | Q3 2025 | Completed |
| 003 | REF - Evidence Presentation & Data Consistency | - *proof\_doc* does not always display a single, correct document reference (filename only). - The required concatenation of “\[proof\_location\] \[proof\_detail\]” before Relatics import is currently manual. - Evidence is sometimes marked as “accepted” even when it should not be. - Dutch verifications do not always follow the verification plan (method & criteria). | Q3 2025 | Completed |
| 002 | DRE - Extraction Quality & Completeness | - Users are unsure whether all relevant content is extracted — missed text fragments reduce trust. - Traceability to source locations is difficult, leading some teams (e.g., Hegeman) to revert to **page-by-page extraction**. - Verbatim extraction often includes text that is **not** a requirement. - When extraction quality is unreliable, users prefer selecting **“all” + “verbatim”** to avoid missing content. - Additional fields, such as *document element* and *text type*, do not deliver useful or accurate results. - These attributes can introduce noise and reduce clarity rather than improving structure. | Q3 2025 | Completed |
| 001 | REF - Reference Processing & Accuracy | - Location references are sometimes duplicated or inconsistent between *proof\_location* and *proof\_detail*. - Page numbers in *proof\_location* can be incorrect. - Multiple REF results per requirement cause complications when updating the correct verification in Relatics. - Differences in REF outputs between runs on the same dataset. | Q3 2025 | Completed |
#### BASEWISE
**Basewise** provides modular AI solutions and applications for process optimisation.
Basewise Consultancy B.V.
Chris Schutweg 3
3632JK Loenen aan de Vecht
The Netherlands
KVK-number 98925717
[Applications](https://basewise.ai/en/applications?hsLang=en)
- [Platform](https://basewise.ai/en/platform?hsLang=en)
- [DRE](https://basewise.ai/en/dre?hsLang=en)
- [RQA](https://basewise.ai/en/rqa?hsLang=en)
- [REF](https://basewise.ai/en/ref?hsLang=en)
[Company](https://basewise.ai/en/about-basewise?hsLang=en)
- [Contact us](https://basewise.ai/en/contact?hsLang=en)
- [AI Disclaimer](https://basewise.ai/en/ai-disclaimer?hsLang=en)
- [Terms and Conditions](https://basewise.ai/en/terms-and-conditions?hsLang=en)
- [Privacy policy](https://basewise.ai/en/privacy-policy?hsLang=en)
Copyright © 2026 basewise.ai