The URS module
A user requirements specification fails review for predictable reasons: requirements that cannot be verified, assumptions presented as facts, and categories quietly left out. The URS module is built around those three failures.
Assumptions are first-class
When you cannot confirm something — a utility rating, an interface, a site standard — you record it as an open assumption attached to the document. Open assumptions are counted on your dashboard and printed in their own section of the export, so nothing is issued while it is still a guess.
Two ways in, one structure
Start from structured questions, or paste a vendor specification and turn its lines into candidate requirements you accept, edit or discard. Either route produces the same categorised document.
- Operational
- Functional
- Data / records
- Data integrity (ALCOA+)
- Security and access control
- Audit trail
- Interfaces
- Environmental / utilities
- Materials of construction
- Cleaning and maintenance
- Safety
- Documentation and handover
- Regulatory compliance
- Qualification support
What it does not do
It does not assess your compliance, approve your document, or replace your site's quality system. It produces a draft that a competent reviewer can work with, and it keeps the unresolved parts visible.