QVscribe · ReqWriter · December 2025 → June 2026
Engineering Intelligence
Upgrades
ReqWriter launched in December. Six months later, it's no longer a feature. It's governed engineering infrastructure. Here's everything that changed across our product releases: QVscribe, ReqWriter, QRAcloud, and Governance.
What's Changed
Then & Now
ReqWriter launched exclusively in QRAcloud.
Every rewrite had to be manually requested after navigating to the requirement.
Only standard rewrites were available. No EARS-specific option.
Rewrite thresholds and AI behavior were baked into the client build. Any change required a redeployment.
No way to capture or compare how requirements changed over time. No milestone benchmarks.
EARS compliance analysis was limited in detail and depended on configuration imperatives.
No filtering. All alert types shown together with no quick-sort or badge controls.
ReqWriter runs inside Word, Excel, Polarion, Jama, and DOORS Next. No more round-trips out to a portal.
Suggestions appear as soon as the authoring view opens. No manual click, no navigation, no extra steps.
Rewrite support is available throughout drafting and refinement, on any requirement at any score, not just low-scoring ones.
Your EARS or standard rewrite mode carries across authoring sessions, so EARS-first teams stay EARS-first.
Quality thresholds update from QRA's servers at runtime. When QRA tunes them, you see the new behavior right away. No install required.
Capture the exact state of each requirement at the moment it's taken. Benchmark requirement quality at SRR, PDR, and CDR milestones.
Duplicate keywords, out-of-order elements, and non-compliant imperatives are all detected and explained.
Toggle alert categories on or off with one click. Card headers now show the detected phrase upfront.
What's New
Key Improvements
Live Quality Tuning
Quality thresholds used to live inside the extension. Every change meant a new release and a fresh security review. Now they update from QRA's servers at runtime. When QRA tunes them, you see the new behavior right away. No install required.
Continuous Authoring Assistance
Rewrite support is available throughout drafting and refinement, on any requirement at any score. ReqWriter becomes part of the daily authoring workflow, not just a remediation step at the end.
In Your ALM Stack
ReqWriter now runs inside Word, Excel, Polarion, Jama, and DOORS Next. Open a low-scoring requirement, see suggestions ready. No round-trip out to a portal.
EARS Rewrite Style
Choose between a standard quality rewrite or an EARS-compliant version. Your rewrite mode preference persists across authoring sessions, so EARS-first teams stay EARS-first without re-selecting.
Smart Splitting
Requirements with multiple imperatives? ReqWriter suggests splitting them into singular statements — each copyable individually or all at once with Copy All.
Precise Compliance
Detected EARS elements are shown in order of appearance. Duplicate keywords, mis-ordered sections, and negative imperatives are all flagged with clear guidance.
Access Groups
Restrict which teams see which configurations. Reduce noise, enforce data security, and keep authors focused on what's relevant to their work.
Quality Timelines
Every analysis snapshot is organised in a document Timeline. Track improvement over time, compare states, and share progress with stakeholders — all from QRAcloud.
Dig Deeper
Release Details
Explore the full release notes and technical breakdown for each major capability.
Customer Voice
What Teams Are Saying
I got a really bad score in the beginning and then I did the Suggest Rewrite option and it broke down the requirements for me… it really, really improved the scoring.
Having the ReqWriter outputs directly in Word or Excel is great… it keeps everybody in one spot to do their work, you don't have to go out to the cloud and then come back.
The ReqWriter is again, another great feature to be part of the product… the suggested rewriting of requirements would be the most valuable for day-to-day users.
I'm very happy that it has the AI integration. I think that's, for the end user, very powerful because it takes a lot of time to come up with better requirements.
The proposed requirements were not so bad. They are very, very much better than the first requirement.
This can definitely reduce your time in writing. Converting your user stories to actual system requirements. Yeah, that's really cool.
Release History
The Journey
Try the June Release
Ready to
Upgrade
Spend less time reworking requirements, and more time engineering.
Get Started