Methods · Ranking
MABAC (Multi-Attributive Border Approximation area Comparison)
MABAC ranks alternatives not against an ideal or an average, but against their distance from a hypothetical "border area" built for every criterion. Sitting above the border strengthens an alternative; sitting below it weakens one.
Base method's data type: Classical
What Is the Method?
MABAC is a ranking method for when you already hold a decision table filled with numbers and want the alternatives placed in a single order. Its output is a score for every alternative, the net distance from the border area, together with the rank that score produces. Dragan Pamučar and Goran Ćirović proposed the method in 2015 as a solution to selecting transport and handling equipment for logistics centres. It is a compensatory member of the ranking family; it does not generate weights, taking them from outside.
The Philosophy Behind It
MABAC's underlying idea is to replace the question "how close am I to the best" with "how far above or below the average performance area do I sit." The method builds, for every criterion, a "border approximation area" that does not actually exist. This is the geometric mean of every alternative's performance on that criterion, and it represents the "typical," or "expected," performance region for that criterion. Every real alternative sits either above or below this border; MABAC measures this difference, the distance, on every criterion and sums it.
This idea has one consequence. An alternative may sit clearly above the border on some criteria and below it on others; the total score is the net sum of these positive and negative distances. This differs from TOPSIS's logic of "distance to two extreme points" (ideal and anti-ideal). MABAC uses a single reference region, the border, and asks how far above or below it an alternative sits. MABAC is also compensatory: falling below the border on one criterion can be offset by sitting well above it on another. There is no veto-like mechanism here of the kind found in the ELECTRE family.
How It Works
The method proceeds through five steps.
First, scale equalisation (normalisation). Criteria are expressed in different units. MABAC places every column between 0 and 1 according to its own minimum and maximum (linear min–max normalisation); for a "lower is better" criterion, this scale is reversed. This differs from the vector normalisation used by TOPSIS and can produce a different order.
Second, weighting and shifting. Every equalised value is multiplied by its criterion's weight, and a constant of 1 is then added to the value. This "+1" shift is a technical necessity: the geometric mean in the third step cannot work with negative or zero values, and the shift moves every value into positive territory.
Third, the border approximation area. For every criterion, the geometric mean is taken across all alternatives' (weighted and shifted) values on that criterion. This is that criterion's "border" value. It represents neither the best nor the worst, but a hypothetical reference point showing the typical magnitude of the alternative set on that criterion.
Fourth, distance from the border. Every real alternative's value on every criterion is subtracted from that criterion's border value. If the result is positive, the alternative sits above the border on that criterion (strong); if negative, it sits below (weak).
Fifth, total score and ranking. An alternative's distance-from-border values are summed across all criteria. The larger the total, the more criteria, and by the larger a margin, on which the alternative sits above the border. Alternatives are then ranked from the highest score to the lowest.
The formulas behind these steps, 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 MABAC score shows how far above or below the "average performance border" an alternative sits, relative to the other alternatives in this analysis. It says nothing more. A positive score does not mean "good," nor does a negative score mean "bad." It shows only relative position within this particular alternative set. The same border is recalculated whenever the alternative set changes, for instance when an alternative is added or removed; scores therefore cannot be compared across different analyses. A small gap between scores signals a ranking that is sensitive to the weights, not a robust one.
For this reason, instead of writing:
"MABAC found the best alternative"
the report should read:
"With these weights and this alternative set, the alternative in the strongest position relative to the border approximation area is this one; the ranking is sensitive to the weight on these criteria"
Data Type and Inputs
MABAC works with crisp data: one number per cell. You need alternatives in rows, criteria in columns, one number per cell with no empty cells; direction information for every criterion; and criterion weights that sum to 1. MABAC does not produce weights, it asks for them; you can draw them from subjective sources such as AHP, BWM or SWARA, or from objective sources such as Entropy or CRITIC. DecisionMind carries fifteen members of the MABAC family alongside the base method, including fuzzy and other data-type extensions. A minimum of two alternatives and two criteria is required; three to twelve criteria work comfortably. If every alternative takes the same value on a criterion (a constant column), the normalisation denominator becomes zero; this must be checked before the data is entered.
When to Use It, When Not To
MABAC is a suitable choice if your criteria can be measured numerically, your table is fully populated, and you accept that a weakness on one criterion may be offset by strength on another. Its typical territory includes supplier selection, logistics and transport equipment evaluation, and materials and technology selection; the computational load is small, and it remains stable even with large alternative sets.
It should not be used where a criterion carries a threshold that can never be compromised; MABAC's additive structure cannot preserve such a threshold on its own. Where criteria are strongly linked, one rising as another rises, that link needs handling first; MABAC treats criteria as independent.
A numerical table, compensation accepted, the goal is ranking → MABAC
No compromise allowed on one criterion, sub-threshold alternatives must be screened out → the ELECTRE family (veto mechanism)
Not "the best" but "the compromise limiting the greatest regret" → VIKOR
Not a ranking but weights are needed → AHP, BWM, SWARA (subjective); Entropy, CRITIC (objective)
Same logic, but the data is fuzzy / grey / neutrosophic → the relevant MABAC extension
Strengths
MABAC's principal strength is computational stability. As Pamučar and Ćirović show, the method produces consistent results under changes of measurement unit and minor changes to criterion formulation (Pamučar and Ćirović, 2015). The border approximation area is easy to explain to a decision-maker: "is my alternative above or below the average" offers a more concrete reference point than "how close am I to the ideal." The computational load is small and stays just as simple as the number of alternatives or criteria grows. According to Torkayesh and colleagues' 2022 survey, the method has been applied across a broad range of fields, including sustainability and circularity, since 2015 (Torkayesh et al., 2022).
Weaknesses
Its limitations stem from the same structure. First, the geometric mean cannot work with zero or negative values. This is why the "+1" shift in the second step requires a technical patch, and how this shift affects the outcome is not transparent to the user. Second, the assumption of full compensation holds: a serious weakness on one criterion can be papered over by others in MABAC too. The rank-reversal risk known across the general MCDM literature applies to MABAC as well (Aires and Ferreira, 2018). Third, a constant criterion column, where every value is identical, zeroes the normalisation denominator and breaks the calculation; this needs checking before data entry. Fourth, the quality of the weights lies outside the method itself; a flawless calculation built on poor weights still produces a poor ranking. Fifth, MABAC is a comparatively new method (2015). Its long-run body of critique and comparison literature is accordingly less mature than that of TOPSIS or AHP. Fuzzy and Gaussian-membership extensions remain an active research area (Yasin et al., 2024).
Common Mistakes
The most common mistake is marking criterion direction wrongly. If a "lower is better" criterion is marked "higher is better," the border area, and with it the whole ranking, is thrown off. A second mistake is feeding in a column where every alternative takes an identical or near-identical value without noticing; the normalisation denominator then approaches zero and that criterion's contribution becomes meaningless. A third mistake is confusing the border approximation area with an "ideal point"; the border represents neither the best nor the worst, but the geometric mean of the alternative set, a different reference from ideal/anti-ideal logic. A fourth is assigning equal weights without justification and reporting the result without showing how much this choice changes it. A fifth is reading the MABAC score as a percentage or a probability, or comparing scores from different analyses.
The governing principle is this:
The MABAC score is your alternative's net position relative to this set's average-performance border. The border itself shifts with the data set, so the score cannot be compared with another analysis's score.
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 example drawn from DecisionMind's own validation record; the remaining cases are illustrative constructions.
1. Logistics: Choosing a warehouse automation equipment supplier (illustrative example)
A distribution centre must choose among three supplier quotations for automated stacking equipment. Three criteria apply: handling capacity and reliability score ("higher is better"), and annual maintenance cost ("lower is better"). The centre set the weights at the highest for capacity (0.40), medium for reliability (0.35), and lowest for cost (0.25).
| Quotation | Handling capacity | Reliability score | Annual maintenance cost |
|---|---|---|---|
| A1 | 3 | 5 | 4 |
| A2 | 5 | 3 | 2 |
| A3 | 4 | 4 | 3 |
| Direction | higher is better | higher is better | lower is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method first equalises and weights the columns (with the +1 shift), then builds the border value for every criterion from the geometric mean. A2 sits clearly above the border on capacity and cost (highest capacity, lowest cost); on reliability it sits below the border. A1 sits highest above the border on reliability but lowest on capacity. A3 sits close to the border on all three criteria, in a middling position.
| Quotation | MABAC score | Rank |
|---|---|---|
| A2 | 0.208 | 1 |
| A3 | 0.058 | 2 |
| A1 | -0.092 | 3 |
The result reads as follows. A2 ranks first because it sits above the border on the two heaviest criteria, capacity and reliability, whose combined weight is 0.75. Its weakness on reliability is offset by its strength on the other two. A1, despite being best on reliability, finishes last owing to its large weakness on capacity.
The centre's hesitation: what if the weights had instead been 0.25 for capacity and 0.50 for reliability, rather than 0.40 and 0.35? The same calculation then equalises all three quotations exactly; all three score 0.058. A change in weights alone is decisive enough to erase the entire difference among A1, A2 and A3. This is a clear sign that the ranking depends heavily on the choice of weights.
In the report: "With the weights given (capacity 0.40, reliability 0.35, cost 0.25), A2 is the quotation in the strongest position relative to the border approximation area (0.208); when the weights are changed to 0.25 for capacity and 0.50 for reliability, the difference among the three quotations disappears entirely."
Source: this is an illustrative example, worked by hand, with 3 alternatives and 3 criteria (it is not the real logistics case from Pamučar and Ćirović's 2015 paper); it is a validation example for DecisionMind's MABAC engine. The MABAC scores and weight sensitivity were independently computed in Python by this card's author and confirmed against the same result (A2 > A3 > A1) as DecisionMind's internal manifest audit record.
2. Energy: A municipality's choice of wind-turbine maintenance contractor
A municipal electricity company must choose among four contractors for wind-turbine maintenance service. Four criteria apply: technical team experience score ("higher is better"), fault-response time ("lower is better"), annual contract fee ("lower is better") and certification-coverage score ("higher is better"). The weights were set by the company's technical team, with fault-response time given the highest weight.
The method brings the four quotations onto the same scale, builds the border approximation area for every criterion, and computes each contractor's net position relative to that border. Suppose the contractor with the lowest contract fee also sits clearly below the border on response time. Its low-cost advantage cannot offset this weakness, and the contractor finishes last. The contractor with the fastest response time comes first, even though its certification coverage is only average.
The company's hesitation: had the response-time weight been lowered and the cost weight raised, the cheapest contractor might have come out ahead. This is a natural consequence of MABAC's compensatory structure; the company must answer plainly in the report whether speed or cheapness takes priority.
In the report: "With the current weights, the contractor with the fastest response time is in the strongest position relative to the border approximation area; the ranking is sensitive to the balance between the response-time and cost weights."
3. Public sector: A fire service's preliminary evaluation for vehicle procurement
A fire service must carry out a preliminary evaluation among three quotations for new response-vehicle procurement. Three criteria apply: water-tank capacity and top speed ("higher is better"), and unit cost ("lower is better"). The service set the weights with capacity carrying the greatest importance.
The method compares the three quotations; the vehicle with the highest capacity but also the highest price stays above the border, thanks to the high weight on capacity, and comes first according to the border approximation area. The cheapest vehicle sits clearly below the border on capacity and finishes last.
The service's hesitation: if a budget ceiling exists and the most expensive vehicle exceeds it, MABAC will not screen it out on its own; cost, as a criterion, has already been offset against capacity. The quotation exceeding budget should be screened out before the analysis, with the remainder ranked by MABAC.
In the report: "The quotation exceeding the budget ceiling was removed by pre-screening; the remaining quotations were ranked with the current weights; the highest-capacity vehicle is in the strongest position relative to the border approximation area."
4. What Not to Do
Had annual maintenance cost been mistakenly marked "higher is better" in the same warehouse-automation table, the most expensive quotation would also be counted as advantaged on that criterion, and the ranking would become meaningless. A second error is presenting the border approximation area as "the best quotation's performance"; the border is the geometric mean of the three quotations, not the value of the best one. A third error is ignoring the point at which a change in weights exactly equalises all three quotations' scores (0.058) and reporting instead that "A2 is clearly first." As shown, the result is extremely sensitive to the choice of weights, and this sensitivity must be stated in the report.
Extensions: for different data types
MABAC has 14 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 the citation formats, see the DecisionMind method page: decisionmind.app/library/mabac
Pamučar, D., & Ćirović, G. (2015). The selection of transport and handling resources in logistics centers using Multi-Attributive Border Approximation area Comparison (MABAC). Expert Systems with Applications, 42(6), 3016–3028. DOI: 10.1016/j.eswa.2014.11.057
Torkayesh, A. E., Tirkolaee, E. B., Bahrini, A., Pamucar, D., & Khakbaz, A. (2022). A Systematic Literature Review of MABAC Method and Applications: An Outlook for Sustainability and Circularity. Informatica, 34(4), 899–929. DOI: 10.15388/23-INFOR511
Yasin, F., Demir, S., Riaz, M., & Aslam, M. (2024). A systematic investigation of multi-attributive border approximation area comparison approach with Gaussian membership function for optimizing water quality. Environment, Development and Sustainability. DOI: 10.1007/s10668-024-05704-0
Aires, R. F. de F., & Ferreira, L. (2018). The rank reversal problem in multi-criteria decision making: A literature review. Pesquisa Operacional, 38(2), 331–362. DOI: 10.1590/0101-7438.2018.038.02.0331