Methods · Outranking
PROMETHEE II (Preference Ranking Organisation Method for Enrichment of Evaluations II)
PROMETHEE II does not compare alternatives one by one against an ideal. Instead it compares them pairwise against each other, grading "how much better" on every criterion with a preference function. Summing these grades into a net flow yields a complete ranking.
Base method's data type: Classical
What Is the Method?
PROMETHEE II is an outranking method for when you already hold a decision table, ranking the alternatives from first to last. Its output, for every alternative, is a positive flow, a negative flow and their difference, the net flow (Φ, between minus one and plus one); the ranking is built from this flow. Unlike TOPSIS and VIKOR, it does not construct an "ideal alternative"; it compares alternatives directly against one another, in pairs. The method was proposed by Brans and Vincke in 1985. Its full-ranking form, PROMETHEE II, was set out clearly in Brans, Vincke and Mareschal's 1986 article. It is one of the most heavily cited outranking methods in the multi-criteria decision literature, applied widely in areas such as supplier selection, project ranking, environmental assessment and energy planning. It does not produce weights; it takes them from outside.
The Philosophy Behind It
PROMETHEE II's starting point is this: whether an alternative is "good" is measured not by how close it sits to a hypothetical ideal, but by how far it outranks its real rivals. The method takes every pair of alternatives and, on each criterion, filters the difference between them through a "preference function." A small difference can be treated as negligible, a large one can turn into a full preference; the shape of this filter is chosen per criterion. These single-criterion preferences are combined with the weights to build an "overall preference degree" for every pair. The extent to which each alternative outranks the others is then summed; this is called the positive flow. The extent to which it is outranked by the others is also summed; this is called the negative flow.
This structure has a consequence: PROMETHEE II is partly compensatory, but not to the same degree as TOPSIS. Strength on one criterion can offset weakness on another, because all the preferences are combined into a single flow. But the choice of preference function also allows small differences to be discounted entirely; the method can therefore also embody the intuition that "noisy small differences are not a genuine preference." The result is a ranking that rests not on a single ideal point but on the whole set of pairwise comparisons among the alternatives.
How It Works
The method proceeds through five steps.
First, pairwise differences. For every criterion, the difference is calculated for every pair of alternatives (a,b). For a "higher is better" criterion, b's value is subtracted from a's; for a "lower is better" criterion, the reverse is done. A positive difference thus always means "a is better than b on this criterion."
Second, the preference function. This difference is converted into a degree between 0 and 1 by a preference function chosen for that criterion. DecisionMind asks you to choose one of six classical forms. The simplest is the usual (absolute) type, in which even the smallest positive difference counts as a full preference. Threshold forms treat anything below a given difference as "no difference" and anything above another given difference as "full preference," rising linearly in between. The Gaussian (smooth) form increases the effect of the difference gradually. The choice depends on how precisely the criterion is measured. For a sharply measured criterion, price, say, the usual function counts every difference. For subjective or noisy scoring, a threshold function treats small differences as meaningless.
Third, the overall preference index. The preference degree on each criterion is multiplied by that criterion's weight and summed. This gives, for every pair of alternatives, a single figure: how much a is preferred to b.
Fourth, positive and negative flow. An alternative's average preference degree against every other alternative gives its positive flow (Φ⁺, how far it outranks the others). The other alternatives' average preference degree against it gives its negative flow (Φ⁻, how far it is outranked).
Fifth, net flow and ranking. The net flow is the negative flow subtracted from the positive flow (Φ = Φ⁺ − Φ⁻). Alternatives are ranked from largest to smallest; this is PROMETHEE II's full ranking (PROMETHEE I gives only a partial outranking relation; DecisionMind produces the full ranking here).
The formulas behind each step, the intermediate tables and the citation formats are given on the DecisionMind method page; this card carries no formulas.
How to Read the Output
The net flow Φ is a value between −1 and +1; a larger value is better. Φ = +1 means an alternative fully outranks every other; Φ = −1 means the opposite. The net flow should be read together with the positive and negative flows, not on its own. A high Φ⁺ shows that an alternative outranks most of its rivals; a low Φ⁻ shows that it is outranked by few of them. Whether an alternative comes out ahead because it "wins a lot" or because it "loses little" should be stated separately in the report. The net flow cannot be compared with the result of a different analysis, the way TOPSIS's closeness score cannot; it is meaningful only for this alternative set and these preference functions.
Thus instead of writing:
"According to PROMETHEE II, A3 is the best alternative"
the report should read:
"With the preference functions and weights chosen, A3 is the alternative most clearly preferred in the pairwise comparisons (Φ = 0.20); this result is sensitive to the type of preference function and to the weights"
Data Type and Inputs
PROMETHEE II works with crisp data, one number per cell. Unlike other outranking methods, the criterion scale need not be only ratio or interval; it may also be ordinal. You need alternatives in rows, criteria in columns, one number per cell; direction information for every criterion; weights summing to 1; and a preference-function type for every criterion. If a function type is not specified, DecisionMind assumes the usual (absolute) type. Threshold values (p, q) are needed for threshold functions, and sigma for the Gaussian function. It does not produce weights, it asks for them; they can be drawn from sources such as AHP, BWM, CRITIC or Entropy. DecisionMind holds eighteen PROMETHEE II members alongside the base method. A minimum of two alternatives and two criteria is required. Five to twenty alternatives and three to ten criteria work comfortably. Beyond thirty alternatives, the number of pairwise comparisons grows quadratically and the computational burden becomes noticeable.
When to Use It, When Not To
PROMETHEE II is a suitable choice if your criteria can be measured numerically or on an ordinal scale, you want a full ranking, and it helps you to define a different "how much of a difference matters" threshold per criterion. Its typical fields are supplier selection, project and investment ranking, environmental assessment, and energy planning.
There are three situations where it should not be used. First, where rank reversal is unacceptable; here, methods closed to reversal, such as SPOTIS or RAFSI, should be considered. Second, where the number of alternatives is very large; beyond fifty, the cost of pairwise comparison rises quickly. Third, where a fully compensatory aggregation is wanted; here TOPSIS or WASPAS is a simpler tool.
Pairwise-comparison logic and a full ranking are wanted → PROMETHEE II
Only a partial outranking relation suffices, a full ranking is not needed → PROMETHEE I
Rank reversal is unacceptable → SPOTIS or RAFSI
Computational burden matters for an alternative set beyond fifty → a lighter ranking method (TOPSIS, SAW)
Not a ranking but elimination or a core set is needed → the ELECTRE family
Strengths
PROMETHEE II's clear strength is the flexibility of choosing a different preference function per criterion; a sharply measured criterion is not judged with the same rigidity as subjective scoring. Second, it works directly between alternatives without constructing an ideal or anti-ideal point; this makes the result read "relative to real rivals." Third, keeping the positive and negative flows separate makes visible why an alternative comes out ahead, whether it wins a lot or loses little. Fourth, it is one of the most heavily cited outranking methods in the literature, with the widest base of application (Behzadian, Kazemzadeh, Albadvi and Aghdasi, 2010).
Weaknesses
Its limitations arise from the same flexibility. First, rank reversal is a known problem: the ranking can change when an alternative is added or removed (Mareschal, De Smet and Nemery, 2008). Second, the choice of preference function and thresholds (p, q) directly affects the result. These choices do not emerge from the data on their own; they require the analyst's or decision-maker's judgement and look arbitrary if left unjustified. Third, the computational burden grows with the square of the number of alternatives (O(m²)), which is costly for large sets. Fourth, criteria are assumed to sit on a comparable scale; if this does not hold, the meaning of the weights is distorted.
Common Mistakes
The most common mistake is applying the usual (absolute) preference function to every criterion without justification and never asking how treating even the smallest difference as a full preference affects the result. A second mistake is reporting the net flow alone without showing the positive and negative flows; this hides why an alternative came out ahead. A third mistake is adding an alternative once the analysis is finished and being surprised the ranking changes (rank reversal); the alternative set must be fixed before the analysis begins. A fourth mistake is applying the method to a set of more than fifty alternatives without ever considering the computational cost. A fifth mistake is reading the net flow as a percentage, the way TOPSIS's closeness score might be.
The governing principle is this:
The net flow is a product of the preference functions, thresholds and weights chosen; when these choices change, the ranking can change too, and the report must state plainly which functions and which thresholds were used.
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 an illustrative validation example; the remaining cases are illustrative constructions.
1. Supply chain: Comparing three supplier bids (illustrative example)
A procurement unit must choose among three supplier bids. Three criteria apply: a delivery-performance score, a quality score, and a flexibility score; all three are "higher is better" and the scores were given by an evaluation panel on a 1–5 scale. The unit has given delivery the highest weight (0.50), quality a middling weight (0.30), and flexibility the lowest (0.20). The simplest preference function, the usual (absolute) type, has been used on all three criteria, under which even the smallest difference counts as a full preference.
| Supplier | Delivery score | Quality score | Flexibility score |
|---|---|---|---|
| A1 | 4 | 3 | 2 |
| A2 | 3 | 2 | 4 |
| A3 | 5 | 1 | 3 |
| Direction | higher is better | higher is better | higher is better |
| Weight | 0.50 | 0.30 | 0.20 |
For every pairwise comparison, the method looks, on every criterion, at which supplier scores higher; because the function is absolute, even the smallest difference counts as a full preference. These preferences are combined with the weights to calculate each supplier's positive flow (how far it outranks the others) and negative flow (how far it is outranked).
| Supplier | Φ⁺ (positive) | Φ⁻ (negative) | Φ (net flow) | Rank |
|---|---|---|---|---|
| A3 | 0.600 | 0.400 | 0.200 | 1 |
| A1 | 0.550 | 0.450 | 0.100 | 2 |
| A2 | 0.350 | 0.650 | -0.300 | 3 |
The result reads as follows. A3 has the highest delivery score and the lowest quality score, yet it ranks first. This is because it is best on the most heavily weighted criterion (delivery, 0.50), which more than offsets the effect of its low quality score. A1 comes second: best on no criterion, but worst on none either. A2 comes third, the only alternative with a negative net flow: it is worst on the most heavily weighted criterion and leads only on flexibility.
The unit hesitates here: would the ranking reverse if the weights were shifted from delivery to flexibility (flexibility 0.50, delivery 0.20, quality held at 0.30)? The same calculation with these weights moves A2 to first with a net flow of +0.30 and A3 to third with −0.10; the ranking reverses completely. This shows how sensitive the gap between the three suppliers is to which criterion is given how much weight. The unit must defend in the report why the weights were set as they were.
In the report: "In this scenario, with the highest weight given to delivery performance, A3 is the supplier most clearly preferred in the pairwise comparisons (Φ = 0.20). When the weight is shifted to flexibility, the ranking reverses completely; the weight distribution must therefore be separately approved by the procurement committee."
Source: the PROMETHEE II documentation example from the pymcdm library (the matrix, weights and expected net flows [0.1 / -0.3 / 0.2] are taken from pymcdm v1.4.0). This is an illustrative example, not a case drawn from the literature. It serves as the validation example for DecisionMind's PROMETHEE II engine, and the engine produces the same result. The figures for the weight-change scenario were independently recalculated by this card's author using the same algorithm.
2. Tourism: Choosing a target city for a region's promotional campaign
A regional tourism association must direct its limited promotional budget to one of three candidate cities. Three criteria apply: the city's annual reachable potential tourist count, the campaign's unit cost, and local businesses' support/satisfaction score for the campaign. Tourist count and satisfaction score are "higher is better"; cost is "lower is better." The association has given the highest weight to tourist potential, with less weight allocated to cost and satisfaction. Because the scales differ, a threshold preference function has been used for tourist count and cost, and the usual function for the satisfaction score.
The method compares the three cities pairwise, calculates the preference degree on each criterion, and finds the net flows. Suppose the city with the highest tourist potential also has the most expensive campaign cost, yet still comes first in net flow, because the weight on tourist potential exceeds the combined weight of the other two criteria. The lowest-cost city comes second, and the city with moderate potential but the highest local support score comes third.
The association hesitates here: choosing a city where local business satisfaction is low could leave the campaign weakly supported on the ground; this risk does not show up in the net flow, because satisfaction carries a low weight. The association should not decide without raising this weight and recalculating. Furthermore, the threshold values chosen for the threshold preference function, that is, which gap in tourist numbers counts as "significant," can change the result, and this choice of threshold must be justified in the report.
In the report: "With the high weight given to tourist potential, the city with the greatest potential comes out clearly ahead. Because the weight on local support is kept low, this criterion's share is limited, and the ranking could change if that weight were raised."
3. Agriculture: A cooperative's choice of irrigation technology
An agricultural cooperative must choose among three irrigation technologies. Four criteria apply: percentage water saving, installation cost, an ease-of-maintenance score, and annual energy consumption. Water saving and ease of maintenance are "higher is better"; cost and energy consumption are "lower is better." The weights were set by a vote among cooperative members, with the highest weight given to water saving; a threshold (v-shape) preference function has been used on every criterion, so that small differences are treated as negligible.
The method compares the three technologies. Suppose the technology delivering the highest water saving also has the highest installation cost, yet still comes first in net flow. The lowest-cost technology comes third, held back by its low water saving.
The cooperative hesitates here: the threshold value in the threshold preference function, that is, which gap in water saving counts as "negligible," is disputed among members. If the threshold is raised, small saving differences are discounted entirely, and the most expensive technology's advantage could weaken. This shows that the question "what should the threshold be" is itself a decision, and one that can change the result.
In the report: "With the weight given to water saving and the thresholds chosen, the technology with the highest saving comes out clearly ahead; how robust this advantage is should be separately tested if the threshold value is changed."
4. What Not to Do
Had the quality score in the same supplier table been mistakenly marked "lower is better," A3, with the lowest quality score, would have been treated as advantaged on this criterion too, and the result would become meaningless through a direction error. A second error is adding a fourth supplier once the analysis is finished and being surprised the ranking changes (rank reversal); the alternative set must be fixed before the analysis. A third error is reporting A3's net flow of 0.20 as "20 per cent better"; the net flow only ranks these three suppliers relative to one another, and is neither a percentage nor a probability.
Extensions: for different data types
PROMETHEE II has 17 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.
Classical5
- PROMETHEE I - Preference Ranking Organisation METHod for Enrichment Evaluations I (partial ranking)Academy card →
- PROMETHEE II - Preference Ranking Organisation Method for Enrichment of Evaluations II1985 ↗
- PROMETHEE III - Preference Ranking Organisation METHod for Enrichment Evaluations III (interval ranking)Academy card →
- PROMETHEE V - PROMETHEE with Integer Programming ConstraintsAcademy card →
- PROMETHEE VI - Walking Weights SensitivityAcademy card →
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/promethee-ii
Brans, J. P., & Vincke, P. (1985). A preference ranking organisation method (The PROMETHEE method for multiple criteria decision-making). Management Science, 31(6), 647–656. DOI: 10.1287/mnsc.31.6.647
Brans, J. P., Vincke, P., & Mareschal, B. (1986). How to select and how to rank projects: The PROMETHEE method. European Journal of Operational Research, 24(2), 228–238. DOI: 10.1016/0377-2217(86)90044-5
Mareschal, B., De Smet, Y., & Nemery, P. (2008). Rank reversal in the PROMETHEE II method: Some new results. 2008 IEEE International Conference on Industrial Engineering and Engineering Management, 959–963. DOI: 10.1109/ieem.2008.4738012
Behzadian, M., Kazemzadeh, R. B., Albadvi, A., & Aghdasi, M. (2010). PROMETHEE: A comprehensive literature review on methodologies and applications. European Journal of Operational Research, 200(1), 198–215. DOI: 10.1016/j.ejor.2009.01.021