Software design and procurement
How to evaluate a software tender demonstration
Give digital technology suppliers the same council service scenario, evidence request and scoring anchors before you compare their software proposals.

A polished dashboard tells an evaluation panel very little about how a supplier handles a disputed service request. Give each bidder the same short task, the same facts and the same definition of a successful result. The demonstration then produces evidence that the panel can compare.
Use a change of mind as the demonstration
Imagine a resident reports a damaged park bench by phone. Later they correct the location, after a work order has already been issued. Give each supplier a fictional record, a staff role and a contractor role. Ask them to show the corrected location reaching the right work order and the previous location remaining traceable.
Tell bidders in advance which facts the panel will score. If configuration is acceptable, say whether it must exist in the demonstration or may be described with separately priced work. Give comparable preparation time and communicate clarifications through the buyer’s agreed process.
Write anchors the panel can actually observe
For the corrected location, an example of a complete result is that the contractor sees the revised site, the resident gets a reference and staff can reconstruct the change. A partial result might require staff to phone the contractor and record the call manually. Agree the anchors and the weight before offers are assessed.
New Zealand Government Procurement distinguishes preconditions from qualitative evaluation criteria. With the procurement lead, decide which requirements genuinely need a pass or fail decision and which deserve a judgement about degree. Match them to the questions and the evidence requested in the tender documents.
Separate what happened from what was promised
Give evaluators a sheet with spaces for the observation, the relevant criterion and the remaining uncertainty. Someone should be able to trace a score back to what the panel saw or to a clearly identified commitment in the offer. Record any dependencies on a paid module, future development or an external integration.
At moderation, read out the evidence behind different scores before discussing the average. If two evaluators interpreted a workflow differently, record the clarification needed and follow the published process. Carry accepted commitments into delivery and acceptance testing. That gives the implementation team a practical record of why this offer was selected.