![](data:image/svg+xml,<svg display="block" id="2531834213" role="presentation" viewBox="0 0 36 36" xmlns="http://www.w3.org/2000/svg"><path d="M 8.667 0 L 8.667 26 M 17.333 0 L 17.333 26 M 2.889 0 L 23.111 0 C 24.707 0 26 1.293 26 2.889 L 26 23.111 C 26 24.707 24.707 26 23.111 26 L 2.889 26 C 1.293 26 0 24.707 0 23.111 L 0 2.889 C 0 1.293 1.293 0 2.889 0 Z" fill="transparent" height="26px" id="lW5iyUDYU" stroke-dasharray="" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" stroke="rgb(0, 0, 0)" transform="translate(5 5)" width="26px"/></svg>)
What Is a Functional Requirement (Funksjonskrav, Norway)?
This is a Norwegian procurement term. A requirement describing what function or result a delivery must achieve, rather than dictating a specific solution.
Why do buyers use functional requirements?
To describe the result they need rather than the solution, which lets suppliers propose approaches the buyer had not thought of and avoids locking the competition to one product.
What is the drawback?
Bids become harder to compare, and suppliers carry more risk because they are responsible for whether their solution actually delivers the stated function.
How should a supplier answer one?
By describing the solution and then showing explicitly how it achieves the stated function, with evidence. An answer that describes the product but not the outcome tends to score poorly.
