A scorecard should make the difficult decision visible. If a required country, language or access method is unresolved, a strong presentation elsewhere should not wash it away.
The idea in view · Planning diagram
Evidence comes before the weighted total
- Mandatory condition
- Confirmed pass
- Pending evidence
- Scored preferences
- Full cost basis
- Written decision
Define non-negotiable requirements
Separate essentials such as an approved access method or required language from preferences such as report styling. A provider that cannot meet an essential requirement needs an explicit exception decision. Do not award points for a marketing claim that has no supporting scope or demonstration.
Use evidence beside the score
For each criterion record the proposal section, demonstration or written answer. Mark missing evidence as unresolved rather than zero capability. Use the same questions with every bidder, and document any clarification after the first scoring round.
Make the decision reviewable
Keep evaluator notes, agreed weights and the final decision rationale. Where a pilot is necessary, label the result provisional until the acceptance tests pass. Revisit the score if pricing or scope changes during negotiation.
Write what each score means
Before reviewing proposals, define the evidence for a satisfactory answer. For example, an export criterion could require an authorized user to retrieve a staged event and open it on the intended receiving device. A brochure statement would then remain pending rather than earning the same result as a completed test.
Use weights for genuine preferences only after deciding which requirements cannot be traded away. Keep evaluator notes and the relevant scope revision. If a negotiation removes a service duty or adds an exclusion, revisit affected criteria. The final document should explain why the chosen proposal fits this site, not merely report the highest total.
Set mandatory requirements before weighted preferences
A scorecard works best after the business distinguishes essential conditions from desirable features. Examples of mandatory conditions might include a supported access method, accepted review hours or a required reporting capability. These are requirements for your procurement, not universal rules for every site. A bidder that cannot meet one should be marked clearly rather than receiving enough points elsewhere to conceal the gap.
Choose weights only after agreeing the operating requirement. Otherwise the team may adjust the scoring to favor a preferred presentation or a familiar supplier. Keep the number of criteria manageable and explain what evidence earns each score. Terms such as good support or advanced analytics are difficult to assess consistently until they are translated into a task, a demonstrated capability or a written commitment.
Score evidence, not the confidence of the sales pitch
Use a consistent evidence ladder. A statement in a presentation, a written scope, a relevant demonstration and an accepted site test carry different information. Record what you actually saw and what remains unverified. A product demonstration at another location can show an interface or workflow; it does not establish the same result with your camera, network and lighting.
Give reviewers a place to record why they assigned a score. If one person scores reporting highly because a sample looks polished and another because it contains complete timestamps, the numerical result hides different criteria. Agree the expected record first. Where a provider cannot yet supply evidence, mark the condition pending and identify the next check. Do not turn uncertainty into either a confident pass or an unsupported allegation of failure.
Keep price and implementation risk visible
A weighted total should not replace a readable comparison of scope and cost. Show the full cost basis, exclusions, setup dependencies and key contract terms beside the score. If a low price depends on reusing untested cameras, the relevant uncertainty belongs in the decision record. If a higher-priced offer includes duties you do not need, a high feature score may not improve its suitability.
Use a short sensitivity review before choosing. Ask whether the result changes when a disputed criterion is rescored or a reasonable priority changes. A winner that depends on one subjective point needs more discussion than the total suggests. Keep the final rationale in prose: the duties accepted, evidence relied on, open conditions and person authorized to accept them. That rationale is more useful at renewal than an unexplained number.
A fictional scorecard with an unresolved requirement
Consider two hypothetical bidders. One has a compelling dashboard and a lower price, but has not confirmed a controlled access method for the existing recorder. The other has a less polished presentation but supplies a written integration path and agrees to a site test. If controlled access is mandatory, the first bidder's result should remain conditional rather than being averaged into a reassuring overall score.
The team can request the missing evidence and set a decision date. It may also discover that the existing recorder needs a change that affects both proposals. Record the new dependency and compare revised scope and cost. The worksheet is not a way to manufacture an objective answer from incomplete information. It is a way to make the business's priorities, evidence and remaining judgement visible to everyone approving the purchase.
Make the call
Separate requirements from preferences
| Situation | Decision to make | What to ask for |
|---|---|---|
| A mandatory access control is unsupported | Whether an exception is acceptable | A named risk decision before selection |
| A capability is described but not shown | Whether the evidence is sufficient | A demonstration or written technical answer |
| Two evaluators score differently | Whether they used the same criterion | A shared definition and evidence reference |
Before you move on
- Agree mandatory criteria and scoring rules.
- Attach evidence to each assessment.
- Resolve critical unknowns before final approval.
A worksheet you can actually use
Start with the blank sheet. Add one row per item, assign an owner and mark anything unresolved as pending. The completed example shows the level of detail to aim for.
Keep completed security plans private. Use aliases; keep passwords, access codes, personal contacts and footage links in your approved systems.
How to fill the worksheet
- Criterion
- Define a requirement in terms that different reviewers can assess consistently against the same evidence.
- Mandatory
- Mark essential conditions before weighting preferences. An unresolved mandatory condition should remain visible outside the aggregate score.
- Evidence requested
- State the document, demonstration or site test needed and avoid treating all forms of evidence as equally conclusive.
- Assessment
- Record the observed answer, pending condition or confirmed limitation with a short reason that another reviewer can understand.
- Unresolved risk
- Describe the consequence of missing evidence without converting an unanswered question into an unsupported allegation of failure.
- Owner
- Name the person responsible for obtaining evidence or accepting a residual condition under the procurement process.
A worked example
Fictional panel: report exports score well, but country-specific data access remains unresolved. The buyer withholds approval until that requirement is confirmed instead of letting other scores compensate.
| Criterion | Mandatory | Evidence requested | Assessment | Unresolved risk | Owner |
|---|---|---|---|---|---|
| Approved access method | Yes | Written architecture | Pending | IT review outstanding | Buyer IT |
Questions readers bring to this task
What else should you know?
Should price be in the same scorecard?
It can be, but first normalize the service scope and identify any mandatory failures. Keep the quoted term, excluded charges and financial comparison visible. The scorecard supports a decision; it cannot decide how much unresolved operational risk the business should accept.
Link to this answer ↗How many criteria should a scorecard include?
Enough to cover the meaningful duties and risks without splitting the same preference into several overlapping scores. A short set of clearly evidenced criteria is easier to review than a long feature inventory. Keep mandatory conditions separate and explain any weighting that could change the decision.
Link to this answer ↗Should a missing answer receive zero?
Distinguish an unanswered question from a confirmed inability to meet the requirement. A pending score with a deadline can be more honest during procurement. Before selection, decide how unresolved mandatory conditions affect eligibility and record the approved decision rather than hiding them in a total.
Link to this answer ↗Can the scorecard prove which provider is best?
It can show which proposal best fits your stated criteria and available evidence. It cannot prove future service performance or establish a universal ranking of providers. Validate the final scope, references where available and representative site conditions before relying on the result.
Link to this answer ↗Notes & sources
This is a decision aid, not a certification or an independent vendor ranking.
Reviewed October 27, 2026. The examples and worksheets are planning aids, not customer results or a statement of contracted service.
- Surveillance Camera Commissioner: Buyers Toolkit (2018)
Historical operational requirements, commissioning and handover context; not current legal advice or certification.
- MonitorCrew: service scope and pricing factors
Provider description of staffing, hours, handovers and scope. No comparative testing is claimed.