Weighted Scorecard

Use this skill to run Weighted Scorecard as a practical consulting method, not as a generic framework explanation.

Method Notes

• Use eligibility gates before weighted scoring.
• Add scoring anchors so reviewers score consistently.

Required Inputs

Collect or infer these inputs before execution:

• evaluation object
• criteria
• weights
• evidence and scoring scale

Record input status and source: supplied / proposed / approved / validated. Supplied values may be used for the requested calculation when the existing comparability and eligibility conditions are met; approval is not an additional prerequisite. Only label an input approved or validated when its source explicitly establishes that status. Pending approval or validation belongs in the next action, not in the stated input facts.

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use before options, criteria, scoring scales, and evidence are comparable. Do not let a strong total score average away a mandatory requirement or a decision-critical unknown.

Adjacent Methods

• decision-matrix: one-time choice with explicit tradeoffs.
• rice-scoring: Reach/Impact/Confidence/Effort backlog.
• wsjf-prioritization: delay-cost sequencing.

Step-by-Step Execution

Output Template

### 1. Purpose And Eligibility
Evaluation purpose:
Entities:
Must-pass gates:
Evidence cut-off:

### 2. Dimensions And Anchors
Input status and source:
| Dimension | Weight | Scoring anchor | Evidence standard |
|---|---|---|---|
|  |  |  |  |

### 3. Scores
| Entity | Dimension scores | Normalized total | Evidence gaps |
|---|---|---|---|
|  |  |  |  |

### 4. Sensitivity And Governance
Recommendation:
Sensitivity:
Override rule:
Review / approval owner:

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Quality Gate

• Produce the method-specific outputs for Purpose And Eligibility, Dimensions And Anchors, Scores; do not substitute a generic framework summary.
• Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
• Preserve the source-established status of weights, scores, scales, and anchors in the output; distinguish supplied or proposed inputs from explicitly approved or validated inputs, and record any pending approval or validation as a next action.
• Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
• Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
• State missing inputs and the smallest validation action instead of inventing precision.
• Keep wording professional and plain enough that a smart non-specialist can use the output directly.