How do I make a decision tree in Excel?

Use Insert > SmartArt > Hierarchy for a small tree, or Insert > Shapes with elbow connectors for full control. For logic rather than a picture, use nested IF formulas or an IFS lookup table on a separate sheet.

Is there a decision tree template for Excel?

SmartArt Hierarchy layouts act as built-in templates. For trees larger than about ten nodes, generating the tree outside Excel and pasting the diagram as an image is usually faster and stays legible.

Can I export a decision tree to CSV for Excel?

Yes. Trees built in elimination mode expose an option matrix that can be exported to CSV from the path view, giving you one row per option and one column per question — ready to open in Excel.

Should decision logic live in Excel or in a decision tree tool?

Nested IF formulas are hard to audit and easy to break silently. A decision tree keeps the same logic readable, lets you walk every path, and can be run by non-spreadsheet users.

Decision Tree Template for Excel

There are two very different reasons people search for a decision tree in Excel: they want a picture of a decision on a sheet, or they want the logic to actually run. Excel can do both, badly. Here is how to do each properly.

→ Build the tree first, then bring it into Excel

If You Want a Diagram on the Sheet

SmartArt (fast): Insert → SmartArt → Hierarchy → Horizontal Hierarchy. Type nodes in the text pane; Tab indents a level. Good up to roughly ten nodes.

Shapes (full control):

Draw and style one rectangle, then copy it for consistency.
Snap to grid (Alt while dragging) and use Align → Distribute per level.
Use elbow connectors attached to shape anchors so lines follow the boxes.
Group each level before you re-space anything.

Generated image (best for larger trees): write the tree as text, screenshot the diagram, and paste it in. The layout stays consistent when you add a branch, which is where hand-drawn Excel trees fall apart.

If You Want the Logic to Run

The spreadsheet-native options, and their costs:

Approach	Works when	Breaks when
Nested `IF`	2–3 levels	Anyone has to audit or edit it
`IFS`	Flat rule sets	Rules become conditional on each other
Lookup table + `XLOOKUP`	Every combination enumerable	The combinations explode
VBA	You control the environment	Sharing, Mac, and web Excel

Nested IF formulas are the usual culprit behind a rule nobody dares change. A decision tree keeps the same logic in a form you can read out loud, walk path by path, and hand to someone who does not open Excel.

Write It Once, as Text

mode: decision

Q1: Is the expense above the policy limit?
  - Yes -> Q2
  - No -> AUTO_APPROVE

Q2: Was it pre-approved in the budget?
  - Yes -> MANAGER
  - No -> FINANCE_REVIEW

AUTO_APPROVE: Approve automatically in the expense tool.
MANAGER: Line manager approves.
FINANCE_REVIEW: Send to finance for review before payment.

That gives you a diagram to paste into the sheet, a path view listing every route so you can prove the logic is complete, and a wizard for the people submitting claims. Full syntax reference →

Export a Decision Matrix to CSV

For comparison-style decisions — choosing a vendor, a database, a plan — build the tree in elimination mode, where each answer rules options out rather than routing to a single branch. The path view then shows an option matrix, and you can export it to CSV and open it directly in Excel: one row per option, one column per question.

That is the clean handoff between the two tools: the tree owns the logic, Excel owns the numbers.

→ See the path view

Excel vs a Decision Tree Tool

	Excel	DrawDecisionTree
Diagram effort	Manual shapes	Generated
Auditing the logic	Read nested formulas	Walk every path visually
Non-Excel users	Need the file	Open a link
Embedding in a wiki	Screenshot	Live embed, always current
Version history	File copies	Plain-text diffs

Keep Excel for calculation. Move the branching decision to a tree, and export the matrix back when you need to model numbers on top.

Build It in a Minute

→ Open the free builder