When to use it
A preferred bid wins by a narrow scoring margin.
A scorecard organizes preferences; it cannot repair an incomplete scope or turn unsupported ratings into evidence. Apply mandatory requirements before examining whether a recommendation depends on fragile assumptions.
Define actual mandatory requirements and their verification before scoring. Identify unresolved or ineligible prerequisites under the authorized procurement rules rather than offsetting them with presentation scores. This guide does not invent universal supplier eligibility requirements.
Keep gates separate from discretionary criteria such as reporting usability or transition support. Confirm qualifications, coverage or contractual prerequisites through their appropriate sources and reviewers. A weighted total does not prove those prerequisites have been met.
Describe each rating using evidence suppliers can provide consistently. A polished presentation, unsupported assurance and tested sample report are different states. Define how missing information is treated; it should not silently become zero or verified fact.
Use the same questions and scope for all candidates. Record source and rationale for material ratings. Approve weights reflecting the decision owner’s priorities before manipulating outcomes. For common-scale scores, total = sum of score × normalized weight. Version genuine priority changes and recalculate everyone.
Hypothetical model with all gates verified: A scores 4 for reporting and 2 for transition; B scores 3 for each. Equal weights give both 3.0. Reporting weighted 60% gives A 3.2 and B 3.0. Reporting weighted 40% gives A 2.8 and B 3.0.
The ranking changes while evidence ratings stay fixed. Discuss which preference is actually endorsed and what unresolved evidence could alter a rating. The example does not establish either candidate’s real suitability. Keep reviewer disagreements and rationale visible rather than concealing them in an average.
Show mandatory status, comparable cost, rating evidence, weights and sensitivity together. Distinguish a model result from an authorized selection and from first-service readiness. Executed terms and transition dependencies remain relevant after scoring.
Retain the model and proposal versions. Changing priorities or new evidence should produce a traceable recalculation. The GAO reference supplies general federal control context, not an association selection rule or compliance certificate.
Hypothetical A scores 4 for reporting and 2 for transition, while B scores 3 for each. A leads when reporting weighs 60%, but B leads when it weighs 40%.
Original fictional example · no completed client assignment or property inspection is represented.
| Record to obtain | Review question or calculation |
|---|---|
| Mandatory-gate evidence | Verify gates separately. With the stated ratings, 60% reporting gives A = 3.2 and B = 3.0; 40% reporting gives A = 2.8 and B = 3.0. |
| Fixed ratings and their rationale | Hold ratings constant during weight tests. At 50% reporting both score 3.0. Explain that this threshold comes from the chosen ratings and weights, not from measured superiority. |
| Authorized weights and alternatives | Disclose ranking reversal. Keep pass/fail requirements outside the weighted average so that a high score cannot erase a failed mandatory condition. |
Useful working output: A selection discussion showing which preference actually determines the model result.
Open each challenge to test the reasoning against a different finding.
Check: Keep proposal evidence and scores fixed while varying the disputed weight. Describe which assumption changes the ranking.
Decision effect: Present a conditional recommendation and request the missing evidence; do not conceal a fragile ranking behind a precise total.
Check: Read eligibility and mandatory scope separately from weighted preferences. Confirm the failure against the actual procurement rule.
Decision effect: Resolve eligibility with the authorized reviewer before using the weighted ranking for selection.
Adapt the record request to authorized access, governing documents and the actual property. The example does not verify any unknown input or replace a professional conclusion.
Property Management Company Selection Scorecard · More vendors and management selection examples
A preferred bid wins by a narrow scoring margin.
Do not treat subjective weights as measured facts.
Keep mandatory gates separate and rerun plausible weights while recording which tradeoffs change the ranking.
Original proposed coordination checks · adapt to authorized access, the actual obligation and the appropriate professional review. These are not findings about your property.
Follow the related handoff workflow · Read the review definitions
A reusable control-definition worksheet. Add property-specific owners, dates, evidence links and status before using it as an action record.
These rows define suggested controls, not completed property findings. Interpret each check against your actual property records, responsible role and acceptance evidence. See the review instructions and reuse terms.
8 checks shown
No check matches those filters. Try a different term or area.
| Review area | Check | Evidence | Responsible owner | Acceptance evidence |
|---|---|---|---|---|
| Gates | Define mandatory requirements | Authorized prerequisites | Approval owner | Gates separate from preferences |
| Gates | Verify each status | Appropriate source evidence | Procurement owner | Unknown not silently passed |
| Scope | Normalize service and cost | Common quantities term and exclusions | Scope owner | Material differences visible |
| Ratings | Define scoring anchors | Observable meaning for each rating | Review lead | Common standard usable |
| Ratings | Retain score evidence | Source rationale and reviewer disagreement | Reviewer | Rating has a traceable basis |
| Weights | Approve and version priorities | Authorized weights and total basis | Decision owner | Changes applied consistently |
| Sensitivity | Test plausible weight changes | Alternative preference scenarios | Review lead | Ranking reversals disclosed |
| Handover | Check delivery readiness | Prerequisites and acceptance | Transition owner | Selection not completed onboarding |
Keep mandatory requirements separate and follow the authorized procurement rules. A score does not verify an unresolved prerequisite.
Disclose sensitivity and discuss the priority endorsed. Seek stronger evidence or clearer preferences instead of treating a narrow lead as certainty.
Confirm the applicable source and any later changes before a property-specific decision. The guide provides coordination controls; professional conclusions remain with the appropriate qualified reviewer.
Bring each proposal to the same service period, quantities and completion standard.
Scroll horizontally to read all columns.
| Criterion | What to check | Practical implication |
|---|---|---|
| Whole cost | Include mobilisation, recurring charges, exclusions, maintenance and expected replacement. | The lowest initial bid may omit work necessary to deliver the intended outcome. |
| Sensitivity | Recalculate after changing the assumption most likely to vary. | A narrow price advantage may disappear when quantities or service frequency change. |
Illustrative example: option A costs $12,000 plus $1,800 annually for five years; B costs $15,000 plus $900 annually. Undiscounted totals are $21,000 and $19,500, excluding any other costs. Different timing or replacement assumptions can change the comparison.
Life-cycle cost analysis compares alternatives over a period of operation. US Department of Energy — Life-cycle cost Source consulted on .