How to document a software selection so auditors and the board can follow it
A software selection is properly documented when a third party can see, without asking, why this option was chosen. That takes six parts: the trigger and goal, the stakeholders and their roles, weighted criteria and separate dealbreakers, the options assessed including the status quo, the scoring with evidence, and the decision with its rationale, residual risks and sign-off. Order matters: criteria and weights are fixed before any vendor presents.
The six parts of a traceable selection
1. Trigger and goal: which problem is solved, by when, within which budget. One sentence on the trigger is enough, such as a contract ending, an audit finding or a new obligation under NIS2 or DORA.
2. Stakeholders: who decides, who must approve, who is consulted. Typically the CISO, CIO, procurement, the business owner, data protection, the works council and finance.
3. Criteria: weighted criteria that add up to 100 percent and, kept apart, the dealbreakers that remove an option whatever its score. Every point on the scale has a written meaning.
4. Options: every vendor seriously assessed, plus the status quo. Leave alternatives out and you cannot later show the chosen option was better.
5. Scoring with evidence: for each option and criterion a score, a reason and a source, such as a proof of concept, a reference call, a certificate or a draft contract. Unverified vendor claims are marked as such.
6. Decision: recommendation, rationale, known residual risks with mitigations, sign-off with a date. Later changes are recorded as a new version, not overwritten.
What auditors and supervisors look for
Auditors rarely ask whether the best option won. They ask whether the selection followed a traceable process: were the criteria fixed in advance, were alternatives assessed, is the vendor risk evaluated, and who signed off?
Under NIS2 that is mainly supply chain security in Art. 21(2)(d) and management body approval and oversight in Art. 20. DORA adds the pre-contract assessment in Art. 28 and the register of information. ISO 27001 controls A.5.19 to A.5.21 require managed supplier relationships.
Which tools exist for it
Spreadsheet and document (Excel, Word, Confluence): flexible and everywhere, weak on versions, multiple raters and showing why a weight changed later.
Architecture decision records: short decision logs, often in a Git repository. Good for technical architecture choices within a team, not for vendor selections involving procurement and the board.
Decision analysis software such as 1000minds: methodically strong at weighting many criteria; evidence, stakeholders and sign-off mostly stay elsewhere.
Procurement and sourcing suites such as SAP Ariba or Coupa: for the formal buying process with bids and contracts, less for the trade-offs before it.
GRC platforms such as ServiceNow or OneTrust: for the ongoing supplier and risk register, after the decision rather than before.
DecisionOS by nexalign: runs one IT decision from criteria to an audit-ready memo, with stakeholder positions, a weighted comparison matrix, marked evidence and versions. It does not replace a procurement suite or a GRC platform; it produces the rationale both of them need.
Checklist before sign-off
Were criteria, weights and dealbreakers fixed and dated before the first vendor meeting?
Is the status quo scored as an option?
Does every score have a reason and a source?
Are objections recorded, even where they were overruled?
Are residual risks named and mitigations assigned?
Is the sign-off recorded by name and date?
Related reading
Insights
Decision guides
