Integrator evaluation should connect proposed capability to documented evidence, delivery responsibility, and support commitments. Compare each proposal against the same enterprise requirements before choosing a preferred supplier.
Part of Enterprise Security Procurement and Bid Evaluation.
Set the evaluation criteria before scoring
Agree on evaluation criteria before reviewing bids. Include the required workflows, relevant project experience, delivery plan, training, documentation, and support commitments. Decide which requirements are mandatory and which can be scored. If weights are used, record them in advance so a low price cannot quietly outweigh a missing essential function.
Compare evidence and unresolved gaps
Ask each bidder to demonstrate the same representative workflow and identify who will deliver and support it. Keep the evidence beside the score: product documentation, a demonstrated result, a relevant reference, or a stated exclusion. Separate verified answers from claims still awaiting confirmation. Give unresolved items an owner and a deadline before selection.
Record the selection and acceptance conditions
Have the responsible stakeholders review the completed matrix and explain material differences between proposals. Record the reasons for selection, remaining conditions, and any follow-up demonstration required. Carry the agreed deliverables and acceptance tests into the final scope. The evaluation record should explain the choice to someone who did not attend the presentations.
Related planning resources
- NERSA Platform and Manufacturer Experience
- Security Proposal and Scope Development Standards
- Commercial Security Service and Support Standards
Let’s talk about your next step
Tell us what you want to improve and which locations are involved. We can help you work through the questions, check what your systems support, and define a practical project scope.


