Where are decision tables used?
Common scenarios where decision tables replace complex branching logic, illustrated with a loan approval example.
Where are decision tables used?
Decision tables fit anywhere a workflow or app must pick an outcome from multiple input factors. A common example is a financial institution automating its loan approval process.
Suppose a bank processes loan applications and needs a systematic way to evaluate eligibility. A decision table can weigh multiple factors — credit score, income, and debt-to-income ratio — and return a decision.
Conditions
Conditions are the criteria used to evaluate input values. For loan approval, you would define ranges for credit score, income levels, and acceptable debt-to-income ratios.
Results
Results are the outcomes that correspond to each combination of conditions. The decision table compares the input values against each row and returns the matching result — approved, denied, or requires further review.
| Credit score | Income | Debt-to-income ratio | Eligibility |
|---|---|---|---|
| > 700 | High | Low | Approved |
| 600 – 700 | Medium | Medium | Further review |
| < 600 | Low | High | Denied |
The table gives a clear, visual representation of every scenario, so the loan process can assess applications automatically and consistently.