URS
User requirement specification. What the system must do, written before anyone falls in love with a product demo.
The URS states needs in the language of the process, not the product: what must be captured, calculated, controlled and reported, and to what tolerances. It is the yardstick against which suppliers are compared and validation is later measured.
Requirements written after the product is chosen describe the product, which makes validation circular. The discipline of writing the URS first is cheap insurance against buying a workflow you then spend years configuring around.
Related terms
Go deeper
All CSVCSV/Jun 2, 2026/8 min
CSA is not the end of CSV. It is CSV finally done right.
FDA's Computer Software Assurance guidance was read by half the industry as permission to stop validating. The other half read it correctly.
CSV/May 21, 2026/7 min
The GAMP 5 software categories, explained like a human
Category 3, 4 or 5 decides how much validation work you are signing up for. Here is how to call it correctly, with a tool that does the asking.