Methods · Ranking
SAW (Simple Additive Weighting)
SAW equalises the scale of every criterion, multiplies it by its weight, and sums directly; it is the oldest and plainest member of the multiple-criteria decision methods. The alternative with the highest weighted sum comes out first.
Base method's data type: Classical
What Is the Method?
SAW is a ranking method; it does not generate criterion weights, it takes them from outside. Given a numerical decision table and criterion weights that sum to 1, it produces a single total score for every alternative and orders the alternatives by this score from the highest to the lowest. Fishburn defined it mathematically in 1967 under the title "additive utilities with incomplete product sets"; in practice it is also known as the Weighted Sum Model (WSM), and it carries the same logic as computing a school grade average: each subject is a criterion, credit is a weight, and the total is the grade. It is the simplest and most easily taught of the multiple-criteria decision methods. For this reason it is commonly used as a baseline against which the results of more complex methods, such as TOPSIS and VIKOR, are compared.
The Philosophy Behind It
SAW's philosophy is a plain summation logic: every criterion's contribution is added to the total independently of the others, in proportion to its weight. TOPSIS measures distance to two hypothetical reference points (ideal and anti-ideal); SAW has no reference point at all, only a direct weighted average. This carries SAW to a compensation logic even stronger than TOPSIS's: its compensation_degree is full, meaning excellence on one criterion can close a weakness on another proportionally and directly.
The consequence of this philosophy is simplicity, but simplicity has a cost: SAW carries no mechanism such as "the penalty grows with distance" or "extremes are weighted differently." However large the gap between two alternatives, it is counted in the total directly and proportionally. If full compensation is acceptable and you want the clearest possible view of how the result is produced, SAW is the right place.
How It Works
The method proceeds through two steps.
First, scale equalisation. The method scales every criterion column against its own best value: for a "higher is better" criterion, every value is divided by the column's largest value (the best alternative becomes 1); for a "lower is better" criterion, the column's smallest value is divided by every value (the best alternative again becomes 1). Unlike TOPSIS's vector normalisation, which is based on the sum of squares, this is a simpler equalisation, a direct "ratio to the best"; different forms of scale equalisation (spreading across the largest–smallest range, vector normalisation) can give the same table a different result. DecisionMind fixes this ratio-to-the-best form for classical SAW and states this in the report.
Second, the weighted sum. The method multiplies every equalised column by the criterion's weight and sums by alternative; the resulting single number is the alternative's total score. The method ranks alternatives from the highest score to the lowest.
The formulas behind each step, the intermediate tables and citation formats are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The total score gives an alternative's weighted average, and nothing more. A score of 0.78 does not mean "78 per cent good" or "78 per cent likely to be the best," because the scale equalisation is carried out over this analysis's own alternatives; it cannot be compared with 0.78 from a different analysis. A score of 1 does not mean "perfect" but "the best in this set on every criterion."
The full-compensation assumption is even more pronounced here than in TOPSIS: a serious weakness on one criterion can be closed directly and proportionally by strength on another criterion with a sufficiently large weight, with no reference point in between to soften this compensation. For this reason, whether a high-scoring alternative is acceptable on every criterion should be checked separately.
Thus instead of writing:
"SAW found the best alternative"
the report should read:
"Under these weights and the full-compensation assumption, the alternative with the highest weighted sum is this one; the ranking is sensitive to the weights and carries no separate safeguard against a weakness on any one criterion"
Data Type and Inputs
Classical SAW works with crisp data: a single number in every cell. Alongside the base method, DecisionMind holds fourteen SAW members (extensions in fuzzy, grey, intuitionistic, probabilistic and other forms of uncertainty); if your data comes as a range, as expert judgement, or in contradictory form, the relevant extension should be consulted.
You need alternatives in rows, criteria in columns, a number in every cell with no gaps; information for every criterion on whether higher or lower is better; and criterion weights that sum to 1. SAW does not produce weights, it asks for them; you can derive weights from expert opinion (AHP, BWM, SWARA) or from the data itself (Entropy, CRITIC). A minimum of two alternatives and two criteria is required; three to twelve criteria work comfortably.
When to Use It, When Not To
SAW is a suitable choice if you want a simple, fast ranking that can be followed by hand at every step, if full compensation is acceptable, and if the result will be explained to a non-expert audience. It is also used as a quick benchmark to check whether the result of a more complex method (TOPSIS, VIKOR) is "reasonable."
Where it should not be used follows from its philosophy: if no compromise can be accepted on a criterion, SAW's full compensation will not prevent this, and a weak alternative can come out ahead through strength on other criteria. If criteria are strongly linked to one another (they overlap), SAW cannot see this, and the weights should be corrected beforehand accordingly.
Simple, fast, hand-traceable ranking, a benchmark → SAW
Same compensation logic, but with ideal/anti-ideal reference points for better balance → TOPSIS
Not "the best" but "the most balanced compromise" → VIKOR
No compromise allowed on one criterion, sub-threshold alternatives must be screened out → screening first, then ranking, or elimination-based methods
Not a ranking but weights are needed → AHP, BWM, SWARA (subjective); Entropy, CRITIC (objective)
Strengths
SAW's greatest strength is its simplicity and transparency: every step can be followed by hand, and the result comes not from a black box but directly from a visible sum. Its computational burden is among the lowest of any method; it can even be applied with pencil and paper. Because it rests on a logic everyone intuitively knows, a weighted average or a grade average, its result is easy to explain. It pairs readily with almost any source of weights, subjective or objective, and provides a reliable baseline against which other methods' results can be compared.
Weaknesses
Its limitations stem from this same simplicity. First, the full-compensation assumption operates here in its strongest form; a serious weakness on one criterion can easily be papered over by another, and the method carries no reference point to limit this masking (Petrović, Madić and Marinković, 2026). Second, in methods based on linear summation, the ranking can become inconsistent when the alternative set changes; this is called rank reversal, or the "decision-making paradox." This was demonstrated early in the literature (Triantaphyllou and Mann, 1989) and has since been supported by further comparative studies (Triantaphyllou, 2000). Third, the form of scale equalisation (ratio-to-the-best, spreading across the largest–smallest range, vector normalisation) can change the result. Fourth, the method treats criteria as independent; where criteria influence one another, weight is implicitly counted twice. Fifth, because it carries no reference point (ideal/anti-ideal), it has no mechanism, unlike TOPSIS, that softens the influence of extreme alternatives.
Common Mistakes
The most common mistake is marking criterion direction wrongly; if a "lower is better" criterion is marked "higher is better," scale equalisation reverses and the ranking becomes meaningless.
A second mistake is assigning weights equally without justification. A third mistake is reading the total score as a percentage or a probability and comparing scores across different analyses. A fourth mistake is using SAW's full-compensation assumption without noticing a threshold situation, one where no compromise can ever be made on a criterion. A fifth is presenting the SAW result on its own as the final decision tool; SAW's real strength is its simplicity and its role as a benchmark, and it should be read alongside a reference-point method such as TOPSIS or VIKOR for serious decisions. A sixth is adding an alternative once the analysis is finished and being surprised that the ranking changes.
The governing principle is this:
A SAW result is a direct sum of the weights you supplied and the full-compensation assumption; simplicity is as much a risk as a virtue, because there is no reference point to soften a serious weakness on any one criterion.
Cases
Each case opens with a decision table, describes in words what the method does to it, and shows how to read the result. The first case is DecisionMind's validation example; the figures are taken from the manifest and the engine produces the same result. The remaining cases are illustrative constructions.
1. Illustrative example: Three alternatives, three criteria (DecisionMind validation example)
This example is not a literature case: although the manifest links this 3×3 table to Fishburn's (1967) short mathematical note as its source, no page number is given in the example, and the table is a small, hand-traceable fixture built to validate DecisionMind's SAW engine. It is presented below through an illustrative frame (a hiring decision); the figures are the manifest's own values.
A company's hiring committee will choose one of three candidates. Three criteria apply: technical interview score, presentation and communication score, and expected monthly salary (thousand TL). Expected salary is "lower is better," the other two are "higher is better." The committee gave the technical score the highest weight (0.50), presentation an intermediate weight (0.30), and expected salary the lowest weight (0.20).
| Candidate | Technical score | Presentation score | Expected salary (thousand TL) |
|---|---|---|---|
| B1 | 4 | 3 | 2 |
| B2 | 3 | 5 | 4 |
| B3 | 5 | 2 | 3 |
| Direction | higher is better | higher is better | lower is better |
| Weight | 0.50 | 0.30 | 0.20 |
The method first scales every column against its own best value: for technical score and presentation score, the largest value becomes 1; for expected salary, the smallest value (the cheapest candidate) becomes 1. It then multiplies every column by its weight and sums.
| Candidate | Total score | Rank |
|---|---|---|
| B1 | 0.78 | 1 |
| B3 | 0.7533 | 2 |
| B2 | 0.70 | 3 |
The result reads as follows. B1 is not the outright best on any single criterion alone; its technical score is middling, its presentation the lowest, but its expected salary is the lowest (and so scores full marks, 1, on this criterion). It comes out ahead because it ranks second on the heaviest criterion, the technical score, and its lead on the lightest criterion, salary, is enough to overtake B3 in the total. B3 is the best on the technical score, yet falls to second place because it is lowest on presentation. B2 is the best on presentation, yet finishes last because it is weak on both the technical score and expected salary.
The committee hesitates here: the gap between B1 and B3 is 0.0267, a small figure. Had the committee given the technical score a weight of 0.60 instead of 0.50, and presentation 0.20 instead of 0.30, the ranking would reverse: the same calculation makes B3 first with 0.8133 and B1 second with 0.80. The report should therefore state that the ranking is sensitive to the technical-score and presentation weights, and that B1 and B3 might both be short-listed together.
In the report: "With the weights given, B1 has the highest weighted sum (0.78); the gap to B3 (0.7533) is small, and B3 moves ahead once the technical-score weight is raised to 0.60 and the presentation weight lowered to 0.20."
Source: DecisionMind SAW manifest, validation example; the steps are built according to Fishburn's (1967) definition. Because no page-level source is given for this table in the manifest, it is presented as an illustrative example.
2. Logistics: A warehouse operator's choice of forklift proposal
A warehouse operator will choose one of three forklift proposals. Four criteria apply: purchase price, annual maintenance cost, lifting capacity and charging/refuelling time. Price, maintenance cost and refuelling time are "lower is better," lifting capacity is "higher is better." The operator set the weights with the operations team, giving lifting capacity the highest weight.
The method scales the four proposals against their own best values, multiplies by the weights and sums. Suppose the proposal with the highest capacity but the highest price comes out first: its superiority in capacity, being the heaviest criterion, offsets its weakness in price and maintenance cost.
The operator hesitates here: if a budget ceiling exists and the top-ranked proposal exceeds it, SAW will not screen it out on its own; price has been traded off against the other criteria. The proposal exceeding budget should be screened out before the analysis, and the remaining proposals ranked with SAW; otherwise the objection "the method chose a proposal over budget" will be raised, and rightly so.
In the report: "The budget ceiling was applied as a pre-screening criterion; the remaining proposals were ranked with SAW using the operations team's weights; the ranking is sensitive to the capacity weight."
3. Environment: A municipality's purchase of a solid-waste collection vehicle
A municipality will choose one of three solid-waste collection vehicle proposals. Three criteria apply: vehicle price, fuel consumption (litres/100 km) and collection capacity (tonnes). Price and fuel consumption are "lower is better," capacity is "higher is better." The weights were discussed in the council committee, and fuel consumption (because of operating cost and environmental impact) received the highest weight.
The method scales the three proposals against their own best values and computes the weighted sum. The result places first the vehicle with the lowest fuel consumption but the smallest capacity; the vehicle with the highest capacity but the highest fuel consumption finishes last.
The committee hesitates here: choosing the smaller-capacity vehicle means more daily collection rounds are needed. This is an operational consequence not separately costed in the report. SAW produces only a total based on the criteria and weights supplied; the number of rounds is not taken into account unless it enters the table as a separate criterion. The committee must either add the number of rounds as a new criterion or read the result together with this gap.
In the report: "The ranking was produced with SAW using the three criteria and weights given; the number of daily collection rounds was not entered into the table as a criterion and so is not reflected in the result, and should be assessed separately."
4. What Not to Do
Had expected salary been marked "higher is better" in the same hiring table, the candidate expecting the highest salary would score full marks on this criterion, and B1's advantage from its low salary expectation would be reversed. A second error is reporting B1's score of 0.78 as "78 per cent suitable"; the score only ranks these three candidates relative to one another. A third error is the committee adding a fourth candidate to the table after the interviews have finished; the ratio-to-the-best scaling is rebuilt and the order of the first three can change.
Extensions: for different data types
SAW has 13 extensions in the library. Same decision logic, different data type: if your data is not a classical number, read the relevant data type card, then open that member.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/saw
Fishburn, P. C. (1967). Additive utilities with incomplete product sets: Application to priorities and assignments. Operations Research, 15(3), 537–542. DOI: 10.1287/opre.15.3.537
Triantaphyllou, E., & Mann, S. H. (1989). An examination of the effectiveness of multi-dimensional decision-making methods: A decision-making paradox. Decision Support Systems, 5(3), 303–312. DOI: 10.1016/0167-9236(89)90037-7
Triantaphyllou, E. (2000). Multi-Criteria Decision Making Methods: A Comparative Study. Applied Optimization, Vol. 44. Kluwer Academic Publishers. DOI: 10.1007/978-1-4757-3157-6
Petrović, G., Madić, M., & Marinković, D. (2026). WSM and WPM: Weighted sum model and weighted product model for multi-attribute decision-making. In Encyclopedia of Multi-Attribute Decision Making (MADM) (pp. 835–849). DOI: 10.1016/b978-0-443-33275-3.00091-9